| |
THE OPERATIONS
BRIEF
|
|
|
|
THE ERP VALUE GAP
|
|
By Bill Murphy · Powered by Colony Spark
|
|
| |
|
| |
|
Hi there,
The gap widening across mid-market manufacturing and distribution right now is not who bought the most sophisticated ERP. It is who is still actively running it six months after the consultant left.
This issue is about that gap. Why it compounds, where it shows up, and the operating rhythm leadership teams can build now to close it before the next quarter of margin drift.
— Bill
|
| |
The gap is not who has AI.
It is who is still running it six months after they turned it on.
The pattern is consistent across manufacturing and distribution right now. A company buys an ERP. They go through the implementation. The consultant team runs the project, trains the team, and gets everything live. Metrics improve. The project closes.
Then the consultant leaves. The team goes back to running the business. The system runs exactly as configured, recording every transaction, processing every order, doing exactly what it was set up to do the day the project ended.
Twelve months later, products have been added. Customers have shifted their buying patterns. Tariffs have restructured the cost stack. A supplier that wasn't a concern before now represents 40% of spend in a tariff-exposed category. The system is still running. It just doesn't know any of that.
|
This is not a technology problem. It is not an implementation problem. It is a discipline problem.
|
The companies pulling ahead are not the ones that bought the most sophisticated ERP. They are the ones still actively running it: connecting it to AI, measuring what's changed since the last configuration, asking the system what it knows that the leadership team hasn't asked yet.
|
Three things shifting at the same time
1. The tools are now accessible. Oracle launched the NetSuite AI Connector Service in April 2026, enabling manufacturers and distributors to connect Claude, GPT, and other AI models directly into live ERP data via the Model Context Protocol. Role-based access controls. Over 100 prompt templates. Bring your own AI model.
2. The investment is happening, but the value isn't following. Rockwell Automation's State of Smart Manufacturing report found that 95% of manufacturing leaders have invested or plan to invest in AI in the next five years. The spend is real. The discipline isn't.
3. The margin environment has no patience for systems that drift. A static ERP that isn't actively connected to current operating reality is annoying in a normal market. With tariffs moving, freight unpredictable, and customer mix shifting, it is expensive. The ERP knows. Most leadership teams never ask.
|
|
The advantage in 2026 is not who has the best AI tool. It is who is still running the tools they already have, every quarter, connected to the operating decisions that actually matter.
|
|
|
| |
Owning the tool is not
the same as orchestrating it.
Ryan Hawk, PwC, on what compounds after deployment
Ryan Hawk, global and U.S. industrials and services leader at PwC, framed the operating reality cleanly in a March Manufacturing Dive interview.
|
"As automation becomes ubiquitous, the advantage shifts from who has tools to who can orchestrate them across the enterprise."
|
Ryan Hawk
Global & U.S. Industrials and Services Leader, PwC · Manufacturing Dive, March 4, 2026
|
|
Hawk's point is not about technology selection. It is about what shows up after deployment. PwC's analysis found that automation in manufacturing is expected to more than double by 2030. The companies that will compound the value of that automation are the ones that can connect it to how they actually operate. Not just turn it on.
The research tracked a consistent pattern: manufacturers who treat AI as a deployment project and move on get a fraction of the value that manufacturers treating it as an operating discipline extract over the same period.
The framing translates directly to the ERP environment most mid-market manufacturers and distributors are sitting in right now. Most bought the tools. Most went live. Most stopped there. The orchestration gap is not abstract. It is the distance between a system that accurately records every transaction and a system that the leadership team actively uses to make decisions every quarter. Most ERP systems don't degrade. They just don't get asked anything new.
|
The question worth sitting with
When is the last time your ERP told you something you didn't already know? Every quarter that passes without someone connecting current operating reality to the system's data model is another quarter where margin pressure, supplier concentration, customer attrition, and inventory drift accumulate without showing up in a conversation that can do something about them.
|
|
|
| |
The Quarterly ERP Health Snapshot.
A working pattern for closing the gap.
Not a dashboard. A dashboard shows what is happening. A snapshot connects what is happening to what it means for the next decision.
The pattern we keep seeing across mid-market operators is the same. The system was working. The team was busy. But nobody was asking the ERP the right questions every quarter. Margin was drifting. Supplier concentration was building. Customer mix was shifting. The data was there. The operating rhythm was not.
A Quarterly ERP Health Snapshot sits between the ERP and the leadership team. It connects to live ERP transaction data, prior quarter benchmarks, and supplier pricing history. The output is a brief, not raw data: a short read that surfaces what changed since last quarter and one decision worth making about it. The framing below is what the operators we have seen run this well actually receive.
|
What the leadership team receives every quarter
Margin drift report. Where margin eroded since last quarter and what drove it. Price change, cost increase, customer mix shift, volume decline. Specific, not aggregate.
Inventory health check. Slow-moving SKUs with capital tied up. Out-of-stock risk in active product lines. Over-procurement flags where seasonal patterns were missed.
Customer concentration watch. Which accounts grew, which shrank, and what the revenue mix looks like now versus six months ago. The ERP has the data. The snapshot surfaces the pattern.
Supplier exposure summary. Which suppliers represent the highest pricing leverage based on actual order history and category concentration. In this tariff environment, this is the analysis the CFO should see every quarter.
|
|
Plus: One Decision
The single highest-priority operating question the data is raising for the leadership team. A snapshot that only describes the past is a report. One that surfaces the next decision is an operating tool.
|
|
Path 1: Through your ERP partner
Add a quarterly intelligence engagement on top of the system you already paid to implement. Most ERP partners can scope this as a recurring layer of post-implementation work; some are doing it already.
|
|
Path 2: Build it internally
Use the AI tools now connected directly into NetSuite, Acumatica, and other cloud ERPs through the new MCP integration layer. The capability is no longer the constraint. The discipline of running it every quarter is.
|
|
The leadership teams asking the ERP four hard questions every ninety days are the ones who will compound through this margin environment. The ones still treating go-live as the finish line will keep paying for a system that runs accurately and tells them nothing. Build the rhythm now, while you still have options.
|
|
|
| |
|
THE OPERATIONS BRIEF
By Bill Murphy · Powered by Colony Spark
|
|
Building the rhythm to ask your ERP something new every ninety days? Or wrestling with a question this issue didn't answer? Hit reply, I read every one. Bill
|
You're receiving this because you subscribed to The Operations Brief.
Unsubscribe
|
| |
|
