Every Monday I open the bank balance and hope.
Story · Case study
Spend analysis that survived the first audit question
Four hundred suppliers across eleven plants, classified once a week. The workings arrive attached to the answer, which is the part that changed the meetings.
The company
- Company
- Calderon Industrial
- Industry
- Manufacturing
- Company size
- 1,001–5,000 people
The starting point
Calderon Industrial buys from about four hundred suppliers across eleven plants on two continents. Once a quarter, a consultancy classified that spend, found the overlaps, and presented a deck. The deck was good. It was also three weeks old on the day it was presented, and the first question in the room was always the same one: where did that number come from.
Answering it meant going back to the consultancy, which meant the answer arrived after the negotiation it was needed for.
What changed
What they described
The procurement analytics team wrote down the classification itself: the taxonomy, the rules for a supplier that trades under two names, what makes two line items the same commodity, and — the part that mattered — that every classified line has to carry the evidence for its classification.
The application that came back does the classification weekly and keeps the workings attached to the answer. When somebody asks where a number came from, the answer is on the same screen as the number, and it is the same evidence every week rather than whatever the analyst reconstructed that morning.
The results
The three per cent is deliberate and the team defends it. A classifier that reaches ninety-nine per cent coverage has been told to guess, and a guessed classification is worse than an unclassified line because it is invisible. The unclassified spend goes on a list, and the list is short enough that a person works through it.
Suppliers classified weekly
412
Spend left unclassified
3.1%
flagged for a human, not guessed at
Savings identified in year one
1.4m
Minutes to a supplier pack
9 min
previously two days of an analyst
“The first question in any spend review is “where did that number come from”. It used to take a week to answer. It is now attached to the number.”
— Marta Beaulieu, Director of procurement analytics, Calderon Industrial (an example business)
The apps
What it cost to run and what to expect
Eleven plants, one tenancy question
Calderon's plants report into two legal entities and the procurement data was never allowed to mix freely between them. Every upload, every job and every result the application produces sits under Calderon's own tenant path, and the connection credentials for the two ERP systems are referenced rather than copied — the application is told which secret to use, never the secret itself, and reads of that reference come back redacted.
That was the condition the security review set, and it is the reason the review took two weeks rather than two months.
What they would do differently
Start with one plant. Calderon described all eleven at once, and the first version was correct about the taxonomy and wrong about three local exceptions, which took a fortnight of correcting to find. A single plant would have surfaced the same three exceptions in an afternoon, and the description would have been right before it was applied to everything.
Connected to this story
Read next
Why: Day in the role, with an example app you can try today
Tell me when it's ready
What happens next
Thank you. We will write once, when it's ready.