Getting to Truly Strategic: Why VPP Is Becoming Your Analytics Layer

I've spent close to two decades sitting across the table from procurement and supply chain leaders at manufacturers and distributors, and I keep seeing the same pattern: the best people in the room are doing the wrong job. They're reconciling three versions of a spend file before a Monday meeting. They're chasing the same supplier for the same three data points every quarter. They're building the analysis instead of acting on it.

That's not a talent problem. It's a data architecture problem, and it's the reason so few procurement organizations ever get to what I'd call truly strategic.

What “truly strategic” actually looks like

When the data layer underneath a procurement or supply chain function is right, the job changes entirely. Category managers stop defending numbers and start making calls. Specifically, that unlocks:

• Supplier Development & Innovation (SD&I) programs run directly with your top supply partners — joint capability-building and innovation work that never gets prioritized when the team is buried in data reconciliation
• Materially faster time-to-savings, because the opportunity is already quantified before the first supplier call
• Implementation and tooling transitions ERP migrations, TMS/WMS changes, category tool consolidations that don't stall for two quarters waiting on clean data
• Footprint decisions — onshoring, nearshoring, dual-sourcing — made on current landed-cost data instead of a model that's stale before it's finished
• Tariff and logistics exposure that's visible before it hits a P&L, not after
• Value analysis / value engineering (VA/VE) that's continuous instead of a once-a-year workshop
• New product development timelines and go-to-market speed that aren't gated by sourcing uncertainty

None of that is aspirational. It's what happens when the underlying spend, contract, and supplier data is structured well enough to trust.

What makes the difference

I've run this pattern across very different situations, and the constant isn't the industry — it's the sequencing. Most procurement engagements start with a sourcing event: pick a category, run an RFP, capture a number. We start with the data model.

The difference in approach: we're not running a one-time savings sprint that erodes the moment the engagement ends. We build the structured data layer — spend, contracts, cost of quality, and supplier performance, including the unstructured documents most tools never touch — so your category team can keep finding and acting on opportunities long after we're gone. Across engagements like these, this approach has contributed to more than $1 billion in identified EBITDA improvement for clients.

What “VPP as your analytics layer” actually means

We're not selling a dashboard. A dashboard shows you a problem you already knew about. What we build is the layer underneath it — the structured spend, contract, and supplier data model that lets your team stop reconciling and start deciding. That's the difference between a procurement function that reports on savings and one that generates them on a predictable cadence.

If your team is spending more time defending the numbers than acting on them, the fix usually isn't more headcount. It's the data architecture underneath the team you already have.

Where does your organization sit on this today — closer to defending the numbers, or acting on them? I'd like to hear how other operators and sponsors are thinking about this.