When an ERP or systems project stalls, the cause is rarely the software. It is usually unclear requirements, a scope that keeps changing, data that turned out messier than expected, or nobody on the business's side with the authority and technical knowledge to hold the vendor to the brief. Getting it back on track means finding which of those it is, resetting the scope and plan, and putting someone on your side of the table who can make decisions and check the work.
Signs a project has stalled
- Go-live has moved more than once, and nobody can say with confidence when it will happen.
- Every meeting produces new questions rather than decisions.
- The vendor keeps asking for more time or budget, and you can't tell whether the request is fair.
- Staff testing the system say it doesn't match how they work.
- Data migration keeps being pushed back "until the system is ready".
- Integrations with your accounting, job or stock systems were "out of scope" and are now urgent.
Why projects stall
Requirements written from the brochure, not the work. If nobody sat with the people who do the job, the system is built for how the business is meant to work, not how it does. The gaps show up in testing.
No technical authority on the client side. Vendors are good at delivering what is specified. When nobody on your side can read a design document, challenge an estimate or say "that isn't what we need", decisions drift and change requests pile up.
Scope that keeps moving. Every new idea added mid-project costs time. Without a clear owner deciding what is in this phase and what waits, the finish line keeps moving.
Data left until last. Old data is almost always messier than expected. Leaving the migration until the end turns it into the critical path.
Integrations treated as extras. The new system has to exchange data with your accounts, job, stock or CRM systems. If that wasn't planned, it becomes the reason you can't go live.
How to get it back on track
- Stop and take stock. Write down what has been delivered, what is left, what has been spent and what is in dispute. Talk to the people doing the work on both sides.
- Reset the requirements. Go back to how the business actually works, and confirm what the system must do for go-live, separately from what can come later.
- Cut the scope to a workable first phase. A smaller go-live that works beats a large one that never arrives.
- Put a technical authority on your side. Someone who can approve designs, check estimates, push back where the work doesn't meet the brief, and make day-to-day decisions with the vendor.
- Start the data work now. Map, clean and test-migrate the data in parallel, so it isn't the last thing holding up go-live.
- Plan the integrations properly. Decide how the new system will exchange data with your accounts and other systems, and build that into the plan.
- Run delivery in the open. Short, regular delivery meetings with a shared board of what is in progress, blocked and done.
Having someone on your side of the table
The most common missing piece is a person on the business's side who understands both how the work is done and how the system is being built, and who has the authority to make decisions. We have played that role ourselves as the client-side technical authority on a company-wide move to Microsoft Azure, from requirements and tender through to cutover and handover. You can read how that project ran.
Frequently asked questions
Should we switch vendors if the project has stalled?
Not as a first step. Switching resets the learning curve and often costs more than fixing the plan. Take stock first; if the vendor genuinely can't deliver, you'll have the evidence and a clear brief for the next one.
Who should be the technical authority?
Someone who understands both how your business works and how the system is being built, and who has the authority to make decisions. In businesses without a senior IT person, that is often an independent consultant or a fractional CTO.
How long does it take to get a project back on track?
Taking stock and resetting the plan usually takes weeks, not months. How long the rest takes depends on how much is left to build, but the reset itself is quick.
Can you help with a project another firm is delivering?
Yes. We can work alongside the vendor as your technical authority, review designs and estimates, and take on the data migration or integrations if they are the sticking point.
If your ERP or systems project has stalled, book a free initial chat. We'll tell you honestly what is holding it up and what it would take to get it moving. See also our software selection and fractional CTO services.