Lexi as Junior Associate, Not Chatbot: The Model Behind the Model

Most AI tools in legal start from the chatbot. A text box, a blinking cursor, a model that will answer anything you ask in the tone you ask it in. That works for research and drafting, where the lawyer is the principal and the model is a faster way to think on the page. It works less well for business development, where the work is not a conversation but a sequence of small, accountable acts — a note logged, an email sent, a meeting requested, a follow-up scheduled — each of which leaves a trace in someone else's inbox and in the firm's relationship record.

Lexi was built around a different metaphor. She behaves like a junior associate assigned to the BD function of an intellectual-property firm. The metaphor is not decorative. It shapes scope, permissions, memory, and the moment of human sign-off.

Scope before capability

A junior associate has a job description. They do not wander into matters they were not asked into. Lexi's scope is business development — prospecting, outreach drafting, meeting preparation, pipeline hygiene, conference logistics, follow-ups, account research. She does not opine on patentability. She does not draft office action responses. She does not review contracts. When a partner asks her to, she declines and points to the tools that do that work — the Harveys and Legoras of the world, which sit alongside her in the firm's stack.

This boundary is not a limitation we apologise for. It is the reason partners trust her with the work she does do. A junior associate who freelances into other practice areas is a liability. So is a BD agent that drifts into legal substance.

An approval ladder, not a kill switch

The standard pattern in agentic AI is binary — autopilot on, autopilot off. That is the wrong shape for a law firm. Partners need gradients. Some actions Lexi can take on her own. Some she can take on her own once a partner has approved the template. Some require explicit sign-off every time, regardless of how many times the same partner has approved similar drafts before.

The ladder in practice looks something like this. Logging a meeting note from a transcript — autonomous. Updating a contact's title after a LinkedIn change — autonomous. Drafting a cold outreach email to a new prospect — requires sign-off. Sending a follow-up to a client the partner has corresponded with for years — autonomous within a tone the partner has confirmed. Sending anything to a name on the conflicts list or the do-not-contact list — blocked, full stop, with an explanation.

The ladder is configurable per partner, per practice group, per contact tier. It is also visible. A partner can ask Lexi at any time which actions she is taking on their behalf without asking, and she will list them.

Firm memory, not session memory

Chatbots forget. That is acceptable when the unit of work is a single question. It is not acceptable when the unit of work is a relationship that has been cultivated for fifteen years across three firms, two continents, and a change of in-house counsel.

Lexi's memory is the firm's memory. Every interaction she observes — meetings, emails, conference encounters, referrals — goes into a per-firm graph that she can reason over. When a partner asks her to prepare for a call with a head of IP at a German automotive supplier, she does not start from scratch. She knows who introduced them, what the last three matters were, which associates worked on each, what was discussed at the most recent INTA, and which colleagues at the same company the firm has touched.

That memory is per-firm and stays per-firm. Lexi does not learn from one firm's data and apply that learning to another. The infrastructure is siloed at the firm level, hosted in Frankfurt, and covered by a DPA signed before the firm goes live. No client data is used to train models, full stop.

No send without sign-off

The single rule that does the most work is the one with the least nuance. Lexi does not send anything to anyone outside the firm without a named human approving the specific message. The approval can be one tap on a phone. It can be batched. It can be delegated by a partner to a BD manager for certain categories. But it exists, every time, for every external message.

A junior associate would not put a partner's name on an email without showing it to them first. Neither does Lexi.

Related: The Four Functions of Legal BD. Where AI Does Well and Where It Doesn't in IP BD. The Disappearing CRM Interface.