studio-launch
Launch
This skill runs ProductOS's recurring launch ritual — the same motion at four moments across the program, each climbing one rung of the signal ladder:
| # | Launch | Phase | What ships | The win (pass bar) |
|---|---|---|---|---|
| 1 | Mini-Launch | Define | The offer, in the persona's words | One reply |
| 2 | "Here's what it looks like" | Design | The landing-page draft, identity, or magic-moment mockup | One "can I try it?" or signup |
| 3 | The beta invite | Develop | The working MVP, into believers' hands | One activated user (reaches the magic moment) |
| 4 | The public launch | Distribute | The live product, announced on the primary channel | First payment |
The mechanics never change — that's the point. Draft from your docs → ship within 48 hours → share a screenshot of the live post or sent message with your cohort → log every response. (In the Product Studio, "your cohort" is your programme group; working solo, share it with an accountability partner or post it publicly — any witness keeps the bar honest.) By launch #4 the user isn't nervously shipping their first ask; they're a founder who launches routinely, to an audience that has watched the product grow since it was a paragraph.
Two threads carry between launches:
- The believers list. Everyone who ever responds gets a name on the list in
docs/LAUNCHES.md. Launch #1's replier is launch #2's preview reader, launch #3's beta user, and launch #4's first customer and testimonial. Every launch goes to the believers first, then to the wider channel — warm before cold, always. - The same channel, by default. Relaunches return to the thread that worked — same community, same feed, ideally the same literal thread ("update on the thing I posted about in March…"). Attention compounds only if it accumulates in one place. Pick a new channel only if the last one was silent after a full send and one rewrite.
And one rule keeps the ladder honest: each rung is a target that triggers a conversation, not a gate. Missing a rung once means rewrite and resend. Missing the same rung twice is a signal worth respecting — open productos/define/BONUS-Pivot-Framework.md, and if the user is in a cohort, this is the moment to talk to their coach. Nobody stalls out of the program for missing a rung; they course-correct because of it.