Solutions · Feature release
A big release deserves more than a changelog entry.
A feature release plan is a dated set of X creator posts that explains one release to current and future users, at a fixed price per post. Creators show it working on the day it ships, and every post comes back with proof.
New plan · Feature release
Ready to signBrief
Who should try it first?
Current users on paid plans
What can creators show?
A short screen recording
Audience fit on X
Distribution plan
X · 4 placements- X creator, analytics engineeringLive Dec 2, 9amFixed price
- X creator, product analyticsLive Dec 2, 11amFixed price
- X creator, AI for data teamsLive Dec 3Fixed price
- X creator, SaaS growthLive Dec 4Fixed price
Nothing is booked or paid until you approve.
How the wave runs.
Posts are spread across the hours and days that matter, timed to your moment. Select a point on the line to see what happens then.
Launch wave on X
Select a moment- Day -5: Creators get early access. Creators try the feature before it ships, so their posts show real use, not a press release.
- Day -1: Drafts are approved. You approve each draft and the claims in it. The feature, not the brand, is the subject.
- Release day: The release goes live. Your announcement and the changelog go up. The plan is timed to the release.
- Same day: Creators show it working. Creators post short walkthroughs for the people who would use the feature this week.
- Day +2: Second look. A second group posts with a use case your users had not thought of.
- Day +3: Proof comes back. Every placement returns its live link, the time it went up and the checks agreed in the brief.
What creators post.
Each creator gets one of 3 angles (per our launch playbook) that fits their audience, so the posts read like them, not like an ad.
The walkthrough
Before and after
The use case
Proof for every post.
Our team checks each post as it goes live. You get the live link, the time and the checks agreed in the brief, placement by placement.
How proof is collected, and what counts, is in the playbook; the brief behind it is what a launch brief should specify.
Proof
4 of 4 returned- Creator, analytics engineeringLive link, disclosure, tracked link9am
- Creator, product analyticsLive link, disclosure, tracked link11am
- Creator, AI for data teamsLive link, disclosure, tracked linkDec 3
- Creator, SaaS growthLive link, disclosure, tracked linkDec 4
Where these go wrong.
Three mistakes we plan around on every one.
Announcing to existing followers only
Posts without the product
No access before release
Short answers
Is a feature release big enough for a plan?
When the release changes what people can do with the product, yes. A small fix is better in your changelog.
Do creators need access before release?
It helps. Posts from people who have used the feature are specific, and specific posts are the ones people stop on.
Can we target current users?
Creators reach audiences, not your user list. Plans pick creators whose audience looks like your users, which reaches both current and future ones.
Send the brief for your launch.
Tell us the date, the audience and the budget. The plan comes back with every post, date and price before anything is booked.