Conflicts at intake

A boutique litigation practice in Central runs a contact form on its website. Enquiries arrive at the rate of three or four a week. The managing partner reads each one personally, runs the firm’s conflict check against the matter database, and decides whether to take a meeting. The system has worked since the firm was three people. It is now eleven.

Last quarter, the managing partner went back through the form submissions and pulled the ones the firm did not respond to within forty-eight hours. There were nine of them. Seven came from prospective clients who, the partner already knew through other channels, had since signed with another firm. Four of the seven were the kind of mandate the partnership existed to do.

The partner did the arithmetic in front of the management committee. The firm had lost, conservatively, eight figures of expected fee revenue in twelve weeks because the existing intake process required the personal attention of someone who is in court three days a week.

This is not an unusual story. We have heard versions of it across at least a dozen boutique law firms in the last six months. It is also not a story about the partner working harder, hiring an associate to triage, or installing a CRM with an “intake module”. The problem is structural.

Three reasons leads go cold at intake

One: the rubric for fit lives in one head. A partner can decide whether an enquiry is the kind of work the firm wants in about forty seconds. They are not running a checklist; they are pattern-matching against a few thousand prior matters. Asking a non-lawyer at the front desk to do this triage produces either bad judgement (signals get missed) or theatre (everything routes back to the partner anyway).

Two: the conflict check requires the matter database. Most boutique firms run their conflict checks against the practice management system itself: Clio, MyCase, Smokeball, NetDocuments, occasionally a hand-maintained spreadsheet. Even with software, the human on the system has to open it, type names, read results, and make a judgment call about whether something is or isn’t a conflict. A junior on the front desk cannot do this; the system is paywalled to people with seats.

Three: urgent and non-urgent enquiries arrive in the same channel. A conveyancing chase from an existing client, a partner from another firm asking for a referral, and a stranger asking about a wrongful-dismissal matter all arrive in the same inbox in the same form. The signal-to-noise ratio is too low for the partner to scan from the back of a courtroom, and there is no good reason for any of them to wait until evening.

None of these are problems with the partner’s effort. They are problems with the design of the intake process.

What “just an intake form” misses

The standard advice from a marketing or CRM vendor is to “qualify enquiries with a better form”. Add fields. Ask for the matter type. Ask for the budget. Ask for a phone number. The partner spends less time deciding because the prospect has done the work.

This advice fails on its own terms. People filling out a form on a website are evaluating the firm at the same time the firm is evaluating them. A long, clinical form sends the same signal a long, clinical questionnaire sends in any other context: that the firm cares more about its own filing than about the person on the other end. The kind of clients a boutique partnership wants to attract are the kind who will close the tab.

It also does not solve the structural problem. The matter type and budget tell the partner whether the enquiry is plausibly fit. They do not run the conflict check. They do not flag urgency. They do not tell the front desk who to bring in next.

The shape of the fix

What boutique partnerships actually need is a thin layer between the contact form and the partner’s inbox that does three things, on autopilot, every time:

It triages against a written rubric the firm itself defines. Not “is this a personal injury matter or a commercial one”; that is the partner’s job. Rather: is this an existing client, a referral from a known source, an enquiry within a vertical the firm covers, or something we politely decline. The rubric is owned by the firm, written down once, and applied a thousand times.

It runs the conflict check against the matter database. This is the step every off-the-shelf intake tool gets wrong. Generic CRMs do not integrate with Clio’s matters at the level conflicts require, and writing the integration once is exactly the kind of small, careful integration work small studios exist to do. The conflict check produces a flagged result that a human reviews; the system does not pretend to make the call.

It routes urgency. A new-matter enquiry from a prospective client during business hours is one thing; the same enquiry from an existing client at 11 p.m. before a court date is another. The triage layer recognises the difference and routes the latter to the covering partner via SMS, while the former gets an acknowledged response within thirty minutes and a calendar link.

What the firm sees, after this layer is in place, is two changes. Response time on new enquiries collapses from days to under an hour. The partner no longer reads enquiries that the rubric should have politely declined.

Crucially, the partner still makes the partner’s decisions. The triage layer does not pretend to be a lawyer. It does the bookkeeping around the lawyer’s judgment so that the lawyer’s judgment is applied only to the things that need it.

The audit comes first

Most engagements that look like this start with a one-week audit, not a build. There are two reasons.

The first is that we have to read the firm’s actual matter database before we can sensibly write the rubric and the conflict-check integration. Every partnership has its own conventions for naming clients, recording related parties, and recording prior representations. A generic conflict-check is worse than the manual process; a fitted one is dramatically better.

The second is that some firms find, during the audit, that the problem is not really intake at all. It is the way enquiries arrive (a contact form alone, with no email or phone alternative), or the absence of any acknowledgement message after submission, or a follow-up process that drops handoffs between the partner and the front desk. Those are problems worth fixing before any software is shipped, and the audit names them honestly.

About one in five audits ends with a recommendation against immediate software. We say so plainly when it is the right answer.

When this fits, and when it does not

The intake-triage engagement is a fit for boutique partnerships at roughly five to twenty-five lawyers, where the volume of enquiries is high enough that partner time is being spent on triage but low enough that the firm has not built a dedicated intake team. It is a fit for firms that already run a real practice management system and treat their matter database as authoritative.

It is not a fit for solo practitioners (the cost of the engagement does not yet justify itself), nor for very large firms (which have BD operations that handle this differently), nor for firms whose conflicts policy is loose enough that the integration would be encoding a mistake.

If your firm is somewhere in the range we have described and the same handful of qualified leads is going cold every quarter, the engagement is well-defined and ready to be scoped. We can write the brief in a week.