Three partners, one form

Every legaltech pitch I have sat through in the last two years begins with a list of features. Document generation. Clause libraries. Workflow automation. Client portal. Billing integration. Each one is a reasonable thing to build. Each one is on the roadmap of three competitors. And each one, I am fairly sure, is the wrong thing to focus on first.

The question that matters for a legaltech MVP is not what does it do. It is: does the partner who tried it on Monday open it again on Tuesday without anyone reminding them?

That is a hard question. It is also the only one whose answer predicts whether the product has a future.

The adoption gap

Lawyers are, as a rule, diligent. They are also, as a rule, completely uninterested in software. Those two things coexist without tension. A lawyer will read three hundred pages of case law before trial and will ignore a Slack message about a new tool update for nine weeks. This is not a character flaw. It is a consequence of the job: legal work is cognitively expensive, and any context-switching tax — how does this button work again — gets charged directly against billable time.

What this means for a legaltech founder is that the space between the first use of a tool and the second use of a tool is a canyon. The first use happens because someone senior leaned on someone junior to try the tool. The second use has to happen without the senior push. If it doesn't, you have a pilot, not a product.

I have watched this happen to tools I liked. The demo was great. The partner was enthusiastic. The pilot got scheduled. The first filing was created on the platform, with some help from the vendor. And then, quietly, nobody opened the tool again. Not because it was bad. Because the next filing was urgent, and the familiar way of doing it was on the partner's desktop already, and the tool was one tab over, and one tab over is a long way.

What to build first, and what not to

The MVP question reframes everything. Instead of what features would make this compelling, the question becomes what is the smallest possible version of this tool that a busy partner will reach for unprompted on the second day?

The answer, almost always, is one thing, done at the exact moment of pain.

Pick one workflow. Not a platform. Not a suite. One specific moment in a legal workflow where the partner is already annoyed at the current process. Engagement letters. Deposition prep. Conflict checks. Witness timelines. Something narrow enough that you can finish it end-to-end in a matter of weeks, and specific enough that the first use produces an output the partner immediately wants to use again.

The features that sound impressive at the pitch — the document libraries, the integrations, the AI chat — are all downstream of that first adoption loop. Build them after you know the partner is reaching for the tool unprompted. Not before.

The adoption test

When I am asked to evaluate an early-stage legaltech product, the question I ask is not how big is the TAM. It is:

If I take this product away from your three pilot partners tomorrow, how many of them notice within a week?

If the answer is all of them, the product has found something real. If the answer is we'd have to tell them, the product has a demo, not a business.

The three-partners-one-form test is not rigorous. It is not a growth metric. It is the crudest possible check for whether the product has crossed into the space where it earns its own second use. But in legaltech, that is the only question at the MVP stage that matters. Everything else — features, scale, pricing — is downstream.

If the second use happens, you have a future. If it doesn't, you have homework.