A Growing Advisory Practice in Umhlanga Needed Cleaner Planning
The client was a professional services firm in Umhlanga, KwaZulu-Natal, with a small but busy team handling consulting work, retainers and once-off projects for clients across Durban and further afield. As the practice grew, the partners were spending too much time checking timesheets, fixing expense allocations and comparing what had been delivered against what had actually been billed.
The brief was straightforward on paper: improve resource planning, keep expenses tied to the right job, and make billing follow the real work done. In practice, the team needed a system that could cope with mixed billing models, changing project scopes and staff working across multiple assignments in the same week. They also wanted something practical for a team that was often on the move, with a few people working from home and others in the office on the same day.
We started by reviewing how jobs were opened, how time was captured and where the handover to invoicing was falling apart. One issue was that project managers were making decisions from spreadsheets that were already out of date by the time they were shared. Another was that expenses were being entered late, which meant invoices went out without all the recoverable costs included. The team needed better visibility before month end, not after it.
What Got in the Way: Time Capture, Approval Delays and Billing Gaps
The main constraints were typical of a growing South African SME, but they still needed careful handling. The advisory practice had a lean internal team, so there was no spare capacity for long admin-heavy changeovers. They also needed to keep billings running during the transition, because stopping the invoicing cycle for even one month would have affected cash flow.
Umhlanga also brings its own practical considerations. Staff were often split between site visits, office work and remote work, so the process had to work well on laptops and phones. Load-shedding added another layer, because the team could not rely on everyone being online at the same time for approvals and corrections. We kept the workflow simple enough that tasks could be picked up in short windows, not only during long uninterrupted sessions.
- Mixed billing models: hourly, fixed fee and monthly retainer work in the same practice
- Late expense capture that pushed recoverable costs out of the invoice cycle
- Manual spreadsheets used for planning, tracking and partner reporting
- Approval delays when project leads were travelling or working off-site
- Need for low-friction adoption by non-technical staff
What We Supplied Across the Four Week Delivery
We delivered a focused ERP and business-systems integration package over four weeks. The first stage was process mapping, where we traced how a matter moved from proposal to delivery to invoice. That gave us the rules for resource planning, job costing and approval routing. The second stage was configuration and integration, linking the core work records to time capture, expense entry and billing so data only had to be entered once.
Custom reporting was important from the start. The partners wanted weekly visibility on utilisation, unbilled time, outstanding expenses and jobs that were drifting over budget. We built reporting views that showed these items by consultant, by project and by billing category. That made it easier to see where capacity was tight and where billing needed follow-up.
We also handled user training and go-live support. Training was practical and role-based, with sessions for partners, project managers and support staff. Instead of a long classroom-style rollout, we worked through real examples from the firm’s own matters. That helped people understand the new steps quickly and reduced the usual hesitation around change. There were a few small adjustments after go-live, as expected, but nothing that disrupted billing.
- Process mapping for project-to-cash flow
- ERP configuration for jobs, time, expenses and invoicing
- System integration to reduce double entry
- Custom reporting for utilisation and margin checks
- User training, adoption support and go-live cover
Results After Go-Live for the Umhlanga Team
Once the new structure was live, the firm had a much clearer view of what was happening in each engagement. Project leads could see planned hours versus actual hours earlier in the week, instead of waiting for month-end summaries. That meant they could rebalance work sooner and reduce the number of small jobs running over budget.
Billing also became cleaner. Because expenses were tied to the right matter at the point of entry, recoverable costs were less likely to be missed. Invoices went out with fewer corrections and fewer back-and-forth queries from the finance side. The firm reported faster approval turnaround and less time spent on manual reconciliations. Put simply, the admin load dropped and the numbers became easier to trust.
For a practice that sells advice and time, that matters. When the team can see what is booked, what is delivered and what is billable, they can plan better and protect margin. It also made partner reporting more useful, because the same information was now coming from one source instead of several disconnected sheets. The result was less duplication and better confidence in the figures.
Lessons We Would Carry Into Another Consultancy Rollout
If we were starting a similar engagement in Durban, Johannesburg or Pretoria, we would follow the same approach: map the actual work first, then configure the system around how the team really operates. That keeps the rollout practical and avoids forcing a small business into a process that looks neat but does not suit client-facing work.
We would also keep the reporting tight from the beginning. Too much reporting creates noise, while too little leaves the partners guessing. The useful middle ground is a few clear views that show utilisation, unbilled work, expenses waiting for approval and jobs nearing their limits. That gives management enough detail to act without burying them in numbers.
Most of all, we would keep training linked to live examples and short support cycles after go-live. In a busy advisory practice, people need to learn the system while still serving clients. The simpler the workflow, the easier it is for the team to keep using it properly once the first rush has passed.
Key facts
| Client type | Professional services advisory practice |
|---|---|
| Town | Umhlanga, KwaZulu-Natal |
| Timeline | 4 weeks |
| Scope | Resource planning, expenses and billing alignment |
| Delivery | ERP implementation, integration, reporting and training |
| Outcome | Cleaner invoicing, better visibility and less manual admin |
