Clio just spent a billion dollars on AI. None of it owns the deadline when it slips through your front door.

01 The pain

It's 8:05 on a Thursday. A matter walks in the door. Someone calls, describes a mess in plain language, mentions in passing that they "were served two weeks ago," leaves a vague request for a call back, and hangs up. Your front desk left at 5. The call gets half-logged — or not logged at all — and then it sits, with nobody's name on it.

Three weeks later, nobody has called back. The two-year limitation clock hiding inside "served two weeks ago" was never flagged by anyone. By the time someone finally surfaces it, the cleanest path is already closed.

That's not a rare accident — it's the industry's default failure mode. And the real cost isn't the missed message; the missed message is cheap. The expensive one is the unowned message: it came in, got half-logged, and then sat there with nobody accountable for it. That's what generates the liability underneath a routine matter.

The judgment is supposed to happen the moment a matter arrives — what practice area is this, is it urgent, is there a deadline hiding inside it that nobody has flagged yet. And the more dangerous part is the silence right after: a matter enters, then waits — visibly or invisibly — for a human to act.

02 Where your software stops

Winnipeg firms mostly run one of three systems. It's worth being precise about what each does in 2026:

Clio is now an AI-first platform. Manage AI extracts deadlines from court documents and creates calendar events. Grow AI qualifies leads from your website forms. Clio Work, built on the $1B vLex acquisition, does research and drafting against a billion-document library. Genuinely impressive — and every piece of it starts after something already exists in the system: a document to read, a form submission to qualify, a matter to research. The Thursday phone call happens before any of that exists.

CosmoLex is the Canadian Bar Association's practice-management partner, Canadian-hosted, with trust accounting built for provincial law-society rules. Its July 2026 AI Intake feature auto-generates structured intake forms and triggers conflict checks. But it's still "the client fills out a form" logic — not "a matter came in by voice and something made sure it didn't fall through a gap."

PCLaw has ended support for 2021-and-earlier versions; the parent company is steering firms toward its cloud successor, LEAP. If you're still on it, the direction is already decided for you.

03 "Can't I just buy an AI receptionist?"

Yes, and the market is crowded — Smith.ai, TeleWizard, AgentVoice, Perspective AI. Some can identify a returning caller, capture practice area and urgency, even run a generic conflict pre-check. If all you need is "answer the phone, don't lose the lead," one of them might be enough, and I'll tell you so.

But for a law firm they share three real gaps:

1. They don't own anything after the answer. They log a lead and book an appointment; then the matter enters the same silence. Nothing watches whether a human actually picked it up. Nothing flags a matter that's been sitting for weeks with a name attached but no action behind it.
2. The default is full automation. TeleWizard's own marketing says "without any human effort." Appointments get booked and leads get created with nobody at your firm approving the step — and for a business where a mis-triaged call is a professional-responsibility problem, "nobody approved it" is exactly the wrong default. I flip it: approval is the built-in behavior, not an add-on.
3. The conflict check is generic name-matching. None of them know Manitoba's Limitations Act runs a two-year discovery clock, or that "served two weeks ago" is a different animal from "thinking about updating my will."

And a data point that isn't a generic small-business stat — it's Clio's own 2026 Legal Trends for Solo and Small Law Firms report (May 2026): 71% of solos and 75% of small firms already use AI, but only ~31–32% have seen revenue grow from it. The tool isn't the problem. The tool with nowhere useful to route its output is.

04 Why Clio won't build this part

Reasonable worry: "if this gap matters, won't Clio just build it next quarter?"

Look where the billion dollars points — deeper into legal work: research, drafting, billing, deadlines inside documents that already exist. Those scale identically for every firm on earth. That's platform territory.

The front door is the opposite kind of problem. It has to be customized firm by firm — your practice areas, your intake questions, your escalation rules — it depends on local law, and when a matter slips, someone has to own the slip. That's precisely why Clio lists third-party receptionists in its app directory instead of building one. It's partner territory, not platform territory — and it's why the right version of this layer gets built for your firm, not subscribed to.

(That's my read on Clio's direction, not an official statement. But it rests on a fact: Clio hasn't built this layer, and has left it to third parties.)

05 The gap I fill — and the gap I don't

I build the intake-and-accountability layer that sits in front of whatever you run — Clio, CosmoLex, or a spreadsheet. (Connecting to Clio needs the Advanced plan or higher for API access; if you're on Essentials, I'll confirm the right path during the free assessment.)

What it does:

• Answers the line or the after-hours email, and captures what the caller actually said — in their own words, attached as evidence.
• Turns every intake into a visible, owned item. Not a message that got half-logged and forgotten — a record that sits in a queue with a status, until a human at your firm picks it up. If it's been sitting too long, it stops being invisible. A matter can no longer quietly disappear, because the system won't let it go unclaimed and silent.
• Surfaces the dates and events mentioned on the call — "served two weeks ago" — and flags them for a lawyer to assess against Manitoba's limitation rules. It does not make the legal call. It makes sure nobody has to remember to make it. It never guesses a deadline; if it can't tell, it says needs review.
• Confirms, reminds, and offers to reschedule appointments — so a client never shows up to a consultation that was quietly cancelled with no notice. Confirmation and reminders are automatic; a cancellation triggers an actual heads-up, not silence.
• Every drafted intake waits for a human to click approve. That click means your firm made the call, and there's a traceable record of who approved what, based on which words. That's not a checkbox — it's an accountability chain a $25/month U.S. bot structurally can't give you. Manitoba's Court of King's Bench has required AI use in filings to be disclosed since 2023; traceability here isn't a marketing angle, it's becoming baseline.

The matter-classification and limitation-flagging shares its approach with CaseFlow MB, my live legal-intake system, built on Manitoba's publicly published legal data — not on my own legal judgment. The voice layer comes from a stack I've already proven on a separate project, reconfigured for a firm context.

What it does not do — because overselling this would be its own kind of malpractice: it can't make a lawyer who's avoiding an active client pick up the phone. If the wound in your firm is that matters go dark weeks after they're accepted — a partner too busy, a file with no follow-up discipline — that's a workflow-and-culture problem an intake bot doesn't fix. What this layer does is make the front door impossible to lose track of, and give every matter an owner and a paper trail from the first minute. It narrows where things can go dark; it doesn't pretend to eliminate it downstream. If your real gap is elsewhere, I'll say so during the assessment instead of selling you the wrong thing.

06 Why trust this build

Three things you can verify, not take on faith:

1. Your data stays in Canada, access stays yours. Everything runs on AWS ca-central-1 — not a U.S. answering service's cloud. Raw call records are visible only to authorized people at your firm, with no secondary use.
2. The finished system is yours — and it doesn't leave when a person does. Built on your accounts, your domain, your keys, with handover documentation. Every intake becomes a durable record your firm owns — so a matter doesn't evaporate because one lawyer retired or moved on. You're not renting it, and it doesn't disappear if the arrangement ever changes.
3. Rooted in Winnipeg, reachable in person. I can sit down in your office. And the build isn't done when the software works — it's done when your front desk is actually using it. I stay through implementation until that's true.

Want to see what this intake system looks like first? Check out the CaseFlow MB demo before deciding whether to apply for the free build.