Most professional-services contracts pad the scope with low-confidence work to absorb risk. We unwound the padding by binding scope at the Epic level and tying payment to acceptance. Here is what changed.

The padding problem

The standard consulting model rewards padding. The contract specifies stories or tasks; the consultant adds buffer to each to cover risk; the client pays for the buffer whether or not it is consumed. Both parties know this is happening and both treat it as the cost of doing business.

It also misaligns incentives. The consultant is paid for activity, not outcome. The client is buying time, not value. Everyone leaves the engagement having transacted but having created less than the contract suggested.

What we changed

Three things.

Scope at the Epic level.

An Epic is a unit of business value — the smallest scope that earns its own outcome. We commit Epics, not stories. The stories and tasks inside an Epic live with the team and can move during delivery, provided the outcome holds.

Value-based pricing.

The fee is tied to the outcome. Time-and-materials is available, but we ask for it expressly when we use it — and most engagements do not.

30 / 30 / 30 / 10 milestones.

Four milestones: kickoff (30), mid-engagement (30), pre-handover (30), acceptance (10). The final ten percent is the lever. It cannot be claimed until the client accepts the deliverables. The acceptance month becomes about handover and knowledge transfer rather than chasing the close.

The padding was buying risk absorption. We exchanged it for explicit risk allocation.

What it took to get here

Two operational changes:

  • The team commits. Senior Principals and Principals stand behind the Epic commitments. If we cannot, we say so before signing.
  • Acceptance is defined in writing. Each Deliverable has acceptance criteria agreed during the Epic's planning. No criteria, no Deliverable.

What surprised us

Three things, over a year of running this model:

  • Clients liked the explicit risk allocation more than we expected. A few preferred T&M for unfamiliar reasons; most preferred the outcome commitment once they saw it written down.
  • The acceptance month became real work. Documentation, runbooks, walkthroughs, knowledge transfer — all the things that get skipped when the final invoice is due before the closing happens.
  • Renewals tracked outcome quality more than rapport. That is healthier than the alternative.

Where it does not work

Discovery engagements with a genuinely unknown scope. We use T&M for these explicitly. Also: very small engagements, where the overhead of the Epic-level structure is not worth the discipline.

Closing

This is not a magic pricing model. It is a deliberate exchange — less buffer for more explicit risk allocation, more outcome commitment for narrower scope flexibility, lower invoicing comfort during the work for cleaner acceptance at the end. The exchange is worth it.