Question 1

How much does LeadLex cost?

Accepted Answer

Every IP firm is different — size, channels, connectors, the practice mix. We put together a tailored proposal after a 15-minute scoping call. Get in touch and we’ll set one up.

Question 2

Is there a setup fee?

Accepted Answer

No setup fee. Lexi is working inside an hour of activation.

Question 3

Is there a minimum contract?

Accepted Answer

Terms are scoped in your proposal. Annual is preferred and discounted; month-to-month is available. We’d rather earn the renewal than lock you in.

Question 4

How do seats work?

Accepted Answer

We price for whole-firm adoption — partners and BD admin together — because the communications moat compounds when everyone is in-channel with Lexi. Exact seat count is scoped in your proposal.

Question 5

Does what we get change with firm size?

Accepted Answer

The product is the same. What changes is the rollout — a 12-fee-earner boutique runs end-to-end inside a week, a 150-fee-earner firm runs as a phased adoption across two practice groups first. The proposal reflects the rollout, not the product.

Question 6

How long does implementation take?

Accepted Answer

Most firms are live inside a week. Connect email and calendar, import contacts (CSV, Excel, or from an existing CRM), and Lexi starts learning the same day. White-glove onboarding from day one — we onboard one firm at a time.

Question 7

Can we try Lexi before committing?

Accepted Answer

Yes. We do a “prove it on your data” read — a 5-minute audit of your email and calendar that surfaces dormant relationships and stalled deals before you sign anything. Request one via the contact form.

Question 8

What does “one firm at a time” actually mean?

Accepted Answer

We onboard each firm with the same handful of people who built the product. That’s deliberate — the firms in the founding cohort shape what LeadLex becomes for the firms after them. The throughput is the cost; the fit is the benefit.

Question 9

Can I import my existing contacts?

Accepted Answer

Yes — CSV, Excel, HubSpot, and most major CRMs. Field mapping and duplicate detection included. Salesforce, Clio, or anything bespoke, our team handles the migration for you.

Question 10

Can we migrate from an enterprise CRM like Intapp?

Accepted Answer

Yes. Most full-service firms with a serious IP group end up running LeadLex alongside an enterprise CRM rather than replacing it — IP-native for the IP group, enterprise for firm-wide governance. We support that pattern explicitly.

Question 11

What makes Lexi different from ChatGPT or other AI tools?

Accepted Answer

ChatGPT generates text you copy-paste. Lexi acts. She lives inside LeadLex, remembers every contact, runs multi-step workflows, drafts outreach in your voice, and updates your pipeline — then waits for your approval before anything goes out. She’s not a chatbot. She’s an associate.

Question 12

What does Lexi need access to?

Accepted Answer

Email, calendar, and your messaging channels — Slack, Teams, WhatsApp, Telegram — are where she works best. You control what she can see, and you can revoke access any time.

Question 13

Does Lexi send things on her own?

Accepted Answer

Never by default. Every outbound action — email, message, calendar invite — queues for your approval. You can grant Lexi more autonomy per relationship or per matter on a delegation ladder (Supervised → Co-pilot → Authorized → Blocked), and you can revoke any rung at any time.

Question 14

What happens if Lexi gets something wrong?

Accepted Answer

Every action she queues is editable before send. After send, there is a 24-hour undo window for messages where the protocol allows it, plus a full audit trail of every action she has ever taken on your behalf. Nothing she does is hidden.

Question 15

Will Lexi draft patent applications or legal opinions?

Accepted Answer

No. Lexi does business development — prospecting, outreach, meeting prep, pipeline, conference follow-up. She does not draft office actions, opinions, contracts, or any work product that touches privileged matter. That work belongs to the partners and associates.

Question 16

Can Lexi sound like our firm — and like each partner?

Accepted Answer

Yes. She learns the partner’s voice from her own historical outbound, and the firm’s tone from the broader corpus. Drafts arrive in the partner’s style by default, and the partner can edit before sending. The voice model is per-partner; one partner’s tone doesn’t bleed into another’s.

Question 17

What languages does Lexi work in?

Accepted Answer

English, German, French, Spanish, Italian, Portuguese, Dutch, plus growing coverage of Japanese, Korean and Mandarin. For IP firms with foreign-associate networks, multilingual drafting is part of the product.

