Playbook
The X launch playbook.
An X launch playbook is how a team gets a launch in front of the right people on X, through creators they already follow. It covers when posts go up, who posts them, what the brief says and how each post is proven.
01 · Plan the wave
Most of a launch happens in its first hours.
A launch post on X gets most of its reach early. Creator posts are timed to arrive while it is new, then again when there is something to report.
Launch wave on X
Select a moment- Day -7: Brief the creators. A week gives creators time to try the product and write a post that sounds like them.
- Day -2: Approve drafts. Read every draft against the brief. Fix claims now, not after the post is live.
- Launch hour: The launch post goes up. From the founder or the company account. Everything else is timed to it.
- First hours: First wave. The creators closest to your buyers post and quote the launch while it is climbing.
- Day +1: Second wave. A second group posts with what happened: the first users, the reactions, the demo.
- Day +3: Collect proof. Every placement returns its live link, time, disclosure and tracked link.
Ship on a weekday morning in your buyers' time zone, and keep a quoteable launch post ready: a quote sends reach back to the original. The same shape works for a funding announcement and a feature release.
02 · Choose creators
Choose by who answers, not by who follows.
Follower counts include people who will never buy. These four signals say more about whether a creator reaches your buyers.
Who replies
What they post now
How past paid posts read
Where the audience is
What these creators cost, and what moves the price, is on X creator rates.
03 · Write the brief
A brief a creator can say yes to.
Every question a creator has to ask costs a day. Tick what your brief already covers.
The long version, with a template, is what a SaaS launch brief should specify.
Your creator brief
2 of 8 covered
A creator would still have to ask about 6 things.
04 · Collect proof
Every paid post should prove itself.
Agree the proof in the brief, before anyone posts. Every placement should return these 6 checks (per our proof standard).
| Check | What it shows | When |
|---|---|---|
| Live link | The post exists, on the agreed account | When it goes up |
| Time posted | It went up in its slot, not a day late | When it goes up |
| Disclosure | The post is marked as paid, the way the brief says | When it goes up |
| Tracked link | Clicks from this post can be counted on their own | When it goes up |
| Content check | It says what was agreed and nothing the brief ruled out | Within the hour |
| Views and replies | How far it travelled and who answered | After 24 and 72 hours |
Disclosure follows the FTC's Disclosures 101 for social media influencers in the US.
Six ways a launch wave goes wrong.
Each of these is common, and each is avoidable in the plan.
Everything in one hour
Big accounts, wrong audience
Copy written for the creator
No launch post to quote
Proof agreed after the fact
No second wave
Keep reading.
The rest of the method, by topic.
Short answers
How many creators does a launch need?
Fewer than most teams think. Four to eight creators whose audiences match your buyers, spread across launch day and the days after, usually beat twenty posts in one hour from accounts that do not.
Should creators post at the same time?
No. The first group posts in the first hours, while the launch post is new; a second group follows a day or two later with what happened. A single burst is gone by the evening.
Do paid creator posts need a disclosure?
Yes. In the US the FTC expects a clear disclosure on any post a brand paid for, and X offers a paid partnership label. Every brief should say how the post is disclosed.
What should a creator never be asked to do?
Pretend to be a customer, post copy written for them word for word, or hide that the post is paid. Posts that read like the creator perform better, and the rest put the brand at risk.
Want this run for you?
Send the brief. We plan the wave, brief and pay the creators and return proof for every post.