Every procurement team has had this conversation. You walk into the quarterly business review with a number. $2.4M saved this year. The CFO's first question isn't "great work," it's "how do you know?"
That question is fair. It's also the reason so many procurement functions lose credibility they never should have lost in the first place. Not because the work wasn't real, but because the number behind it wasn't defensible.
The problem isn't effort. It's proof.
Most procurement teams are good at the work: renegotiating contracts, consolidating suppliers, running RFPs, catching scope creep before it hits a PO. What they're inconsistent at, through no fault of their own, is capturing that work in a way that survives scrutiny six months later, from someone who wasn't in the room.
A saving isn't just a number. It's a number tied to a baseline, a category, and a point in time when it became real. Strip out any one of those three and what you have is a claim, not a saving.
Baseline is where most claims fall apart
Ask five analysts how they calculated a saving and you'll often get five different baselines: last year's spend, the original quote, budget, a market index. Each is defensible in isolation. None of them are comparable to each other. That inconsistency is exactly what a skeptical CFO, or an internal audit, will find first. It's also the fastest way to have an entire year of reported savings discounted wholesale, including the ones calculated correctly.
This is where a Hackett-style framework earns its keep, not as academic rigor for its own sake, but as a shared language. Should-cost baselines, historical price baselines, budget baselines, and index-based baselines each answer a different question, and each fits a different category of spend. The framework isn't the point. Consistency across the team, spend category, and reporting period is the point, and you can't get consistency without agreeing on the framework first.
Reported, validated, and Finance-grade are not the same thing
The other place claims fall apart is stage. A saving identified in an RFP is not the same as a saving negotiated into a contract, which is not the same as a saving that's actually flowed through and been recognized by Finance. Most teams track all three the same way, as one running total, so the number in the deck is always some blend of hope and fact. Nobody outside procurement can tell which is which.
The fix isn't more spreadsheet columns. It's treating stage as a first-class fact about every saving, not a note in a comment field. A saving that hasn't reached a contracted, Finance-recognized state should never appear in a number a CFO is going to repeat to the board. Not because the earlier-stage work doesn't matter (it does, and it should be visible to procurement leadership as pipeline), but because mixing pipeline and fact in the same total is what erodes trust over time, one quarter at a time, until "procurement savings" becomes a phrase Finance quietly discounts by 30% before they even look at the detail.
Why this matters more as spend scale grows
At smaller spend levels, an inconsistent baseline or a blurred stage is an annoyance. At $50M, $100M, $300M+ of addressable spend, it's a structural risk. The gap between what procurement claims and what Finance will certify compounds, and it shows up exactly when it's most expensive: budget season, board reporting, the CFO deciding whether procurement's number belongs in the company's own guidance.
Teams that get this right don't have smarter analysts. They have a consistent methodology applied the same way by everyone, every time, with the baseline and the stage captured as structured facts from the moment a saving is identified, not reconstructed later when someone asks. That's a system problem, not a discipline problem, and it's why spreadsheets top out here regardless of how careful the person maintaining them is.
That's the gap Clero is built to close: a system of record for procurement savings that enforces a consistent baseline methodology and keeps pipeline and Finance-grade savings clearly separated, so the number in the deck is always one you can defend.