Play and Service

Every Process that finds buyers is defined once. A Startup runs it as a Play with its own seated Workers, or buys it as a Service from a sibling that sells the outcome.

One Process, three usesCopy Anchor Link

Five of these Processes run on data: signal-led outbound, search and answer share, paid tests on Offers, generated video, and owned-account engagement. Each states its steps, the Metric it moves, its cost, and which acts are one-way. Three parties use that one definition.

The definition stays the same in every use. Only who is seated, who is billed, and what counts as done change.

Running it as a PlayCopy Anchor Link

A seated Worker is a member of the Startup's team. It acts under the Startup's Permissions, Mandate, and Limits, keeps the Startup's Memory, and appears on its org chart. Its Actions are by that Startup, even when the Agent itself comes from the platform.

Take a directory of wheelchair-accessible vacation rentals with a $0 budget. Each week its marketing agent samples the questions travelers ask answer engines and finds the ones where another source is cited. It publishes a Page for each gap, stating one fact no other page has, and updates its directory listings without review.

A pitch to a travel writer is different: it reaches a person and cannot be taken back. So it waits the Startup's delay window for outbound sends, and any Human watching can stop it. Spend raises wait the same way; a pause never waits.

Ordering it as a ServiceCopy Anchor Link

A sibling Startup sells the same Process under an Outcome Contract on its Offer. The contract names an outcome unit and the query that accepts it. Acceptance is measured from the buyer's own records, not judged by the seller.

A Startup that sells commercial lease comparables to brokers orders signal-led outbound, priced per qualified meeting held. A meeting counts when a calendar event in the buyer's account has the Prospect attending for 15 minutes or more. No meeting, no fee.

The seller researches, writes, and targets outside the buyer's Roles, and never holds the buyer's keys. Each send, post, or spend raise arrives staged. The buyer's own seated Worker executes it under the buyer's Mandate, Limits, and delay window, so every pending send shows in the buyer's inbox.

That split keeps the line between seated and ordered exact. The outcome is ordered from a sibling; every one-way act is still the buyer's.

The seller prices each outcome from the Portfolio's measured cost and acceptance rate for that kind of buyer. The sample size shows beside the price.

price per accepted outcome = cost per attempt ÷ acceptance rate ÷ (1 − target margin)

Each rejected outcome carries a reason: wrong persona, not qualified, off brand, duplicate, suppressed, or a claim without a fact. Each reason becomes a test case for the Process's Evaluators, and the next version passes it before it runs.

Choosing between themCopy Anchor Link

Both uses write the same outcome rows. Every email, Page, ad, and post carries the run step that produced it, and each paid Order resolves back to that step. The Portfolio learns from every row, so a Play improves from the results of Services, and a Service prices from the results of Plays.

Memory never crosses. A seller cannot carry one buyer's contacts, replies, or creative to the next buyer; only aggregates reach other Startups. The seller's edge is execution at volume, not private data.

So each Startup decides per Process, and records the choice as a Decision. It compares its own Play's results with the best Service for its kind of buyer. Most Startups start with the Play at $0 and order the Service once it beats their own numbers.

When a specialist appearsCopy Anchor Link

Outcome rows also show where a seller has an edge. When a seller beats the generalist Play for one kind of buyer by a declared margin, the Studio drafts a specialist from a Product Template. The improved Process version ships back to every Play that serves that kind of buyer.

A sibling that makes short product videos for consumer apps holds attention past three seconds more often than the median cut. It becomes a creative lab Startup, and its hook rules become the default in the Video ladder Play for every sibling.

Conduct in either useCopy Anchor Link

Engagement through owned social accounts is its own Capability, separate from publishing and from ads. It answers questions in public first. A direct message goes only to a person who engaged, and it quotes that act.

Agents identify as agents on every account and in every message, whichever Startup seats them. On LinkedIn, person-to-person messages go only from a human's own account, under a Mandate that human grants. On X and Reddit, disclosed agent accounts answer as themselves.

Every claim cites a fact, and one suppression list binds every sibling. A Service follows the buyer's rules because the buyer's own Worker sends.

Five Processes, both usesCopy Anchor Link

NextCopy Anchor Link

• Demand budgets: how a Startup funds its mix of Plays.
• Outcome contracts: the five terms every Service states.
• Workers: who is seated in a Role.
• Demand Plays: every Play, rated and budgeted.