I have a pretty low tolerance for vague “AI is transforming procurement” talk.
Most of it collapses the minute you ask basic questions like: Where exactly is the value? What workflow changed? Who saves time? What decision gets better? What data had to be fixed first?
What stood out to me here is that the useful conversation wasn’t about magic. It was about fairly concrete applications:
- spend classification and data cleansing
- tail spend management
- supplier onboarding and third-party risk checks
- sourcing prep and negotiation support
- cross-functional decision support between procurement, engineering, and supply chain
That’s the level where this gets interesting.
The biggest takeaway for me: procurement is moving from process automation to decision augmentation.
That sounds subtle, but it matters. Saving a few hours a month on manual classification is nice. Redirecting teams away from spreadsheet cleanup and toward sourcing strategy, supplier discussions, and stakeholder work is much more meaningful.
And there was a second, more important point buried underneath that:
bad data is still the tax you pay on every AI ambition.
No consultant deck wants to say that because it’s not sexy, but it’s true. If your spend is misclassified, supplier master data is messy, and critical information lives in buyer laptops and random spreadsheets, AI won’t “unlock value.” It will just produce faster nonsense.
That’s why I actually like the sequencing discussed: use AI first to help clean and structure procurement data, then use that improved data foundation to power better sourcing, forecasting, and risk decisions. Pragmatic. Not glamorous. Correct.
I also think the tail spend examples are where the ROI becomes easiest to defend.
Not in the “look, we saved 11 analyst hours” sense. In the actual money sense.
If agentic workflows can route users to preferred suppliers, compare quotes automatically, and stop bad buying behavior before it turns into leakage, that’s not a pilot theater exercise. That’s real procurement value. Same thing with supplier onboarding and risk orchestration: if a system can pull D&B, ESG, cyber, and compliance signals into one flow and escalate only the cases that need human judgment, you’re not replacing procurement. You’re finally using procurement time where it matters.
That distinction came up a few times, and I think it’s the right one:
AI shouldn’t replace judgment. It should remove the administrative sludge wrapped around judgment.
That’s also why I agreed with the skepticism toward giant suite-first thinking.
I’ve spent enough time around enterprise software to know the pitch: one platform, one workflow, one source of truth, one vendor to blame. Nice story. In practice, big suites are rarely best at everything, and once they lag in a critical module, you’re stuck waiting on someone else’s roadmap.
I’m generally in the best-of-breed, but be disciplined about it camp.
Not 25 disconnected tools with broken APIs and no ownership. But also not blind faith that one procurement suite will suddenly become best-in-class at spend analytics, risk intelligence, contract analytics, and agentic sourcing all at once. It won’t.
Another part I liked: the emphasis on sandboxing with real data.
Honestly, if a vendor doesn’t want you testing with your own use cases, that tells you a lot. Scripted demos are where bad software goes to look smart for 30 minutes. I’d rather see where the system breaks, how quickly it recovers, and whether the team behind it can handle real procurement messiness.
Because procurement data is messy. Supplier structures are messy. Stakeholder behavior is messy. That’s the job.
On adoption, the panel got something right that a lot of leadership teams miss: resistance usually isn’t “people hate AI.” It’s that people don’t trust the output, or they think leadership is just adding another layer of tooling without removing any work.
That is a completely rational concern.
If you tell a team AI will “free them up for strategic work,” but then keep the same approvals, same reporting, same manual checks, and same volume expectations, nobody believes you. They shouldn’t. The operating model has to change too.
Otherwise you haven’t transformed procurement. You’ve just accelerated the old mess.
The future skill discussion was solid as well. I don’t buy the lazy take that procurement people just need to “learn AI” and they’ll be fine. That’s incomplete.
Yes, teams need to understand prompting, validation, tool limitations, and when not to trust an output. But the real premium shifts even harder toward human skills that were always undervalued:
- commercial judgment
- stakeholder influence
- supplier relationship management
- negotiation on complex, high-value decisions
- cross-functional problem solving
In other words, the repetitive parts of procurement get compressed. The messy, ambiguous, high-context parts become more important.
That’s not the death of procurement. It’s the end of hiding behind process.
My broad conclusion is pretty simple:
Procurement teams should stop asking, “Where can we use AI?” and start asking, “Which decisions are too slow, too manual, too fragmented, or too poorly informed today?”
Start there.
Then get painfully honest about data quality.
Then test on real workflows.
Then scale what actually changes outcomes.
Not what looks good in a steering committee deck.
That’s where I think procurement is headed next: not autonomous everything, not overnight replacement of teams, but a more intelligent procurement function that is finally less trapped by admin work and more capable of shaping business decisions.
That’s a future I can take seriously.