If your implementation is stalled or nobody trusts the system

ERP implementation off track? How to recover a stalled project

Most stalled implementations are recoverable. The software is rarely the reason. The delivery is, and that can be fixed.

By Rob Griffin, Founder and Principal · Updated

Take the free ERP assessmentTalk to our team
The short version
If you only read one thing on this page
  1. 1Stop adding scope. Get an independent review of what was built against how you actually work.
  2. 2Fix what blocks the close, billing and payroll first, then re-plan with a named senior team.
  3. 3Rob Griffin has spent years stepping into implementations that weren’t delivering and restoring trust in them.

Sound familiar?

If more than one of these is true, the project needs a reset, not another change order.

“We’re live, but nobody trusts the numbers.
“The go-live date keeps moving and the budget keeps growing.
“Our partner staffed the project with whoever was available.
“We’ve rebuilt our old system’s problems in the new one.

How we recover an ERP project

Short answer: Pause, assess, stabilize, re-plan, finish. A recovery starts with an honest written list of what’s broken and ends with your team able to run the system without us.

  1. 1StopFreeze new scope. Nothing new gets built until we know what exists.
  2. 2AssessAn independent review of what was configured against how you actually work, and a written list of what’s broken.
  3. 3StabilizeFix what blocks the close, billing and payroll first.
  4. 4Re-planA realistic plan and date, set with the people doing the work, with a named senior team.
  5. 5Finish and hand overComplete the implementation and train your team to run it themselves.
Leadership team reviewing a recovery plan
“He knows how to align teams and deliver systems that work in the real world.”
Ken B.on Rob Griffin
“Dominate didn’t just implement software. They learned our business, down to the crew level.”
Todd H.VP, Bright Star Solutions

Questions we hear from companies in this spot

Can a failed ERP implementation be saved?

Usually, yes. Most failures are delivery failures: unclear scope, undiagnosed data problems, inexperienced staff or a go-live date set from above. Those can be corrected without starting over.

Should we switch ERP partners mid-project?

If the partner can’t name a senior team, explain what’s broken in writing and commit to a realistic plan, yes. On Acumatica, the software company manages partner changes, so the first step is to tell Acumatica.

How long does an ERP recovery take?

It depends on how much was built and how clean the data is. The assessment comes first, and it produces a written plan and date before any new work starts.

Start where you are. Six questions, and you’ll know which path fits your business.

Or call (469) 489-1490. You will talk to a senior practitioner, not a sales rep.

Where to go next

Step 415 ERP implementation mistakesRead the list →Step 3How to choose an ERP partnerThe checklist →AboutMeet Rob GriffinAbout Dominate →
1aThe other side