Skip to content

Sell a Service

Choose how buyers pay for the work, what the price counts and when it is collected, and what a buyer's agent reads before it orders.

A Service sells through Offers whose shape matches how the buyer already pays for this kind of work. The price counts what the Service's checks can prove, and nothing earns before the buyer accepts.

How buyers pay

ShapeThe buyer paysEach purchase is
PackageA fixed price for a fixed scopeOne Order
RetainerMonthly, for a set amount of workA Subscription, with an Order per delivery
Per deliveryEach accepted deliveryAn Order per delivery, billed on acceptance
Scoped quoteA price set for this jobA Quote, accepted into an Order
Booked sessionA slot on the calendarAn Order held to a time

How customers buy a service covers each shape with its bound.

What the price counts

An Offer's basis names what its price counts: access, effort, usage, output or outcome. The Service's assurance caps it, because a price on an outcome needs a check that measures the outcome.

Assurance of the weakest checkHighest basis
declaredeffort
estimated, sampledusage
graded, attestedoutput
measured, confirmedoutcome

Catalogmend's checks are graded, so it prices per listing fixed, an output. It cannot price per sale the fixed listings bring in, because no check measures that before the fee is earned.

When it is collected

payment separates collecting from earning: onEarn, deposit, prepaid or milestones. A deposit Offer collects its depositShare at the order. Revenue still posts only on the Event the contract earns names.

What a buyer's agent reads

A buyer's agent reads the Offer and its contract as data: done, the window, revisions and the remedy. It asks in the try Mode whether the Service covers its input, then orders inside its Mandate. An Offer listed for agent buyers needs graded checks or an Evaluator that accepts, so a buyer's agent never pays for work nobody checked.

Selling to agents shows a buyer's agent subscribing end to end.