Why the procurement route decides everything else.

A failure of incentive, not of intelligence

The people running these procurements are usually sharp, experienced, and senior. The pattern is not a failure of intelligence. It is a failure of incentive. The person running a procurement inside a client organisation is rarely rewarded for a better outcome. They are rewarded for an uncontested process. An approval that sails through the committee. A tender that returns on time. A contract signed on the scheduled date. A consultant panel whose names the Board already recognises.

The actual performance of the project sits years downstream of the decision. By the time the claims arrive, the person who chose the procurement route has often moved on, been promoted, or left.

"The short-term reward is for ticking the boxes cleanly. The long-term cost is absorbed by the organisation."

This creates a standing demand for exactly the service the traditional consultancy is set up to deliver. A familiar client wants a familiar recommendation, because a non-standard recommendation introduces risk into the approval process. Even if the non-standard route would produce a better project, it requires the client-side lead to defend a choice that does not look like the choices the committee has seen before. That is a harder internal conversation than approving the familiar route. The path of least resistance inside a client organisation is to buy the standard product. So the standard product is what gets bought.

How the recommendation gets manufactured

The traditional consultancy reads this accurately. A firm that tried to talk a client out of a single stage lump sum tender would be giving advice the client is not paid to hear, and risking the appointment. So the firms have adapted. The playbook gets polished to the point where the recommendation arrives looking like considered advice, even though the conclusion was fixed before the conversation began. Tender strategy papers get written that evaluate three procurement routes and arrive at the one the client wanted all along. Fee proposals get shaped to match what the Board expects to approve. Risk allocation gets described in the language of transfer, because that is the language that gets signed off, even though the transfer is largely fictional.

The dynamic in the room is recognisable to anyone who has sat through enough of these meetings. The client arrives with a project and some anxiety about getting it right. The consultancy arrives with a playbook and some confidence about how these things are done. The client reads the consultancy's confidence as expertise. The consultancy reads the client's willingness to proceed as endorsement. Both parties conclude that the approach is sound. Neither has actually tested it against the specifics of the project. They have tested it against each other's body language.

"The conviction is being manufactured in the room. Neither side is the source of it."

From that point forward, every decision gets made through the same mirror. The consultancy recommends. The client approves because the consultancy seems sure. The consultancy treats the approval as confirmation, and builds the next recommendation on top of it. By the time the contract is signed, the procurement route is no longer a decision anyone is examining. It is the architecture of the project. Everyone has moved on to detail, and the team has a collective interest in defending the architecture they have agreed to.

What the project gets

What the client ends up with is a version of the project that looks correct on paper and performs badly in practice. The tender returns come back inflated, because contractors are not naive. They know what they are being asked to carry. The winning bid is rarely the most competitive one. It is the most optimistic one. The programme that gets signed into the contract is usually undercooked, because nobody had an incentive to test it properly before signature. Design development continues after contract award, producing a steady stream of early change events that the client pays to absorb.

Then the back half of the project happens. The claims arrive. The forecast outturn cost moves. The commercial correspondence becomes a letter-writing exercise. The consultancy switches into defensive mode, because the original procurement advice is now exposed and the firm needs the record to support the decision that was taken. The client's own internal lead, who approved the route eighteen months earlier, is under pressure to defend the cost growth. The easiest defence is to blame the contractor. The consultancy supports that framing because it protects the original advice. The contractor is left carrying a disproportionate share of the risk they priced in at tender, and the relationship has collapsed.

Nobody is well served by this. The client has paid too much for a project that underperformed. The contractor has delivered a job that probably broke even or lost money. The consultancy has protected its fees, but at the cost of spending the back half of the project defending its earlier advice rather than improving the outcome.

The test worth asking

The pattern is not a failure of any one firm or any one client. It is a system that produces a predictable bad outcome because the incentives of the people making the decisions are pointed at the wrong things. The traditional consultancy exists in its current form because there is a standing client demand for it. The client demand exists because the internal approval culture rewards the familiar choice over the better one. The two sides reinforce each other, and the project pays the cost.

There is a test worth putting to any consultancy on a new appointment, and it is simple enough to be useful in the room. Ask why the recommended procurement route is the recommended procurement route. If the answer is that it is what the market expects, or what the Board is used to approving, or the safest option given the circumstances, the answer is not about the project. It is about the firm.

"A recommendation that begins with the project can land anywhere. A recommendation that begins with the firm lands in the same place every time."

A genuine recommendation begins with the project. What is the scope certainty. Where is the design maturity. Where does the risk actually sit, and which party is best placed to carry each element. How will change be managed. A recommendation that answers those questions will rarely land on single stage all-risk lump sum for a modern complex job. It will land on something more collaborative, more flexible, and more honest about where the risks really are.

The client who decides to procure differently is not being naive. They are not taking a risk by moving away from the standard product. They are taking a risk by continuing to buy it, because the evidence has tipped. The familiar route used to be the safe choice. It is not any more.