I regularly talk to procurement managers who do great work. They just can't prove how much that work was worth.
That sounds like a communication problem. It's actually a structural one.
"We negotiated well this year." That's not enough for the CFO. Not because he doesn't value procurement's work, but because he manages by numbers. If procurement doesn't deliver numbers, he doesn't manage it. He cuts it instead.
Procurement controlling is the way out of this dilemma. Not as bureaucratic overhead, but as the precondition for procurement being taken seriously as a strategic function.
It's not about dashboards. It's about four questions that need to be answerable at any time.
Which RFQs did we run this year? Sounds trivial. In practice, the answer often lives across several spreadsheets, email inboxes, and the department head's memory. Then it isn't trivial at all.
What did each RFQ cost, and what did it deliver? Old price, new price, volume, contract term. That's what the savings contribution is built from. Without these four fields, the savings figure is an estimate, not a number.
Which suppliers did we evaluate? Not just who delivered. Who delivered on time, at what quality, with what deviations. That's the foundation for every follow-up conversation.
Where do we stand against plan? Annual procurement targets exist on paper in many companies. They only become measurable once there's an actual plan versus actual comparison. Monthly, not just in December.
Many procurement departments have the data. It sits in the ERP, in spreadsheets, in emails. The problem isn't data availability. It's structure.
If every RFQ is documented differently, if savings definitions vary from person to person, if the department head is the only one with the full picture, then procurement controlling isn't possible. Not because information is missing, but because it isn't comparable.
The first step, therefore, isn't a new system. It's a shared definition. What counts as a saving? How do we measure it? When does an RFQ count as closed?
These decisions take an afternoon. They pay off for years.
The classic position of procurement in a company is cost center. There's a budget, procurement is expected to stay within it, and at year-end someone checks whether the result was in range.
No strategic weight. No budget discretion of its own. No investment in process improvement.
That changes once procurement becomes measurable.
An example. A procurement department that can prove it realized 1.2 million euros in savings last year through structured sourcing, and can trace that back to five concrete RFQs with volume, old price, and new price, gets a different hearing in the next budget conversation than one that says "we negotiated well."
The CFO thinks in numbers. Savings documentation is the language procurement needs to speak with him.
The most common mistake is waiting for the right system. For the ERP module that's coming soon. For the consultant who will eventually build it. The result is that nothing happens.
Procurement controlling can start with three pragmatic steps. No new system, no project.
Step one. Define what counts as a saving. Once, in writing, binding. How do we define a saving? Price reduction versus the last period? Versus market average? Versus the initial quote before negotiation? Any variant is defensible. There just has to be one.
Step two. Introduce an RFQ log. After every completed RFQ, capture date, category, volume, number of quotes, outcome, and savings amount. Takes 20 minutes per RFQ. By year-end, the savings report builds itself.
Step three. Quarterly review with leadership. Don't report annually, report quarterly. Three slides are enough. What was put out to tender, what it delivered, what's planned. Do this four times a year, and December holds no surprises.
A good procurement tool takes manual documentation off your plate. RFQs are set up in the system, quotes captured digitally, comparisons generated automatically. The savings figure comes from the data on file, not from the buyer's memory.
cusoso Target is built for exactly this. RFQ management, quote comparison, and savings documentation in one system. Proof of savings doesn't get built at year-end. It's generated with every completed RFQ.
What the software doesn't do is define what counts as a saving, or supply the will to work in a structured way. That has to come from the organization itself.
When is the right time to start procurement controlling? Now. The most common mistake is waiting for "better conditions." Whoever starts today, even with simple tools, has data by year-end. Whoever waits has nothing again by year-end.
Our procurement volume is too small for elaborate controlling. Is that true? No. Transparency matters most for small procurement teams, precisely because every resource counts. Controlling doesn't need to be elaborate. It needs to be consistent.
Which KPIs make sense? Four are enough to start. Savings volume, absolute and as a percentage of procurement spend, number of RFQs, average number of quotes per RFQ, supplier on-time delivery. Everything else can come later.
What if management isn't interested? Then procurement builds the data anyway, as the foundation for the next budget conversation. Whoever shows up with numbers gets heard. Whoever shows up without them gets cut.
Procurement controlling doesn't start with a tool. It starts with the decision to document every RFQ directly from now on, instead of reconstructing it at year-end.
This week, roughly estimate the four core metrics for your own organization. Starting with the next RFQ, document in parallel instead of postponing it.
cusoso Target connects procurement planning, RFQs, and savings documentation in one system, turning scattered spreadsheets into continuous controlling without a months-long rollout. Whether it fits your procurement organization is something our quick check shows in 3 minutes.
→ To the quick check
That sounds like a communication problem. It's actually a structural one.
"We negotiated well this year." That's not enough for the CFO. Not because he doesn't value procurement's work, but because he manages by numbers. If procurement doesn't deliver numbers, he doesn't manage it. He cuts it instead.
Procurement controlling is the way out of this dilemma. Not as bureaucratic overhead, but as the precondition for procurement being taken seriously as a strategic function.
What procurement controlling actually means
It's not about dashboards. It's about four questions that need to be answerable at any time.
Which RFQs did we run this year? Sounds trivial. In practice, the answer often lives across several spreadsheets, email inboxes, and the department head's memory. Then it isn't trivial at all.
What did each RFQ cost, and what did it deliver? Old price, new price, volume, contract term. That's what the savings contribution is built from. Without these four fields, the savings figure is an estimate, not a number.
Which suppliers did we evaluate? Not just who delivered. Who delivered on time, at what quality, with what deviations. That's the foundation for every follow-up conversation.
Where do we stand against plan? Annual procurement targets exist on paper in many companies. They only become measurable once there's an actual plan versus actual comparison. Monthly, not just in December.
The real problem is data without structure
Many procurement departments have the data. It sits in the ERP, in spreadsheets, in emails. The problem isn't data availability. It's structure.
If every RFQ is documented differently, if savings definitions vary from person to person, if the department head is the only one with the full picture, then procurement controlling isn't possible. Not because information is missing, but because it isn't comparable.
The first step, therefore, isn't a new system. It's a shared definition. What counts as a saving? How do we measure it? When does an RFQ count as closed?
These decisions take an afternoon. They pay off for years.
Why the CFO wants to see this
The classic position of procurement in a company is cost center. There's a budget, procurement is expected to stay within it, and at year-end someone checks whether the result was in range.
No strategic weight. No budget discretion of its own. No investment in process improvement.
That changes once procurement becomes measurable.
An example. A procurement department that can prove it realized 1.2 million euros in savings last year through structured sourcing, and can trace that back to five concrete RFQs with volume, old price, and new price, gets a different hearing in the next budget conversation than one that says "we negotiated well."
The CFO thinks in numbers. Savings documentation is the language procurement needs to speak with him.
Three entry points for procurement controlling without a big project
The most common mistake is waiting for the right system. For the ERP module that's coming soon. For the consultant who will eventually build it. The result is that nothing happens.
Procurement controlling can start with three pragmatic steps. No new system, no project.
Step one. Define what counts as a saving. Once, in writing, binding. How do we define a saving? Price reduction versus the last period? Versus market average? Versus the initial quote before negotiation? Any variant is defensible. There just has to be one.
Step two. Introduce an RFQ log. After every completed RFQ, capture date, category, volume, number of quotes, outcome, and savings amount. Takes 20 minutes per RFQ. By year-end, the savings report builds itself.
Step three. Quarterly review with leadership. Don't report annually, report quarterly. Three slides are enough. What was put out to tender, what it delivered, what's planned. Do this four times a year, and December holds no surprises.
What the software should do, and what it shouldn't
A good procurement tool takes manual documentation off your plate. RFQs are set up in the system, quotes captured digitally, comparisons generated automatically. The savings figure comes from the data on file, not from the buyer's memory.
cusoso Target is built for exactly this. RFQ management, quote comparison, and savings documentation in one system. Proof of savings doesn't get built at year-end. It's generated with every completed RFQ.
What the software doesn't do is define what counts as a saving, or supply the will to work in a structured way. That has to come from the organization itself.
Frequently asked questions
When is the right time to start procurement controlling? Now. The most common mistake is waiting for "better conditions." Whoever starts today, even with simple tools, has data by year-end. Whoever waits has nothing again by year-end.
Our procurement volume is too small for elaborate controlling. Is that true? No. Transparency matters most for small procurement teams, precisely because every resource counts. Controlling doesn't need to be elaborate. It needs to be consistent.
Which KPIs make sense? Four are enough to start. Savings volume, absolute and as a percentage of procurement spend, number of RFQs, average number of quotes per RFQ, supplier on-time delivery. Everything else can come later.
What if management isn't interested? Then procurement builds the data anyway, as the foundation for the next budget conversation. Whoever shows up with numbers gets heard. Whoever shows up without them gets cut.
The next step
Procurement controlling doesn't start with a tool. It starts with the decision to document every RFQ directly from now on, instead of reconstructing it at year-end.
This week, roughly estimate the four core metrics for your own organization. Starting with the next RFQ, document in parallel instead of postponing it.
cusoso Target connects procurement planning, RFQs, and savings documentation in one system, turning scattered spreadsheets into continuous controlling without a months-long rollout. Whether it fits your procurement organization is something our quick check shows in 3 minutes.
→ To the quick check