What these rollout stories cover
The examples in this hub focus on daily legal operations rather than theory. Some firms needed cleaner template control for letters and pleadings, while others were dealing with scattered matter notes, slow handovers or evidence files hiding in shared drives. The stories point to the parts of the platform that matter most in practice, from workflow setup to permissions and secure hosting.
They are not client testimonials and they do not name private matters. Instead, they give a clear read on the setting, the team size and the operational pressure behind each rollout, so a firm in Sandton can compare itself with a practice in Pretoria or Cape Town without guessing.
A quick way to scan the cards
Each listing card is built to help an attorney, practice manager or ops lead spot the relevant pattern fast. Look at the firm type first, then the place, then the operational issue that triggered the project. That usually tells you whether the story is mostly about document automation, matter tracking or review queue control.
- Document-heavy firms: often need template builds, field mapping and approval steps.
- Litigation teams: usually want deadlines, matter visibility and evidence handling in one place.
- Multi-office practices: tend to need permissions, user roles and steadier handovers.
- Growing teams: often start with onboarding, training and data migration.
Document assembly pressure in busy practices
Several stories deal with firms that were tired of manually retyping the same clauses, names and case details into every new document. In those rollouts, the work centred on templates, cleaner data fields and a tighter approval path so staff could generate consistent documents without hunting through old files or copied drafts.
For smaller teams in Johannesburg and Rosebank, the issue was often speed at the point of drafting. For larger practices in Pretoria or Centurion, the problem was control, with several users touching the same templates and each one needing the right version. A clean setup reduces that drift and keeps the file trail easier to follow.
Matter pipelines that do not lose sight of the file
Some firms came to us because matter updates lived in too many places at once. The story cards in this group show how a pipeline can give each matter a visible stage, assigned owner and practical next step. That matters when articles, associates and support staff all need the same current view, especially around deadline heavy weeks.
- Open, pending and closed work stays easier to sort.
- Tasks can be assigned without rewriting the whole matter note.
- Everyone sees the same filing status and follow-up point.
- Supervisors can check workload without pulling separate spreadsheets.
Evidence review in a search-friendly queue
Other stories focus on e-discovery style review, where the challenge was not only volume but order. Teams needed a way to tag, search and review evidence without relying on one overfilled shared drive. The rollout stories show how searchable queues help when documents arrive from many sources and need to be checked against a live matter list.
Data handling also sits here, because legal teams have to keep access sensible and records protected. POPIA-related controls are part of that wider discipline, along with permissions, audit trails and hosting arrangements that suit the firm’s internal rules.
Cities that shape the rollout
The place tags matter because legal workflows often look different from one office network to the next. A firm in Sandton may be managing a fast commercial brief flow, while a practice in Durban has to think about coastal humidity, office spread and document access across teams. Cape Town and Bloemfontein stories often lean into structured handovers and clearer matter ownership.
That is why the hub spans Johannesburg, Pretoria, Cape Town, Durban, Bloemfontein, Centurion and Rosebank. The core software stays the same, but the rollout emphasis changes with team size, file volume and how the office actually works day to day.
Names behind the rollout work
The stories also reflect the people who carry a rollout through. Implementation planning, template work, security checks and user setup sit with different specialists, and that mix shapes the experience a firm sees. In a legal environment, a neat build is only useful if it holds up when a paralegal is preparing a bundle, an associate is updating a matter or an ops lead is checking access.
- Thabo Shezi: overall direction and product oversight.
- Naledi Hadebe: operations and rollout coordination.
- Marelise Smit: template builds and document structure.
- Sibusiso Tau: security and access controls.
- Ayesha Sekgobela: onboarding and user setup.