StartupBuilder
StartupBuilder turns an Idea into an operating Startup with SiteBuilder, SoftwareBuilder, ServiceBuilder, and SalesBuilder.
StartupBuilder turns an Idea into a running Startup. The Startup is one definition: api.sb serves it, Agents operate it, and its owners steer it.
StartupBuilderWhat it does
StartupBuilder holds the Startup's definition and directs the four other Builders that build its parts. All five share one set of records. A Price changed once is the price on the Site, in the API, and on the next Invoice.
A new Startup starts from a Startup Template: an operating model, one or more Product Templates, and the Motions they sell through. It arrives complete, with a Brand, Offers, a Site, every System on shared data, and an Agent seated in each Role.
StartupBuilder then runs it through its Lifecycle, from Idea to Live and on to Scale. Processes wake on Events, and every Action records who acted, for whom, and under which Mandate. Any Change can run as an Experiment, and a Studio runs the same machinery across a Portfolio.
Built from
Surfaces
Three Apps run StartupBuilder:
- startups.studio is where founders and operators build and run Startups, from one Startup to a whole Portfolio.
- startups.new creates a Startup from one sentence and opens it in startups.studio.
- startup.games shows a founder's progress as quests and streaks.
Four Interfaces reach the same Verbs under the same names: the API, SDK, CLI, and MCP. One command scaffolds a Startup as a project (details):
npm create startupsNext steps
- Vision: why a business runs as a program.
- The Startup as code: the model every definition is written in.
- What every call returns: statuses, reasons, and the three ways to call.
- What a Startup sells: four kinds, who supplies them, and how each earns.
- Operating models: what changes as humans join.
- Principles: seven rules the platform enforces.
Everything StartupBuilder covers, generated from the registry:
| Term | Kind | Definition |
|---|---|---|
| StartupBuilder | Product | StartupBuilder turns an Idea into an operating Startup with SiteBuilder, SoftwareBuilder, ServiceBuilder, and SalesBuilder. |
| startups.new | Product | startups.new creates a Startup from one sentence and opens it in startups.studio. |
| Founding Team | Team | The Founding Team decides what the Startup pursues: its Idea, its strategy, its Goals, and every call escalated to it. |
| Legal Team | Team | The Legal Team keeps the Startup lawful: Agreements, privacy and Consent from day one, screening of every Offer, and every Reserved Act. |
| People Team | Team | The People Team staffs every Role: it names an Agent for each one, recruits the Humans the law or the Startup needs, and pays them. |
| Product Team | Team | The Product Team decides what gets built and why: Product definitions, list Prices and packaging, the build list, and the Site’s Pages for each ICP. |
| Quality Team | Team | The Quality Team checks all work: the checks inside each Process, every outbound Message, and every money move, with verdicts, never Approvals. |
| Building | Lifecycle state | Building is the state of a Startup whose Agents build its Brand, Products, Offers, site, API, and MCP server from its template. |
| Dormant | Lifecycle state | Dormant is the state of a Startup with no work running on it, whose records, site, and domain stay kept until it returns to Live. |
| Graduate | Lifecycle state | Graduate is the state of a Startup that leaves its studio for a company of its own, keeping its Brand, Customers, and records. |
| Hold | Lifecycle state | Hold is the state of a Startup that keeps operating and serving Customers while its owner adds no new investment. |
| Idea | Lifecycle state | Idea is the state of a Startup that states its Idea and who pays, before any build work starts. |
| Live | Lifecycle state | Live is the state of a Startup that is publicly reachable and takes money from Customers for at least one Offer. |
| Scale | Lifecycle state | Scale is the state of a Startup that compounds: Customers stay and expand, demand comes from several sources, and margins hold. |
| Sell | Lifecycle state | Sell is the state of a Startup whose owner has agreed to sell it, with its Brand, domain, Customers, and records. |
| Agent-run services firm | Startup Template | An Agent-run services firm runs with no humans and sells warranted outcomes as Services-as-Software, with the Agent behind them for hire. |
| Autonomous agent business | Startup Template | An Autonomous agent business runs with no humans and sells Agent as a Service to businesses, people, and other Agents. |
| Autonomous data API | Startup Template | An Autonomous data API runs with no humans and sells a Dataset API and Headless SaaS to developers and their Agents. |
| Autonomous directory | Startup Template | An Autonomous directory runs with no humans and sells listings in a Directory to Organizations that want buyers and Agents to find them. |
| Autonomous storefront | Startup Template | An Autonomous storefront runs with no humans and sells physical goods as a Dropship store to people and the Agents that shop for them. |
| Founder-led marketplace | Startup Template | A Founder-led marketplace has one Human founder who signs for a Marketplace, while Agents recruit Suppliers and serve buyers. |
| Licensed professional network | Startup Template | A Licensed professional network extends the Founder-led marketplace into a Licensed-human marketplace that buyers and their Agents book. |
| Managed service firm | Startup Template | A Managed service firm extends the Agent-run services firm with Humans who share Roles and an E2E managed service for businesses. |
| Solo SaaS | Startup Template | A Solo SaaS has one Human founder and Agents in every other Role, selling SaaS and its Headless SaaS to businesses and people. |
| Autonomous | Operating model | Autonomous is the operating model with no humans: Agents fill every Role, and one-way decisions wait out a delay window before they proceed. |
| Multi-human | Operating model | Multi-human is the operating model where several Humans share Roles with Agents, each Human working under their own Mandate and Limits. |
| Single human | Operating model | Single human is the operating model with one Human, a working CEO or a passive board chair, and Agents in every other Role. |
| Corporate records | System | Corporate records keeps the legal Company behind a Startup: formation, officers, registered office, filings, board resolutions and good standing. |
| Discovery | System | Discovery runs buyer research: Interviews, Problems, graded Evidence, ICPs and Personas, so every Offer starts from what buyers said. |
| Documents | System | Documents keeps every versioned Document, deck or sheet, generated from records and rendered to the web, PDF, slides or spreadsheets. |
| Equity | System | Equity is the core System that keeps the cap table of each Company: shares, SAFEs, options and their holders, grants, vesting and conversions. |
| Experiments | System | Experiments tests Hypotheses by varying copy, Price or behavior through Flags and decides each winner from primary and guardrail Metrics. |
| Goals | System | Goals records what each Thing is trying to achieve: its Goals, Key Results read from Metrics, and the Decisions behind them. |
| Hiring | System | Hiring fills open Roles with Humans: postings, candidates, screening calls held as Meetings, assessments and employment Agreements. |
| Intellectual property | System | Intellectual property keeps a Startup’s trademarks, patents, Domains and handles as one register, with deadlines and renewals watched. |
| Ledger | System | Ledger is the double-entry book of record: Entries posted from Events, reconciled to Transactions, and closed each Period into statements. |
| Pay runs | System | Pay runs keeps each employee’s pay record, prepares every run with withholding and deductions, and posts it to the Ledger. |
| Product analytics | System | Product analytics turns the Visits and Events captured on every Domain and API into the conversion, activation and retention Metrics every Team reads. |
| Reports | System | Reports arranges saved Metric queries into Dashboards, weekly reviews and investor updates, delivered on a schedule and watched for thresholds. |
| Spend management | System | Spend management controls money going out: budgets, bills, expenses and cards issued on Stripe, each paid against Limits and spend states. |
| Surveys | System | Surveys measures sentiment, such as NPS, CSAT and the product-market-fit question, and turns every answer into Metrics and Evidence. |
| Tax | System | Tax calculates and collects sales tax and VAT, tracks registrations, and prepares every return and information return. |
| Treasury | System | Treasury holds a Startup’s cash accounts and balances on Stripe, moves money between them, and forecasts runway. |
| Workforce | System | Workforce keeps every Worker, Human or Agent: the Roles they fill, their Teams, Skills, onboarding, assessments and offboarding. |
| Customer research | Process | Customer research learns from what buyers did and paid, never from their predictions. |
| Founder Run | Process | Founder Run walks every Startup Template through its published Interfaces in test, as a synthetic founder and buyers, and records each step that stops. |
| Iteration | Process | Iteration improves the Startup one change at a time: one number, the worst step, and one change a week. |
| Role review | Process | Role review checks every filled Role against its contract each week and turns each missed result into a Decision. |
| Runway | Process | Runway tells the Founder every week whether the Startup reaches profit before its cash runs out. |
| Staffing | Process | Staffing fills every Role in a Startup with an Agent by default and a Human where one is required. |
| Strategy | Process | Strategy keeps the Startup’s ambitions, focus, and positioning true to its Evidence. |
| Owned following | Play | Owned following grows a niche newsletter, community and shared accounts in a Studio media Startup and lends its slots to siblings by expected value. |
| Reserve drop | Play | Reserve drop opens refundable deposits for 72 hours after one creator post and moves the Startup to Building only if deposits cross the entry check. |
| Agreement | Noun | An Agreement is a contract between two or more Parties, with its term, liability, and economics, that travels with the Startup. |
| Builder | Noun | A Builder is a named part of api.sb that builds one side of a Startup; StartupBuilder directs SiteBuilder, SoftwareBuilder, ServiceBuilder, and SalesBuilder. |
| Cohort | Noun | A Cohort is a set of Startups that receives one Version of a shared definition, or one step of a Play, at the same time. |
| Company | Noun | A Company is a legal entity that holds Startups, signs Agreements, and owns equity, authority, and profit rights. |
| Evidence | Noun | Evidence is a recorded quote, reading, or artifact that supports or refutes a claim, graded as behavior, commitment, or opinion. |
| Experiment | Noun | An Experiment is a test of a Hypothesis that varies copy or behavior through Flags and judges the variants by a primary Metric. |
| Exposure | Noun | An Exposure is the moment one unit meets the Variant its Flag assigned, logged with every option and its propensity. |
| Forecast | Noun | A Forecast is a dated week-by-week projection of a Startup’s cash, revenue and Cost, computed from its records, that sets its spend state. |
| Goal | Noun | A Goal is what a Thing is trying to achieve: an objective with one or more Key Results. |
| Human | Noun | A Human is a Worker who is a person, acting on Tasks through Apps, Mailboxes, and Channels. |
| Hypothesis | Noun | A Hypothesis is a belief about a Startup stated so it can be proved wrong, with the Metric and threshold that settle it. |
| ICP | Noun | An ICP is the ideal customer profile a Startup is built to win: who they are and what they do. |
| Interview | Noun | An Interview is one person’s pass through a question script, led by an Agent, whose answers become Evidence. |
| Key Result | Noun | A Key Result is one measurable target inside a Goal: a Metric, a baseline, a target, and a deadline. |
| Lifecycle | Noun | A Lifecycle is the states a Thing of one Noun moves through and the Verbs that move it between them. |
| Minimum Success Criteria | Noun | Minimum Success Criteria is the one number a Startup must reach by a date to stay worth running: a Goal the Founder sets once. |
| Persona | Noun | A Persona is a named type of person with a job to do, such as a buyer, a seller, or an admin of an App. |
| Policy | Noun | A Policy is a ruling a Startup declares on how its numbers are computed or its choices made, such as revenue recognition. |
| Portfolio | Noun | A Portfolio is a managed set a Thing allocates attention and money across, by membership: a Studio’s Startups, a Startup’s child Startups, or its Products. |
| Problem | Noun | A Problem is what an ICP struggles with, in their own words: how they solve it today and what it costs them. |
| Project | Noun | A Project is a body of work toward a Goal: its Tasks and Issues, a start, and a target date. |
| Readout | Noun | A Readout is an Experiment’s result per Variant on its Metric, with the sample size, the interval, and how far the number can be trusted. |
| Role | Noun | A Role is a seat that owns a set of work and holds the Permissions to do it, filled by a Human or an Agent. |
| Startup Template | Noun | A Startup Template is an operating model, one or more Product Templates, and the Motions they sell through, which a new Startup starts from. |
| Story | Noun | A Story is the customer narrative for one ICP, compiled from its Founding Hypothesis and Interview quotes, never written by hand. |
| Studio | Noun | A Studio is an organization that builds Startups, holds them through Companies, and runs Plays across its Portfolio. |
| System | Noun | A System is the headless software for one job, such as CRM or billing, that every Startup runs on shared data. |
| Team | Noun | A Team is a named group of Roles under one owner; every Startup starts with eleven default Teams. |
| Variant | Noun | A Variant is one value an Experiment can assign, such as a revision, a Price on a sibling Offer, or a prompt, with its lineage. |
| Worker | Noun | A Worker is a Human or an Agent that fills a Role and acts on Tasks. |
| Idea.pursue | Verb | Pursue starts a Startup on an Idea as one variant of the Experiment that tests the Idea. |
| Play.apply | Verb | Apply runs a Play across a Portfolio cohort, one wave at a time, measured as an Experiment. |
| Startup.advance | Verb | Advance moves a Startup to its next Lifecycle state once every entry check of that state passes. |
| Startup.build | Verb | Build provisions the Systems, Sites and Interfaces a Startup’s definition declares, and moves the Startup to Building. |
| Startup.claim | Verb | Claim binds a provisional Startup to a verified owner, which enables payments and every Verb that moves money. |
| Startup.clone | Verb | Clone copies a Startup’s definition into a new Startup once, with no link back to the source. |
| Startup.graduate | Verb | Graduate moves a Startup to a Company of its own, with its Customers, Domains and records intact. |
| Startup.hold | Verb | Hold keeps a Startup running in its current Lifecycle state with no new investment from the Studio. |
| Startup.import | Verb | Import builds a new Startup from an existing business’s definition: its Offers, Pages, Nouns and Processes. |
| Startup.launch | Verb | Launch puts a Startup live on its domain, serving its Offers to Customers. |
| Startup.pause | Verb | Pause moves a Startup to Dormant: its scheduled Workflows stop, and its Sites and records stay in place. |
| Startup.resume | Verb | Resume returns a Dormant Startup to the Lifecycle state it held when it paused. |
| Startup.sell | Verb | Sell transfers a Startup, with its Customers, Domains and records, to a buyer under a signed Agreement. |
| StartupTemplate.extend | Verb | Extend adds a Startup Template to a Startup’s bases, pinned to a Version, so the Startup inherits its definition. |
| StartupTemplate.promote | Verb | Promote moves one Startup’s refinement into a Startup Template, so every Startup that extends it inherits the refinement. |
| StartupTemplate.upgrade | Verb | Upgrade moves a Startup to a newer Version of a Startup Template it extends, through a Change it can review. |
| Template.extend | Verb | Extend adds a Template to a Startup’s bases, pinned to a Version, so the Startup inherits its definition. |
| Template.promote | Verb | Promote moves one Startup’s refinement into a Template, so every Startup that extends the Template inherits it. |
| Template.upgrade | Verb | Upgrade moves a Startup to a newer Version of a Template it extends, through a Change it can review. |