Nov 19, 2026
Fixed Price Is Insurance: What the Premium Covers and When It’s Worth Paying
What a fixed price costs you, when it is the right tool, and three questions to ask before you sign. A fixed price feels like the safe choice. You get a number, you sign, and in theory the risk of getting it wrong sits with the vendor. Procurement likes it, finance likes it, and it is easy to explain to a board. The risk does not disappear, though. It moves into the price. This article looks at where it goes, what…
What a fixed price costs you, when it is the right tool, and three questions to ask before you sign.

A fixed price feels like the safe choice. You get a number, you sign, and in theory the risk of getting it wrong sits with the vendor. Procurement likes it, finance likes it, and it is easy to explain to a board.
The risk does not disappear, though. It moves into the price. This article looks at where it goes, what it costs, and how to decide when the premium is worth payingEstimates miss, and everyone in the room knows it
McKinsey and the University of Oxford studied more than 5,400 large IT projects, those with initial budgets above $15 million. On average they ran 45% over budget and 7% over time, while delivering 56% less value than predicted. The same research found that every additional year of scheduled duration added 15% to cost overruns.
These were large projects, and a small build will look different. The lesson still carries over: software estimates are made before the work is understood, and they miss often. A vendor who commits to a fixed number knows this and has to price it in.
Where the premium sits
To commit to a firm price on an uncertain build, a vendor has to price in the risks it can see and add a margin for the ones it cannot. Estimates commonly cited by software agencies put this risk buffer at 15–30% of the quote. These figures come from vendors’ own writing and vary by project, so treat them as a range to ask about.
On a $100,000 scope, 15–30% is $15,000 to $30,000. You pay it whether or not the risks materialize. If the project lands cleanly, the premium has been paid for nothing.
That is the insurance. The risk being insured is uncertainty that neither side can remove at the start, and the client pays the premium.
The second bill: change
Specifications are written before anyone has used the product. Once people see something working, requirements shift, so changes arrive in nearly every project. Under a fixed price, each one becomes a change order: a written request, an assessment of effort and cost, a revised quote.
This is where fixed-price projects most often go wrong: at the boundary between scope and change, more often than on the price itself. It also creates a quiet tension. A narrow reading of the scope favors the vendor, and a broad reading favors the client. Clear acceptance criteria are the best protection for both.
When fixed price is the right tool
Fixed price works when the scope is stable, written down, and well understood: a migration, a defined integration, a compliance deliverable. In these cases the premium buys real certainty, and the risk of change is low.
Make sure the contract contains acceptance criteria and an explicit list of what is out of scope. The more detail upfront, the fewer change orders later.
When the scope is still fuzzy
Fixing a price on a vague scope trades real risk for arguments over change requests. Two arrangements fit better.
Paid discovery first. A short, paid discovery phase clarifies requirements, boundaries, and risks. The fixed price then covers the clarified scope. This hybrid, with time and materials for discovery and a fixed price once the scope is defined, is widely recommended.
Capped time and materials. Work is billed by time with an agreed ceiling. The client keeps the flexibility to change direction, and the vendor carries the risk beyond the cap. Both sides keep an interest in efficiency.
McKinsey’s advice to negotiators points the same way: look beyond unit price and seek agreements that share risk.
Getting the number procurement needs
Many companies cannot approve a budget without a firm figure, and that requirement is often what pushes a team toward a fixed price. There are ways to meet it without paying for certainty you do not need.
Use the cap as the approved number. With capped time and materials, the ceiling is the figure you take to finance. You approve a maximum, and you pay for the work actually done.
Fix the price per phase. After discovery, agree a fixed price for the first phase only, with payment tied to milestones. Each phase is estimated with more information than the one before it.
Hold the contingency yourself. Some contingency is needed in either model. The difference is where it sits. Inside a fixed price it is invisible to you and owned by the vendor. In your own budget it is visible, you decide when to release it, and you keep whatever is left.
Three questions before you sign
- What share of the price is a risk buffer? A clear answer shows the vendor has thought about risk. A refusal to answer means you cannot compare quotes.
- What happens with every change: who estimates it, and how fast? Look for a defined process and a turnaround time.
- Who gets the savings if we finish under budget? A vendor who has considered this will have a view.
The estimate is a forecast. The contract decides who pays when the forecast is wrong. A fixed price gives you predictability in exchange for a premium and a change-order process, and that exchange is sensible when the scope is stable. When it is not, a discovery phase or a capped arrangement usually costs less than certainty you are paying for in advance.
Before signing, put one number on the table: how much of the price is insurance.
Wamisoftware has been building software products since 2014. Our senior engineers work with startups and enterprise clients on projects where scope, architecture, and cost are agreed early.


