Launch planning for X
Your launch on X,planned like the ones that went viral.
A dated roadmap — warmup posts, a launch-day sequence, follow-ups — built from real launch teardowns, a curated playbook, launches you admire, and your own posting history. Every step says which one it came from. It never connects to your account, and never posts for you.
- Warmup → day → after
- a dated plan, not one post
- 4 labeled layers
- playbook, teardowns, your picks, your history
- Never touches your account
- no connection, no posting, no scheduling
01The roadmap
A plan that knows what day it is.
Warmup posts, a launch-day sequence, follow-ups — every step dated from your launch date and labeled with where it came from. Open it any morning and the top of the page is about today: what’s due, what you’ve already ticked off, and what’s coming. Fall behind and it offers to refit the rest of the plan around the days you have left.
Today · Wednesday
One step is due today, and launch day is Saturday.
Next up: day 0, Saturday — launch post.
- Day −12Mon 21 JulWarmup✓ Done
Post the problem you kept hitting, before you mention building anything.
Real launch - Day −7Sat 26 JulWarmup✓ Done
Show one ugly screenshot of the thing half-working.
A launch you added - Day −3Wed 30 JulWarmup
Name the launch date out loud so the timeline has a reason to come back.
PlaybookDraft - Day 0Sat 2 AugLaunch day
Launch post — open on the story, not the feature list.
Real launchDraft - Day +2Mon 4 AugFollow-up
Answer the sharpest objection you got, as its own post.
Your own posts
Every step names its source — nothing generic wears a personal label
02The four layers
Every step tells you where it came from.
Generic launch advice is easy to find and easy to ignore. OnPilot blends four sources into one plan, weakest to strongest, and labels every step with the one behind it — so you can weigh each move by its evidence rather than taking the whole plan on faith. Generic advice never wears a personal label, and a claim the layers don’t support is dropped before you see it.
Playbook
Curated general launch practice — the base layer. Always available, never dressed up as personal. Where a step has nothing stronger behind it, it says so.
Real launches
Teardowns of launches that actually went viral, curated by us. A step drawn from one tells you it came from a real launch rather than from received wisdom.
Launches you add
Paste a launch you want yours to look like. OnPilot reads it — including the video — breaks down why it worked, and folds it in as its own labeled layer.
Your own posts
Upload the analytics export X gives you and your own record becomes the fourth layer. Below a reliable sample, OnPilot says so instead of guessing.
And no number OnPilot can’t stand behind. The plan never predicts how big your launch will get. The only figures in the product are computed from your own posts in code — never written by a model — and withheld entirely when the sample is too thin.
03Ask
Every answer shows its working.
Ask anything about your launch and the answer is built from the same four layers as the plan — and says which ones it used. It still won’t give you a number it can’t stand behind.
You
My launch date slipped a week. Should I re-run the warmup posts or skip ahead?
OnPilot
Skip ahead. The warmup exists to make launch day land on people who already know the problem — reposting the same beats a week later costs you the novelty without buying more of that. Move the launch date instead and let the roadmap refit; the two warmup steps you already ran still count.
Grounded in: Playbook · Real launch · Your own posts
04Score a post
Half your text posts land between
1,240–3,900
Paste a draft before you post it. This is your own record for that format, read back to you — not a forecast of what this particular post will do.
- A range, never a guess
- p25–p75 of your own posts in that format — the middle half of what you have actually done. Nobody can tell you what one post will get, so OnPilot doesn’t.
- The words don’t move it
- The band belongs to the format, not the phrasing. Nothing reads your draft and nudges the number — there would be no evidence behind the nudge.
- Or it refuses outright
- Under 30 posts in that format, you get a refusal instead of a band. One viral night can’t drag it either: posts above 5× your median are excluded and flagged.
05How it works
From idea to launch plan in one sitting.
- 01
Answer six questions
A short form: what you’re launching, who it’s for, what it’s called, when it ships, why you built it, what would make it a win. Paste your site and the first two boxes fill themselves in for you to correct. Six questions because six is what the plan reads — nothing here is asked for its own sake.
≈ 5 min - 02
Get the roadmap
Warmup posts, a launch-day sequence, and follow-ups — dated from your launch date, with drafts to edit, and every step labeled with the layer it came from. Tick steps off as you go; the top of the page always says what today needs.
labeled - 03
Sharpen it as you go
Ask why any step is there. Paste launches you want yours to look like. Upload your X analytics export so the plan leans on your own record. Band a draft against your history before it goes out. Run more than one launch — each gets its own roadmap and countdown.
your call
06Questions
Answered plainly.
Does OnPilot post for me?
No — and it goes further than that: it never connects to your X account at all. No OAuth, no read access, no scheduling, no publishing. It writes you a plan and drafts; you decide what goes out and you post it yourself.
What happens if my launch slips?
The roadmap notices. Miss steps and the top of the page says how far behind you are and offers to refit the rest of the plan into the days you have left — showing you exactly which steps it would cut. It is always an offer; moving the launch date instead is right there too.
Do I need a big following already?
No. The playbook and the real launch teardowns work at any size. Uploading posting history sharpens the plan, but it is not required — and nothing is gated behind it.
What if I have never launched before?
That is who this is for. The roadmap walks you from warmup through launch day to follow-up, one dated step at a time, each with a draft and a stated source. If you want to know why a step is there, ask it.
How do the launches I paste in get used?
Paste a viral launch you admire and OnPilot fetches it, watches the video if there is one, and breaks down why it worked — then folds those tactics into your plan as their own labeled layer, never blurred with your own history.
How does my own history factor in?
Upload the analytics export X gives you — a CSV, no account access — and the plan leans toward the formats that already work for you. Two honest limits: the export carries no thread or media column, so those formats can’t be derived from it, and below a reliable sample OnPilot says so instead of guessing.
Will it tell me how many views I’ll get?
No, and that is deliberate. The only number in the product is the band on a draft you paste — the middle half of what your own posts in that format have actually done. Nothing forecasts your launch, and no figure anywhere is written by a model.
Can I plan more than one launch?
Yes. Each launch gets its own roadmap, its own countdown, and its own set of pasted references.
Plan the launch your product deserves.
Not open yet. Leave your email and you’ll be first in.