Building your own case management system, and the two jobs it cannot do
Airtable, Make and an AI model will get you something that fits your practice better than the software you are paying for. Here is what it really costs to keep running, and the point where a homemade system becomes a liability with your name on it.
The build usually starts the same way. You are paying for software you fight with, you ask it to do something that feels simple, and it will not. So you open Airtable, wire it to Make, point an AI model at the messy parts, and within a fortnight you have something that fits your practice better than the thing you were paying for. That is not a fantasy. Capable solos do it every year and some of them never go back.
This page is not going to tell you it cannot be done. It is going to tell you what it costs, which parts hold up, and the two jobs where a homemade system stops being a productivity project and starts being a liability you are personally on the hook for.
What a homemade stack genuinely does better.
It fits your workflow exactly
No vendor models your practice the way you do. A build you control matches your intake questions, your stages and your naming, with none of the fields you will never use. This is the real advantage and it is a big one.
Automations you can actually change
When a step changes you edit the scenario yourself that afternoon, instead of filing a feature request and waiting two release cycles for an answer that may be no.
The monthly cost looks tiny
A few base subscriptions and some API credits. On a spreadsheet of line items it beats per-seat legal software comfortably, and that comparison is the one most people run.
You understand every part of it
Nothing is a black box. When something goes wrong you know precisely where to look, which is more than most people can say about the software they license.
The subscriptions are not the cost.
The build is a weekend. The maintenance is forever, and it lands on the person with the highest hourly rate in the building.
Count it honestly for one year. A fortnight of evenings to get to something usable. Then a few hours most months when a form changes, an API deprecates, an automation silently stops firing and you find out three weeks later from a client. Say four hours a month once it settles, which is conservative for anything touching billing. At a $300 hourly rate that is roughly $14,400 of your time a year, and it is time billed to nobody.
Then there is the part that does not show up until it matters. A system only you understand is a system only you can fix. The week you are in trial, or in hospital, or simply on holiday, your firm's intake and billing sit behind a set of scenarios nobody else can read. Every solo who has built one knows this feeling and most of them describe it the same way, as the thing they think about at two in the morning.
What a build has to prove
BalancedThe moment it touches trust, you are building a compliance system.
Everything above is a productivity project. A client ledger is not. The obligation is not to keep good records, it is to be able to prove the records were never wrong, on a day someone else chooses, about a period you may not remember. That is a different kind of software and a different kind of risk, and it is yours personally rather than your vendor's.
- Nothing stops the overdraw. A base will accept any number you type. Paying one client with another client's money is a shortfall the moment it happens, however briefly, and however quickly you fix it.
- Revision history is not an audit trail. It shows a cell changed. It does not show who moved money, against which matter, and why, in a form you can hand to an auditor.
- You are the vendor now. When the reconciliation is questioned, "my automation had a bug" is your problem, not a third party's. There is nobody to escalate to.
The other one that does not survive a homemade build.
A conflict check across every party
Searching your matter table finds clients. A real check covers opposing parties, spouses, corporate affiliates, witnesses and the consultation that never opened a file. That is a data model, not a search box, and retrofitting it into a base you already built is harder than starting from one that assumed it.
Answering the security questionnaire
Corporate and insurer clients ask who is hosting their data, under what certification, and what happens when someone leaves. SOC 2 Type II and a signed BAA are answers. A personal Make account is not, and that conversation tends to arrive with the client you most want to keep.
Where to draw the line.
The firms that get this right rarely build everything or buy everything. They put the regulated core on software that carries the obligation, and they build the parts that are genuinely theirs.
Worth building: the referral tracker your practice depends on, the intake questionnaire nobody else asks, the report you look at every Monday, the odd integration between two things only you use. These change often, break harmlessly, and are exactly where a vendor will never serve you well.
Not worth building: the client ledger, the conflict database, the audit trail, and anything a regulator can ask you to produce. Not because you could not, but because the day it is questioned you want the answer to be a system of record rather than a scenario you wrote at midnight eighteen months ago.
CaseFuze has an open API for exactly this reason. Keep your build for the parts that make you different, and let the ledger be something you can point at.
Run it against your build. Not against a demo.
You already know what your system does well, which makes you the best possible judge of what a platform has to beat. CaseFuze is $49 per user per month with everything included, no tiers and no compliance add-on. Run it alongside what you built, through a real reconciliation and a real month-end, and decide on evidence rather than a sales call. One seat is a fine place to start, and your data exports whole if you go back.
Common questions about building your own.
Can I do trust accounting in Airtable if I am careful?
What actually breaks first in a homemade system?
Is it cheaper than case management software?
Can I keep the parts of my build I like?
What happens to my build if I hire someone?
How hard is it to move what I built into CaseFuze?
The software that does this for you.
CaseFuze handles the ledger, the statement, and the checks. $49 per user per month.