In partnership with
FINANCE
Procurement Is Becoming a Data and Systems Function
Procurement used to feel like a moment in time: a deal, a signature, a renewal date circled on a calendar.
Cloud broke that rhythm with usage-based pricing, marketplaces, and self-serve tools turning buying into a continuous stream of decisions. Someone starts up a new service, adds a vendor, upgrades a tier, or clicks a private offer… and the financial impact starts before finance even knows a request existed.
So procurement is changing roles. Tactically, but fast.
More teams are realizing procurement is not just a negotiation function anymore. It is becoming a data and systems function, responsible for how purchasing flows through the business, what gets captured, and whether the company can learn from its own spend behavior.
That shift matters a lot for FinOps, because FinOps lives downstream of decisions that procurement can shape upstream.
The New Procurement Stack
If you zoom out, modern procurement is starting to resemble an internal platform team:
It owns the intake experience (how requests enter the system).
It routes work across stakeholders (security, legal, finance, engineering, leadership).
It enforces policy through workflow (what gets approved, when, and why).
It maintains system-of-record data that everyone else depends on (vendor, contract, pricing, usage, renewal, owner, risk).
This is why “procurement orchestration” keeps showing up in the market. Multiple sources describe orchestration as coordinating people, systems, and workflows from intake through payment, so purchasing runs through a connected flow instead of scattered tools and inbox threads.
When procurement operates like a system, it creates something finance and engineering both need: a traceable line from request to justified cost.
Data is the Leverage, Not the Spreadsheet
Negotiation still matters, obviously. However, the leverage is increasingly coming from whether procurement can produce clean, trusted data at the moment decisions are made.
Think about the minimum dataset that actually makes cloud and SaaS spend governable:
Who is the business owner?
What environment is this for (prod, dev, pilot)?
What is the pricing model (flat, usage-based, tiered)?
What is the unit (seat, GB, request, token, hour)?
Which account or billing entity is this tied to?
Does it draw down a commitment, credit, or private pricing agreement?
What is the renewal trigger and termination shape?
What is the approval chain when usage ramps?
When that data is missing, every downstream function has to guess:
Finance guesses during forecast.
FinOps guesses during allocation.
Engineering guesses when costs get questioned later.
Procurement guesses at renewal time, usually under deadline.
McKinsey has been blunt about where procurement is headed: more advanced analytics and AI, more predictive decision-making, more capability built around procurement data itself.
So the “systems function” part is not hype, it is the operating model catching up to how spend behaves now.
Why This Matters to FinOps
FinOps wants the same thing finance wants, even if we use different words: make variable spend clear enough to manage. The challenge is that each function is looking at the same purchase through a different lens, and without clean upstream data, all three are operating on assumptions.
The scenario below shows what that gap costs, and what changes when procurement closes it.
A Scenario: The Purchase Is the Same. What the System Knows Is Not.
An engineering team purchases an observability tool. $80,000 annually, usage-based, priced per host. Six months later, a production migration doubles their host count. The bill jumps from $6,700 to $14,000 a month.
What happens next depends entirely on what procurement captured at purchase, and whether that data connects to anything downstream.
When procurement functions as a checkpoint:
Finance sees a cost spike with no owner, no context, no usage driver
FinOps opens a ticket. Engineering responds two weeks later
The growth was planned and legitimate, but the system had no record of that
Forecast assumptions were flat because nobody captured the expected ramp
Month-close is delayed, every function reconstructs the story from scratch
When procurement functions as a system:
The same spike appears, but the record already exists: owner, environment, usage driver, expected growth trigger, billing entity
Finance matches the increase to a pattern the system already described
No investigation needed. Forecast is updated and month closes cleanly
Nobody made a bad decision in either path. The purchase was the same. What changed is whether the system held enough context to make the spend explainable later.
This pattern scales fast: per-GB data pipelines, per-seat security tools, token-based AI inference services. When none of those records include a usage driver or expected ramp, FinOps is assembling cost stories after the fact, finance is forecasting off patterns that don't reflect what engineering planned, and procurement loses renewal leverage because utilization was never documented.
What This Means for FinOps
Procurement functioning as a system produces one thing that a checkpoint never does: data that travels forward and stays useful across the cost lifecycle.
The inputs that matter at purchase:
Who owns it and what environment it serves
What the pricing unit is and what makes it grow
Which commitment, credit, or billing entity it draws from
What the renewal trigger looks like and who needs to know
When those fields are captured consistently and connected to the right systems, downstream functions stop guessing:
Finance forecasts from signal, not assumption
FinOps allocates from day one instead of reverse-engineering spend
Procurement arrives at renewal with utilization history, not questions
A lot of FinOps pain originates before FinOps ever touches the spend. The untagged resource, the unexplained spike, the renewal that catches everyone off guard. Those usually trace back to a purchase where context was never captured in a form that traveled forward.
That is the shift worth paying attention to. Not because intake is a new idea, but because the value of doing it well compounds across every function that touches that spend later.
Still searching for the right CRM?
Attio is the AI CRM that builds itself and adapts to how you work. With powerful AI automations and research agents, Attio transforms your GTM motion into a data-driven engine, from intelligent pipeline tracking to product-led growth.
Instead of clicking through records and reports manually, simply ask questions in natural language. Powered by Universal Context—a unified intelligence layer native to Attio—Ask Attio searches, updates, and creates with AI across your entire customer ecosystem.
Teams like Granola, Taskrabbit, and Snackpass didn't realize how much they needed a new CRM. Until they tried Attio.
RESOURCES
The Burn-Down Bulletin: More Things to Know
2025 Global Chief Procurement Officer Survey (Deloitte) Useful context on where CPO investment is going and why siloed operations remain the top barrier to procurement delivering value.
Gartner Says Generative AI for Procurement Has Entered the Trough of Disillusionment (Gartner, July 2025) Fragmented, low-quality data is the reason AI in procurement underdelivers, not the tooling itself.
Revolutionizing Procurement: Leveraging Data and AI for Strategic Advantage (McKinsey) Less than 20% of available procurement data is actually used to inform decisions, and most organizations know their infrastructure is not ready.
What Is Procurement Orchestration? (Ramp) A clean explanation of what it means for procurement to operate as a connected system from intake through payment.
That’s all for this week. See you next Tuesday!