What Rolls-Royce figured out in 1962

In 1962, airlines didn't want to buy jet engines. The engines were fine. The business model was the problem — millions of dollars upfront, specialized maintenance the airline couldn't do itself, and if the engine failed, they were grounded until Rolls-Royce fixed it. The buyer carried all the risk.

Rolls-Royce stopped selling engines and started selling thrust. Pay per flight hour. Rolls-Royce retains ownership, handles maintenance, guarantees uptime. The airline's cost becomes predictable. Rolls-Royce's incentive shifts from "sell more engines" to "make engines that don't break." Today every major engine OEM uses this model. The U.S. Navy has a $66M contract on these terms.

The manufacturing parallel

Contract manufacturing today has the same structural problem. Risk is shared on paper — contracts have chargebacks, warranties, shared liability. But in practice, when a quality question arises, the factory's cash flow freezes while the OEM's is unaffected. The contractual risk-sharing is symmetric. The cash flow impact is not.

What Rolls-Royce understood is that when you price by outcome instead of asset, incentives align. The airline doesn't care about the engine — they care about flight hours. The OEM doesn't care about "a production run." They care about validated units that meet spec.

Per-service settlement

At Fairbuild, each manufacturing service — EVT, DVT, PVT, mass production — is a discrete order with its own escrow and acceptance criteria. The OEM deposits payment before work begins. The factory knows the money is committed.

An independent verification layer — and this is the hardest part of the system — checks the test artifacts against the agreed spec. It needs to understand what a passing MTF measurement looks like, how to distinguish process drift from noise, whether a failure mode is systematic or a one-off. This is where 20 years of building the test equipment itself matters — knowing which measurements to trust and which to flag.

If the work passes and the OEM doesn't object within 48 hours, payment releases automatically. If they object, deterministic re-inspection resolves within 96 hours. Bounded, not open-ended.

Where the analogy breaks

The analogy has limits. Rolls-Royce owns the engine and controls the entire lifecycle. Manufacturing is fragmented — the OEM designs the product, the factory builds it, neither controls the other's process. Flight hours are continuous and easy to meter. Manufacturing services are discrete and complex to verify.

There's also design-flaw risk: what if the factory can't hit the MTF spec because the OEM's design is fundamentally unmanufacturable? An automated verification layer can't adjudicate that — it requires engineering judgment outside the system. This is a real boundary.

Within that boundary, a neutral verification layer still matters. In Rolls-Royce's model, trust comes from ownership. In manufacturing, neither side owns the other's process, so trust has to come from verifiable proof — shared, tamper-proof, independently attested.

It's not as elegant as vertical integration. But for a structurally fragmented industry, it's the closest equivalent to what Rolls-Royce achieved: pricing by verified outcome, with automatic settlement.