WoolsackOpen the demoEvery matter, every deadline, and the dates that end a claim.
Matter management, conflict searching, time recording and billing, built around the way a file actually runs in practice — not a generic CRM with the words changed.
No sign-up, nothing to install. A fictional firm with fictional clients — open anything you like.
| Delgado v. Northline Freight Systems | 44 days |
| Meridian Senior Living — lease renewal | 17 days |
| Okonjo v. Brightline Retail Group | 74 days |
Three things go wrong on a file, and they go wrong everywhere.
Whatever a firm runs on, the same three failures cause the claims, the write-offs and the awkward conversations with the insurer.
Nobody owns the deadline
A key date lives in one timekeeper's calendar, or in the back of one person's mind. When they are on vacation, or they leave, it lives nowhere at all.
Conflicts are checked by memory
Someone searches the client list. Nobody searches the opponents, because the opponents were never recorded anywhere searchable in the first place.
Time is remembered, not recorded
Written up on Friday for the whole week. Recovery drops, bills go out late, and the work in progress figure on the report is a guess.
Ten modules, one file.
Everything hangs off the matter, so opening a file shows the whole picture: the deadlines, the tasks, the time, the disbursements, the documents, the parties and the money.
Matters
Every file with its client, work type, timekeeper, funding basis, court reference and fee estimate — with the estimate burning down as time is recorded against it.
Tasks & deadlines
Assigned, prioritized and dated. Overdue work is colored, counted in the sidebar and pushed to the front of the dashboard rather than waiting to be looked for.
Time recording
Tenths of an hour, the way time is actually kept. Rates are captured on each entry, so a rate rise next year cannot silently reprice work already done.
Billing
Raise an invoice from unbilled time and advanced costs in one action. Fees and advanced costs are kept apart because they are not treated the same way.
Clients
The client register with contact details, matter history, outstanding balance and the state of their intake in one view.
Documents
Filed against the matter with version history. Filing under an existing name supersedes the previous version rather than sitting beside it.
Contacts
Opposing counsel, experts, court reporters and courts — held once, linked to the matters they appear on, and searched by the conflict check.
Dashboard
What is overdue, what is coming, what is unbilled, what is owed, and which timekeeper is carrying what. The morning position on one screen.
The four things a generic system will not do for you.
Any developer can build a list of matters. These are the parts that need somebody to have read the Rules of Professional Conduct.
Conflict searching
One search runs across every client, every recorded party on every matter, every contact and every matter title at once. It catches the case where a company is your client on one file and the opponent on another — the conflict a name-by-name look through a spreadsheet is most likely to miss.
A nil return is recorded too, so the file shows the check was carried out.
Client intake and conflicts clearance that actually gates the work
Identity verification, risk rating and source of funds sit on the client record. A matter cannot be opened for a client whose intake is incomplete — refused by the system, not by a policy nobody reads.
Enforced server-side, so it holds however the request arrives.
Statute of limitations as a first-class field
Not a note in a file, not a line in a diary. A dedicated field with its own warning window, its own dashboard tile, and a banner on the matter itself from ninety days out.
A blown statute of limitations is the most common basis for a legal malpractice claim.
Audit trail
Every change writes an immutable line: who, what, when. Status changes, payments recorded, due diligence updated, documents filed.
The record malpractice carriers and bar audits ask for.
This system does not hold client funds.
There is no trust account and no part of the IOLTA trust accounting rulesimplemented anywhere in it. That is deliberate. Handling client funds is the highest-risk thing a firm does, and it belongs in accounting software built and audited for that purpose.
What this does instead is record time, raise bills and track what is outstanding — then hand the figures to whatever you already use. Your accounts stay where they are.
Built to fit the firm, not the other way round.
What you are looking at is a demonstration, not a package to be bought off a shelf. The system delivered to a firm is shaped around how that firm actually runs.
What you are looking at
- A working system, not a set of screenshots — the conflict search really searches, the bills really calculate, the deadlines really count down
- Loaded with a fictional firm so that nothing needs setting up before you can look
- Built to show the reasoning: why a limitation date deserves its own field, why due diligence should block file opening
- Every part of it open to being changed
What a firm would get
- The modules your practice actually needs, in your terminology, following your file-opening and supervision procedures
- Your existing data migrated in, and your people trained on it
- The source code handed over, so you are never dependent on one developer remaining available
- Ongoing support at a fixed monthly fee, with changes quoted separately
One thing it will not do, whatever the firm: hold client funds. That stays with your accounts package, for the reasons above.
Have a look around, then tell me what is wrong with it.
The demo is loaded with a fictional firm — matters mid-flight, deadlines approaching, bills unpaid. Open a matter, record some time, generate an invoice, run a conflict search. Nothing you do affects anything real.
If it is close but not quite right for how your firm runs, that is the useful conversation. It is built to be shaped around a practice.
Or write to hello@codecart.org