r/Procurement_HI_AI

Spending a lot of time around enterprise procurement teams this year, and the framing in most vendor decks is backwards. Everyone's pitching "how much can the agent automate." The teams actually getting value are asking the opposite question first.

Quick context on where things are: the category genuinely shifted in 2026 from copilots that suggest to agents that act — an agent finds a supply need, negotiates inside pre-set parameters, routes the PO, and a separate compliance agent clears or escalates it. Gartner pegs supply chain software with agentic AI going from under $2B in 2025 to $53B by 2030, and McKinsey notes procurement is still only ~6% of enterprise AI use cases with just 36% of teams running a real GenAI deployment. So lots of forecast, much lower floor.

Here's the heuristic that's actually held up: don't sort by how complex the task is. Sort by what happens when the agent is wrong.

Automate the stuff that's high-frequency, bounded, reversible, and data-rich:

• transactional sourcing, reorder routing
• RFQ generation, bid normalization
• 3-way invoice matching
• supplier-risk monitoring (continuous scanning of financial/geopolitical/ESG signals)

Keep humans on the stuff that's high-stakes, relational, ambiguous, or irreversible:

• sole-source strategic supplier selection
• multi-year contract terms
• escalating a relationship that's gone bad
• anything with ethical/reputational weight

The biggest failure I see is automating a high-stakes decision because the data looks clean. Gartner says 74% of procurement leaders admit their data isn't AI-ready — and an agent on bad data just makes the wrong call faster. Gartner also expects 40%+ of agentic AI projects to get cancelled by 2027, and it's almost never the model's fault. It's missing guardrails, unclear ownership, and data.

Curious what others here are seeing:

• Where have you actually let an agent execute without a human in the loop, and did it hold up?
• Anyone drawn an explicit "never automate" list, or is it ad hoc?

(Disclosure: I work at Heizen, we build supply chain systems for enterprise CPG/manufacturing — not pitching anything, genuinely want the practitioner read on where the human line should sit.)

Working through Bain's new report "The Rise of Autonomous, Intelligent Procurement" and a few stats stuck out:

- 60%+ procurement productivity gain where AI is effectively deployed

- 3–7% incremental savings on spend

- $180M projected from a single scaled agentic deployment

- ROI up to 5x

The part I keep circling back to: only ~5% of procurement orgs have AI fully deployed. ~60% are in planning or pilot.

Default read I'm seeing on LinkedIn this week is basically "pick the right agentic source-to-pay vendor and capture the upside." I don't think that's what the report actually says.

A sourcing tool waits for a buyer to specify the category, suppliers, criteria, timing. A sourcing agent monitors the category continuously, decides when an event is warranted, prepares the tender, qualifies suppliers, and surfaces a buyer only when a strategic trade-off needs human judgment.

That's not a software upgrade. That's a change in who initiates action — and most enterprise S2P stacks weren't built to host autonomous agents alongside human buyers in the same category.

McKinsey's recent work points the same way — they cite a chemicals company piloting autonomous sourcing in consumables that lifted staff efficiency 20–30% and pushed value capture up 1–3% on the spend in scope. The wins all come from workflow redesign, not vendor swap.

Curious what people on the inside are actually seeing:

- For those piloting AI agents in procurement — what's the actual blocker? Data? Governance? Change management? Vendor immaturity?

- Has anyone seen a deployment where the workflow was redesigned first vs. agents bolted onto existing source-to-pay?

- Are your suppliers deploying agents on their side yet? (My read is the buyer-with-tools / supplier-with-agents asymmetry is going to bite first.)

I've been having a lot of conversations with procurement leaders lately, and there's a topic everyone dances around in public but talks about openly over coffee: agentic AI is about to eat a huge chunk of procurement work, and nobody has a real plan for the people.

Not "AI will augment your team." Not "humans + AI partnership." I'm talking about agents that autonomously run RFQs, negotiate with suppliers within set guardrails, raise POs, chase invoices, flag contract risk, and reconcile three-way matches — end to end, with a human only stepping in for exceptions.

The math gets uncomfortable fast. A typical mid-market procurement org has 60–70% of its headcount on transactional and tactical work: sourcing execution, supplier onboarding, PO management, invoice matching, expediting, basic category analytics. That's exactly the work agents are now demonstrably good at. The remaining 30–40% — strategic sourcing, supplier relationship management, risk, ESG, complex negotiations — still needs humans, but it doesn't need that many humans.

So the honest question: if agents credibly take 60% of the workload in the next 3–5 years, what actually happens?

A few scenarios I keep going back and forth on:

