What happens between a successful negotiation and a smaller bill
Jon Wensley
Procurement has had a good year.
The team has negotiated hard, challenged suppliers and reported a substantial saving. The presentation is clear, the numbers are impressive and the target has been achieved.
Then Finance asks a slightly awkward question.
Why hasn’t expenditure gone down?
It is tempting to assume that somebody has got the calculation wrong. Sometimes they have. But it is also possible for both teams to be reporting accurately, while describing quite different things.
Procurement may be measuring an improvement against a supplier’s proposal. Finance may be comparing actual expenditure with last year or looking for money to remove from a budget.
The difficulty begins when those different measures acquire the same label.
Before celebrating a saving, we need to understand what has changed, compared with what, and when.
A discount needs something to be compared with
Consider an illustrative software renewal.
Last year the organisation paid £1 million. The supplier proposes £1.2 million for the same scope. Procurement negotiates the renewal to £1.05 million.
That is £150,000 below the opening proposal. It is also £50,000 more than last year.
The negotiation may represent an excellent commercial result. But it has not reduced like-for-like annual expenditure below the previous level.
If the approved budget was £1.2 million, the agreement also creates £150,000 of headroom against that budget. If it was £1 million, the business still has a £50,000 pressure to manage. Whether budget headroom becomes money released depends on what Finance does with it.
None of those statements contradicts the others. They answer different questions.
There is another question too: was the supplier’s opening proposal a credible alternative outcome? A reduction from an inflated quotation is a weak foundation for an impressive savings claim.
The baseline needs to be agreed before the result is known. Choosing whichever comparison produces the largest number afterwards is unlikely to improve trust.
Different achievements deserve different descriptions
I would distinguish a negotiated price improvement from the financial outcome it eventually produces.
A negotiated saving records an agreed commercial improvement against a defined baseline, for a stated scope and period. It might be a lower unit price, a reduced annual charge or a better rate for future purchases. Signing the agreement establishes the entitlement; it does not establish how much the business will actually use or spend.
Cost avoidance concerns expenditure that would otherwise reasonably have occurred. Preventing a justified increase can matter enormously, even if this year’s bill remains unchanged. The credibility of the claim depends on the alternative being realistic and evidenced.
Reduced demand is a way of changing cost, rather than a separate financial destination. Cancelling unused licences, simplifying a specification or deciding not to proceed with a project can reduce expenditure. But demand can fall without the bill changing if the business remains committed to a minimum payment.
An actual budget reduction is a financial decision to remove money from an agreed budget. It should have a credible basis in lower expected costs, with the timing and consequences understood. Cutting a budget alone does not make the underlying obligation disappear.
These can overlap. A demand reduction may allow a lower contractual commitment and then a budget reduction. We should follow that sequence without counting the same benefit three times.
Cost avoidance also deserves recognition. The answer to inflated savings claims is accurate language, not pretending that preventing an increase has no value.
A better price can accompany a bigger bill
Software provides an obvious example, but the principle applies much more widely.
Suppose a business improves its licence discount while buying more licences and upgrading users to a broader package. Procurement can negotiate a lower price for the chosen basket while total expenditure rises.
The added capability might be worthwhile. A business growing rapidly may also need to spend more. Lower total expenditure is not the only legitimate outcome.
But the organisation needs to understand the different effects of price, quantity and specification. Otherwise Procurement can announce success while the budget owner wonders why the bill is larger.
One useful way to explain the movement is to separate price, volume and mix. Did we pay less for the same thing? Did we buy more or less of it? Or did we change what we bought? A negotiation may improve the price while increased demand or a richer specification pushes total expenditure the other way.
And demand management requires action. Identifying an unused tool is useful. Establishing whether it can be retired, removing it safely and reducing the contractual commitment is what changes the cost.
There can also be a gap between reducing a rate and reducing a commitment. A cheaper unit price is a genuine commercial improvement, but if the organisation remains committed to a minimum quantity, lower consumption may not reduce the invoice. It is therefore useful to distinguish the commercial improvement from the contracted commitment and, finally, the expenditure actually realised.
Timing can turn an annual saving into a small in-year result
There is an important difference between saving £120,000 a year and saving £120,000 this year.
If a £10,000 monthly reduction starts with only three months of the financial year remaining, the gross in-year benefit is £30,000. The annual run rate is still £120,000, provided the reduction continues.
Both numbers are useful. They should not be exchanged according to which makes the presentation look better.
Then consider the cost of achieving the change. Migration, exit charges and temporary overlap may absorb some or all of the early benefit. A sound long-term decision can produce little immediate relief, or even require additional spending at the outset.
Cash timing and the effect on reported profit can differ too. Paying an invoice later may help cash flow without reducing the cost of the service. A multiyear benefit should not be presented as though it all reaches this year’s results.
The practical question is what reaches the period and financial measure the organisation is trying to improve.
Being cheaper does not always add value
The danger works in the other direction as well. An organisation can reduce a supplier’s invoice and make the overall situation worse.
A support contract may cost less because response times are slower, coverage is narrower or more work has been passed back to employees. If that creates disruption or additional internal cost, the smaller invoice tells only part of the story.
Equally, a more expensive agreement may remove duplication, improve reliability or provide valuable flexibility. The important comparison is not simply old price versus new price, but old outcome versus new outcome.
That is not a licence to justify every expensive choice through vague claims about quality. Additional value should be explained and, where possible, evidenced without forcing every benefit into a speculative cash equivalent.
What would make the conversation more useful
For each material opportunity, I would want a plain account of the starting point, the change, the delivery actions and the expected financial result.
What is the agreed baseline? Does the claim concern price, demand, an avoided increase or a reduced commitment? Who must act before it can be realised? When will the benefit start, and what will it cost to achieve?
Finance and the business should agree how that result will affect expenditure, cash and budgets. Procurement should be able to evidence the commercial improvement and identify the dependencies it cannot control.
That is not an argument for constructing an elaborate approval process around every small purchase. It is a way of making the important claims understandable.
It also follows directly from the question of procurement accountability. A savings forecast dependent on a migration, a cancellation or a business decision should remain conditional until somebody owns that action and has the means to complete it.
A more useful question
I would like organisations to recognise good negotiation, sensible demand management and the prevention of unnecessary increases. They all contribute to commercial performance.
But I would also like us to be more precise about the result.
Before asking how much Procurement has saved, perhaps we should ask:
What will the organisation actually spend differently because of this work?
Sometimes the answer will be that the bill is smaller. Sometimes it will be that a larger bill has been prevented. Sometimes the business will receive more value for the money. And sometimes the opportunity still needs an operational decision before anything changes.
Being clear about which of those we have achieved would make the savings conversation considerably more honest—and considerably more useful.