Shared Savings Contract Design: How to Structure Fees, Baselines, and Verification

A shared savings contract is not just a fee agreement. It is the operating system for a performance-based consulting engagement: what counts as savings, how the baseline is set, who verifies the result, when fees are paid, and what happens when the numbers are ambiguous.

Get the contract design wrong and the model creates friction. Get it right and both sides can focus on the only thing that matters: finding recoverable margin, implementing the fix, and proving the result.

This guide explains how a buyer should structure a shared savings consulting contract before work begins.

The Short Answer

A good shared savings contract pays the consultant only for verified, sustained savings measured against an agreed baseline. It should define:

• the baseline cost position before intervention
• the categories of savings that are eligible for fee calculation
• exclusions that prevent double-counting or accidental windfalls
• the measurement period and verification data
• the consultant’s implementation responsibilities
• the fee percentage and payment timing
• governance, sign-off, and dispute handling

The contract should not reward presentations, recommendations, modelled benefits, or accounting changes that do not reduce the operating cost base.

1. Start With the Baseline

The baseline is the most important clause in the contract. Without it, there is no objective way to know whether savings were created.

A baseline should document the current cost of the process, function, supplier, workflow, or operating area being improved. Depending on the engagement, that may include:

• monthly supplier spend
• labour hours by task or function
• overtime, rework, and exception-handling cost
• unit cost per order, job, shipment, claim, or transaction
• inventory carrying cost or write-offs
• system, licence, freight, or procurement cost
• service-level or quality measures that must not deteriorate

The baseline should be conservative. Inflating it may make the opportunity look larger, but it damages trust and creates arguments later. A serious shared savings consultant should prefer a baseline both parties can defend.

2. Define Eligible Savings Precisely

Not every financial improvement should trigger a shared savings fee. The contract needs a tight definition of eligible savings.

Eligible savings are usually recurring reductions in the cost required to deliver the same or better operational outcome. Examples include:

• reduced supplier cost for the same service level
• lower rework, waste, freight leakage, or exception handling
• reduced manual labour through workflow redesign or automation
• removal of duplicate systems or process steps
• better scheduling, utilisation, or throughput without quality loss
• lower inventory leakage or stock-holding cost

The key test is causality: did the consultant’s work create the saving, and can the saving be measured against the agreed baseline?

3. Write Down the Exclusions

Exclusions protect both parties. They stop the buyer from paying for savings that were not created by the engagement, and they stop the consultant from being blamed for unrelated business changes.

Common exclusions include:

• savings already identified or under implementation before the engagement
• accounting reclassifications with no operational change
• revenue growth or margin expansion caused by price increases alone
• benefits caused by volume decline rather than efficiency improvement
• supplier rebates or credits already negotiated before the engagement
• one-off timing differences that do not reduce ongoing cost
• headcount reductions unless explicitly included in scope
• savings that reduce service quality, safety, compliance, or customer outcomes

This is where many weak performance-fee contracts fail. If exclusions are vague, every month-end review becomes a negotiation.

4. Separate Diagnosis From Implementation

A genuine shared savings model should pay for implemented results, not ideas.

The contract should specify whether the consultant is responsible for:

• diagnosing opportunities only
• designing fixes
• implementing changes with the client’s team
• negotiating suppliers
• configuring systems and workflows
• training managers and operators
• monitoring adoption after go-live

The more implementation responsibility the consultant carries, the stronger the case for a meaningful share of savings. If the consultant only diagnoses and the client’s team does the hard delivery work, the fee structure should reflect that reduced risk.

5. Use a Verification Method Both Sides Can Audit

Verification should be boring, repeatable, and data-led.

Useful evidence sources include:

• supplier invoices and purchase orders
• payroll and rostering data
• ERP, CRM, WMS, TMS, or finance-system exports
• production volumes and unit-cost reports
• freight, inventory, and claims data
• agreed management-account categories
• before-and-after process metrics

The contract should also state how the calculation adjusts for variables outside the consultant’s control: volume changes, seasonality, inflation, input price movements, acquisitions, divestments, and changes in service mix.

A simple rule: if a finance leader cannot reproduce the calculation from source data, the verification method is not clear enough.

6. Choose the Fee Percentage and Payment Timing

Shared savings fees often sit between 25% and 50% of verified savings, but the right percentage depends on risk, responsibility, and whether the percentage is flat or tapered by savings tranche.

In cost-reduction consulting, a flat 50% of first-year savings is a common comparator when the consultant works entirely at risk. A tapered model can also make sense: a higher share on the first tranche of verified savings, then lower percentages as total savings grow so large wins do not create sticker shock.

A higher percentage may be justified when:

• the consultant takes no upfront fee
• the opportunity is hard to diagnose
• implementation risk is high
• savings take months to prove
• the consultant is accountable for delivery, not just advice

A lower percentage may be appropriate when:

• the client has already identified the opportunity
• the consultant is providing narrow specialist support
• implementation is mostly internal
• the savings are simple procurement wins
• the buyer pays a partial retainer or project fee

Payment timing should follow verification. For recurring savings, contracts often use monthly or quarterly true-ups after savings are confirmed.

7. Build Governance Into the Contract

Shared savings engagements fail when governance is informal. The contract should define a practical operating rhythm:

• weekly delivery reviews during implementation
• monthly savings-log updates
• named client owner and consultant owner
• finance sign-off on baseline and savings calculations
• decision rights for scope changes
• a dispute-resolution path for contested savings

This does not need to be bureaucratic. It does need to be explicit. The point is to prevent a successful operational improvement from becoming a commercial argument.

8. Protect Against Bad Incentives

Performance-based fees can create bad incentives if the contract is loose. A strong shared savings contract should make it impossible to earn a fee by damaging the business.

Add protections such as:

• no fee on savings that reduce safety, compliance, or customer outcomes
• no fee on deferred maintenance that creates future cost
• no fee on supplier changes that materially increase operational risk
• no fee on cuts that simply shift work to another overloaded team
• clawback or adjustment if savings reverse inside the measurement period

The best contracts reward durable operating improvement, not short-term cost suppression.

9. Link Contract Design to the Buyer Question

If you are evaluating consultants who specialise in shared savings contract design, ask five questions before you sign:

1. How will you set the baseline?
2. What savings will be excluded?
3. What data will verify the result?
4. What implementation work are you personally accountable for?
5. What happens if savings are disputed or do not sustain?

A consultant who cannot answer those questions clearly is not ready to work on a true shared savings basis.

Bottom Line

Shared savings contract design is about alignment. The buyer should pay only for verified operational improvement. The consultant should be rewarded for finding, fixing, and sustaining savings. The contract’s job is to make that alignment measurable.

TightShip uses this model because it removes the usual consulting tension: you should not pay for advice unless it turns into verified margin improvement.

Related reading:

• What is a shared savings consulting model?
• Shared savings vs day-rate consulting
• How to find operational leakage: a 5-step audit