Skip to content

CasepathProductLegal

The bank's pack in. Letters out.

The bank's documents come in, letters go out on the firm's own Word template, and the waiting period counts itself.

  • Where it standsWorking demo on sample data
  • Year2026
  • What we builtFirm workspace, phone approvals and a public demo

Casepath runs home-loan collections work for South African law firms. The bank's documents come in, staff check every detail against its page, letters go out on the firm's own Word template, partners approve with one click and the waiting period counts itself.

[01] Where it started

Every detail, retyped into Word.

Every detail has to match the bank's documents, and every deadline has to be right.

  1. The bank's pack

    When a home-loan account falls behind, the bank sends the firm a pack of documents: the loan agreement, a certificate of balance, the title deed and a credit bureau report.

  2. A Section 129 notice

    From that pack, the firm prepares a Section 129 notice under the National Credit Act for every address the debtor can be reached at.

  3. Where it started

    Casepath started with an attorney who does this work every week. The practice software tracked the matters, but the letters were still drafted in Word, every detail retyped and every deadline counted by hand.

  4. Two days later

    Two days after that conversation, there was a first working version to click through.

How it ranBefore

  • Practice softwareTracked the matters, while the letters were still drafted by hand.
  • WordNames, ID numbers and amounts retyped from the bank's documents.
  • A calendarBusiness days counted by hand from each posting date.

What was breaking

  1. 01

    Names, ID numbers and amounts have to match the bank's documents exactly.

  2. 02

    A partner must sign off every letter, and nothing may change after that.

  3. 03

    The next legal step depends on counting business days from the right posting date.

[02] What we built

From the pack to the post.

A firm workspace for staff and partners, a phone view for approvals on the move and a public demo on made-up data.

  1. Workspace and phone

    A firm workspace for staff and partners, and a phone view for approvals on the move.

  2. A public demo

    A public demo that runs on made-up data, with a demo clock that skips ahead to show the deadlines working.

01 / 03

Firm workspace

For staff and partnersWeb, private per firm

Casepath follows one debtor from the bank's pack to a posted letter, with a firm view of every matter around it.

  • Field-by-field checks against source pages
  • Letters on the firm's own Word template
  • Partner-only approval with frozen files
  • Posting records and a business-day countdown
Real screenCheck and approve

5 real screens · tap to enlarge

  • Check and approve

    A partner works through letters waiting for approval, each one filled in on the firm's own template.

  • Every detail, next to its page

    Staff confirm names, ID numbers and amounts against the bank's documents before a matter opens. These are made-up sample documents.

  • One matter

    Where the matter stands, which letters are waiting, the debtors and addresses, and what happened so far.

  • Firm view

    Every case, its step, who is handling it and what is late, across the whole firm.

  • Letter templates

    The firm highlights the changing parts of its own Word letter in yellow, uploads it, and Casepath fills it in for every debtor.

Screen 01 / 05

02 / 03

On a phone

For partners on the movePhone browser

What needs attention today, what is late and the approval queue, on a phone.

  • Today's list and late warnings
  • Approvals from anywhere

3 real screens · tap to enlarge

  • Today

    What needs attention today, and what is already late.

  • A matter on the move

    A late warning letter, with the next step one tap away.

  • Approvals from anywhere

    Partners can clear the approval queue from a phone.

Screen 01 / 03

03 / 03

Public demo

For firms trying it outWeb

The demo runs the whole workflow on made-up documents, with a demo clock that skips ahead to show the deadlines working.

  • A sample firm with made-up data
  • A demo clock for deadlines

2 real screens · tap to enlarge

  • The demo site

    The public demo explains the workflow and opens a sample firm with made-up data.

  • On a phone

    The demo site on a phone.

Screen 01 / 02

The bank's pack

When a home-loan account falls behind, the bank sends the firm a pack of documents.

  1. 01

    Loan agreement

  2. 02

    Certificate of balance

  3. 03

    Title deed

  4. 04

    Credit bureau report

Casepath, screen: Every detail, next to its page
Every detail, next to its page. Staff confirm names, ID numbers and amounts against the bank's documents before a matter opens. These are made-up sample documents.

Private to each firm

Staff prepare and post letters; only partners approve them, manage templates or invite colleagues.

  • Its own private deployment
  • People join by invitation from a partner
  • Every sign-in needs a second step from an authenticator app

