ServiceBuilder
ServiceBuilder builds the service Products a Startup sells, delivered by Agents.
ServiceBuilder turns a promised result into a Service a Startup can sell, deliver, and get paid for. Agents do the work by default, and credentialed people join only where the promise or the law needs them.
What it does
ServiceBuilder reads the Outcome Contract on an Offer and builds everything the promise needs. Five terms in, a working delivery line out:
- Delivery. Each step of the work is a Verb on the Order, run by code, a model, an Agent, or a Human. The Customer sees one status whoever runs it.
- Assurance. Evaluators grade every delivery before the Customer sees it. Failed work goes back for another pass at no cost.
- Acceptance and earnings. Delivery opens an acceptance window. The fee is held until the Customer confirms or the window closes, then it is earned.
- Remedy and disputes. A miss runs the remedy the contract names. A contested result becomes a Dispute with Evidence, a decision, and one appeal.
- Supply. Where people do the work, ServiceBuilder recruits Suppliers, verifies their Credentials, dispatches work, and pays them out.
- The legal floor. Every Reserved Act goes to a credentialed Human, whose Attestation travels with the work.
Built from
Surfaces
- The Customer's Portal on the Startup's Site: Orders, delivered work with its evidence, and the open acceptance window.
- The supplier App: eligible work, Credentials on file, and earnings, on a phone.
- startups.studio: the ServiceBuilder area holds every Order in delivery, the Tasks waiting on people, open Disputes, and pending Approvals.
- api.sb: every delivery Verb under one name on every Interface, so a buyer's Agent orders, tracks, and accepts work the way a person does.
Order.deliver- API
POST /{namespace}/orders/{order}/deliver- SDK
$.Order.deliver(input)- CLI
startup-builder do Order.deliver --json '<input>'- MCP
do: $.Order.deliver(input)
| Term | Kind | Definition |
|---|---|---|
| ServiceBuilder | Product | ServiceBuilder builds the service Products a Startup sells, delivered by Agents. |
| startups.new | Product | startups.new creates a Startup from one sentence and opens it in startups.studio. |
| Customer Team | Team | The Customer Team serves every Customer after the first acceptance: onboarding, support, retention, and the one Thread each Person has. |
| Finance Team | Team | The Finance Team moves and records the money: Invoices, dunning, refunds within a Limit, payouts, the monthly close, tax, and runway. |
| 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. |
| Operations Team | Team | The Operations Team runs the Startup day to day: it delivers outcomes, keeps human supply booked, stops abuse, and runs the Monday Role review. |
| 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. |
| 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. |
| Live | Lifecycle state | Live is the state of a Startup that is publicly reachable and takes money from Customers for at least one Offer. |
| Repeatable | Lifecycle state | Repeatable is the state of a Startup whose Customers arrive, pay, and stay, while its work runs without its founder. |
| 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. |
| 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. |
| E2E managed service | Product Template | An E2E managed service runs a whole business function for the Customer, with Agents doing the work and Humans in the loop. |
| Licensed-human marketplace | Product Template | A Licensed-human marketplace matches buyers with credentialed professionals and adds recruiting, Credential checks, and an App where they take work. |
| Marketplace | Product Template | A Marketplace matches buyers with Suppliers who deal with each other directly, and earns a take rate on every transaction it settles. |
| Services-as-Software | Product Template | Services-as-Software sells a warranted outcome that Agents deliver end to end under an Outcome Contract, billed only once accepted. |
| Agreements | System | Agreements drafts each Agreement between two or more Parties from Templates, routes it for signature, records who signed, and tracks its term and economics. |
| Compliance | System | Compliance maps controls to frameworks, tests each from the records every Action leaves, and publishes the trust center buyers read. |
| Credentialing | System | Credentialing verifies each Supplier’s Credentials with the issuer, tracks expiry, and decides who may perform a Reserved Act. |
| Dispatch | System | Dispatch proposes each job to eligible, available Suppliers, books shifts, and proposes it again on decline before the deadline. |
| Earnings | System | Earnings pays Suppliers, Partners and affiliates their earnings through Stripe, holds disputed amounts, and sends statements and year-end tax filings. |
| Evals | System | Evals grades outputs with versioned Evaluators, gates every Change before merge, and keeps each Worker’s track record. |
| Knowledge base | System | Knowledge base holds the articles Customers and Agents answer from, in a searchable help center that cites every answer. |
| Matchmaking | System | Matchmaking pairs buyers with Suppliers’ Offers, records the merchant of record on each Order, and takes the Startup’s fee through Stripe. |
| Phone | System | Phone holds a Startup’s numbers and runs voice calls and SMS, with voice Agents, transcripts and handoff to a Human. |
| Scheduling | System | Scheduling books Meetings between Workers and Contacts from shared availability and keeps the notes, Decisions and Tasks they produce. |
| Service delivery | System | Service delivery runs each job to its Outcome Contract: steps, oversight per Verb, delivery, acceptance, remedy and proof. |
| Success | System | Success moves each Customer to value and keeps them: onboarding checklists, health scores, renewals, saves and win-backs. |
| Supplier onboarding | System | Supplier onboarding recruits Suppliers: applications, identity and background checks, tax details, Agreements and a first assignment. |
| Support | System | Support answers Conversations with Customers across email, chat and API, and links each reported bug or request to an Issue. |
| Trust and safety | System | Trust and safety screens accounts, posts and Transactions for fraud and abuse, and acts on each report by stated rules. |
| Delivery | Process | Delivery runs the Orders Customers place for Agent and Service outcomes, and bills only on confirmation. |
| Licensed review | Process | Licensed review puts a credentialed Human’s Attestation on every Reserved Act before it reaches a Customer. |
| Onboarding | Process | Onboarding gets every new Customer to first value, by hand until the Startup automates each step. |
| Retention | Process | Retention keeps Customers by catching silence early, saving once, and winning back once. |
| Screening | Process | Screening tags the legal floor of every Offer and withdraws any Offer the Startup cannot lawfully deliver. |
| Supply | Process | Supply keeps enough credentialed Suppliers booked to meet demand and suspends any whose Credential lapses. |
| Support | Process | Support answers every Conversation from the record in one Thread and fixes causes, not symptoms. |
| Bill on confirmation | Workflow | Bill on confirmation captures and bills each Service Order line the Customer confirms, as the Outcome Contract’s earns names. |
| Fan out an outcome | Workflow | Fan out an outcome turns one confirmed Customer outcome into a dated number, and with Consent into a case study, quote and referral invite. |
| Start the remedy | Workflow | Start the remedy holds the fee on a disputed Service Order and runs the Outcome Contract’s remedy: redo, refund, or credit. |
| Attestation | Noun | An Attestation is the signed, frozen act by which a credentialed Worker performs or declines a Reserved Act. |
| 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. |
| Conversation | Noun | A Conversation is a Thread with one or more Contacts that a Worker must answer, such as a support request. |
| Credential | Noun | A Credential is a standing authority a regulator grants a person or entity to perform certain acts in a jurisdiction. |
| Dispute | Noun | A Dispute is a contested payment or delivery, such as a chargeback, a rejected Service outcome, or a buyer’s claim against a Supplier. |
| Evaluator | Noun | An Evaluator is a versioned Function that grades an output against a rubric and returns a verdict. |
| Human | Noun | A Human is a Worker who is a person, acting on Tasks through Apps, Mailboxes, and Channels. |
| Incident | Noun | An Incident is an Issue where an Interface or Site fails Customers in production, tracked from detection to postmortem. |
| Issue | Noun | An Issue is a Task reporting a problem or request, such as a bug or a feature request, with a reporter and a triage step. |
| Outcome Contract | Noun | An Outcome Contract is the terms on an Offer that warrant a Service’s result: done, acceptance, assurance, remedy, and earnings. |
| Product Template | Noun | A Product Template is a reusable definition of one kind of Product: what it sells, who supplies the work, who buys, and how it earns. |
| Reserved Act | Noun | A Reserved Act is a Verb the law reserves to the holder of a named Credential, so its Function is always human. |
| Service | Noun | A Service is a Product that warrants an outcome, delivered by Agents and Humans under an Outcome Contract. |
| Source | Noun | A Source is something a Product draws on to keep its promise but did not build: owned, wrapped, or recruited. |
| Supplier | Noun | A Supplier is a Person or Company that delivers work through a Startup’s human supply: recruited, credentialed, and paid out. |
| Action.attest | Verb | Attest records a credentialed Human’s signed performance of a Reserved Act that an Action needs to finish. |
| Credential.verify | Verb | Verify confirms a Credential with the authority that issued it and records when it expires. |
| Dispute.answer | Verb | Answer submits the seller’s Evidence on an open Dispute before its deadline: the contract, the delivered work, and its verdicts. |
| Dispute.appeal | Verb | Appeal asks for one review of a decided Dispute by a Worker who took no part in the first decision. |
| Dispute.decide | Verb | Decide rules on an answered Dispute for the buyer, the seller, or a split, and releases or returns the held amount. |
| Human.hold | Verb | Hold sets aside part of a supplying Human’s earned balance against an open Dispute or an Order inside its clearance period. |
| Human.onboard | Verb | Onboard admits a recruited Human to supply work once their identity, Credentials and payout details verify. |
| Human.recruit | Verb | Recruit invites a person to supply credentialed work to a Startup through its supply App. |
| Human.release | Verb | Release frees a held amount for payout once its Dispute closes or its clearance period ends. |
| Human.remit | Verb | Remit pays a supplying Human’s earned balance to their bank account through the Startup’s payment account. |
| Human.suspend | Verb | Suspend stops a supplying Human from taking new Tasks while a Credential lapses or a dispute is open. |
| Order.confirm | Verb | Confirm records the Customer’s sign-off on delivered work, which closes the Order and earns the Startup its fee. |
| Order.deliver | Verb | Deliver hands the finished work of a Service Order to its Customer and opens the acceptance window. |
| Order.dispute | Verb | Dispute contests a delivered Order under its Outcome Contract and starts the remedy the contract names. |
| Order.place | Verb | Place commits a Customer to buy an Offer once and records the Offer Version and price at that moment. |
| Order.revise | Verb | Revise sends delivered lines back for one counted revision, with the changes the Customer asks for. |
| Order.start | Verb | Start checks a Service Order’s inputs against its brief, then moves it from intake to working and starts its deadline. |
| Quote.decline | Verb | Decline records the buyer’s refusal of a sent Quote, with the reason in their words. |
| Quote.request | Verb | Request asks a Startup for terms on one or more Offers, with the volume, term or scope wanted. |
| Quote.send | Verb | Send presents a drafted Quote to its buyer and freezes its lines, total and payment terms. |
| Quote.supersede | Verb | Supersede replaces a sent Quote with a newer one on the same Deal; only the newest Quote can be accepted. |
Next steps
- Services: what a Service sells, and how it differs from Software and a Marketplace.
- Outcome contracts: the five terms every Service keeps.
- Delivery and acceptance: an Order from placed to earned.
- Services-as-Software: start from the Product Template.