Startup

A Studio builds it; a Company holds it.

PropertiesCopy Anchor Link

ObjectCopy Anchor Link

{
  "$id": "https://api.sb/ledgerlark.com/startups/startup_1",
  "$type": "Startup",
  "name": "LedgerLark",
  "domain": "https://ledgerlark.com",
  "launchedAt": "2026-10-22T12:00:00Z",
  "template": "Example template",
  "idea": "Example idea",
  "spendState": "free"
}

RelationshipsCopy Anchor Link

• A Startup is built by one Studio: a Studio founds and builds its Startups and runs Plays across them. builtBy, inverse builds.
• A Startup is built with many Builders: StartupBuilder directs SiteBuilder, SoftwareBuilder, ServiceBuilder and SalesBuilder, each building one side of a Startup. builtWith, inverse builds.
• A Startup compiles many Play Mixes: a Startup compiles one Play Mix version a week and keeps every earlier version for the diff. compiles, inverse startup.
• A Startup has many Domains: a Startup holds each Domain registration and pays for the hostname. domains, inverse registeredTo.
• A Startup employs many Agents: an Agent holds a seat in the Startup and acts within the authority it grants; one Agent can hold seats in many Startups. employs, inverse employedBy.
• A Startup extends many Startup Templates: a Startup inherits a Startup Template’s definition, pinned to a Version it upgrades through a Change. extends, inverse startups.
• A Startup has many Forecasts: the default-alive check writes a Forecast every week and after every large money Decision; the latest sets the spend state. forecasts, inverse startup.
• A Startup funds many Demand Budgets: a Startup commits monthly Demand Budgets, each with a target and a stop rule. funds, inverse fundedBy.
• A Startup is held by one Company: the holding Company is the Startup’s owner of record: it signs its Agreements and owns its profit rights. heldBy, inverse holds.
• A Startup makes many Products: each Product belongs to exactly one Startup, which builds it and stands behind its promise. makes, inverse madeBy.
• A Startup has many Markets: where the Startup sells, hires, or keeps books. Each Market wakes its floor rows. markets, inverse startups.
• A Startup must reach one Minimum Success Criteria: the one number that decides whether the Startup keeps running. mustReach, inverse setFor.
• A Startup has many Offers: each Offer has one maker, which earns its revenue and answers for its terms. offers, inverse offeredBy.
• A Startup operates under many Agreements: the Agreements a Startup operates under travel with it when it graduates or sells. operatesUnder, inverse covers.
• A Startup has many Portfolios: a Startup can sit in many Portfolios, each with its own membership: held, owned, contracted or made. portfolios, inverse includesStartup.
• A Startup pursues one Idea: many Startups can test one Idea side by side; the Idea outlives each Startup that pursues it. pursues, inverse pursuedBy.
• A Startup has many Recovery Objectives: one Recovery Objective for each Capability the Startup depends on. recoveryObjectives, inverse startup.
• A Startup has many Risks: the Risks scored for one Startup, open and closed. risks, inverse startup.
• A Startup runs many Systems: a Startup runs its work on headless Systems, such as CRM or billing, that every Startup shares. runs, inverse runBy.
• A Startup serves many Customers: a Startup serves every party that has accepted one of its Offers. serves, inverse servedBy.
• A Startup states many Hypotheses: a Startup states Hypotheses about itself, the Founding Hypothesis first, each settled by a Metric and a threshold. states, inverse statedBy.
• A Startup targets many ICPs: a Startup is built to win its ICPs; its Offers, Story and Plays compile toward them. targets, inverse targetedBy.
• A Startup has many Teams: a Team does its one kind of work for every Startup it serves; a Startup wakes a Team when its trigger Event happens. teams, inverse serves.

LifecycleCopy Anchor Link

VerbsCopy Anchor Link

1. createCreates a Startup.
   POST /{namespace}/startupsdoStartup.created
2. getReturns one Startup by id.
   GET /{namespace}/startups/{id}readNo Event
3. listReturns Startups, newest first, one page at a time.
   GET /{namespace}/startupsreadNo Event
4. updateChanges the given properties of a Startup.
   PATCH /{namespace}/startups/{id}doStartup.updated
5. deleteDeletes a Startup; its history is kept.
   DELETE /{namespace}/startups/{id}doStartup.deleted
6. advanceAdvance moves a Startup to its next Lifecycle state once every entry check of that state passes.
   POST /{namespace}/startups/{startup}/advancedoStartup.advanced
7. buildBuild provisions the Systems, Sites and Interfaces a Startup’s definition declares, and moves the Startup to Building.
   POST /{namespace}/startups/{startup}/builddoStartup.built
8. claimClaim binds a provisional Startup to a verified owner, which enables payments and every Verb that moves money.
   POST /{namespace}/startups/{startup}/claimdoStartup.claimed
9. cloneClone copies a Startup’s definition into a new Startup once, with no link back to the source.
   POST /{namespace}/startups/{startup}/clonedoStartup.cloned
10. graduateGraduate moves a Startup to a Company of its own, with its Customers, Domains and records intact.
    POST /{namespace}/startups/{startup}/graduatedoStartup.graduated
11. holdHold keeps a Startup running in its current Lifecycle state with no new investment from the Studio.
    POST /{namespace}/startups/{startup}/holddoStartup.held
12. importImport builds a new Startup from an existing business’s definition: its Offers, Pages, Nouns and Processes.
    POST /{namespace}/startups/importdoStartup.imported
13. launchLaunch puts a Startup live on its domain, serving its Offers to Customers.
    POST /{namespace}/startups/{startup}/launchdoStartup.launched
14. pausePause moves a Startup to Dormant: its scheduled Workflows stop, and its Sites and records stay in place.
    POST /{namespace}/startups/{startup}/pausedoStartup.paused
15. pivotPivot records a Decision that moves a Live Startup back to Building under a new Founding Hypothesis version.
    POST /{namespace}/startups/{startup}/pivotdoStartup.pivoted
16. readRead compiles a Startup’s records into one scoped room, such as a diligence room, with every number citing its Proof.
    POST /{namespace}/startups/{startup}/readdoStartup.read
17. resumeResume returns a Dormant Startup to the Lifecycle state it held when it paused.
    POST /{namespace}/startups/{startup}/resumedoStartup.resumed
18. sellSell transfers a Startup, with its Customers, Domains and records, to a buyer under a signed Agreement.
    POST /{namespace}/startups/{startup}/selldoStartup.sold

PermissionsCopy Anchor Link

Which Access level may call each Verb. One-way Verbs wait their delay window.

Call itCopy Anchor Link

Launch QuietCopy.

ExampleCopy Anchor Link

A debt-recovery Startup shares its holding Company with two siblings. It keeps its own Customers, Offers and P&L, so Startup.sell transfers it to a buyer without touching the other two.