Launching Leaseline
Tutorial 12 of 12 claims Leaseline, reads its launch checks and takes it Live, then points to the same path for other templates.
Launch moves a Startup from test to Live when every launch check passes. Leaseline claims its Stripe account, reads what still fails, and launches.
What you build
You claim Leaseline with its claim token, preview launch with --try, close the failing checks, and launch. After launch, real cards are charged and real Messages leave.
Steps
To take real money, claim the Startup with the claim token that tutorial 1 printed, then finish Stripe onboarding at the link it prints:
npx startup-builder do Startup.claim --json '{"startup":"startup_l3hr1EnUGY", "claimToken": "ct_7Hq2xV"}' To see what stands between Leaseline and Live, preview launch:
npx startup-builder do Startup.launch --json '{"startup":"startup_l3hr1EnUGY"}' --try To close each failing check, follow the fix it names. The scenario from tutorial 11 passes the test run; the slot check needs Evidence from outside people.
To launch, call it without
--try:npx startup-builder do Startup.launch --json '{"startup":"startup_l3hr1EnUGY"}'
Result
Leaseline went Live on 2026-04-10. Its launch read these checks:
Launch reads 10 checks for leaseline.app, a Solo SaaS Startup: the ones every Startup passes. Some templates add more; the launch checklist lists them all.
| Check | Id | Kind | Passes when |
|---|---|---|---|
| Offers published | live-offers | registry | At least one Offer is published with a price and terms; launch refuses a Startup without one. |
| Work defined | live-work | registry | Every published Offer has a workflow that delivers it, with each step assigned to software, an Agent, or a person. |
| People assigned | live-people | registry | Every role the workflows need is held by an Agent or a person, with instructions and limits. |
| Site published | live-site | ui | The site serves home, pricing, terms, and privacy pages under the Brand, readable by people and agents. |
| Test run passed | live-test-run | transcript | A sample Customer completes every published Offer end to end in test, with no real charge or message. |
| Portal ready | live-portal | ui | The customer portal on the site shows each Customer their orders, deliveries, invoices, and messages. |
| Agent API open | live-agent-api | contract | The API, MCP server, OpenAPI document, llms.txt, and agents.json serve every published Offer and pass conformance. |
| Payouts connected | live-payouts | contract | Stripe takes payments for the Startup and pays out to its bank account. |
| Address resolves | live-address | contract | The canonical Domain serves the Site over HTTPS with a valid certificate and, where it embeds a payment form, Stripe lists it as a payment method domain. |
| Proof people want it | live-slots | grade | All five Founding Hypothesis slots hold Commitment Evidence from outside people. Slots customer, problem, approach, switch, differentiation at Commitment or stronger, outside Evidence only. |
Checkpoint leaseline@ch12 (status planned) is the launched project. The other templates take the same path with their own files: an API business, a service business, first revenue and first revenue by asking.
Next steps
- The Leaseline year: Leaseline from day 0 to 2026-10-22.
- Launch checklist: every check, for every template.