AI-delivered Services: you pay for the outcome you accept

The reference for every call on this page is Compose your own.

A Service bills the outcome, never the effort

A Service promises the outcome under an Outcome Contract. Where done lives draws the line. An agent task is graded on its output. A Service holds the work until the outcome arrives.

The warranty test decides which you are buying. A first email is graded work. A held meeting with a budget owner is an outcome. Each Service names its done Event and its price per accepted unit. It also names what is credited, and the remedy for a short month.

Term	What it settles	Booked first calls
Done	The Event that counts one unit	A held first call at an account that fits your customer sentence, with a person whose title matches, and a budget owner confirmed on the call. Counted by `Meeting.held`.
Billed	What one accepted unit costs	$90 a held meeting
Target	What the month owes	12 held meetings a month, fixed when you order.
Credited	What is never billed	No-shows, and any meeting you disqualify within 48 hours with a reason.
Remedy	What happens on a short month	Continued work at no charge until the target is met: more lists, more first touches and more follow-ups, inside the same sending limits.
Evaluator	Who decides done	Code reads `Meeting.held` from the calendar and checks the account and title against your sentence; you confirm the budget owner.

Each Service warrants an outcome you can count

Each is hub Services-as-Software. Agents do the work, and the contract names any step a person takes. Each is built from the agent tasks and Workflows it orders, in your own accounts.

Demand generation deepens the Capability demand-generation. It runs your strategy's Plays and reads revenue back to each one. Sales closing deepens sales-closing. A commissioned closer takes a qualified lead to a signed order.

Service	Done when	Billed	Built from	Plays that order it
Ranked page	The page ranks in the top 20 on Google Search for its term, in its locale, within 120 days of going live.	$25 a ranked page	Keyword opportunity map, Answer page per question, Index the site	Answer engine optimization, Category hubs, Editorial SEO, Programmatic SEO, Switch kit
Sales closing	A signed order from a qualified lead you handed over, its first payment collected and past the 30-day refund window.	$268.20 a signed order on the $1,788 plan	Account brief, Inbound routing	Closer handoff, Data residency, Paid pilot, Risk-reversal offers, Trust pack, Written references
Booked first calls	A held first call at an account that fits your customer sentence, with a person whose title matches, and a budget owner confirmed on the call.	$90 a held meeting	Build a verified list, Personal first touch, Answer every inbound, Account brief	Benchmark rows, Cold email, LinkedIn outbound, Proof-of-work outreach, Warm intros
Demand generation	A qualified lead: a person at an account that fits, whose title matches, who asked for a call or a trial, with the Play that sourced it recorded.	$40 a qualified lead	Personal first touch, Answer threads, Directory submissions, Answer every inbound, Inbound routing, Weekly readout	Cold email, Community answers, Directory listings, Launch sites, Warm intros
Verified list with a bounce warranty	A contact at an account that fits, at the right company, whose address checks valid and does not push the list past 2% bounces at first send.	4¢ a contact	Build a verified list	Account ads, Buying committee, Cold email, Show up in person

A person performs a step in Sales closing and Booked first calls, because the stakes are high; every other step is an agent's or code's.

One worked month, billed per held meeting

November, Leaseline’s first full month, ordered at a target of 12. 12 meetings were booked, 10 were held, and 9 were accepted, so the month bills 9 × $90 = $810.

The 2 no-shows and the 1 meeting you disqualified bill nothing. The target was 12, so the work continues into the next month at no charge until 3 more are held.

Two warmed inboxes at 25 a day send about 1,000 first emails in 20 weekdays. Then 3.4% reply, 4 in 7 replies are positive, and 60% of those book. Planning estimate.

Each step names its doer and its checker

Each step is a Verb that runs as a Function: code, agentic or human. The doer is never the checker. Each checker names what it reads, and the weakest check sets the assurance.

Booked first calls runs these steps each month. A review pass is the checker of the step it reviews, never a row of its own.

Step	Function	Doer	Checker	Assurance
1. Build the month’s lists	`code`	Code	Code reads each address’s check result and its domain against the account’s own before the row joins	`measured`
2. Write and send personal first touches	`agentic`	The SDR agent	A second model checks every fact in each message against the row before it sends	`graded`
3. Answer every reply within 5 minutes	`agentic`	The SDR agent	A `Lead.created` read-back for every routed reply, timed from the reply	`measured`
4. Book the call	`code`	Code	A `Meeting.booked` read-back from both calendars	`measured`
5. Brief you before each call	`agentic`	The AE agent	A second model checks each fact in the brief against its source	`graded`
6. Read who attended	`code`	Code	The calendar’s attendance and the conference join log, read 15 minutes after the slot	`measured`
7. You confirm the budget owner on the call	`human`	You, on the call	Code reads your qualification back onto the lead; silence for 48 hours accepts the meeting	`attested`

A person steps in where stakes are high

Oversight is the review the work needs, set by what the work is. The hub names five postures on oversight. Each above none names its reason: regulatory, high-stakes, physical or consumer-harm.

Two Services are performs-step for high-stakes. You take each first call in Booked first calls. A commissioned closer gets each signature in Sales closing. A capability gap is never a reason.

You see the plan and its price before anything runs. Sends and posts go out within the limits you set; one approval rule on a class such as send makes every action in it wait for you, and going over a limit always asks. Your rules and limits together are a standing approval (a Mandate, set with Mandate.authorize).

Posture	What the reviewing party does
`none`	Nothing beyond automated review
`spot-check`	Samples finished work after delivery
`review-on-exception`	Reviews what an Evaluator or a Guard flags
`approves`	Approves each output before it is delivered
`performs-step`	Does one step in person

You pay only for outcomes you accept

A Service bills only accepted units. You accept each one, or its window closes with no dispute. An agent's own claim of done never bills.

A month short of its target gets continued work at no charge until the target is met. A unit that fails after delivery is credited, such as a bounce past the allowance.

Each Service's card prices the calls inside it, so you see what the agents spent beside your bill. Composition on the hub covers how cost and remedy roll up.

Order one in one call

The Service's own Verb is the short form of Order.place on its fixed offer. Both return the same order, and you watch its Events either way.

TypeScript

import { $ } from 'startup-builder'

// The Service Verb: the plan and its price, in try mode
const plan = await $.try.Meeting.deliver({ icp: 'US property managers with 20 to 400 units', titles: ['Director of Operations', 'COO'], target: 12 })

// The same order, placed on its fixed Offer: billed per held meeting you accept
const order = await $.Order.place({ offer: 'offers/booked-first-calls', quantity: 12 })

// Count what the month delivered
on.Meeting.held((meeting) => console.log(meeting.account, meeting.budgetOwner))

Plays order Services, and read their done Event

A Play orders a Service, then reads its done Event against the Play's Metric. Cold email orders Booked first calls and counts Meeting.held. Closer handoff orders Sales closing and counts Order.paid.

When the Metric stalls, the Play's agent changes the order, never the contract. It narrows the list, tests a new first line, or switches Plays.

A Service bills the outcome, never the effortCopy Anchor Link

Each Service warrants an outcome you can countCopy Anchor Link

One worked month, billed per held meetingCopy Anchor Link

Each step names its doer and its checkerCopy Anchor Link

A person steps in where stakes are highCopy Anchor Link

You pay only for outcomes you acceptCopy Anchor Link

Order one in one callCopy Anchor Link

Plays order Services, and read their done EventCopy Anchor Link

Contents