Picture the meeting. You're presenting $4.2M in savings to the CFO. Slide looks clean. Number is real. You did the work.
Then: "Walk me through the methodology on this one."
And you're suddenly very aware that three different people updated that spreadsheet three different ways, nobody defined what "baseline" means, and the audit trail is basically vibes.
The savings were real. The number just can't survive a question.
This is the problem Clero exists to solve. Not because procurement teams are sloppy, but because no spreadsheet can enforce methodology consistency before the number gets entered.
The question isn't hostile
When a CFO asks to walk through the methodology, they're not trying to catch anyone out. They have their own reporting chain to answer to, and they can't put a number in front of their board unless they understand how it was built. That's a reasonable ask. The problem is that most procurement teams can't answer it cleanly, not because the savings weren't real, but because the process that produced the number wasn't designed to be audited.
A spreadsheet doesn't care how you calculated the baseline. It just records what you typed. So when three people update the same tracker over six months, each using a slightly different approach, the total is technically accurate but methodologically inconsistent. Finance can't validate that. And when they can't validate it, they discount it.
The context disappears faster than you think
Even if the person who built the savings model knew exactly what they were doing, that context rarely survives. People move roles. Spreadsheets get handed off. The comment that explained the baseline calculation gets buried under six months of edits. By the time Finance asks the question, the person best positioned to answer it may not even be on the team anymore.
This is why audit trails matter so much in savings reporting. Not as a bureaucratic exercise, but as a practical one. The documentation needs to exist at the time the work is done, not reconstructed weeks later when someone asks.
Methodology has to come first
The only way a savings number survives scrutiny is if the methodology was locked before anyone typed a figure. What's the baseline? Where did it come from? Is this a hard saving or cost avoidance? Who approved it? Those questions need answers at the start of an initiative, not at the end of a quarter.
That's what Clero enforces. Before a number enters the pipeline, the methodology is set. The classification happens automatically. The audit trail builds in real time. So when the CFO asks to walk through it, the answer is already there.
The savings were real. Now the number can prove it.