“How do I plan a product launch week on Threads and X?”
How do I plan a product launch week on Threads and X?
Short answer
Spend the week before launch building the voice and the drafts, raise the share of posts that carry your link to about 50% for launch week, post two a day, and drop back to 25% afterward. Threadgehog writes the drafts and sends approved ones to your scheduler, so launch week is review, not writing.
Steps
- 1
Two weeks out: set up the project
Name the product, say who it is for, add your link and paste 10 to 20 example posts. Setup writes 30 first drafts.
- 2
One week out: write and approve the launch batch
At two posts a day, launch week needs 14. Write 20 and approve the best, editing in dates and details.
- 3
Raise the link share
Set the share of posts that carry your link to 50% for the week. Half point to the launch; half stay useful on their own.
- 4
Launch week: keep the app open
Threadgehog sends while it is open. Check the Queue each morning, drag key posts up, and answer replies yourself.
- 5
Week after: drop back and read Insights
Set the share back to 25%. Open Insights to see which posts did 2x or more your typical post.
The shape of the week
A launch has three phases on a feed. Before launch you build a voice and some interest. During launch you say what it is and where to get it, more often than usual. After launch you keep the account alive with posts that are useful by themselves.
Threadgehog's two settings map onto that. Posts a day sets the pace, from 1 to 500. The link share (the Posts that include your link setting), from 0% to 100% in steps of 5, sets how many of those posts end with your link. Change both on the day the phase changes.
You do not have to do all three phases. A small product can run the middle phase alone: one week of launch posts at a 50% share and nothing special before or after. The extra weeks are there because a voice takes a few days to settle and because a quiet account after launch wastes the attention you just earned.
A worked example: a Mac app, 14 days
Take Tabweight again, a Mac menu bar app (an example from our app developers page). Two weeks out you set it up and approve the first 30 drafts, mostly about tabs and memory. The link share is 25%. The account is warming up without asking for anything.
The week before launch you write 20 more drafts and approve 14. You edit in the release date and the price. On launch day you raise the share to 50%. For seven days, two posts a day go out, about one in two with the download link, spread from 9 AM to 9 PM.
On day 8 you drop the share to 25% and set posts a day back to 1 or 2. The launch posts do not disappear: the Insights view shows which ones beat your typical post, and Write more like this gives you more in the same style.
Day-by-day: what you actually do
Day -7: approve the launch batch. Day -1: open the Queue, drag the posts that announce the release to the top, and check your link works. Day 0 to 6: each morning, open the Queue for two minutes, then spend your time on replies. Replies are the one job a scheduler cannot do for you.
A rule from practice, not a measurement: answer comments in the first hour after a post goes live. See how to grow on Threads for the routine behind it.
A short daily check keeps you out of trouble: is the app open, is the Queue full for tomorrow, did anyone ask a question you can answer in a post? That last one feeds the next day's drafts, since a real question is the best seed for an edit. See turning customer questions into posts.
Use a thread for the main announcement
One post per day should be a thread: what it is, the problem it solves, and the link in the last post. Threadgehog writes multi-post threads and keeps them in order. Buffer, Typefully and Postiz post them as real threads. Publer and Metricool take single posts, so a short thread is joined into one post and a long one stays in Pending.
On X, the version written when you approve keeps your link and trims the text. For two voices, one project, see keeping one voice on Threads and X.
After launch week
The week after a launch is where accounts often go quiet. A queue of regular posts at 25% link share keeps the account moving while you work on the product. If you prepared 30 drafts in setup, you likely still have some left.
For the numbers on pace, read how often to post on Threads. Join the waitlist on pricing so the app is ready before your own launch date.
What to post during launch week
Mix four kinds of post. The announcement thread says what it is, who it is for and where to get it. Problem posts describe the situation your product fixes, with no link. Behind-the-scenes posts tell one small story from building it. Question posts ask your audience something they will answer.
At 14 posts, a balanced week might be one announcement thread, five problem posts, four stories, two questions and two reminders with the link. With the link share set to 50%, about seven carry it. Threadgehog writes in the style of your example posts, so choose examples that include a mix of these shapes.
Review the batch with the list beside you. Reject drafts that repeat a shape you already have enough of.
Mistakes that cost a launch day
Three avoidable ones. The app is closed on launch morning, so nothing is sent. Check that it is open and the Mac is awake. The link in the brief is wrong or points at the wrong page. Click it. A draft claims a feature that is not in this release. Read every launch post against your notes before you approve.
Also check your scheduler's limits. Free plans on schedulers can cap scheduled posts. See how to schedule Threads posts with AI for the plan limits Threadgehog's five schedulers have.
None of this is hard, but all of it is easy to forget at 8 AM on launch day.
Questions
How early should I start?
Two weeks gives the voice time to settle and the first approvals time to teach it. Even a few days helps, since setup writes 30 drafts right away.
What link share is right for launch week?
A setting of about 50% is a reasonable launch-week choice: half the posts point to the product. Pick any value from 0% to 100% in steps of 5.
Can I time a post for a specific hour?
Threadgehog picks a time for each post from your posts-a-day setting, spread from 9 AM to 9 PM. You can reorder the Queue to change what goes out next.
Does the launch need the app open?
Yes. Threadgehog sends to your scheduler while it is open.
Can I use it for several launches?
Yes. Each product is a project. Solo includes 2 projects, Pro 10, and Unlimited has no project limit.
Does it write images?
Paid plans include Threadgehog images each month (30 on Solo, 75 on Pro, 150 on Unlimited). You can also attach your own image or video.
Is the app open yet?
It is on a waitlist. The 14-day free trial starts when it opens.
Sources
- Threadgehog home (checked 2026-10-17)
- Threadgehog FAQ (checked 2026-10-17)