AI, Operational Modeling, and the Future of ERP Transformation: A Conversation with Greg Mader and Chris Cappelli of Gray Matter Logic

Enterprise ERP projects are undergoing a significant shift. As artificial intelligence becomes embedded into enterprise software, organizations are rethinking not only how ERP systems are implemented, but also how operational knowledge is captured, modeled, and translated into long-term business value.

At the same time, enterprises are facing growing pressure to modernize without disrupting operations. The rise of AI copilots, intelligent automation, digital twins, and increasingly complex application ecosystems is challenging traditional assumptions about ERP transformation. For implementation partners, success is no longer defined solely by technical deployment, but by their ability to understand how businesses actually operate and to translate that understanding into scalable systems.

In this executive Q&A, Greg Mader, President of Gray Matter Logic, and Chris Cappelli, Executive Vice President, discuss the evolution of ERP implementation, the growing importance of operational modeling, the role of AI in discovery and transformation projects, and why the future may belong to company-specific ERP strategies rather than one-size-fits-all industry templates.

Rethinking ERP Transformation in the AI Era

Q: ERP implementation projects have historically been associated with long timelines, customization complexity, and operational risk. From your perspective, what is fundamentally changing in how enterprises approach ERP transformation today?

A: A few trends are moving at once, and together they’ve changed how we define what an ERP project is.

First, the ERP publishers are getting better. The software is more capable every year, and most platforms are now integrating some form of AI copilot meant to pull more value and more function out of the system you already own. That part is genuinely impressive.

Second, expectations about what even is an ERP in 2026. There’s a live debate right now — does the ERP get stronger and absorb more, maybe as a composable stack of applications coming together, or does it narrow to the system of record for transactions while other applications, including AI systems, move to the front? I’ll state my position on that at a later time. The point for now is that the question is open in a way it wasn’t five years ago.

Third, the buyer got smarter. Users are more educated, they ask sharper questions, and they expect more. Nobody wants to sign up for an 18-month implementation anymore. The expectation now is real, measurable improvement in time to value.

Q: Gray Matter Logic emphasizes tailoring ERP systems around how organizations actually operate rather than forcing businesses into rigid workflows. Why does operational alignment remain so critical, particularly in industries like aerospace, manufacturing, electronics, and logistics?

A: Start with the thing too many people forget: an ERP exists to create efficiency, optimization, and visibility for the business, not the other way around.

There are vendors who walk into a company and say, “You need to change everything to fit the software.” That ends in change-management pain, general dissatisfaction, and, worst of all, the business loses the small, specific things that actually gave it an edge.

It gets more acute in more regulated or traceable or specialized industries.

In manufacturing, the supply chain is built as much on relationships — on being able to call or text the right person — as on any formal sourcing policy. In electronics, you’re working across time zones into Asia-Pacific and Europe to source the right materials.  None of that survives if you flatten it to fit a default workflow.

So, the real question is how you use these systems to create alignment and get the best out of each other. The ERP should be a communication platform, not a control platform.  The companies that understand that difference are the ones that keep their edge.

The ERP should be a communication platform, not a control platform. The companies that understand that difference are the ones that keep their edge.

Operational Modeling as the Foundation for ERP Success

Q: Your “Implementation Blueprint” methodology introduces the concept of building a Knowledge Graph of a customer’s operating model before implementation begins. Why is operational modeling becoming increasingly important in modern ERP projects?

A: Early in my career, a wise advisor named Clark Swinehart told me, “Greg, don’t run ready-fire-aim projects.” It stuck with me, really resonated. Because it’s so easy to jump straight to a solution — to coding and development — without ever confirming the thing actually fits what the project needs.

What we’ve built is the opposite of ready-fire-aim. We use a set of concepts to create a knowledge graph to map what an ERP could be in plain human language and turn it into a representation we call an “Implementation Blueprint,” which is a different kind of digital twin. We build a complete model of the clients business and operations that we can represent however it’s useful: drawings, diagrams, flowcharts. But underneath, we understand not just the mechanics of the business but the actual flows — how one part hands off to the next.

