§ 00 — Outcome as a Service

Buy the outcome. Not the hours.

Traditional IT services sell capacity and let you carry the risk that it adds up to something. We start from the number you need to move — and put part of our own fee behind it.

Risk transfer Who carries delivery risk
Staff augmentation 0% ours
Staff augmentation: 100% you
Time & materials 8% ours
Time & materials: 85% you, 15% shared
Fixed scope 40% ours
Fixed scope: 45% you, 30% shared, 25% us
Outcome as a Service 73% ours
Outcome as a Service: 15% you, 25% shared, 60% us
You carry Shared We carry

Schematic. Actual allocation is set per contract and written into the agreement before work begins.

500+ Projects delivered
130+ AI and data engagements
12+ Years in delivery
4.7/5 Average client rating

§ 01 — The model

Accountability for a number, not a timesheet

A conventional contract pays the vendor whether or not the number you cared about ever moves. This one starts from the business result, agrees how it will be measured, and settles against that reading.

What you buy Developers, hours, a scoped SOW One agreed business metric
Who carries the risk You, entirely Us, with fee at stake
What settles the invoice A status report A verified reading
Who owns the how You approve line items Our problem to solve
How an outcome is measured Schematic
100 TARGET BASELINE MEASURED WORK STARTS VERIFIED READING BASELINE DELIVERY VERIFY & SETTLE
Measured baseline Under contract

Schematic of the mechanism, indexed to a baseline of 100. Not client data.

§ 02 — What you can buy

Outcomes we take accountability for

Every one of these is a number with a direction. If we cannot baseline it, and you cannot verify it independently of us, we will not contract against it.

Reduce

Cost and margin

Cut the unit economics of a workload you already run.

Inference spend Cost to serve Cost per transaction

Reduce

Cycle time

Compress the elapsed time of a process that matters.

Underwriting Onboarding Claims Month-end close

Increase

Revenue and conversion

Move a commercial number in a funnel you already operate.

Conversion rate Attach rate Pipeline velocity

Reduce

Manual effort

Take defined human hours out of a repeatable process.

Hours returned per month Touches per case

Reduce

Risk exposure

Reduce measurable exposure, not documentation about it.

Audit findings closed Incidents per quarter MTTD

Increase

Reliability at scale

Hold an agreed service level while volume grows.

Availability Latency at p95 Throughput ceiling

§ 03 — How we are paid

How you pay, and what we put at risk

Three structures. The dial shows what is guaranteed to us, and what we only collect if the number moves.

Outcome Fee

Well-defined targets with a clean, agreed baseline.

Guaranteed At risk
How you pay
Fixed and milestone-weighted. The final tranche releases against the verified reading.
What we put at risk
30% of our fee, forfeited if the metric does not move.

Baseline plus Gainshare

Upside that is large but hard to predict in advance.

Guaranteed At risk Gainshare
How you pay
A reduced delivery rate, plus an agreed share of the value measured after go-live.
What we put at risk
Our delivery margin, exchanged for a share of the gain we help create.

Build, Operate, Transfer

Capability you ultimately want to own in-house.

Guaranteed At risk
How you pay
A monthly operating fee that steps down as your team takes over.
What we put at risk
Continuity to the agreed service level until transfer completes.

Illustrative proportions. Every model starts from an agreed baseline and an agreed measurement method, documented before work begins. No baseline, no outcome contract.

Bring us a number

Which structure fits? Start with the number.

Tell us the metric you need to move. We will tell you whether it can be baselined — and which of the three models we would put behind it.

§ 04 — The engagement

From a number you care about to a number that moved

Two of these six are measurement events — the only points where money is decided, both using a method agreed in writing before delivery starts.

  1. Outcome definition

    The single metric, the timeframe, and what counts as met. If it cannot be written down precisely, it is not ready to be an outcome contract.

  2. Baseline and instrumentation Measurement event

    We measure the current state from your systems before anything is built, and both sides sign off on the method.

  3. Joint business case

    We model what the movement is worth to you, and choose the commercial structure from that.

  4. Build and operate

    One accountable squad designs, ships and runs the system in production.

  5. Verified reading Measurement event

    The metric is read against the baseline by the agreed method. Terms settle on that reading, not on a status report.

  6. Scale or transfer

    Expand into the next outcome, or hand the running system and the operating knowledge to your team.

§ 05 — Against the alternatives

Where this sits against the models you already buy

Dimension Staff augmentation Time & materials Fixed scope Outcome as a Service
What you buy People Effort A deliverable A measurable result
Who owns the result You You Shared Us
You pay for Seats per month Hours logged An agreed scope The outcome, on agreed terms
When scope shifts Renegotiate headcount Billed as extra hours Change request, re-priced Absorbed — the target is fixed, the path is not
Our incentive Keep seats filled Log more hours Close the scope Move the number
Best when You know exactly what to build Discovery is genuinely open Requirements are frozen The result matters more than the method

We still sell the other three, and will say so when one of them fits you better. Outcome contracts are the wrong instrument for open-ended research, or for work with no measurable baseline.

What actually counts as an outcome?

Anything you can baseline and verify independently of us — cost per transaction, time to close, conversion rate, incidents per quarter, hours removed. If measuring it depends on our own reporting, it is not an outcome we will contract against.

What happens if the outcome is not achieved?

The contracted portion of our fee is not paid. That is the point of the model. The exact share, and any partial-attainment ladder, is agreed up front rather than argued about afterwards.

How do you stop the baseline being gamed?

The baseline is measured before work starts, from your systems, using a method both sides sign off on. Where it matters, we will accept a third party or your own audit team as the arbiter.

Is this not just fixed-price with extra steps?

No. Fixed price fixes the scope and bills for delivering it. This fixes the result and leaves the scope to us, which means we absorb the cost of changing approach when the first one does not work.

Who owns the IP?

You do, on the same terms as any of our delivery contracts. Outcome pricing changes how we are paid, not who owns what we build.

What size of engagement suits this?

Outcomes worth roughly $250k a year or more in measurable value. Below that the measurement and governance overhead costs more than the model returns, and we will recommend a conventional engagement instead.

§ 07 — Start

Start with one outcome.

Bring us the number you need to move. Within two weeks you will know whether it can be moved, what moving it is worth, and on what terms we would take it on.

Week 0

You bring the metric, the systems it lives in, and the timeframe.

Week 1

We test whether it can be baselined and verified independently of us.

Week 2

You get a target, a measurement method, and a commercial structure.