What CEOs Should Know Before Starting an ERP Selection Project

Most CEOs treat an enterprise resource planning (ERP) selection project as a capital decision. Approve the number, name a sponsor, ask for a status update once a quarter. That instinct is reasonable. It is also one of the most reliable reasons these investments underdeliver.

The system you choose will shape how your company plans, schedules, buys, builds and reports for the next decade. But most selection efforts get run as software evaluations, which means the decision that defines your operating model is made by people who were never asked to think about your operating model. That gap is what this article closes.

The temptation is to hand the effort to your CIO and expect a clean technical deployment. It rarely works that way. The core of an ERP program is process work: standardizing how jobs move between functions, deciding which local practices survive and agreeing what a number means before anyone reports it.

None of that is an IT decision. It belongs to you and to your operating leaders, or it belongs to nobody. We often guide our clients to frame the effort as a question about the business they intend to run in five years, not the software they need this year. ERP is an operational transformation, and treating it as a technology refresh puts the work in the wrong hands from day one.

If your operating leaders are not in the room, you are buying software rather than choosing how your company will run.

The most consequential work happens months before a demo is scheduled. It is the unglamorous part: mapping how orders actually flow, where planners override the system, why month-end close takes eleven days and which reports your team quietly rebuilds in spreadsheets.

Skip that and your requirements become a wish list assembled from vendor marketing. That means every conversation with a vendor becomes a conversation on their terms. Structured process work ahead of selection gives your team something a vendor cannot supply: a defensible picture of the operation you are trying to change.

Before anyone builds a shortlist, you should be able to answer a short set of questions:

• which operating decisions your company gets wrong today, and how often
• which processes must be identical across sites and which can stay local
• what a successful first year looks like in operational terms, not system terms
• who has the authority to settle a disagreement between finance and operations
• what you are willing to change about how the business works

Vendors will show you an impressive range of capability. That display is real, and it tells you almost nothing about whether the system suits your business. A long feature list is a statement about what software can do somewhere. Fit is a statement about what it will do here.

So push your team and your vendors past capability claims and into your specifics. How does the system handle a bill of materials (BOM) that changes three times during a build? How does it reconcile inventory when receiving happens on second shift and posting happens the next morning? How does it schedule when your longest lead time comes from a single supplier? Measuring business fit instead of feature lists is the difference between a system your people use and one they work around.

You may be thinking, ‘the demo covered all of that.’ Demos are built to sell, and a scripted demo will not reveal operational reality unless your team writes the script from your own transactions.

Your finance leader and your operations leader do not agree about how inventory should be valued. Your sales leader and your plant leader do not agree about what a promised date means. Those disagreements exist today. Selection does not create them; it exposes them.

That exposure is useful, if you treat it as your work rather than the project manager’s. A project manager cannot arbitrate between two executives. When you leave those calls unmade, teams resolve them locally, and the local resolutions become configuration. The result is a system that encodes your organization’s unresolved arguments and then reports on them inconsistently forever.

Our experts have found that the projects that stabilize fastest are the ones where the CEO settled two or three contested definitions early, in writing. The executive alignment problem behind many ERP failures is rarely about capability. It is about decisions nobody was willing to force.

Funding the project signals that it matters. Attending it signals that it matters more than the thing you skipped to be there. Your team reads the second signal, not the first. When you miss three steering meetings in a row, the message lands clearly: this is not important enough for your time.

Sponsorship is a cadence, not a title. It means a standing slot on your calendar, a short list of questions you ask every month and a visible willingness to make unpopular calls. Ask about outcomes rather than configuration status:

• which decisions are waiting on an executive and how long they have waited
• what has been added to scope and what came off to make room
• which operational metric this phase is supposed to move
• where the team is working around a process rather than fixing it

Those four questions take fifteen minutes a month and surface most of what goes wrong.

Ownership does not mean running the project. You should not be reviewing configuration decisions or sitting in requirements workshops. It means defining the operational outcome, resolving the conflicts that only you can resolve and holding the standard when the schedule pressures your team into shortcuts.

It also means accepting a slower start. Selection done properly takes longer at the front and far less time at the back. Companies that compress the front end almost always pay for it after go-live, in stabilization work, workarounds and reports nobody trusts. A disciplined enterprise technology selection process protects the years that follow.

The organizations that get this right are not the ones with the best software. They are the ones where the CEO treated the choice as a decision about the business and stayed close enough to make the hard calls quickly.