Plans

Which plan does a Service like yours need? check reads it off your files, line by line. Every key runs on every plan in test, so you build the whole Service on Free. On Free, services.dev earns only when your Service gets paid, and there is no trial clock: each gated key runs three paid live jobs, however long they take.

$ npx services.dev check
services/translation.ts · 14 lines · $89 per job, within 48 hours, charged on file's receipt.
  plan    Launch (services.dev) · roles.translator.pool at services/translation.ts:6 · subject at :13 · clocks at :14
          every key runs in test on any plan · deploy --live asks for Launch
  take    your plan's take on each released charge · never on the translator's $30.00

check --fit free prints the rewrite that stays on Free: sign the act yourself, and leave out the subject and the clock. You can also answer it before you write a file. Each yes names the line that needs a plan, and your plan is the highest one any yes names:

Free sells finished work on your builder.domains address, with you and two staff as the only people. Launch adds your own domain, your own people, and work that recurs or is paid on its outcome. Team adds a market: tiers, a door of your own, and members paid a share of the win. Scale adds what a buyer's security review asks for.

Each reference Service, rung by rung: what it sells, who does the steps, and the run that prints its plan. Every rung is derived from the Service's own files.

# Free · four Services AI delivers alone, each at a price per job
#   who: AI delivers every job; nobody signs
#   sides: AI is the whole cost: no pay line, and the take sits on all of each price
# Launch · Translation, signed by a sworn translator from lingua's own Pool
#   who: up to five sworn translators sign, $30 an act
#   sides: a signed job leaves $59.00 of $89.00 after the translator's $30.00, and the take sits on the $59.00 alone

On Launch, a Pool's members come from three places, and only the Pool you own has a cap of five:

Past five members, rent a door's Pool and pay placement per Task, or open your own door on Team and pay none; the plan card shows which costs less. Time and outcome pricing need no market, so they sit here.

At a limit, the next member, tenant or region answers the same OFFER; nothing already running stops.

What keeps a reserved act lawful, a member paid and a refusal uncharged runs on every plan. A floor row names no number: your services.dev plan sets how many people you seat, never whether an act is lawful.

Each gated key runs three live jobs before your services.dev plan is asked for. A job counts when its charge releases, so the sample ends on money you were paid. Then deploy --live answers OFFER, with the plan, each key that needs it and the cure (take the first real job):

The gate reads each Service, not the folder. apis.tax sells transcripts on Free while its annual return's sample runs.

Each dollar of a released charge has one claimant. services.dev's take sits on one line: the value your brand adds.

you = charge − tax − processing − AI − pay − pass-through − coverage − placement − nested Services − services.dev's take

npx services.dev ledger --claims job_7Hq2   # lingua

job_7Hq2 · Translation, signed · $89.00 released on delivery
  line                  amount  claimant              services.dev's take
  The translator's pay  $30.00  the sworn translator  $0
  lingua's value added  $59.00  lingua                the take
  AI $0.84 comes out of lingua's line. The take sits on $59.00 and nowhere else.

The take applies only when a charge releases, reverses with it, and falls as your services.dev plan rises. A line leaves its base only with its proof, and check fails double_take when a definition would put two claims on one dollar.

A plan pays for itself once the take it saves passes its price: your month's take base, times the gap between the two takes, against the gap between the prices.

Each charge runs on behalf of your account, and each month's statement shows every dollar services.dev touched: your plan's Stripe subscription, the take withheld at each release, the debits made outside a charge, and on an outcome price the month's netting of lost cost, returned as one transfer on take.credited:

→ GET /owner/statements/stm_2026-11   # api.forsale: everything services.dev charged, withheld, debited and returned in November 2026
  plan       Launch · $— a month · services.dev's own Stripe subscription, billed to your card …4242 on 1 Nov
  withheld   the take on $10,200.00 of won bases · 3 charges released, each withheld as your share transferred · le_ per charge
  debits     $5,500.00 · py_… for setters, nurturers, placement and AI on the month's lost deals · each on its own deal's ledger
  netting    won bases $10,200.00 less lost cost $5,500.00 · the month's base $4,700.00, never below zero
  credited   take.credited · the take on $5,500.00, returned as one transfer, tr_…N26, to acct_…F0r5 on 1 Dec

The owner console prints the services.dev plan your files need, each key's sample, and what each key you wrote would have saved on your own jobs. Thirty days before a schedule would spend a sample, it offers plan.ahead, which your agent accepts within the ceiling. Buyers and members never see it.

→ GET /owner/plan   # the owner console's plan card, for a tax brand on Launch
← plan · Launch (services.dev) · your files need Team for 2 keys
  needs      Team · Pool.standby at pools/preparers.ts:32 · 3 of 3 sampled jobs released · new Tasks fill on the ladder
             Team · subject.of_record.custodian at services/annual-return.ts:31 · 1 of 3 sampled jobs released

Next: Money, every way a Service earns and pays, or the plans side by side on pricing.