Firmviz is the law firm terminal: matters and conflict checks, deadlines that say when they still need verifying, a trust ledger nobody can edit, billing, the Court Map of each case, and Jarvis, an assistant you type or speak to.
Nothing on these screens was typed into a spreadsheet. The matter box, the dates, the money and the case map are one record, and every change is written to an audit log that cannot be edited.
Clients, parties and their other names. A conflict check runs on every new matter and searches the whole firm; a matter leaves intake only when an attorney clears it, and the check goes stale the moment a party is added.
Vance v. Keller Freight Lines
A date counted from a rule carries VERIFY until an attorney checks it against the source. Limitation periods come from the statute, with the citation and the day it was retrieved. Nothing is invented.
Each case as a board: the elements to prove, the evidence, the witnesses and the filings, linked. Memos recorded or typed land on the card they belong to, and a timeline replays the map as it was on any date.
An append-only ledger: no edits, no deletes, corrections by reversing entries. No client goes below zero. Two-person approval above an amount the firm sets, and a three-way reconciliation each month signed by an attorney.
$15,000.00 to the executor of the Brennan estate · entered by Rosa, bookkeeper
APPROVE AND POST Tier 2 · passkeyTime and costs into invoices an attorney approves; what each client owes, with aging; fees move from trust only against an approved invoice, never for more than it owes, and the transfer is written on both the ledger line and the invoice.
“open vance”, “what’s on Thursday”, “log 1.5 hours on Osei”, “deposit 500 for Vance”.
Jarvis understands close spellings and asks when two names are alike; it never guesses. Anything that changes data shows a confirm card first, with exactly what it understood. Money, access and anything that leaves the firm need your passkey, and voice never approves those. Voice is transcribed on the firm’s own server, never by the browser.
See it on your own mattersunderstood: “huors” → hours · matter: Vance v. Keller Freight Lines
Log 1.5 h on MS-2026-0001, “reviewing the police report”, today, by Elena Meridian.
CONFIRM cancelsaid by voice · transcribed on the firm’s server · money is always Tier 2
$500.00 into trust for Vance · IOLA account ****4421 · the exact line that will be posted.
APPROVE WITH PASSKEY password fallbackSix things Firmviz does whether or not anyone is watching.
Every row belongs to a firm and the server enforces it at two layers: the application and the database’s own row-level security.
Every view, change and refusal is written to a hash-chained log the database refuses to edit, anchored outside the database on every commit.
Windows Hello, Face ID or a security key approves trust money, access changes and anything sent outside the firm. Voice never approves.
Uploads, memos and backups are sealed with the firm’s data key. Uploads are read by content, never by name, and scanned.
The browser’s speech recognition is never used; voice is transcribed on the firm’s own server. AI drafting exists but stays off until the firm turns it on, with client details replaced by placeholders first.
Closed matters keep their files for the period the firm sets; nothing is disposed of without an attorney’s approval, and a legal hold blocks it.
The law card is a research starting point, not legal advice; an attorney verifies every date before it counts.
One record, with a memory.
The dates, the money, the documents and the map of each case are one record the whole firm works in, and every change is signed, chained and kept. What was true on any date can be shown again on that date.
Tell us about your firm and we will write back to set a time. Nothing is sent anywhere else; the request is kept on Firmviz’s own server.
Thirty minutes on an invented firm, then Firmviz on a server your firm controls.