What a support retainer covers
A support retainer is for businesses that already run ERP and integrated systems and need steady help after go-live. It keeps your finance, stock, sales, operations and reporting systems supported by people who understand your setup, your users and the way your teams actually work. For many SMEs in Centurion, Johannesburg, Pretoria, Durban, Cape Town and Gqeberha, this is the difference between patching issues ad hoc and having a clear support plan in place.
Our retainer agreements are suited to businesses with between 10 and 300 users, multiple branches, or teams that rely on connected systems across procurement, invoicing, payroll hand-offs, stock control, approvals and reporting. We support day to day faults, user queries, small configuration changes, report adjustments and workflow fixes that keep operations moving.
- Priority troubleshooting for ERP and integrated systems
- Minor configuration changes and small workflow adjustments
- Report tweaks and dashboard refinements
- User access support and permission reviews
- Advice on upgrades, patches and maintenance windows
- Guidance for load-shedding related continuity steps and backup routines
How the retainer is structured
We keep the structure simple so you know what is covered, what sits outside scope and how requests are handled. Each retainer is based on the size of your environment, the number of modules in use, the number of branches and the volume of support requests. A single-site finance team in Pretoria will not need the same plan as a multi-branch group in the East Rand with warehouse users, sales reps and head office reporting.
The agreement usually includes a monthly allocation of support hours, a named support contact and an agreed escalation path. Where needed, we also include scheduled health checks and small maintenance tasks such as user clean-up, validation checks, report reviews and interface monitoring. If your systems have seasonal spikes, for example month-end in finance or stock counts in retail, we can shape the retainer around those peak periods.
- Monthly block of support hours
- Priority response based on issue severity
- Named support owner and escalation route
- Scheduled maintenance and health checks
- Optional after-hours cover for critical incidents
What happens during onboarding
Before the retainer starts, we review your current setup so the support team is not starting from scratch. This includes checking the live environment, reviewing users and roles, understanding your custom reports and confirming any integrations with payment tools, warehouse systems, payroll hand-offs or third-party applications. We also look at recurring problems, because the same issue should not keep coming back every month.
The onboarding step gives us a baseline for support and helps set practical expectations. If your team works across branches or remote sites, we document which users are permitted to log tickets, who approves changes, and which issues can be handled immediately versus those that need testing. That way the service stays orderly, and your staff get answers without long back-and-forth.
- Environment review and access audit
- Known issue register and priority list
- Support contacts and approval workflow
- Integration and reporting checkpoint
- Maintenance calendar for planned work
Turnaround times and response standards
Most SMEs need to know how quickly a support team will come back to them, especially when users are blocked from processing orders or reconciling figures. Our retainer support is structured according to severity. Critical issues affecting operations receive immediate attention, while lower priority requests such as report changes or interface tweaks are scheduled into the next support window.
Turnaround depends on the complexity of the problem, but we keep communication steady throughout. A simple user access fix may need only a minor change. A report correction or workflow change may need testing. More involved items, such as a multi-step integration fault or a data correction after a failed import, can take more work, but you will always know where the work stands. We avoid the kind of support experience where people are left in the dark. That is not useful.
Pricing approach for support retainers
We price support retainers in a practical way, based on scope rather than guesswork. The main factors are the size of your user base, the number of systems connected to the ERP, the complexity of your reports and workflows, and whether you need standby cover outside normal business hours. A company with one finance administrator and a few supervisors will need a different support model from a business running multiple branches with stock movement, approval chains and live integrations.
Retainers are usually quoted as a fixed monthly fee for a defined service level, with additional work quoted separately if it falls outside the agreement. That gives you predictable spending and makes budgeting easier for the year ahead. If you need extra hours during audit season, year-end close or a systems upgrade, we can agree those in advance. We do not believe in vague pricing that changes every time someone asks for help.
- Fixed monthly retainer for agreed scope
- Optional ad hoc work outside the agreement
- Scales with users, modules and integrations
- Can include after-hours and priority response cover
Maintenance intervals and ongoing reviews
Support is not only about fixing faults when they appear. Regular maintenance keeps small issues from becoming expensive ones. Depending on your plan, we schedule monthly, quarterly or biannual reviews to check system performance, outstanding tickets, user access, workflow exceptions and report accuracy. For businesses operating through load-shedding or with branch sites in coastal areas such as Durban and Gqeberha, these checks are especially useful because interruptions and humidity can affect connectivity and hardware more than teams expect.
During maintenance intervals we can review integration logs, confirm backup routines, test key processes and advise on upgrade timing. We also look at adoption issues, because sometimes a system problem is actually a training gap or a process that needs tightening. Small refinements at the right time save a lot of admin later. It is better to catch a broken approval rule before month-end than after.
- Monthly service review for open tickets and priorities
- Quarterly system health and access review
- Biannual workflow and reporting check
- Upgrade planning when patches or version changes are due
When a retainer makes the most sense
A support retainer is a good fit if your business depends on the system every working day and cannot afford long delays when something stops working. It is also useful if your internal team is busy, your users need steady guidance, or you have had repeated issues after implementation. Many businesses in Johannesburg, Pretoria, the West Rand and Centurion use retainers to keep support predictable while they grow.
It is especially valuable after go-live, after a merger or restructure, when you add new branches, or when you are preparing for an upgrade. If you need continuity, a consultant who knows your setup and small improvements over time, a retainer gives you a cleaner way to manage support than relying on urgent one-off calls. That usually means less disruption, fewer repeat errors and better use of your internal time.
To request a support retainer discussion, use the enquiry form on our contact page and tell us about your current systems, user count, locations and the type of support you need.
Key facts
| Service area | Centurion, Johannesburg, Pretoria, Durban, Cape Town, Gqeberha, East Rand and West Rand |
|---|---|
| Typical client size | Small to medium businesses, usually 10 to 300 users |
| Support model | Monthly retainer with agreed scope and priority response |
| Common coverage | Troubleshooting, minor enhancements, reporting, user help and system checks |
| Review intervals | Monthly, quarterly or biannual depending on the plan |
| Typical turnaround | Same day for simple issues, 1 to 3 working days for scheduled changes |
