ERP Implementation & Consulting
From selection to go-live, without the six-figure disaster
Most ERP projects fail on process, not software. I map how your business actually runs, choose the right platform for that reality, configure it around your workflows, migrate your data cleanly, and stay with your team until the system is the way people work — not a licence you pay for and ignore.
What you end up with
- One system of record instead of twelve spreadsheets
- Inventory, purchase, sales and accounts reconciled daily, not monthly
- Month-end close cut from weeks to days
- Owners get real numbers without chasing staff for reports
Engagement: Discovery sprint from a fixed fee
Signs you need this
If two or three of these sound familiar, it is probably worth a conversation.
- You run the business from spreadsheets that only one person fully understands
- Stock on the system and stock on the shelf routinely disagree
- Month-end close takes more than a week and still needs corrections afterwards
- You are quoted wildly different prices by ERP vendors and cannot tell which is honest
- Every new branch or product line means more people rather than more capacity
What is actually delivered
Not a statement of intent — the concrete artefacts and outcomes you receive.
Process & requirement blueprint
A documented as-is and to-be map of every core flow — procure-to-pay, order-to-cash, inventory, manufacturing, payroll touchpoints — signed off before a single module is configured.
Platform selection with a scorecard
ERPNext, Odoo, Zoho, Tally-plus-layer or custom, scored against your processes, budget, team capability and growth plan. You see the reasoning, not just the recommendation.
Configuration & customisation
Chart of accounts, item masters, warehouses, tax and GST setup, approval workflows, print formats, role permissions, and custom modules where the standard product genuinely does not fit.
Data migration & reconciliation
Cleaned, de-duplicated and reconciled masters and opening balances, migrated with a verification report your accountant can sign.
Training & adoption
Role-based training for every user group, SOP documents, recorded walkthroughs, and a hypercare window where I sit with your team through the first close.
How the engagement runs
- 01
Discovery
Two weeks inside your operation: interviews, shadowing, document and data review.
- 02
Blueprint
To-be process design, platform scorecard, gap list, phased rollout plan and honest budget.
- 03
Build
Configuration, customisation, integrations and migration in reviewable sprints.
- 04
Go-live
Pilot, parallel run, cutover, and hypercare through the first month-end close.
- 05
Scale
Reporting layer, automation, next-phase modules and capability transfer to your team.
ERP Implementation: common questions
That is the real risk, not the software. Adoption is designed in: role-based training on your own data, written guides at each desk, named internal champions, and a firm date when the old spreadsheet stops being an option. Leaving the old path open is the most common reason ERP projects quietly fail.
It gets cleaned before it gets moved. Duplicate items, inconsistent customer records and opening balances that do not reconcile are fixed first, then migrated with a verification report your accountant can sign off. Migrating a mess just makes the mess faster to query.
Yes, and I usually recommend it. A phased rollout — sales and inventory first, then purchase, then manufacturing — means you get value from the first module while the last is still being built, and each phase teaches you something that improves the next.
A focused SME rollout covering sales, purchase, inventory and accounts typically runs 8–14 weeks from discovery to go-live. Manufacturing, multi-location or multi-entity setups usually run 4–7 months. I phase the work so you get value from the first module before the last one ships.
There is no universal best. ERPNext suits businesses that want low licence cost and deep customisation. Odoo suits teams that want a broad app ecosystem and polished UX. Zoho suits sales-led businesses already in that ecosystem. The decision should follow your process complexity, internal IT capability and five-year plan — which is exactly what the selection scorecard measures.
Three reasons, in order: processes were never documented, so the software encoded chaos; no one owned adoption, so staff kept their spreadsheets; and the project was treated as an IT purchase rather than an operating change. Every engagement I run is designed against those three failure modes.
Yes — a meaningful share of my work is recovery. I start with an independent audit of configuration, data integrity and adoption, then give you a straight answer on whether to fix, re-implement or migrate, with the cost of each path.
ERP Implementation in your industry
The problems look different in each of these, so the way I approach them differs too.
Services that usually go with this
Business Process Automation
Remove the manual work that quietly eats your margin
Accounting, Reconciliation & Revenue Assurance
Stop losing money you never knew you were losing
AI & Agentic Automation
Hand the boring, repeated work to software
Want a straight answer on your situation?
Thirty minutes, no pitch. I'll tell you what I would do and what it costs.