Contingency in a quote

Why every quote needs one

No estimate is perfect. A fiddly integration takes twice as long. A migration hits dirty data. A client needs one more round than you allowed. None of these are failures, they're the normal texture of project work, and they're exactly why experienced studios build in a buffer. A quote with no contingency is a quote betting that nothing will go wrong, which is a bet you lose often enough to hurt.

Contingency is what turns "we lost money on that one" into "that one had a few surprises, and we were fine". It's the difference between a fixed price you can stand behind and one you're quietly hoping holds.

How much: size it to the risk

Contingency isn't a fixed habit, it's a response to how much you don't know. Match it to the uncertainty in the specific job.

• ~10%, a clean, well-understood build with a tight scope and no novel parts.
• ~15%, some moving parts: a couple of integrations, moderate content migration, a new client.
• 20%+, real risk: complex migrations, unproven third-party APIs, a vague brief, or a client

you can't yet read.

If a project has so many unknowns that no honest contingency feels safe, that's a signal to scope it better first, ideally with a paid discovery phase, rather than to guess a bigger buffer. The best contingency is a smaller scope of unknowns.

Hide it or name it?

Both are legitimate; it depends on the client and the model.

• Inside the number (fixed price). On a fixed-price quote, contingency usually sits within the

total. The client is buying a defined outcome for a defined price; how you arrived at the figure is your business, and the buffer is simply prudent pricing.

• As a named line (open or larger engagements). On bigger or more collaborative projects, a

visible "contingency / risk allowance" line can build trust, it signals you're planning for reality, and on some engagements any unused portion is returned.

What you should never do is add contingency and then feel guilty and discount it away under pressure. It isn't padding, it's the price of the risk you're carrying on the client's behalf.

Word it so it holds

If you name contingency, be clear about what it's for, so it isn't mistaken for a slush fund or a licence to expand scope.

Contingency: this quote includes a 15% contingency to cover reasonable unknowns within the agreed scope, for example, additional testing or integration effort. It does not cover new work outside the scope, which is handled through change control.

That last sentence is the important one. Contingency covers surprises inside the agreed scope. It is not a budget for change requests, which are new scope and priced separately. Keeping that line clear stops contingency from silently absorbing scope creep.

Contingency vs a quote range

Contingency and a quote range solve related problems from different ends. A range communicates uncertainty to the client before the scope is firm. Contingency absorbs uncertainty for you once you've committed to a number. Early on you might quote a range; as the scope firms up, the range collapses to a fixed figure with contingency baked in.