What Practical AI Looks Like for an ERP Customer
Read Part 1
Read Part 2
In 2026 the AI conversation usually collapses into two camps, and both are wrong.
The first says AI is transformational and inevitable, already remaking every industry, and if you’re not moving fast you’re falling behind. That’s not entirely wrong. But it’s pitched at companies with data teams and cloud infrastructure. It isn’t pitched at a mid-market manufacturer with 250 employees running an ERP they implemented ten years ago.
The second says AI is mostly hype. Vendor noise, unproven returns, not ready for real operations. That’s not entirely wrong either. But it’s become a convenient excuse to wait, and the companies using it to put off a decision are starting to notice the gap between them and the ones who moved is getting harder to close.
Neither camp gets you anywhere. What helps is a straight answer to a specific question: what does practical AI look like for a company running a mid-market ERP today?
Want to see this answered on a live ERP, not a slide? Join us for AI ERP Insights: Cut Through the Noise with InsightsAI — July 29 at 11:00 AM ET.
Start With the Data You Have. Then Clean What Matters.
The assumption that stops most mid-market operations from moving on analytics is the belief that they have to build a perfect data foundation first. Clean up the whole ERP. Consolidate into a warehouse. Hire a BI developer. Then, someday, get to AI. That all-or-nothing thinking has cost a lot of companies twelve to eighteen months they didn’t need to lose.
The truth cuts both ways. You don’t need spotless data to start. The production history, purchase orders, labor records, delivery numbers, and inventory movements in a mature ERP system are good enough to answer real questions today. But don’t kid yourself that the data is clean. Most systems carry years of drift: duplicate part records, inconsistent customer codes, work orders never closed, fields that different people use differently. That’s normal. It’s also what quietly eats away at trust in every report you run.
Start with the data you have, and let it show you what to clean. Put an analytics and intelligence layer on top of live ERP data and two things happen at once. You get answers to operational questions right away, and you get a clear, ranked picture of where the underlying data can’t be trusted. Cleanup stops being an open-ended, twelve-month project you fund on faith. It becomes a focused effort aimed at the specific data that’s costing you decisions right now.
That’s why this isn’t a one-tool job. We treat trustworthy data as the foundation and give you a path to it. A data health check that scores where you actually stand. Targeted reconciliation for the inventory, WIP, and GL problems quietly costing you. And InsightsAI as the layer your whole team uses to ask the ERP questions from day one. The more that reconciliation work resolves in parallel, the more you can lean on what InsightsAI tells you, but you don’t have to wait for that to start getting value.
What Answerable Really Means
A VP of Operations we surveyed framed the problem this way:
“Better reporting fields, easier ability to make custom reports without the need of gurus.”
Vice President, Operations · WM Synergy 2026 Voice of the Customer Report
That word. Gurus. The ERP has the data. Getting to it takes specialized knowledge, how to work the reporting module, which fields to pull, how to join data across modules. That knowledge lives with one or two people. Everyone else waits.
These aren’t edge cases. They’re the everyday reality for teams running mid-market ERP. The data is there. The only questions are how long it takes to get to it, and how much you can trust it when you do.
Practical AI removes the wait, and surfaces the trust gaps as it goes.
An operations manager types: why did our delivery performance drop last month? The answer comes back in seconds from live ERP data. No report request, no query. Just the answer, with the causes already identified.
This is guided decision support, not autonomous action, not AI making calls without you. The people still make the decisions. InsightsAI makes sure they have the right information to make them faster and with more confidence.
What Separates Practical AI From the Noise
ERP-native connection, not a generic connector. A general-purpose AI bolted onto an ERP through a generic API is not the same as a tool built for that ERP’s data model. The difference shows up right away in the quality of the answers. Most implementations use an indirect connection model backed by a purpose-built data layer, designed for that ERP’s schema. Connection patterns can vary depending on your environment, which is why the fit conversation matters.
Predictable pricing, not usage billing. The AI tools most discussed in the enterprise market charge by token consumption. For a mid-market company without anyone watching the meter, that means costs you can’t predict. The right tool charges a flat price per seat each month. Finance can budget it, so it gets approved.
Delivered by your partner, not a new vendor. A partner who has implemented your ERP dozens of times can connect an analytics layer in weeks, not months, because they already know the schema, the setup, and the quirks of your environment.
Human-in-the-loop by design. InsightsAI is designed for guided decision support. Your team remains in control. The system surfaces information, flags anomalies, and generates plain-English narratives so your people can make faster, more confident decisions. This supports progressive automation, not autonomous execution.
What the First 90 Days Look Like
The first conversation is 30 minutes, and it’s a business discussion, not an IT audit. What are your top three visibility gaps? Which decisions take too long?
Connecting and setting up a standard environment typically takes one to two weeks, though this can vary depending on your ERP configuration and environment. Dashboards are pre-built for the way mid-market manufacturers and distributors actually work.
By weeks three and four, the analytics layer is live. Your leaders are asking questions and getting answers, and the first data problems worth fixing are already visible. The AI narrative layer, the part that flags anomalies and explains what changed without being asked, comes on shortly after.
Within 90 days, your team stops asking what the data says and starts asking why. That shift, from pulling data to analyzing it, is where the value starts to compound.
Book a 30-Minute Fit Conversation →
Stay tuned for the final part of our four part series…
Frequently Asked Questions
ERP analytics is built on your ERP’s data model, the specific schema, field relationships, and operational logic of your system. A general-purpose AI tool connected to an ERP through a generic API doesn’t understand that structure. The result is answers that are technically correct but operationally meaningless. ERP-native analytics understands what your data means, not just what it says.
Yes. InsightsAI connects to Infor Visual, Infor CSI/SyteLine, Acumatica, and XA. Most implementations use an indirect connection model backed by a purpose-built data layer, though configuration varies by environment. The fit conversation with our InsightsAI team will clarify what the right approach looks like for your setup.
InsightsAI is designed for human-in-the-loop decision support, meaning your team remains in control. The system surfaces information, flags anomalies, and generates plain-English narratives so your people can make faster, more confident decisions. It supports progressive automation and guided workflows. It does not take autonomous action without human review.
InsightsAI is seat-based, a flat monthly fee per named user. No usage overages, no token charges. Finance can budget it like a standard SaaS subscription. It is sold and delivered by WM Synergy, the same team that implemented your ERP.
Sources: WM Synergy 2026 Voice of the Customer Report · Infor.com, Industry AI and Machine Learning · Diginomica, “Infor in the AI Age” (April 2026) · top10erp.org, “AI in ERP: The Next Wave” (2026)