Spend analytics consolidates spend from many systems, classifies it into a taxonomy, enriches supplier records, identifies savings (consolidation, tail spend, off-contract), shapes category strategies, and monitors realized savings against plan.
The 6 tasks — the nature of each, and the oversight it needs
Tag each task in plain terms — what kind of work it is and how hands-off it can run — before any mention of AI. The kind of work is what later decides which tool, if any, fits.
A data-intensive, analytical process. The binding step is spend classification — accurately sorting millions of transactions into a taxonomy is what every downstream insight depends on. The analysis and savings detection are ML-driven; setting category strategy is a human judgment call.
Drives sourcing and savings decisions — classification errors mislead strategy, so accuracy and a human on category strategy matter.
The question isn’t only “is there savings” — it’s can I run this better: cheaper, faster, higher quality, better service? Here’s what best-in-class looks like, and how teams get there. (How much of it AI specifically drives — and how proven that is — is Section 04.)
Process discipline first, then automation — AI is one slice of the second column, not the whole answer.
- Spend taxonomy (UNSPSC / custom)
- Data-quality standards
- Category strategy cadence
- Tail-spend policy
- ML spend classification
- Supplier enrichment (D&B, risk, ESG)
- Savings-opportunity detection
- Executive savings dashboards
“Who runs the work” is its own question, separate from AI. AI shows up across these options — sometimes heavily, sometimes not at all. Vendor-neutral; the real options mapped to PR04.
Recall the tasks and their nature from Section 01. AI is one lever, not the whole story — the mix below is simply the result of matching the right kind of solution to each kind of work, weighted by where the work concentrates.
ML/Predictive leads (~40%) because spend analytics is a multi-dimensional analytical problem — classification, market intelligence, and total-cost optimization. GenAI supports narrative and category strategy; the rest is rule-based data consolidation. (McKinsey State of AI 2025, Deloitte State of AI 2025.)
The right lever fits your volume, variability, control needs, and appetite to operate a system. Start here.
The autonomy question: agent or copilot?
Whichever delivery model you pick, one choice cuts across them — who presses enter.
AI agent
Runs the steps end-to-end, completes the clean cases on its own, and routes only the exceptions to a person.
AI copilot
Sits beside the person and speeds up each step; the human acts on every decision.
What to evaluate — whichever you choose
- Accuracy on your own inputs — vendor benchmarks are on clean data; test your messiest cases.
- Straight-through / touchless rate — the real efficiency number, not “AI-powered.”
- Exception-handling experience — most of your team's time goes here, not the happy path.
- ERP write-back & integration depth — does it post cleanly to your system of record?
- Data residency — does data leave your environment, and is that acceptable to compliance?
- The accountability surface — what happens, and who owns it, when the model is confidently wrong?
See every lever across your processes
Run your portfolio through the assessment — work profile, improvement potential, confidence, and executor options across all your blocks, scored against 127 enterprise subprocesses.
Open the AI Value Assessment →