A stalled ERP rollout taken to production in one quarter
An in-house ERP project had run for over a year without going live. We audited it, reset its scope and put it into production in a single quarter.
Manufacturing · Mid-market discrete manufacturer
- 1 quarter
- Time to production
- 100%
- Manual weekly reports removed
- 6
- Extensions shipped
from 12+ months stalled
all upgrade-safe
The challenge
The internal ERP project had been running for more than a year with no go-live date. The standard modules did not fit the company's tiered pricing or its stock-reservation policy. Operations had gone back to spreadsheets and had stopped trusting the system entirely.
What we did
We audited the existing build and sorted what could be saved from what had to be rewritten. The 80% of the platform that works the same in any business was left untouched. Three processes were different here: priority stock reservation, tiered customer pricing and the weekly operations report. We rebuilt those as upgrade-safe extensions, which add to the platform without editing its core objects. Rollout went one plant at a time, so production never stopped.
More configuration was never going to get this live. It went live on a small number of extensions, built the way the framework intends, that cover the 20% of the business no standard product can know about. We also decided to stop customizing the other 80%.
We judge this kind of work by what happens at the next version upgrade. Nothing in the vendor's own objects was edited, so the extensions get re-tested and the upgrade goes ahead. The spreadsheets went away and stayed away.
Stack
Related case studies
Three CRMs consolidated into one, with the history intact
Three regional sales teams, each on its own CRM, moved onto one platform. Their stage history came across too, so year-on-year forecasts still worked.
A support copilot that shipped because the evals said it could
A support assistant that answers from the company's own documentation. It went from a prototype nobody trusted to production, gated by a test set built from past tickets, and cut first-response time.
A storefront rebuilt to hold up on launch day
The storefront moved to a headless front end and held up under campaign traffic. Marketing got a content model it can edit without raising a ticket.
Have something to build?
Tell us the problem. We'll come back with a plan, a price, and who would build it.
- Free scoping call
- Reply within 1 business day
- No lock-in