22 July 2026 / How we engage

Fixed price is a constraint, not a discount

A day rate pays for hours. A fixed price pays for a result, and the difference shows up in what actually gets built.

Most buyers hear a fixed price and think concession. It is not a concession. It is a constraint we accept before the work starts, and it quietly decides what the finished system looks like.

On a day rate, scope is elastic and time is the product. Every extra requirement is revenue. Nobody in the room has a reason to say no, so nobody says it, and nine months later there is a model with four hundred business rules in it and three people who understand them. That is not bad faith. The incentive is simply pointed the wrong way, and incentives win.

The scope argument happens at the start

When the number is agreed up front, the hard conversation cannot be deferred. We have to know, before we sign, which entities are in, which currencies matter, how many of the legacy adjustments survive the move and who signs off on the chart of accounts. Those questions are unpleasant and they are exactly the ones that sink a delivery when they are asked in month six instead of week two.

Clients often experience the first fortnight of a fixed price engagement as slower than they expected. It is. We are buying certainty with it, and the certainty is what makes the rest fast.

Simplicity stops being a virtue and starts being an interest

Once our margin sits on the other side of the estimate, every hour of unnecessary complexity is our money. A configuration that a client administrator can maintain is worth more to us than a clever one that only we can maintain. So we build the plain version first, we push back on the rule that exists because one person asked for it in 2019, and we spend the saved time on the parts that carry real risk: data quality, the security model, the first live close.

This is the part that surprises people. Fixed price does not make us defensive about change. It makes us allergic to the wrong kind of change, which is not the same thing.

What it does not mean

It does not mean the scope is frozen. Businesses reorganise, acquisitions land, a regulator moves a deadline. We carry a named change budget in the price and we spend it in the open, with the client deciding what it buys. What is not allowed is silent scope drift billed at the end.

It also does not mean we bid on a brief we do not believe. If a discovery tells us the data model cannot support the reporting the client has asked for, the honest answer is that the number would be a guess. We say so, we scope the model work separately, and we price the build when there is something real to price. A twelve week Abacum rollout priced against a chart of accounts nobody has agreed is not a fixed price. It is a deposit on an argument.

The test

A fixed price is worth having only if the person selling it also has to deliver it. Ask whoever quotes you whether the same people stay on the engagement to the end. If the answer involves a handover to a delivery team you have not met, the number is a sales artefact, not a commitment.