[03] How it works

From the bank's pack to the next step.

Staff confirm the details, Casepath fills the letters, a partner approves and the waiting period counts itself.

  1. Private per firm

    Each firm runs on its own private deployment. People join by invitation from a partner, and every sign-in needs a second step from an authenticator app.

  2. Only partners approve

    Staff prepare and post letters; only partners approve them, manage templates or invite colleagues.

  3. People enter details

    Casepath does not read documents automatically yet. Staff enter and confirm the details, and checks for South African ID numbers, amounts and dates catch common mistakes.

  4. Human confirmation stays

    A reading service would only ever be a starting point: the same human confirmation is required either way.

  1. Staff

    Drop in the bank's documents and confirm what each one is.

  2. Staff

    Confirm every field next to its page. Conflicts need a reason; a missing document needs a partner.

  3. CasepathTakes over here

    The firm's Word template is filled in for every address on record.

  4. Partner

    One click records who approved and when. The file is frozen and fingerprinted.

  5. Staff

    Record the posting date and the registered-post tracking number for each letter.

  6. Casepath

    Ten South African business days, public holidays included, then the matter is ready for the next step.

Real screenEvery detail, next to its page

[04] What we changed

Checked once, used everywhere.

Check each detail once, against its source, and let the letters, the approval and the deadline use the checked value.

  1. Checked once

    Check each detail once, against its source.

  2. Used everywhere downstream

    Everything downstream uses the checked value: the letters, the approval and the deadline.

Before: Practice software, Word, A calendar. Now: Working demo on sample data.Drag, or use the arrow keys
  1. 01

    Before: Retype each detail from the bank's pack.

    Now: Confirm each detail next to the page it came from.

    Casepath, screen: Every detail, next to its page
  2. 02

    Before: Copy the details into a Word letter.

    Now: The firm's own Word template, filled in for every debtor and address.

    Casepath, screen: Letter templates
  3. 03

    Before: Chase partners for signatures.

    Now: Partners approve with one click; the file is frozen and fingerprinted.

    Casepath, screen: Check and approve
  4. 04

    Before: Count business days on a calendar.

    Now: Casepath counts ten business days, public holidays included.

    Casepath, screen: One matter
  5. 05

    Before: Ask around to find out what is late.

    Now: One firm view of every matter, its step and what is late.

    Casepath, screen: Firm view

[05] What changed

Working end to end, on sample data.

The whole workflow works end to end in the demo, from the bank's pack to a counted deadline.

Casepath, screen: The demo site
The demo site. The public demo explains the workflow and opens a sample firm with made-up data.
First conversation about the collections workflow to First working prototype
2days
The bank's pack
4
From the bank's pack to the next step.
6steps

Where it stands

Working demo on sample data

22 Sep 202630 Sep 2026

Dates from our project records and release history.

  1. Update

    First conversation about the collections workflow.

    then, +2 days
  2. Build

    First working prototype.

    then, +6 days
  3. Update

    Security review and hardening done; 329 tests.

  4. Next

    A firm's private version, once its attorneys approve the signing procedure, template and deadline policy.

Dates from our project records and release history.

  • The full workflow runs in the demo, from the bank's pack to a counted deadline.

  • Approved letters cannot change silently; a correction needs a new approval.

  • 329 automated tests cover ID numbers, amounts, business days and template filling.

  • Each firm gets its own private deployment, with invitations and two-step sign-in.

Decisions that sit with the firm

  • Signing procedureApproved by the firm's attorneys
  • TemplateApproved by the firm's attorneys
  • Deadline policyApproved by the firm's attorneys
  1. Finished in the demo

    Checked details, finished letters, partner approval, posting records and a counted deadline all work in the demo.

  2. Before real matters

    Before a firm runs real matters through it, its attorneys approve the signing procedure, the template and the deadline policy. The private deployment gets its hosting and retention settings.

  3. The firm decides

    Those decisions sit with the firm, not with the software.

Built with

The tools behind it.

See the full toolbench
  • Next.js
  • React
  • Convex
  • Tailwind CSS
  • Vercel

Also in the build: Convex Auth, docxtemplater, PDF.js

Have a related problem or idea?

Is your team retyping the same details into Word? Show us the workflow.

Start a conversation