ERP implementation services for SMEs: what "implementation" should include
Business Systems · 11 min read
Two ERP proposals can both say "implementation included" and mean very different things. One means installing the software, setting up users and a two-hour training session. The other means mapping your processes, cleaning your data, testing month-end with your staff and being on call during the first weeks after go-live.
For a small or medium business, the gap between those two is often the gap between an ERP that runs the business and one that staff quietly work around with the old spreadsheets.
This guide sets out what a complete ERP implementation should cover, so you can compare proposals properly. It applies whether you are implementing a packaged product through a partner or a custom ERP built for you.
Why "implementation" means different things to different vendors
The software is usually the easy part. The hard parts are understanding how your business actually works, getting clean data into the new system, and getting people to change how they work. Some vendors price all of that in. Others price the software and leave the rest to you, or charge for it later as extra days.
Neither approach is dishonest if it is clear. The problem is when you only find out which one you bought after signing.
The eight parts of a complete ERP implementation
1. Process discovery
Someone maps how work really flows, not how the policy document says it flows. That means talking to the people in the warehouse, workshop, branch or dispatch office, not only management. The output should be written workflows, including exceptions such as returns, partial deliveries, credit notes and stock write-offs.
Ask for: documented process maps you can keep.
2. Solution design
This decides how the system will handle each process, which modules are in the first phase, which system owns each type of record (for example, whether customers live in the ERP or in Sage), and what reports are needed. Reporting belongs here, not at the end. If you only discover a missing report at the first month-end, the pressure is at its worst.
Ask for: a design document or scope that lists modules, users and roles, integrations and reports for phase one.
3. Data clean-up and migration
Your data probably lives in Excel sheets, a Pastel or Sage company, an old system and some people's heads. Before it moves, it needs cleaning: duplicate customers merged, product codes standardised, obsolete stock removed. Then someone has to decide how much history to bring across, and how opening balances and stock quantities will be set and checked.
Dirty data in means untrustworthy reports out. This step is often underestimated in both time and effort.
Ask for: who cleans the data, who validates it, and how opening balances are signed off.
4. Build or configuration
For packaged ERP, this is configuration: settings, workflows, permissions, document templates. For custom ERP, this is the build of the agreed modules. Either way, you should see working software regularly, not just at the end.
Ask for: regular demos against the agreed scope.
5. Integrations
Common connections for SA SMEs include accounting (Sage, Pastel, Xero), payment gateways, POS, WhatsApp Business or SMS notifications, courier systems and eCommerce stores. Each integration needs its own design: what data moves, in which direction, how often, and what happens when it fails.
Ask for: a list of each integration with its direction, frequency and error handling.
6. Testing with real scenarios
Vendors test that the software works. You need to test that it works for your business. That means running realistic scenarios with your own staff: a normal day, a month-end, a stock take, a return, an approval that gets rejected, a branch transfer. This is user acceptance testing, and it needs time on your side.
Ask for: a test plan built from your real scenarios, and a sign-off step before go-live.
7. Training
Floor staff and office staff need different training. Drivers or technicians on phones need short, practical sessions on the few screens they use. Finance needs to understand how the ERP feeds the books. Train on real examples from your business, not generic demo data. Nominate a super-user in each department who can help colleagues after launch.
Ask for: a training plan by role, and training materials you can reuse for new staff.
8. Go-live and hypercare
Go-live should be planned: which day, which branch or department first, whether old and new systems run side by side for a short time, and who makes the call to switch fully. The first weeks after go-live are when most issues surface. A proper implementation includes a period of close support, often called hypercare, with faster response times and someone checking in daily.
Ask for: the go-live plan, rollback plan, and what support looks like in the first weeks.
Commonly excluded items to check in any proposal
| Item | Why it matters | Question to ask |
|---|---|---|
| Data clean-up | Often assumed to be the client's job | "Who cleans and validates our data?" |
| Historical data | Bringing across years of history takes time | "How much history is included?" |
| Integrations | Each one is real work | "Which integrations are included, and which are extra?" |
| Custom reports | Standard reports may not match what you use | "Which of our reports are included?" |
| Staff time for testing | Your team's hours are a real cost | "How much of our time will testing take?" |
| Training for all roles | Training only admins leaves the floor behind | "Who gets trained, and how?" |
| Post go-live support | Issues surface after launch | "What support is included after go-live, and for how long?" |
| Ongoing licences or platform fees | Recurring costs continue after the project | "What will we pay each month or year after go-live?" |
South African realities to plan for
- Month-end and VAT periods. Avoid going live right before month-end or a VAT submission. Plan the cutover so finance can reconcile cleanly.
- Load-shedding and connectivity. If branches, yards or field staff lose power or signal, decide how they capture work offline and how it syncs later. Test this before go-live, not after.
- Moving off Pastel or Sage data. Plan how existing company data, customer and supplier records and balances will be mapped and checked, and whether accounting stays in Sage with the ERP connected to it.
- POPIA. An ERP holds customer, supplier and staff information. Set role-based access, keep audit trails on stock and financial changes, and make sure any provider processing personal information on your behalf is covered by a written contract, as Section 21 of POPIA requires.
- Staff on their own phones. If staff use personal devices, design for small screens, limited data and quick logouts.
What your team has to put in
No implementation partner can do this alone. You will need:
- An owner-level sponsor who can settle disagreements between departments.
- A project lead on your side who answers questions quickly and chases internal decisions.
- Process experts from each department for discovery and testing.
- A finance lead to define how operational data flows into the books and to sign off opening balances.
- Super-users who learn the system first and help others.
If you cannot free up these people, the project will slow down whatever the vendor does.
Go-live readiness checklist
- Process maps signed off by each department.
- Phase one scope agreed, with exclusions written down.
- Data cleaned, migrated, and opening balances validated by finance.
- Each integration tested, including what happens when it fails.
- User acceptance testing completed with real scenarios and signed off.
- Every user trained for their role, and super-users named.
- Offline and power-cut behaviour tested where relevant.
- Access permissions reviewed.
- Go-live date chosen away from month-end pressure.
- Rollback plan agreed.
- Hypercare support contacts and response times confirmed.
Frequently asked questions
Can I implement ERP without hiring a consultant?
For a very small, simple setup, some businesses do. For most SMEs, an experienced partner saves time and mistakes on process mapping, data migration, integrations and testing. Whoever implements it, your own team still needs to own the process decisions and testing.
How long does it take to set up ERP software?
It depends on the number of modules, the state of your data, the integrations and how quickly your team can test and make decisions. Phased implementations get a first module into daily use sooner. Ask for a timeline after discovery, when the scope is clear.
What are the hidden costs of implementing ERP?
The usual ones are data clean-up, extra integrations, custom reports, your own staff's time for testing and training, support after go-live, and ongoing licence or platform fees. A complete proposal names each of these.
How much does it cost to train staff on new ERP software?
It depends on how many people, how many roles and how different the new process is from the old one. Budget for training time by role, a super-user in each department, and refresher sessions after go-live.
Will ERP software work with my existing business processes?
Discovery and testing should answer this before go-live. With packaged ERP, test your real scenarios in a demo. With custom ERP, the system is designed around your process. In both cases, it is a good moment to simplify steps that no longer make sense.
Plan your implementation with us
ThinkinCode designs, builds and implements custom ERP systems for SA SMEs, from discovery and data migration through testing, training and support after go-live. We build custom systems rather than reselling or implementing packaged ERP products. If a packaged product suits you better, we will tell you, and this checklist will still help you hold any partner to a complete implementation.
Email [email protected] to book a Discovery call with a senior engineer, or read about our ERP development approach. If your first pain is approvals and notifications rather than full ERP, start with business automation systems.
Ready when you are
Book a Discovery call
Tell us what you are trying to fix. We will tell you honestly whether custom software is the right next step.