Ask a business owner what an ERP project costs and you’ll get a licence number. That number is almost never the problem. The problem is everything that happens after the go-live date slips.
I reviewed a 250-person building products company that budgeted $120,000 over seven months. It took fourteen months and $310,000. Nobody stole anything. The money leaked out of ordinary places.
The hidden invoice nobody shows you at the start
- Nine months of double entry — two finance staff at 12 hours a week each, about $46,000 in payroll
- Overtime in the warehouse during three failed cutover attempts, $18,500
- Two experienced order desk staff who quit and were replaced through recruiters, $27,000
- Repeat stock counts and manual reconciliations, 400 hours across teams, roughly $21,000
- Orders shipped late to four major accounts, two of which reduced volume the following year
The licences were $38,000 of the total. Everything else was friction. That ratio is normal, and it is the reason scoping matters more than features.
Four scoping rules that keep projects boring
Boring is what you want. The engagements that go well share the same four habits, and an experienced ERPNext Consulting partner will insist on all of them before signing anything.
- Phase one covers the three transactions that touch cash — quote to order, order to invoice, purchase to payment — nothing else
- Every phase has a written finish line, a named business owner, and a date that does not move because of a new idea
- Data rules are agreed before migration starts: which customer duplicates get merged, which items get retired, how far back history goes
- The acceptance test is written by the users who will live in the system, not by the project team
Notice what’s missing from that list: reports, dashboards, custom screens, nice-to-haves. All of it can come in phase three, when people already trust the basics.
The question that predicts failure before it happens
Ask the project sponsor this: “Who is losing two hours a day for the next ten weeks, by name?” If the answer is vague, the project will slip. If the answer is three specific people with their calendars already blocked, you will go live on time.
One more thing worth doing: put a real number on your internal labour. Every hour of double entry during a rollout costs you twice — once in wages, once in the errors it creates. Track it weekly. When the sponsor sees a $4,000 weekly bleed, scope conversations get very short, very fast.