GuidesTutorials
Earning first revenue by asking
The 30-day first-revenue calendar with no code: each day is one sentence you say to your agent and the guide it runs.
The same 30 days as the command tutorial, told as what you say. Your agent runs every call, and each step links the guide that lists them.
What you build
cleanshelf.com, a Solo SaaS that cleans a small store's product catalog. You ask for money before you build, and you sell the first Customers yourself.
Launch on day 18 opens Live once these pass:
Launch reads 10 checks for cleanshelf.com, 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. |
| Five slots at Commitment | 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. |
Steps
- Day 0. Say
Start a business that cleans product catalogs for small online stores. Your agent writes the Founding Hypothesis with you; the guide lists what it creates. - Day 0. Say
Take a refundable deposit. A reserve page goes live; the guide shows its terms. - Days 1 to 4. Say
Find out if anyone wants this. Your agent sets the bar before the page goes live, as the guide explains. - Day 4. Say
What are people asking for. The problems from your interviews come back ranked, as the guide shows. - Day 9. Say
How is it going. Your agent answers from the records and keeps a dashboard, as the guide shows. - Day 18. Say
Are we ready to launch, thenGo live. The launch guide lists each check and what clears it. - Day 21. Say
Welcome every new customer. Each new Customer gets the same first steps, as the guide lists.
Result
You have outside paying Customers, payouts to your bank and a Founding Hypothesis graded on all five slots. You wrote no code.
Next steps
- The command tutorial: the same calendar, with every command and its output.
- How to ask: phrasing that finds the right guide.
- Guides: every sentence your agent acts on.