Services-as-Software
Services-as-Software sells a warranted outcome that Agents deliver end to end under an Outcome Contract, billed only once accepted.
The Customer pays for the result, never for hours.
The business
| Line | Default |
|---|---|
| Earns | usage |
| Typical Prices | $99 to $499 per accepted outcome |
| First revenue on | A Demand Budget of $100 |
| Supply | digital: Agents do the work |
| Motions | b2b, b2c, b2a2b |
| One metric per state | Idea: Problem interviews; Building: Committed ICP members; Live: Accepted outcomes; Repeatable: Month-3 retention; Scale: Net revenue retention |
| Seed Plays | Cold email, LinkedIn outbound, Reserve drop |
| Compounding Plays | Editorial SEO, Customer referrals, Answer engine optimization |
| Offer | Price | Features | Limits | At its bound | On sale |
|---|---|---|---|---|---|
One outcome (one-outcome) | $99 per outcome | None. | Order.place: 1 in all; Order.revise: 2 in all | stop | Always |
An Entitlement bounded by a Limit has kind limit; one without has kind feature. The kind is computed, never set.
atBound | A call past the Limit |
|---|---|
stop | Refused: the Verb replies 402 payment-required. |
Offer.publish puts each Offer on every buy surface: checkout, paymentLink, pricingTable, portalEntry, mcpBuyTool, http402.
Adds
| Kind | Item | From |
|---|---|---|
| Built from | Agent as a Service | This template |
| System | Service delivery | This template |
Wakes
Staffing
Floor
None.
Controls
- Worker competence
- Control wake review
- Control definition
- One-way Action windows
- Control sameness
- Adversarial control testing
- Namespace isolation
- Append-only records
- Change approval
- Agent definition evals
- Environment separation
- Input validation
- Action completion
- Outcome confirmation
Builders
Next
Example
A Startup sells app-store listings translated into 12 languages at $180 per app. The Outcome Contract defines done as every field translated within its character limit, and the Customer accepts before any charge.