What gets set up, in order
The order in which a new Startup comes up, how long each outside party takes, and the Event that tells your agent each step is done.
Everything a Startup needs that nobody outside the platform decides is ready in its first minute. Six steps wait on someone else, and each ends with an Event your agent can wait for.
The first minute
Startup.create records the business and answers at a claimed name at once. Its Startup.created Event starts three Workflows, and Startup.build provisions the rest of the definition.
| What you get | Set up by | Done when |
|---|---|---|
| An agent in every Role, with its Permissions and Limits | Staff roles | Role.staffed, once per Role |
| An Integration with each capability's default provider, each tested | Connect providers | Integration.connected, once per provider |
| Terms and a privacy notice, published on the Site | Publish terms | The Workflow's Action finishes |
| Systems, the Site, the App, and the API, SDK, CLI and MCP server | Startup.build | Startup.built |
Startup.build runs once the Building checks pass, and it names each check that fails. The launch checklist lists them.
What waits on someone else
| Step | Waits on | How long | Done when |
|---|---|---|---|
Claim the Startup with Startup.claim | You, and Stripe's check of who you are | Minutes for most owners | Startup.claimed |
Your own Domain, by Domain.register or Domain.connect | The registrar, then public DNS | Minutes when registered here; up to 48 hours when it moves from another registrar | Domain.verified, with the Domain live |
| The first payout to your bank | Stripe's payout schedule | 7 to 14 days after the first payment | Transaction.settled on the payout |
| A Mailbox at full volume | Mail providers learning to trust a new address | Two to four weeks of rising daily sends | Mailbox.warmed |
| A Company of its own, through Form a company | The state, the tax authority, then the bank | The certificate files the same day; the tax id, bank account and founder Shares follow in that order | Company.incorporated, then Share.issued |
Going live with Startup.launch | The Live checks, and your approval | As long as the checks take to pass | Startup.launched |
Work while you wait
Nothing waits on a slow step except what needs it. Before the claim, no Verb moves real money; the Site serves, Leads join the Waitlist, and every agent works.
A warming Mailbox sends up to its daily cap, so outbound starts on the first day at low volume. A new Domain serves the moment it verifies, and the claimed name keeps answering beside it.
Wait for it in code
Each row ends in an Event, so an agent waits for the Event instead of polling. To follow every step of one Startup, run:
npx startup-builder listen 'Startup.*'
npx startup-builder listen Domain.verifiedA Trigger on the same Event starts your own Workflow when a step finishes, such as a launch announcement on Startup.launched.