Launches
Launches tell the right Audiences a Startup is live, where those Audiences already look.
Outcome
| Part | This Process |
|---|---|
| Outcome | A new Startup’s Audiences hear it is live through its launch post, listings and registries, each recorded for attribution. |
| Reads | Startup, Story |
| Leaves | Content, Page, Offer |
| Runs in | Each Startup |
Accountable
Marketing Lead, Marketing Team.
Workflows
| Workflow | Runs | Team |
|---|---|---|
| Launch announcement | on Startup.launched | Marketing Team |
| Compile the demand kit | on Startup.advanced | Marketing Team |
Who does each step
| Workflow | Step | Role | Calls | Approval |
|---|---|---|---|---|
| Launch announcement | 1. Publish the launch post on the Startup’s Site. | Content Lead | Content.publish | Asks first; waits 1 business hour |
| Launch announcement | 2. Submit the Startup to the directories and agent registries its demand Plays name. | Marketing Lead | Play.apply | None |
| Launch announcement | 3. Admit the Waitlist. | Sales Lead | Waitlist.admit | None |
| Launch announcement | 4. Record each listing as a Source for attribution. | Marketing Lead | Source.create | None |
| Compile the demand kit | 1. At Building, compile versus and alternatives Pages and an importer stub from the alternatives slot. | Content Lead | Page.create | None |
| Compile the demand kit | 2. Compile one free tool Page per read-only Verb with a one-field input. | Content Lead | Page.update | None |
| Compile the demand kit | 3. Compile the lead magnet as a $0 Offer from the Story’s transitional call to action. | Marketing Lead | Offer.create | None |
| Compile the demand kit | 4. Compile listing copy per venue, the launch post and the pricing Page from the Story, Offers and Prices. | Content Lead | Content.create | Within a Mandate |
| Compile the demand kit | 5. Leave the proof-chain shell empty until the first delivered outcome fills it. | Content Lead | ||
| Compile the demand kit | 6. On a pivot, recompile the kit and print which assets changed. | Marketing Lead | PlayMix.compile | None |
Events
| Direction | When | What happens |
|---|---|---|
| In | On Startup.launched | Starts Launch announcement |
| In | On Startup.advanced | Starts Compile the demand kit |
| In | On Startup.launched | Wakes this Process, the first time only. The Startup goes live. |
| Out | Content.published | Raised by step 1 of Launch announcement |
| Out | Play.applied | Raised by step 2 of Launch announcement |
| Out | Waitlist.admitted | Raised by step 3 of Launch announcement |
| Out | Source.created | Raised by step 4 of Launch announcement |
| Out | Page.created | Raised by step 1 of Compile the demand kit |
| Out | Page.updated | Raised by step 2 of Compile the demand kit |
| Out | Offer.created | Raised by step 3 of Compile the demand kit |
| Out | Content.created | Raised by step 4 of Compile the demand kit |
| Out | PlayMix.compiled | Raised by step 6 of Compile the demand kit |
Plays
- Integration partners
- Marketplace listings
- Agent registries
- Directory listings
- Launch sites
- House ads
- Launch week
Controls
No Control names this Process or a Workflow of it.
Settings
None.
Failure
A failed step retries; when retries run out, the Action goes to the Marketing Lead.
Loop
| Step | Value |
|---|---|
| Hypothesis | Launching only where the ICP already looks brings more Play-sourced Customers than launching everywhere at once. |
| Measure | Play-sourced Customers over 14d, at least 20 observations |
| Learn | The learn step reads the Readout, records Evidence and a Decision, and drafts the next Variant. |
Code
Turn on launchesEnable
On by default for every Product Template. Process.pause stops new Actions; Actions in progress finish.
Example
A currency-conversion API goes live. Launch announcement posts the launch, lists it in two MCP registries and one launch site, and admits its 80-Lead Waitlist the same hour.