That’s what lets us build an implementation that fits with precision and delivers better results.   We offer faster time to value, but also something far more maintainable.  The company can grow and evolve by adding to and changing the knowledge graph instead of tearing things out. We built this approach by building on the experience of hundreds of customer engagements and the experience is what predictably lets us do it.

Q: The Peregrine platform appears to be designed to reduce the time needed to assess technical deficiencies and implementation requirements. How is AI changing the discovery, planning, and design phase of ERP implementations?

A: Our discovery doesn’t start at kickoff. With  our Peregrine AI, it starts during the first pre-sales conversations. We’re already capturing the small moments: a concern raised in a meeting, a requirement buried in an email, a worry someone mentions in passing. A lot of what looks like office politics is really an unmet need, and you catch those far better when you capture them early.

We have a goal that nobody should ever have to repeat themselves. As requirements surface, we’re refining and solving, not re-asking. Peregrine can agentically scan existing documents and system configurations, memos, diagrams, the million little notes people keep, so that when we do get in a room together, the whiteboarding and the face-to-face sessions are better formed.

I don’t think we’ll ever eliminate those in-person sessions, and we shouldn’t.  But we want to walk in already understanding the business, so the time we spend together goes to the hard problems instead of the basics. That’s how we deliver a superior result.

We want to walk in already understanding the business, so the time we spend together goes to the hard problems instead of the basics.

Beyond AI Copilots: Building Connected Enterprise Operations

Q: Many ERP vendors are heavily promoting AI copilots and automation layers today. In your view, where is the real value of AI inside ERP environments, and where is the industry still overhyping the technology?

A: It’s the right move for the publishers to build AI into their systems. Frankly, without it, these systems get less and less relevant. And the internal, publisher-sponsored AI is genuinely useful for things like labor planning, production forecasting, and technician scheduling.  But that’s the beginning, not the destination.

Here’s where the real value is, and it’s the position I deferred on earlier. The goal is to actually build a common operating picture for the entire organization.

You will only get that when the ERP opens up and extends into the rest of the stack, through better connective tissue to Data Lake technology, PLM or Marketing Automation or other functionality, via MCP or other tools. 

I remember a diagram from years ago laying out the enterprise software stack — ERP, but also PLM, CRM, e-commerce, and more. The integration between all of those stacks have always been, to some degree, a hassle. The companies with the means have always tried to assemble those pieces into something that runs like a single operating system for the business. With AI, that’s more achievable than it’s ever been.

So, the ERP probably stays as one component of a larger enterprise architecture and need to connect better with other systems. The publishers who allow their systems to be managed and orchestrated as part of the bigger picture are building toward where CIOs and enterprises are actually going. That’s the bet I’d make.

Q: As organizations become more dependent on interconnected systems, fragmented operational knowledge often becomes a major obstacle during transformation initiatives. How do you approach capturing institutional knowledge before implementation work begins?

A: We do a few things deliberately. The first you’ve already heard — Peregrine captures from notes, spreadsheets, conversations, and emails across the whole life of the project, even back into pre-sales, so we pick up the character of the organization from those early exchanges.

But we don’t put human, face-to-face work in the backseat. We think it’s essential to spend real time on site to walk the floor, take pictures, and ask people about their part of the process: where they’re stuck, what would let them do better work, what would make the job more satisfying.

Those interviews touch on something some friends of ours named “high-tech anthropology,” choosing to study how people actually use technology and work together. You have to understand those human elements to build something that genuinely solves the problem, instead of something that’s technically correct and useless.

In our case, these elements of  change management, adoption, alliances and frictions between departments  goes into the knowledge graph. Because if you know where the friction is before you start, you can build a system that feels like it was made for people, instead of at them.

Balancing Innovation with Human Expertise

Q: There is growing pressure on enterprises to modernize ERP systems while maintaining operational continuity. What are the biggest mistakes organizations make when trying to balance innovation with business stability?

