Every founder has heard an ERP horror story: the eighteen-month implementation that shipped two years late, the system staff quietly refused to use, the consultancy invoices that kept arriving long after the value stopped. The stories are real — but the cause is rarely the software.
ERP projects fail for organisational reasons: scope defined around features instead of workflows, no internal owner, and a big-bang go-live that asks the whole company to change habits overnight.
Start with the workflow, not the module list
The wrong question is “which modules do we need?” The right question is “which three processes, if they ran without spreadsheets and WhatsApp messages, would change our month?” For most SMEs the answer is some combination of sales orders, inventory, and purchasing — occasionally payroll.
Implement those first, prove the value, and let adoption pull the next phase. An ERP that runs three processes well beats one that runs fifteen processes badly.
The defaults are not your business
Off-the-shelf ERP defaults encode someone else’s business. If your team has to bend their actual process to fit generic screens, they will go back to spreadsheets within a month — and they will be right to.
Configuration around how your business actually operates is the single highest-leverage investment in the entire project. It is also the work most implementations skip, because it requires understanding the business, not just the software.
Adoption is a project of its own
Plan the human rollout with the same seriousness as the technical one:
- Phase by team, not by module — get one team fully working before the next starts
- Train on real company data, never demo data
- Keep a feedback channel open and fix friction within days, not quarters
- Run the old process in parallel for one cycle, then switch off deliberately
What it looks like with a digital department
The reason we bundle ERP implementation into a subscription rather than a fixed-bid project is simple: the work does not end at go-live. Reports evolve, workflows change, new staff need onboarding, and integrations accumulate.
With an embedded team, the same people who configured the system keep running it — which is exactly the continuity that turns an ERP from a risky project into a quiet piece of infrastructure your business stops thinking about.
Superdot Labs Team
Your complete digital department