1. The "everyone moves up the value chain" story. Tactical buyers become category strategists. Sounds great. But not every tactical buyer wants to be — or can be — a strategist. And the math doesn't work: you don't need 50 strategists where you had 50 buyers.
2. The quiet attrition path. No layoffs, no announcements. Just don't backfill. Hiring freezes for 2–3 years and the org shrinks by 40% through natural turnover. This is probably what most companies will actually do.
3. The CFO-led contraction. Procurement becomes a 5-person team running 50 agents, reporting into finance. The function as we know it basically disappears.
4. The supplier-side mirror. This one nobody talks about. If buyers deploy agents, suppliers will too. We end up with bot-on-bot negotiation, and procurement value shifts entirely to whoever designs the better guardrails and incentive structures.

What I haven't seen anywhere yet:

• A serious workforce transition plan from any major company
• Honest conversations with procurement teams about what their job looks like in 2028
• Universities adjusting supply chain curricula for this
• Any union or professional body (ISM, CIPS) staking out a clear position

Genuinely curious what folks here think — especially anyone working in procurement right now. Are you seeing agentic pilots in your org? Is leadership talking about the headcount implications, or is it all "productivity gains" framing? And if you're early-career in procurement, are you re-thinking your path?

Not trying to be doomer about it. I actually think the work that's left is more interesting. But pretending the workforce shift isn't coming feels like the same mistake retail and customer service made five years ago.

I've now sat through enough "we tried AI forecasting and it didn't work" conversations to notice a pattern. The technology isn't the problem. The rollout is.

Some context: modern ML forecasting (gradient boosting ensembles, temporal fusion transformers, hierarchical models with reconciliation) consistently beats classical methods by 15–40% on MAPE for the SKUs where it should — mid-velocity, seasonal, promotion-driven, multi-channel. That's been settled science for years now. The M5 competition basically closed the debate.

And yet, most enterprise pilots stall. Not because the models are bad. Because of stuff like this:

1. Starting with the wrong SKUs. Teams almost always pilot on either their top 20 runners (where classical forecasting is already 95% accurate and AI has no room to win) or their long-tail intermittent items (where no model wins because there's no signal). The sweet spot — the 60% of SKUs in the middle that drive most of your working capital pain — is where you should pilot. Nobody does this.

2. No causal features, just history. I've seen six-figure ML platforms deployed where the only input is shipment history. That's expensive ARIMA. The whole point of ML forecasting is that you can shove in promotions, pricing, weather, web traffic, competitor stockouts, macroeconomic signals, and let the model figure out the interactions. If your data team can't get promo calendars and price changes into the feature store, don't bother starting.

3. Forecasting at the wrong grain. Forecasting daily SKU-store when the business plans weekly SKU-DC is a guaranteed disappointment. The model can be technically more accurate and still useless because nothing downstream can consume it. Hierarchical reconciliation is the unsexy part of the stack that actually decides whether the forecast ships.

4. No one owns the override behavior. Demand planners will override the model. That's fine — sometimes they should. But if you don't measure override accuracy vs. model accuracy and feed that back, you end up with a forecasting system that's actually just a planner's gut with extra steps. Half the orgs I've seen don't track this at all.

5. Treating it as an IT project, not a planning transformation. This is the big one. If the S&OP process, KPIs, and incentive structures don't change, the forecast doesn't matter. Planners still get yelled at for stockouts and forgiven for overstock, so they still bias high. Sales still sandbags. The model produces a beautiful unbiased forecast that nobody uses.

A rough playbook that actually seems to work:

• Pick 1 category, mid-velocity SKUs, 12-week pilot. Not the whole portfolio.
• Get clean POS + promo + price data into a feature store before picking a model.
• Run the new model in shadow mode for 6 weeks against the incumbent forecast. Measure MAPE, bias, and forecast value-add (FVA) at the grain that drives the actual buy decision.
• Define what "good" looks like upfront: e.g., "10pp MAPE improvement on B-class SKUs, with no degradation on A-class." Without this, every result is debatable.
• Tie forecast accuracy to a working-capital outcome (inventory turns, stockout rate, expedite freight spend). Forecast accuracy alone is not a business case.
• Build the override-tracking loop on day one, not month six.
• Plan the S&OP process change in parallel with the model build, not after.

The orgs I've seen do this well aren't the ones with the biggest data science teams. They're the ones where the VP of Supply Chain personally owns the rollout and isn't afraid to change the planning process.

Genuinely curious what folks here have seen. Anyone running ML forecasting in production at scale? What was the thing that almost killed your rollout — was it data, change management, or the model itself? And for anyone earlier in the journey — what's the biggest blocker right now?

Not pitching anything. Just trying to compare notes because the public case studies are all sanitized to uselessness.