Prebuilt mandates
Each one has shipped before: a purpose-built agent, a fixed price, and acceptance criteria you can read right here. Open any card. No estimate round, no review cycle; a prebuilt mandate takes an open slot and starts.
Test coverage raised to the number you set on the ingest and dispatch paths.
From 18,000 · fixed
Acceptance criteria, as signed
Warranty 90 days · evidence pack on acceptance
Start via the probeAdvisories resolved, pinned, proven closed across carrier integrations.
From 16,000 · fixed
Acceptance criteria, as signed
Warranty 90 days · evidence pack on acceptance
Start via the probeIntermittent failures fixed and held green 30 days in the scheduling suite.
From 14,000 · fixed
Acceptance criteria, as signed
Warranty 90 days · evidence pack on acceptance
Start via the probeOne major version jump behind flags, zero regression on the TMS core.
From 22,000 · fixed
Acceptance criteria, as signed
Warranty 90 days · evidence pack on acceptance
Start via the probeTraces, dashboards and alerts, documented across yard and dock telemetry.
From 15,000 · fixed
Acceptance criteria, as signed
Warranty 90 days · evidence pack on acceptance
Start via the probeIdempotent, monitored, replayable ingest on shipment event ingest.
From 19,000 · fixed
Acceptance criteria, as signed
Warranty 90 days · evidence pack on acceptance
Start via the probeUnused paths removed with proof nothing broke in the dispatch console.
From 12,000 · fixed
Acceptance criteria, as signed
Warranty 90 days · evidence pack on acceptance
Start via the probePublic surface documented, versioned, enforced on the rating engine.
From 17,000 · fixed
Acceptance criteria, as signed
Warranty 90 days · evidence pack on acceptance
Start via the probePipeline cut to a signed wall-clock bar across partner EDI feeds.
From 16,000 · fixed
Acceptance criteria, as signed
Warranty 90 days · evidence pack on acceptance
Start via the probeEvery mandate below has shipped for a logistics operator. The examples name their systems, not ours.
New to the model? Read what a mandate is
Standing mandates
Someone in your company answers the insurance questionnaire and faces the auditor, and the evidence they need is engineering work nobody scheduled. A standing mandate fixes that: one named outcome delivered every month with proof, at a printed monthly price. That person is the buyer. Engineering is consulted, never sold.
Custody means the CVE queue is ours to hold: we watch it, we patch it, and we sign the proof. Your engineers stay on the product.
The probe report says whether custody fits your codebase, before any money moves.
New criticals fixed inside 7 days, zero at month close, with evidence.
Signed every month
Base
2,500 / month
Up to 5 repositories
Evidence
4,500 / month
Multi-repo, with the PCI and SOC 2 pack
The probe report says whether custody fits your codebase, before any money moves. Run the free probe →
The full page →The same custody, for the apps your team built
Someone on your team shipped a real internal app with Claude Code. Now the Monday meeting runs on it, and its builder became the support desk. App custody makes keeping it alive our job: a named owner, a timed restore every month, and evidence that it works.
The apps your own people built, kept alive and provably so, every month.
Signed every month
Watch
1,500 / month
Up to 3 apps
Base
2,500 / month
Up to 8 apps
Evidence
4,500 / month
Up to 20 apps, or any app touching customer or payment data, with the register written for an auditor
The census is the door: one 30-minute interview produces the register, one page per app, and the count. Free. Book the free census →
The full page →Where we say no
If we cannot write criteria you would sign, it is not a mandate yet. It becomes a paid diagnostic until it is.
Buying our time makes the risk yours again. We would rather lose the deal than sell the wrong unit.
Under 12,000 the review time costs more than the outcome earns. Small asks belong in a prebuilt mandate.
Agents scale; accountability does not. Every mandate ships under a senior who actually read it. We take what the gate can sign, and give the rest a date.
Bespoke mandates start the same way: the probe reads your codebase, Cambrian sizes the work into criteria and prices, and a senior engineer signs the estimate. If we cannot write criteria you would sign, we say so.