Launch week
Launch week batches a quarter’s tier 1 and tier 2 Changes into five dated days of posts, Pages, listing refreshes and newsletters.
Ratings
| Dimension | Rating | Reads |
|---|---|---|
| Scalability | 3 of 5 | medium: higher grows further with spend or automation |
| Cost | 1 of 5 | very low: lower costs less per Customer |
| Latency | 2 of 5 | low: lower answers sooner |
Budget
| Property | Value |
|---|---|
| Tier | $0 |
| Minimum effective budget | $0 a month |
How it runs
The Studio rolls it out to one cohort at a time: startups that shipped tier 1 or 2 Changes this quarter.
Processes
Runs as Launches, accountable to the Marketing Team.
Fits
| Fits | Value |
|---|---|
| Family | demand |
| Shelf | Seed: finds the first Customers (Launch) |
| Moves | Organic share |
| Motions | b2b, b2c, b2d, b2a |
| Venues | Product Hunt, Hacker News, X, LinkedIn, Gmail |
| States | Live, Repeatable, Scale |
Loop
| Step | Value |
|---|---|
| Hypothesis | Five dated days of batched Changes earn more organic first touches than announcing each Change as it ships. |
| Measure | Organic share over 30d, at least 50 observations |
| Learn | The learn step reads the Readout, records Evidence and a Decision, and drafts the next Variant. |
Example
A Startup that shipped an importer, a mobile app and three integrations this quarter launches them over five weekdays. Each day gets one post, one Page and one listing refresh, and the last day's newsletter recaps the week.