A: Let me start with the immediate red flag with a type of project that wrecks both innovation and stability at once: trying to do a migration inside an implementation. Customers will float the idea of jumping to the latest version or platform while they’re still mid-implementation. This road ends in tears, every time.

With that out of the way, here’s the part that sounds crazy.

Innovation matters more than operational continuity. I can point to companies large and small that chose stability over innovation again and again, and in the long run they got neither. They ended up behind and scrambling for change.

What actually matters is knowing your appetite for change and being willing to be more than a little uncomfortable — to operate, as a friend of mine puts it, at a healthy sweat. That’s how you build and defend a real competitive advantage.

I’m not saying gamble with the fundamentals. Back office, accounting, HR- those stay continuous and uninterrupted. But a certain amount of risk is the whole reason we do these projects. Be straight about it: there will be moments of discomfort while you build the system that’s going to carry you for the next decade.

Q: AI is increasingly being positioned as a way to accelerate ERP implementation and optimization. Where do you still believe human expertise, industry knowledge, and consulting experience remain irreplaceable?

A: AI is going to keep accelerating implementation and optimization. 

This puts real pressure on the lower and middle tiers of my industry. The body-shop model is not the future of this profession. AI supercharges experienced people instead and lets them spend their time on real customer problems.

So where do humans stay irreplaceable? Experienced, educated people have always used new tools, and AI is no different.

We pride ourselves on being the best partner we can be, and a lot of that happens standing in a client’s facility, eating lunch with their team, catching the one offhand comment about how something could be better. That sparks an optimization you’d never find in a requirements doc. Trust, collegiality, friendship, and treating ourselves as continuous learners is how we partner with AI and show up for our customers.

Q: ERP consulting itself appears to be evolving rapidly as AI becomes more embedded into enterprise transformation projects. How do you see the role of ERP implementation partners changing over the next few years?

A: Two things about this I find genuinely fascinating.

First: no kid grows up dreaming of becoming an ERP consultant. And yet it’s one of the most rewarding professions I can think of.   Most of us stumbled into it or heard about it from a friend. It’s more craft than job. You learn from other people, from your customers, from reading, from the implementations themselves. A good chunk of our staff are former customers. They liked the work and our approach to it enough to make it their profession. I’m proud of that every time.

Second: this industry is aging out. The first generation of ERP consultants retired a few years back, and the second generation isn’t far behind. So, we’re working hard to bring in new blood, and we’re proud of the relationships we’ve built with universities and with individuals all over the country.

The partners who win from here will invest in their people and also invest in AI tools and in the management practices that get the most out of people and tools together. It’s not enough to say you have intense customer focus, even though we do. You have to understand how customer expectations are shifting and build deliberate learning into the work, for the humans and the AI both. That’s the craft, updated for the moment we’re in.

The partners who win from here will invest in their people and also invest in AI tools.

The Shift Toward Company-Specific ERP

Q: Looking ahead, how do you expect AI-assisted operational modeling, intelligent automation, and industry-specific ERP strategies to reshape enterprise transformation projects across complex industries?

A: This might be the most important question our industry faces right now.

For years, industry-specific ERPs and accelerators were the mitigation strategy, a way to avoid over-customized, unmanageable, expensive systems. AI changes that formula.  We’re moving past industry-specific ERPs toward something better: company-specific ERPs. That’s an enormously creative and fertile place to be standing right now.

Operational modeling has been around in many ways for decades; I remember the UML days of my youth. What we are seeing now is operationalizing digital twins into something that actually is the blueprint for the optimized implementation that works.

Intelligent automation, edge computing, real-time telemetry from every corner of an operation have existed in some form for years. What was missing was a way to manage it. Real-time data from across an enterprise used to overwhelm an ERP. AI doesn’t just absorb it; it turns a flood of data into actual information products you can use.

Honestly, this is the most creative moment of my career. The chance to use these models, this automation, and this ability to tailor to a specific customer makes this a remarkable time to be part of this profession.