What a custom ERP project actually looks like, in six steps
Custom does not have to mean slow or open-ended. Here is the sequence that keeps a project small, visible and finishable.
Published · 4 min read
A custom ERP has a reputation for running late and over budget. Most of that comes from trying to build everything at once. A project shaped as small, shippable stages avoids it.
1. Map the real process
We sit with the people who do the work and follow one order, one invoice or one shipment from start to finish, including the workarounds. The output is a short written map you can correct.
2. Choose the first slice
Pick the one part that hurts most and can stand alone, such as quotations to invoices, or stock in and out. Everything else waits.
3. Agree scope, price range and milestones
In writing, with what is out of scope stated as clearly as what is in.
4. Build and show every week or two
You see working software early, on real examples, and change direction while it is cheap.
5. Pilot with real users
A small group uses it for real work alongside the old method. We fix what they find, and train them to train others.
6. Go live, then grow
Cut over, keep watching, and add the next slice. Roles, approvals, reports and integrations arrive one at a time, each paid for by the value of the previous one.
What makes it work
A named person on your side who can decide, access to the people who do the work, and a willingness to keep scope small. With those, a custom system is often delivered in stages that each earn their place.