Clio's 2024 Legal Trends Report put a secret shopper on the phone to 500 US law firms: 60% of calls from prospective clients went unanswered, and nearly half the firms never answered and never called back either. Nobody with a problem worth solving waits on that — they work down the page until somebody picks up. We close that gap, and the others like it, with automations that run on your own server, under your own accounts, watched by us.
What we build
Each one is fixed scope and fixed price. You'll know what it does, what it costs, and what you have to do before you agree to anything.
Turn finished jobs into public reviews — and catch the unhappy customers privately, before they post.
The phone rings out, and ten seconds later they get a text asking what they need. Most of them reply.
Answer every new enquiry in under a minute, at 3am, without hiring anyone.
Contract signed at 11pm, project fully set up by 11:01pm.
Stop typing invoices into your accounting software. They arrive, they get read, they land as drafts.
How it goes
The whole thing takes about a week, and about fifteen minutes of your time.
A short call. You describe what happens now — who does it, how often, and where it slips. If automating it is a bad idea, we'll say so.
It runs on a server you own, under your accounts. You connect your own tools; we never see your passwords or API keys.
If it breaks, we're told before you notice. Once a month you get a plain email showing what it actually did.
Where we're up to
We're new, and pretending otherwise would be the first thing we got wrong. So the first three clients pay half the setup fee — $750 rather than $1,500 on the missed-call build — on the condition that we can publish the real numbers afterwards, good or bad. The monthly fee stays as listed, and you can stop it any time with thirty days' notice. There's no countdown: it's three, and when the three are gone the price is the price. And if we can't make it work against your real data, you don't pay the setup fee at all.
Before you ask
If yours isn't here, ask on the call — we'd rather answer it than have you guess.
Then we haven't finished. We don't consider a build done until it's run against your real data, including the messy cases. If we can't make it work for you, you don't pay the setup fee.
Watching it, and the work that comes out of watching it. When a run fails we're told automatically and we go and fix it — you don't have to notice it or report it. When your phone system changes a setting, or a provider changes something underneath, that's ours to sort out too, and small changes to the wording or the rules are included rather than quoted. Once a month you get a plain email showing what it actually did, which is also how you decide whether this is still worth paying for.
Thirty days' notice and the monthly fee stops. The automation doesn't — it's on your server, under your accounts, so it carries on working without us, and we hand over everything needed to keep it that way. There's nothing to migrate off and nothing to export. What you're cancelling is us watching it, not the thing itself.
You do, entirely. It runs on your own server, under your own accounts, with your own API keys. There's no platform to be locked out of. If you leave, it keeps running and we hand over the keys.
No. You tell us what happens now and who it happens to. We build it, test it against your real data, and hand you one page explaining what it does and how to switch it off.
We're told automatically, usually before you notice. Every automation we build has failure alerting wired in before it goes live — that's not an upgrade, it's a condition of us shipping it.
Onto infrastructure you control and nowhere else. We never hold your API keys — you enter those yourself, and they're encrypted where even we can't read them back. For regulated work this is usually the whole reason people call us.
About fifteen minutes to connect your accounts, a description of the process you want automated, and someone to answer a question or two while we build. That's it.