The "One Firm at a Time" Onboarding Model — Why LeadLex Doesn't Self-Serve

A short line on the LeadLex site has produced more questions on first calls than any other piece of copy: "We onboard IP firms one at a time. Sign-up by waitlist only."

Inside a category — legal software — that has spent five years racing to self-serve, the line lands as a deliberate choice that needs explaining. It is.

What the line means in practice

In practice, the line means three things.

First, it means LeadLex is not available to a firm the day the firm decides it wants it. A short conversation, sometimes a longer one, is the door. Some firms move through that door in two weeks. Some take three months. A small number have been politely told that the timing is not right yet, often because the product was not yet ready for what their practice needed.

Second, it means the implementation that follows the door is structurally personal. The same handful of people who built LeadLex sit on the early calls with the partnership. The first weeks of running with the firm are run by the people who built the product, not by an onboarding team handing the firm off to support.

Third, it means the rate at which LeadLex onboards firms is bounded by the throughput of those people. Not by pricing, not by capacity in any technical sense, but by the throughput of design partnership. The waitlist exists because the work cannot be done quickly without losing the quality that makes it worth doing at all.

Why the model is structural, not pricing

The temptation, looking at a slower onboarding pace, is to read it as a pricing strategy — keep supply tight, prices firm, demand visible. That reading is wrong for LeadLex, and it misses the actual reason.

The reason is that every firm running on LeadLex in the first three years shapes what LeadLex becomes for the firms running on it in the years that follow.

An IP boutique whose origination comes through Latin American referring firms uncovers patterns no one else's data exposes. A patent prosecution group inside a full-service firm in Germany surfaces workflow needs around UPC and EPO oppositions that a trademark-only practice would never reveal. A partner running a specific kind of BD review at the Monday morning meeting articulates a Lexi query the team had not anticipated.

Each of those interactions is, in product terms, a design conversation. The product shape that emerges from sixty of them is materially different from — and materially better than — the shape that would emerge from six hundred onboardings run as a process by an onboarding team.

The category language for this is "design partnership." The honest description is that the early customers and the team are still building the product together, and the cadence of that work is what determines the cadence of the waitlist.

What partners get from the model

For a partner whose calendar is full and whose patience for software vendors has thinned over twenty years of failed CRM implementations, the model produces a particular kind of buying experience.

The first call is short. The second call, if there is one, includes the people who built the product. The implementation that follows is run by those people, not by a customer success function. The questions a partner asks during the first month are answered by someone who can change the product in response — not someone who can submit a feature request to a roadmap.

For a partnership making a decade-long bet on the infrastructure their practice runs on, that experience is qualitatively different from the standard SaaS purchase. It is more like hiring than buying.

Why this changes over time, but only gradually

The model will, in time, scale. As the product becomes more deeply shaped by the first cohort of design-partner firms, the onboarding throughput required per new firm will decrease. The waitlist will move faster. A self-serve flow may eventually emerge for the parts of the product that have stabilised into clear defaults.

But it will not happen quickly, and it will not happen by replacing the model that produced the product in the first place. The relationships that early firms have with LeadLex — and the influence they have over what the product becomes — are part of the architecture, not a phase.

What this leaves behind

For IP firms looking at LeadLex right now, the model is something to evaluate on its merits. A slower pipeline that produces a product fitted to the practice is a different proposition than a faster pipeline that does not. Most of the firms currently running on LeadLex were ready for the first proposition. A growing number of firms are arriving at the same conclusion.

"One firm at a time" is, on the surface, a description of throughput. Underneath, it is a description of how the product was built and how the firms inside it have shaped what it is. The waitlist is a feature of the development model, not a friction in the buying process.

That is the line, and that is what it means.

Related: How AI assistants reach firm data through MCP — the architectural decision behind the model. Choosing a legal CRM in 2026 — the framework alongside the model.