Skip to content

Lifecycle

How a Startup moves from an idea to a business that sells, one gated state at a time.

Read as
GuideSpec

A Startup's Lifecycle is the state it holds on the way from its first Idea to a business that compounds. A state is entered when its entry checks pass, never by hand, and every Interface reads it.

Nine states

Five states climb: Idea, Building, Live, Repeatable and Scale. Four leave the climb. Hold keeps a Startup running with no new investment, and Dormant stops its work and keeps its records.

Graduate and Sell hand the Startup to a new owner, intact. Nothing ends in deletion.

Checks move a Startup

Every entry check is an assertion over the Startup's records. Its kind says how the assertion is proved.

KindProvesExample check
registryA record exists and resolvesBrand named
contractAn outside system confirms itPayouts connected
transcriptA recorded run succeededTest run passed
uiA rendered page shows itSite published
metricA Metric holds its line over a window, outside parties onlyCustomers stay

A failing check whose dependencies pass becomes a Task for the Role that owns it. advance reads every check and moves the Startup the moment they all pass.

Startup.advance
API
POST /{namespace}/startups/{startup}/advance
SDK
$.Startup.advance(input)
CLI
startup-builder do Startup.advance --json '<input>'
MCP
do: $.Startup.advance(input)

Metric checks cannot be filled in. An Agent can write a Problem statement; it cannot write ten outside Customers who paid.

The outside paid Order

Every state after Live counts one fact: an outside Customer paid for an Order. A party is outside when it shares no owner, no Studio account, no Agreement and no sibling chain with the Startup.

A sibling Startup buying 40 seats, the owner's own card, and trades between Startups of one Studio are real revenue, reported apart. None of them counts toward Outside revenue, so none moves a Startup up the climb.

The climb reads that one fact at rising strength. Live can take an outside paid Order and starts the clock to the first one. Repeatable needs ten outside Customers who arrived through Plays, stay, and pay back what they cost; Scale needs them spending more a year later.

One number per state

Each climbing state names the one Metric that matters while the Startup holds it.

StateOne metric that mattersWhat it proves
IdeaProblem interviewsOutside buyers describe the problem's past cost
BuildingCommitted ICP membersSome of them commit: a deposit, a pre-order, a paid pilot
LiveOutside paying CustomersStrangers pay
RepeatableMonth-3 retentionThey stay
ScaleNet revenue retentionThey spend more

Every number is computed from records. The Weekly review reads the state's number first; every other Metric is context.

The weekly loop

A Startup climbs one week at a time. Weekly review finds the step where most buyers leak and makes one change per path, with an undo note, recorded as a Decision.

Office hours follow. A Studio partner Agent reads the Startup's Dashboard, asks the questions for its state, and checks last week's commitments against the records.

A human Founder answers in a short session and signs the Decision. A Founder Agent answers in writing, and an answer that cites no record counts as opinion. When the number stays flat, Pivot review decides whether to change course.

Next