Question 18

Where does Lexi’s contact data come from?

Accepted Answer

Prospector covers professionals across global registries and verified public filings, with IP-native filters layered on top — patent attorneys, trademark attorneys, in-house IP counsel, by jurisdiction and technology area. Your firm’s own data stays private, isolated, and never shared between tenants.

Question 19

Which IP registers do you ingest?

Accepted Answer

EPO Register, USPTO, EUIPO, WIPO PCT and Madrid System, JPO, KIPO, CNIPA, and the major national patent and trademark offices. UPC, EPO opposition divisions and several national IP courts for litigation signal. Coverage and update cadence are in the Integrations page.

Question 20

How do you turn IP filings into BD opportunities?

Accepted Answer

Lexi cross-references new filings, prosecution events, renewals, oppositions, and counsel moves against the firm’s footprint. Where there’s a match — an existing relationship, a prior matter, a target prospect — she surfaces the signal to the right partner with a drafted next step.

Question 21

How does Lexi help at INTA, IPBC and other IP conferences?

Accepted Answer

Pre-event briefings on confirmed attendees pulled from filings and relationship history; on-site card scanning that enriches and queues a follow-up automatically; personalised follow-up drafts in the partner’s voice within 72 hours of the close — the window where response rates actually convert.

Question 22

Is my client data safe?

Accepted Answer

EU-hosted (Frankfurt). GDPR-compliant. Built on SOC 2 Type 2 and ISO 27001-certified infrastructure. Complete tenant isolation. Your data is never used to train AI models — not ours, not anyone else’s. DPA signed with every firm.

Question 23

Is our data co-mingled with other firms?

Accepted Answer

No. Every firm runs on per-firm siloed infrastructure. The boundary is architectural, not policy. A query a partner runs is answered by a Lexi instance that has only ever seen that firm’s data.

Question 24

Do you train AI models on our data?

Accepted Answer

No. None. Not for ours, not for any model provider. The model sees what it needs to answer the question, returns the answer, and the data does not persist outside your siloed environment.

Question 25

How is this different from US-built legal AI?

Accepted Answer

Most legal-AI vendors are US-based companies on US infrastructure. For firms with European clients, regulated-industry clients, or strict data-residency requirements, EU-sovereign architecture removes a procurement-conversation gate that US-hosted tools don’t. We cover the question set in detail on the blog.

Question 26

How does LeadLex handle GDPR?

Accepted Answer

GDPR-native by architecture: lawful basis documented per processing purpose, data-subject rights served by the per-firm architecture, DPA on every plan. Not a compliance bolt-on.

Question 27

Are you EU AI Act-compliant?

Accepted Answer

Yes. Lexi’s use cases (BD support, drafting that requires human approval) fall outside the prohibited and high-risk categories under the Act. We publish an AI Policy that maps the product to the Act’s transparency and human-oversight requirements.

Question 28

Can we block Lexi from specific matters or clients?

Accepted Answer

Yes. Per-matter and per-relationship blocks are first-class controls. Privileged work, sensitive matters, anything ongoing in conflict — flag it once and Lexi stays out, with no exceptions in the audit trail.

Question 29

Does Lexi work with Claude via MCP?

Accepted Answer

Yes. LeadLex exposes its data and actions as a Model Context Protocol server, so Claude (and any future MCP-aware client) can read and act on firm data under the same permissions the user has. Setup takes about 20 minutes.

Question 30

Do you integrate with Anaqua, Clarivate, Questel, Dennemeyer or Patrix?

Accepted Answer

IP management system connectors are on the roadmap. Status varies by system — patentee/agent record sync first, deeper docketing integration second. Tell us which IPMS your firm runs and we’ll prioritise.

Question 31

How is LeadLex different from Harvey or Legora?

Accepted Answer

Harvey and Legora are AI for legal research and drafting — substantive lawyer work. LeadLex is AI for business development — the operating layer that wins and retains the work. The two coexist. We don’t compete on the same job.

See it run on your own book.

First, who are we meeting?

Built in Munich, for firms across Europe.

Where to find us.

Common questions, plainly answered

We onboard law firms one at a time.