← Back to Field Notes

June 11, 2025 · The Bloomfield Team

How to Spot a Bad ERP Implementation Before It Costs You a Year

Panorama Consulting's 2024 ERP report found that 74% of ERP projects in manufacturing exceed their original timeline. The average overrun is 7.5 months. The average cost overrun is 2.5x the initial budget. For a mid-size manufacturer spending $250,000 on an ERP implementation, that means $625,000 and two years before the system is fully operational.

The warning signs show up early. Within the first 90 days of an implementation, you can see whether the project is headed toward a successful go-live or a slow-motion disaster. Here are the seven indicators that predict failure.

1. No One Has Mapped Your Actual Workflow

The implementation partner shows up with a standard configuration checklist. They ask about chart of accounts, bill of materials structure, and inventory locations. They do not ask the estimator how they build a quote. They do not walk the floor with the shop foreman to see how jobs actually move between machines. They do not sit with the purchasing manager to understand how material orders get placed.

Every ERP system ships with an assumed workflow. That workflow was designed for a generic manufacturing operation. Your operation has 50 to 200 deviations from the generic model, built up over years of adapting to your specific customer base, machine mix, and team strengths. If the implementation partner does not document those deviations in the first 30 days, the system will fight your team instead of supporting them.

2. Data Migration Gets Pushed to "Phase 2"

Your historical job data, customer records, material pricing, and vendor performance history are the most valuable assets in your operation. If the implementation plan treats data migration as a cleanup task to handle after go-live, you will launch with a system that knows less about your business than the spreadsheets it replaced.

We wrote about the real value of ERP data in depth. The short version: five years of job cost data, quoted-versus-actual comparisons, and supplier pricing history are the foundation of every intelligent decision your team makes. Leaving that behind is starting over.

3. The Shop Floor Team Was Not in the Room

ERP implementations that involve only the owner, the controller, and the IT consultant fail at a much higher rate than those that include the people who will use the system daily. The estimator who quotes 30 RFQs per month. The scheduler who manages machine loading. The receiving clerk who enters POs against deliveries. These people know where the current system breaks and where the new system needs to work differently.

If they were not in the requirements meetings, the new system will have the same gaps as the old one. You will have spent six figures to move from one set of workarounds to another.

4. Customization Requests Start Before Training Ends

Early customization requests are a signal that the base configuration does not match how your operation works. A few are normal. More than five in the first 60 days suggests the implementation partner did not do adequate discovery or chose a system that does not fit your business model.

Every customization adds cost, extends timeline, and creates a maintenance burden for future upgrades. The right sequence is: configure the base system to match your workflow as closely as possible, train users on the configured system, run a pilot period, then identify the gaps that require customization based on actual usage data.

5. Go-Live Keeps Moving

One schedule adjustment is expected. Two is a yellow flag. Three or more postponements mean the project has lost its way. Each delay increases cost (the implementation partner bills hourly), extends the period where your team is running two systems simultaneously, and erodes confidence in the project.

If go-live has moved twice and you are less than halfway through the implementation, pause the project and conduct an honest assessment. It is cheaper to reset at month four than to push through to a broken go-live at month fourteen.

6. Reporting Gets Minimal Attention

The point of an ERP system is visibility. If the implementation plan dedicates more time to data entry workflows than to the reports and dashboards your management team will use to run the business, the system will capture data without producing insight.

Before go-live, your team should know exactly how to answer these questions from the system: What is our current backlog by machine group? Which jobs are running over quoted hours? What is our actual delivery performance for the last 90 days? What is our quoting win rate by customer segment? If the system cannot answer these questions on day one, your production dashboard needs more work before launch.

7. The Implementation Partner Sells Features You Did Not Ask For

Advanced planning and scheduling modules. Quality management add-ons. Customer portal integrations. These are all valuable tools for a mature ERP environment. During initial implementation, they are scope creep. Every additional module adds configuration time, training requirements, and points of failure.

A good implementation follows a specific sequence: core financials and order management first, production and scheduling second, advanced analytics and integrations third. Each phase is stable before the next begins. An implementation partner who pitches add-on modules during Phase 1 is optimizing their revenue, and that revenue comes at the expense of your timeline.

What to Do If You See These Signs

Document the specific issues. Schedule a meeting with the implementation partner's project manager and your internal project lead. Present the concerns with examples. Ask for a revised project plan that addresses each one.

If the response is defensive, vague, or involves yet another timeline extension, consider bringing in an independent assessor. A half-day audit by someone who has seen 50 ERP implementations can tell you whether the project is salvageable or whether cutting losses now is the smarter financial decision.

The broader lesson: your ERP is infrastructure. How well it works determines how well every system that connects to it performs. Getting the implementation right is the foundation for everything that follows.