Go-live is not the finish line. It is the day the vendor stops being in the building every day, and the day your own people either own the system or slowly drift back to spreadsheets.
I have seen this drift in maybe a third of the rollouts I’ve been near. It never announces itself. It starts with one person keeping a private file “just in case,” and six months later the official report and the real numbers disagree.
Days 1 to 30: watch behaviour, not features
Forget dashboards for a month. Track three things daily and put them on a wall where people walk past.
- Percentage of transactions entered on the day they happened — target above 90% by week four
- Number of items or customers created by hand instead of chosen from the list — any number above zero is a conversation
- Support tickets by department. The department with the most tickets is usually the one whose process was changed least
One logistics manager told me his team was “fully on board” while the ticket log showed 41 entries from his department in a fortnight. Behaviour tells the truth. Opinions don’t.
Days 31 to 60: hand over the keys
Identify two super users per department — the people others already go to with questions. Give them real authority: they can change a field label, adjust a report layout, and approve small process tweaks without a committee.
Then run your first full month-end close in the new system with no outside help in the room. It will be uncomfortable. That discomfort is the point; it is how knowledge actually transfers.
Days 61 to 90: prove the numbers are trustworthy
- Pick one number the business cares about — gross margin, stock value, overdue receivables — and reconcile it manually against source documents
- Compare it to the system report. Any gap over 1% needs a root cause, not an explanation
- Publish the result to the management team, including the gap. Transparency here buys you years of credibility
- Set a quarterly review where an ERPNext Consulting advisor checks whether the process has drifted from the design
That last item is the one most companies drop first when budgets tighten, and it is the one that pays for itself. Systems don’t fail at go-live; they fail nine months later when nobody is watching.
If you take one action from this, do it this week: ask each department head to name their two super users and write the names down. If they can’t, you’re not finished implementing — you’re just running software.