Why the Wrong KPIs Keep Procurement a Cost Centre
Measure procurement only on cycle time and unit price, and it will behave like a cost centre — fast, cheap, and strategically invisible. The metrics a function is held to define the behaviour it produces, so a strategic mandate requires strategic measurement. This is the instrumentation layer of the IT procurement transformation: without it, value created is value unproven, and unproven value does not earn a seat at the planning table.
The framework below balances four lenses — savings, efficiency, service, and risk — because over-weighting any one distorts behaviour. A team chased only on savings stops measuring whether the business is happy; a team chased only on speed stops capturing value. The art is the balance, and the discipline is reporting the soft-but-real metrics as rigorously as the hard ones.
Hard Savings and Cost Avoidance
Savings is two distinct metrics that are routinely conflated. Hard savings measure the reduction on completed purchases — initial proposed cost minus actual cost — and best-in-class technology teams deliver 8–12% annualised savings on addressable spend, rising to 15–25% on categories run through structured strategic sourcing. Cost avoidance measures value created before a purchase happens: a negotiated-away price increase, an eliminated redundant licence, a demand challenged before it became a contract. Best-in-class avoidance runs at 2–4% of managed spend.
Avoidance is the metric that separates strategic from transactional procurement, precisely because it never appears as a budget line. A licence harvested through software asset management — where mature programmes recover 15–30% of annual software spend — is avoidance the spreadsheet will not credit unless procurement claims it. Anchoring both numbers to independent benchmarks, such as those in the Price Benchmarking Report, is what makes them defensible to a CFO.
Cycle Time and Operational Efficiency
Operational metrics keep the function honest about responsiveness. The headline benchmark is PR-to-PO cycle time under 24 hours for technology categories, against 48 hours elsewhere. Cycle time matters less for its own sake than for what it prevents: a slow desk pushes the business toward shadow IT, recreating the unmanaged spend that procurement exists to eliminate. Advanced procurement platforms report 40% faster cycle times than manual processes, which is part of why the technology budget pays back.
Efficiency metrics are necessary but never sufficient. A fast desk that captures no savings is still a cost centre, which is why cycle time belongs in a balanced framework and never as the sole headline. The renewal-timing discipline in the procurement calendar is the structural complement — speed on intake, lead time on renewals.
Internal Service: NPS and Responsiveness
The business is procurement's customer, and a function the business avoids cannot be strategic. Procurement Net Promoter Score of 60+ and requisition response under 24 hours mark a team the business chooses to use rather than route around. This is the quantitative side of the relationship-versus-management distinction applied internally: service quality is what earns procurement the early involvement that creates leverage in the first place.
Service quality is also the leading indicator of every other number. A function the business trusts is brought into decisions early, while one it avoids is handed contracts already signed — and early involvement is where the 15–25% strategic-sourcing savings actually originate. Track requisition response time, the proportion of spend that reaches procurement before a vendor is selected, and the rate of off-contract or "maverick" buying. A maverick-spend figure above 10–15% of addressable spend is a reliable sign that the business is routing around procurement, and that the savings and avoidance numbers are understated because the function never sees the deals in the first place.
Total Cost of Ownership and Risk
Unit price is a poor proxy for value in technology, where implementation, integration, support, and exit costs often dwarf the licence. A strategic KPI framework measures total cost of ownership, not headline price, and tracks risk-adjusted outcomes — supplier financial health, concentration, and continuity exposure. The Broadcom–VMware episode, where a renewal looked routine until the TCO of staying versus migrating diverged sharply, is the cautionary case behind our guide to procurement strategy during vendor EOL. Supplier performance feeds this lens directly through a structured vendor scorecard.
Risk metrics deserve their own discipline because they are the ones a price-only scorecard misses entirely. Supplier concentration — the share of a category or the whole estate dependent on a single vendor — is the metric that would have flagged the VMware exposure long before Broadcom's repricing. Track it alongside supplier financial health and contractual lock-in, and review it whenever a vendor's roadmap or ownership changes. These measures rarely move month to month, but when they move they move fast, and a function that is not watching them learns about the risk from the vendor's renewal quote rather than its own dashboard.
Building a Balanced KPI Framework
Focus on a manageable set — roughly 5–10 core KPIs across the four lenses — rather than drowning the function in fifty metrics nobody acts on. Set each against a best-in-class benchmark, report monthly, and review the weighting annually as priorities shift between cost reduction and value creation. The maturity of the measurement should match the maturity of the function, which is why the framework evolves alongside the procurement maturity model. To benchmark your current position against best-in-class and build the framework that fits, request a confidential briefing, or engage our SaaS optimisation practice to turn the avoidance metric into recovered spend.