Every Procurement leader we talk to says the same thing: "Every company struggles with this."
Not some companies. Not the ones without proper tools. Every company.
So we kept asking why.
The spreadsheet isn't the last resort. It's the default. Even teams with CLMs, P2P suites, and ERP systems fall back to a shared spreadsheet for savings tracking. The tools they have weren't built for this. So they build something themselves and make it work, until Finance asks a question the spreadsheet can't answer.
The methodology problem is universal. The solutions are all one-offs.
Some teams baseline against prior cost. Others use budget lines. Others use the lowest competitive bid. All of them call it savings. None of them are using the same definition. When leadership rolls up a number, the total is effectively meaningless.
Leaders can't see the pipeline. They can only see the outcome. No visibility into what's identified, what's active, what's at risk. Finance visibility and forecasting exist in sales. Procurement is still flying blind.
The audit trail problem only shows up when it's too late. Everything looks fine until Finance asks to see the supporting docs. Then it's three days of digging through comment threads that were never meant to be evidence.
These aren't edge cases. This is the norm for Procurement teams measured on savings. It's what we built Clero to fix.
The tools exist everywhere except here
Sales teams have had pipeline visibility for years. They know exactly what's in the funnel, what stage each deal is in, what's at risk, and what's likely to close this quarter. That visibility didn't make sales teams better at selling. It made their results legible to the rest of the company, which changed how leadership invested in and trusted the function.
Procurement teams deliver real, measurable value. The problem is that value often isn't legible until after the fact, and even then it's presented in a format that requires Finance to do extra work before they can use it. That extra work creates friction, and friction creates doubt, even when the underlying numbers are solid.
The one-off solution trap
When a team recognizes the problem, they solve it the only way they can: they build their own system. Someone creates a more structured spreadsheet template. Someone adds a validation tab. Someone writes up a methodology guide that lives in a shared folder nobody opens. These are genuine efforts to fix a real problem, and they work, until they don't.
The template drifts when someone edits it for a specific initiative and forgets to update the master. The methodology guide is ignored under deadline pressure. The validation tab breaks when a new column gets added. And when the next Finance question comes in, the team is back to reconstructing context from a spreadsheet that was never designed to hold it.
The solution isn't a better spreadsheet. It's a purpose-built system that enforces the methodology before anyone types a number, and keeps the audit trail in real time so there's nothing to reconstruct later. That's what we built. And based on every conversation we've had, we didn't need to look hard to find the problem.