Start with the work your firm wants to remove
Budgeting starts with the pressure points in the firm, not with a rough guess at a subscription fee. A practice that wants cleaner document assembly may spend more on template design, while a team battling loose matter tracking may need more work on workflow configuration and permissions. The number in Rand depends on how many people will use the platform, how many matter types need setup, and how much old data has to be moved without upsetting live work.
Map the daily pain first. A litigation team in Sandton may need fast matter stages and evidence review queues. A conveyancing or commercial team may need document assembly that cuts down copy paste errors and keeps versions in order. Those differences matter because they shape the implementation effort, not only the software itself.
Break the budget into clear cost lines
A sensible budget separates fixed items from project work. That makes it easier to compare suppliers and spot where the effort sits. The monthly fee may be only one part of the picture.
- Software subscription or licence cost
- Implementation planning and project setup
- Template builds for letters, pleadings, notices or forms
- Workflow configuration for matter stages and task routing
- Permissions setup for attorneys, paralegals and support staff
- Data migration from shared drives, spreadsheets or older systems
- User training and admin training
- Secure hosting setup and access control
- Evidence imports and review queue configuration
- Go live support and health checks
Some firms also set aside a small reserve for incident response or extra clean-up where file names, matters or scanned evidence arrive in poor order. That reserve is useful in offices where several departments have used their own naming habits for years, and nobody wants a messy cutover week.
Estimate migration work before you move a single file
Migration is often the budget item that gets underestimated. Moving data from shared drives, inboxes or informal folders takes time because every matter may carry a different structure, naming style and document history. The cost is not only copying files. It includes checking folder logic, matching matters to the right users, cleaning duplicates and deciding what stays archived.
If the firm handles evidence-heavy work, the migration effort can grow quickly. Scanned records, images, correspondence and attachments need a sensible structure so people can search them later. In Johannesburg and Pretoria, firms often want clearer control over large matter sets, while Cape Town and Durban offices may be more concerned with long-term access and secure storage in humid coastal conditions. That kind of detail shapes the setup work and the budget.
- Count the number of active matters to move
- List the file types that need importing
- Mark any material that must stay restricted
- Decide who will validate the migrated data
- Set aside time for testing before go live
Training costs less than fixing confusion later
Training is not a soft extra. It is the part that turns software into a usable system. If attorneys know how to assemble documents but support staff do not know where templates live, the firm will still lose time. If administrators understand matter setup but nobody knows how permissions work, the risk moves into daily operations.
Budget for different levels of training. User training covers the people who draft, update and close matters. Admin training covers those who handle templates, access rules, workflows and document structure. In larger teams, one short session is rarely enough because different practice groups work in different ways. A firm in Bloemfontein may need a very different handover from a commercial office in Rosebank, even if both use the same platform.
Training also has an internal cost. The person leading the project may step away from fee earning work to gather documents, test templates and answer staff questions. That time should be counted in Rand even when no invoice is attached.
Build internal ownership into the numbers
A legal-tech rollout does not run on software alone. Someone inside the firm has to own decisions, approve changes and keep the team aligned when deadlines are tight. If no one has that role, small issues sit unresolved and the platform never settles properly.
Internal ownership usually sits with a partner, operations lead, practice manager or senior administrator. The person does not need to do every task, but they do need time for review, sign-off and coordination. For a firm with several branches, such as Sandton, Centurion and Johannesburg, that role may also include keeping the same rules across offices so matters are handled in one standard way.
Good budgets recognise that ownership is labour. If the firm expects one person to approve templates, check evidence imports and manage user access, that person needs protected time. The cost sits in the project even when it never appears on a supplier invoice.
A practical budget checklist for the partner meeting
Use this checklist before the firm approves a change budget. It keeps the discussion grounded in work, not guesswork.
- How many users need access on day one
- Which matter types need templates and workflows
- What data must be migrated, and from where
- Who approves template wording and document structure
- Which staff need training, and at what level
- What security controls or permission limits are needed
- Whether evidence review needs searchable queues
- Who will carry internal ownership after go live
- What old process will be retired or reduced
Once those answers are on the table, the budget conversation becomes more useful. You can see whether the firm needs a lighter setup or a fuller rollout with more automation. It also helps the team avoid paying for features that do not fit the way the office works.
Keep a reserve for the first operating cycle
Even a careful rollout benefits from a modest reserve. The first weeks often reveal naming gaps, permission tweaks, template changes or matter stage adjustments that were not obvious during planning. A reserve gives the firm room to fix those items without having to stop the project and go through a separate approval round.
For legal work, that reserve is useful because deadlines do not wait for tidy administration. A firm may need a stronger approval step for sensitive files, a cleaner evidence import structure, or a better way to separate active matters from archive material. POPIA considerations also belong in the budget in a general sense, especially where access control and data handling need tighter rules. When the reserve is built into the plan, the team can settle the system properly instead of patching it under pressure.
The final budget should feel like a working plan, not a gamble. If the figures cover software, migration, training and ownership, the firm has a clearer path to a system that supports daily legal work without drowning staff in clutter.
