Why change management matters in ERP rollouts
When a business moves to a new ERP or connects more systems together, the software is only half the job. Staff must understand what is changing, why it matters, and how their day to day tasks will look once the new process goes live. Without that support, projects can stall, reports get mistrusted, and people fall back to old spreadsheets. In our work with SMEs in Johannesburg, Pretoria, Durban, Cape Town and Gqeberha, we see the same issue again and again: the technical build is ready, but the business is not yet aligned.
Our change management service is built to keep those gaps small. We work with owners, managers and end users to prepare the business for each stage, from planning through testing and go live. That includes communication planning, role based training, process walkthroughs, and support for supervisors who need to answer questions on the floor. The aim is practical adoption, not just sign-off on a project plan.
What is included in our change management support
We tailor the support to the size of the project and the number of users involved. A 12-person team in Centurion needs a different approach from a multi-site business with branches in the East Rand, West Rand and coastal offices. We start by checking how the current process works, who is affected, and where resistance is likely to appear. From there, we build a clear plan for communication, training and follow-up.
- Stakeholder mapping and impact assessment
- Change communication plan for owners, managers and staff
- Process maps showing current and future workflows
- Role-based user guides and training notes
- Readiness checks before testing and go-live
- Supervisor support and issue triage after launch
- Adoption tracking, feedback capture and refresher planning
We also help identify practical concerns that affect adoption, such as shift work, branch handovers, loading times during load-shedding, and access for teams working from different sites. If the process depends on approvals, stock movement, invoicing or job cards, we make sure those hand-offs are clear before users are asked to work in the new system.
Our step-by-step approach
We keep the process structured so that everyone knows what is happening and when. The exact timeline depends on scope, but most projects follow the same core steps. This helps reduce confusion and gives management something useful to measure, not just a pile of meeting notes.
- Discovery: We review the current workflow, user groups, pain points and any likely resistance.
- Planning: We define the change plan, communication schedule and training needs.
- Preparation: We brief managers, draft user messages and align process owners.
- Testing support: We help users understand what to test and how to log issues properly.
- Go-live support: We stay close to the team during launch and the first busy period after cutover.
- Stabilisation: We review adoption, follow up on gaps and adjust the support plan where needed.
This structure works well for businesses that cannot afford long downtime or repeated rework. It also helps when the same process needs to be rolled out to several branches at once, because each site can be prepared with the same message and the same expectations.
Turnaround time and project pacing
For smaller change management engagements, we can usually start within 1 to 2 weeks after the brief is confirmed, depending on project load and the readiness of your internal team. A focused assignment for a single department may run for 2 to 4 weeks. Broader ERP change support for multiple departments or branches often runs alongside the implementation itself and may continue for 6 to 12 weeks, with follow-up sessions after go-live.
We work to realistic milestones rather than forcing a fixed template. If your finance team is closing month end, or your warehouse is under pressure to keep dispatch going, we schedule sessions around the business cycle. That matters in South African SME environments where the same people often handle more than one role and cannot sit in meetings all day. We keep the pace steady and the instructions practical, with clear actions after each workshop.
Pricing approach and what affects cost
Our pricing is based on scope, user count, number of sites and the level of support needed. A simple change readiness plan for one team is priced differently from a multi-site rollout with training, communications and post-launch support. We quote after a proper review of your workflows, existing systems and the level of business impact involved. That way you are not paying for work you do not need, and there are no surprises once the project starts.
Things that affect the fee include the number of departments affected, how many process maps need to be redrawn, whether managers need extra coaching, and whether support is needed after hours or over a cutover weekend. If the business operates across Centurion, Durban and Cape Town, travel and site coordination may also form part of the scope. We keep billing clear, with deliverables listed upfront and maintenance or support retainers separated from once-off project work.
Post go-live maintenance and adoption checks
Change does not end on go-live day. In most projects, the first 30 to 90 days are where adoption either sticks or slips. We recommend scheduled maintenance intervals after launch so the business can catch issues early and keep users confident. This is especially useful where processes changed a lot, or where a branch has limited in-house system support.
- Week 1: Daily or near-daily check-ins for key users and managers
- Weeks 2 to 4: Weekly issue review, process correction and refresher guidance
- Month 2: Adoption review with reporting on problem areas and support trends
- Month 3: Stabilisation meeting and decision on refresher training or workflow changes
After that, many SMEs prefer a light support retainer so they can call on us for new users, revised procedures or extra coaching when staff change. This is often a better fit than waiting for problems to build up. It keeps the process current, supports compliance with internal controls, and helps new staff settle in faster.
Key facts
| Service type | ERP and systems change management |
|---|---|
| Primary focus | Communication, adoption and process alignment |
| Typical turnaround | 2 to 12 weeks depending on scope |
| User support format | Role-based guidance, workshops and go-live support |
| Coverage | Centurion, Johannesburg, Pretoria, Durban, Cape Town, Gqeberha, East Rand and West Rand |
| Maintenance interval | Weekly to monthly after go-live, based on project size |
