startups.new
startups.new creates a Startup from one sentence and opens it in startups.studio.
startups.new is where a founder and their agent vibe-code a Startup. One sentence builds the product and the business around it: a Site, a Domain, payments, sales, support, legal, books and Agents.
What it does
The first screen is one prompt. A founder types Track lease renewals for small property managers, and signs in. The sentence survives the sign-in, and the build starts on return.
| Step | What happens |
|---|---|
| Read back | The agent restates the sentence as customer, problem and price, and asks at most one question: Up to 200 units, |
| Pick a brand | Four to six cards each show the home page under one Brand, with its name, logo, colors and Domain price. Choosing one records a Decision with the others attached. |
| Build | Named steps stream with counts: Drafted 3 Offers, Wired 4 Processes, Seated 2 Role agents. |
| Test | The real Processes run on sample Customers. No card is charged and no message leaves. |
| Claim | One link: connect Stripe with your identity and bank details, and become the owner of record. Sponsor claim shows the page. |
| Publish | The Live checks run, and the Startup goes live at a Version. |
Publishing runs every check below. Each failing check names what clears it.
Launch reads 10 checks for leaseclock.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. |
After that, the founder asks for one task at a time: put up a page, take a payment, charge monthly. Every ask is one or more Verb calls that any Interface makes, so a terminal or a coding agent takes the same path.
What the agent knows
The agent reads these docs: llms.txt, asks.json and every page as Markdown.
It offers a guide only when the guide is documented and live or beta. A guide on the wakes shelf waits for its Event. The agent offers single sign-on only once a buyer asks for it.
Chat, code and files edit one definition
Each Change returns as an edit card with an undo button: Price $29/. Undo reverts the definition; it never refunds a payment or unsends a message.
Agents never apply bulk writes. Two or more record writes from chat, any delete, or an agent write that matches an ask-first rule becomes one change set a person applies.
Built from
Surfaces
- The web app at startups.new. After the first build, the Startup opens in startups.studio.
- Runs live on the server and resume by id: closing the tab never stops a build.
- No one picks a model in the app; developers set models through the Interfaces.
- Each Startup serves its own Site, checkout, Portal, API, MCP server,
llms.txtandagents.json(apps every Startup gets).
Next steps
- startups.studio: where the new Startup is built and run.
- With your agent: the first ten minutes, step by step.
- With code: the same Startup from a terminal.
- Beside your app builder: the business around an app built anywhere.
- Test and Live: what each environment guarantees.
- Live: every check that publishing runs.