The IP Conference Loop, End to End: INTA, ECTA, MARQUES, AIPPI

Every year, the IP profession reconvenes. INTA's annual meeting in May. ECTA's annual conference in June. MARQUES in the autumn. AIPPI's World Congress shortly after. Smaller regional events — INTA Trademark Administrators, the EPO's user gatherings, the Asian regional IP events — punctuate the calendar between the big four.

Each event compresses the same opportunity into three days. A few hundred meetings booked. A few thousand handshakes that could be meetings. Several thousand business cards exchanged across the floor.

And, in most firms, a stack of those cards sits on the partner's desk in the second week of the following month, and the names quietly fade out of memory by the time the next event lands.

This is the IP conference loop, and almost no firm runs it well. The reason is not effort. It is that the loop is three workflows — preparation, on-site capture, post-event follow-up — and at most firms each of them lives in a different place, with a different owner, and a different rhythm. The handoffs are where the value leaks.

LeadLex was built to close that loop.

Before: preparation as a system, not a scramble

Two weeks before a conference, Lexi reviews the partner's calendar for confirmed meetings and cross-references them against existing firm relationships. Each attendee gets a per-person briefing note — their recent IP filings pulled from the public registers, their role and tenure, the firm's history with their company or with them personally, and a suggested angle for the conversation.

For a partner attending INTA with twelve confirmed meetings and twenty soft introductions, the difference between walking in cold and walking in prepared has historically been five hours with an analyst. LeadLex returns those five hours and produces sharper briefings — because the analyst was never going to pull the EPO record on every attendee.

On-site: capture without the catch-up

The card scan workflow on the conference floor is the single most useful product surface LeadLex has built. A partner photographs a card with their phone. Lexi extracts the contact details, validates against the firm's existing records, links the contact to any public IP filings on which they appear as agent, applicant or inventor, and queues a follow-up draft before the partner leaves the venue.

The partner is not opening a CRM. The partner is not promising to "log it later". The partner is taking a photograph and continuing the conversation.

For an event that produces sixty meaningful interactions across three days, that workflow is the difference between a CRM that has gained sixty enriched contacts and a desk drawer that has gained sixty business cards.

After: personalised at scale

The post-event work is where most firms quietly underperform. A partner returns from INTA with good intentions, sends three or four well-crafted follow-ups, and stops when the practice ramps back up. The remaining sixty contacts hear from the firm, if at all, weeks later, in a generic template that signals exactly what it is.

LeadLex generates the post-event follow-up sequence in the partner's voice — not a generic template, but a personalised note that references the specific conversation, any IP work the contact's company has on file, and a concrete next step. Every draft sits in the partner's approval queue. Approving a batch of sixty takes about ten minutes; not approving them takes nothing at all.

The result is a follow-up rhythm that scales the partner's attention without scaling the partner's time.

What changes

The economic case for closing the conference loop is the case for measuring conferences correctly. Most firms measure them by cards collected. The right measurement is mandates won and relationships sustained twelve months out — and on that measurement, the firms that run the loop end-to-end consistently outperform the ones that don't.

LeadLex is tuned for the major IP events on the circuit. The conferences change. The loop does not.

Related: The 30-minute pre-meeting workflow inside Lexi. How Prospector reads market and filing signals continuously.