A small firm pays for practice-management software heavier than it uses, and still loses the time that matters most. Calls with clients are a real part of every working day, and they are the part that goes unrecorded — remembered on Friday, rounded down, or never written up at all. This is the page for the version where the call books itself.
Calls are where the billing leaks. A timer is easy to start for drafting and easy to forget for the phone. By the time the week is reconstructed, the twenty-minute call is a vague memory and the six-minute one is gone.
The tools that exist make it worse in small ways. Timers count ring time. Pausing fragments a task into pieces that each get rounded up, so the bill inflates and the client notices. Reports come out in the wrong language, or the wrong format, or need building by hand in Excel.
And the heavy practice-management platforms solve this per seat, per month, with more features than a small firm will ever open — while the reports the firm actually needs are still exported and rebuilt by hand.
Dor Iluz's law office, Israel
Built for a working law office in Israel, Hebrew-first and right to left, and in daily use. The same client commissioned three other builds in this portfolio, which is its own kind of evidence.
Figures are read from the production system, not estimated. Where something has not been measured, this site says so rather than filling the gap. How we count · All case studies →
The same pieces, in your language and your billing increments.
A browser dialler that bills itself: call a client from their record, and when the call ends a time entry exists against the matter you chose before dialling — connected time only, never ring time, rounded and rated exactly like a typed entry. Unanswered calls are logged and bill nothing, with one click to bill them anyway.
A timer built around sittings, so pausing and resuming never fragments a task or inflates the bill. Rounding is applied once per session.
Invoices from tracked hours, fixed fees or both, carrying your logo and case numbers, printable or emailed, marked paid or unpaid.
Reports that survive Excel — on-screen in your language, CSV that opens with characters intact, printable PDFs — plus a scheduled monthly report and per-case hour and money alerts that email the client once per threshold.
Optionally, a drafting assistant that is closed-book by construction: it cannot cite a case you did not upload, and anything it cannot account for is turned into a marked placeholder before the draft can be downloaded.
No, deliberately. Recording was left out because of attorney–client privilege. The dialler captures who was called, when they answered, how long you were connected and which matter it belongs to — the billing facts — and never the audio.
A browser softphone on Twilio Voice. You talk through the computer; the client sees one shared office number. No desk phones, no PBX, nothing to install.
It replaces the parts a small firm uses every day — timer, calls, invoices, reports — and leaves the rest. It can run alongside an existing system while you decide, and everything exports to CSV so nothing is trapped.
The rule that it may only cite what you uploaded is written into the prompt and then enforced by code: a verification pass walks the finished draft, checks every authority against the uploaded material, and rewrites anything unaccounted for into a placeholder. A prompt is a request; that pass is the enforcement. It is also optional — the billing system works without it.
In a Postgres database and a hosting account that you own. The firm's client data does not pass through a third-party practice-management vendor.
Time tracking, calls and invoicing are a defined build. The drafting assistant is a separate scope. You get a fixed price and a delivery date before anything starts.
Tell me how a call becomes a line on an invoice today, and how often it does not. If your current software can be made to do this, I will tell you how rather than build a replacement.