Legal Intake Is a Category, Not a Module

I spent years thinking of legal intake as a feature. A form on the front of a matter management system. A nice-to-have. That framing is quietly costing in-house legal teams their most valuable resource: time. Here is the case for treating legal intake as its own category, and the opportunity that opens up when you do.

Matters are only half the job

Matter management earns its place. Matters run a large share of the budget, much of it outside counsel, and they need handling from the simplest request to the evergreen IP and contracts watched for years.

But matters are one side of the ledger. The other side is every request that never becomes a matter. The "can I sign this," "do we have a template," "what's the policy on this" that arrives all day, by email, Slack, and the hallway. None of it shows up in a matter report, and it quietly eats the week.

That half of the week is the opportunity. Reclaiming it is worth more than any improvement to how matters get managed.

Why the module approach falls short

You cannot win back that time with a bolt-on. A matter management system is built to manage the matter, often with e-billing attached. That is the product, and that is where the engineering goes.

Intake rode along as a side module, and the architecture shows:

• Every request gets forced into a matter, whether it is one or not, which muddies reporting and caps what intake can do.
• The forms were built by and for legal: required fields, unfamiliar terms, a form the business has to hunt for, and no way to see status after hitting send.
• Vendor attention goes to the core product, so intake gets the leftovers.

Stretching a general ticketing system does not solve it either. A legal ticket misses the context, routing, and judgment legal work actually needs. As I've written before, legal software has to be easier than Slacking a lawyer, or people just go around it.

History keeps repeating this

When a job hides inside a bigger product, it stays small until someone builds for it on purpose. Then it becomes a category of its own.

• CRM started as a module inside ERP systems, until Salesforce pulled it out and created a true category. Then it evolved again as customer success outgrew CRM, and Gainsight turned that into a category of its own.
• IT and support requests sat buried in tracking databases, until the help desk became its own staffed, budgeted discipline.

Same pattern every time. The capability was treated as a feature. Someone built for the neglected user first, and a category was born. Legal intake is at that moment now.

Start where the need starts

There is a deeper reason to start at intake. Everything in legal begins with a question. Can I sign this. Should we pursue this. What is our exposure. The matter, the contract, the spend decision, all of it starts as a request someone made. Intake is not the small end of the work. It is the front of it. Get the front door right and you are organizing the whole flow behind it, because the front door is where resource allocation begins: what is routine, what needs a lawyer, what becomes real legal work.

This is also where building AI-native pays off. When you design around the actual need first, instead of inheriting a data model someone drew up a decade ago, you can move fast on what comes next without dragging old architecture behind you. Start with intake done right, and the work behind the front door extends naturally from it, rather than getting bolted on backward.

The opportunity, captured through product focus

Reclaiming the other half of the work takes a product built for intake first, not a feature added on the side. Built for intake first means the business never hunts for a form, because the front door is the Slack and email they already use. It means a routine question gets an answer instead of a ticket. And it means every time a lawyer answers, the system keeps that answer, so no one answers it twice. That last part is the self-building knowledge base we set out to build.

Do that, and the outcome shows up where it counts: fewer interruptions, faster answers, and lawyers spending their time on judgment instead of repetition. That is the next frontier for in-house legal, and it belongs to the teams that stop treating intake as a module and start treating it as the work itself. It's also why we decided to own the experience end to end, for the business and for legal alike.

Craig Raeburn

Craig Raeburn is a cofounder of LegalOperator, where he leads go-to-market. He's spent 20+ years in B2B software, often brought in at the messy inflection points: turnarounds, acquisitions, and integrations.