BD for IP Litigation Groups: A Docket-Driven Approach

IP litigation BD does not look like the rest of legal business development. There is no top-of-funnel volume to optimise, no email cadence that scales linearly, and no proxy metric that meaningfully predicts a mandate. The work runs on dockets, not campaigns. Fewer mandates, longer cycles, sharper conflicts — and far more partner time per dollar of pipeline.

Why the standard BD model breaks

A trademark prosecution practice can run a respectable BD operation off filing data, renewals, and a steady contact cadence. A litigation group cannot. The mandates are too lumpy, the conflicts are too sensitive, and the buyer behaviour is too event-driven. By the time a litigation buyer is in the market, the shortlist is usually already informal — three or four names that come to mind, often shaped by reputation, prior engagement, and a single decisive recommendation.

The implication is that BD for litigation has to be done long before the trigger event. It is relationship work disguised as information work. The firms that win the unexpected call are usually the ones that have been quietly relevant for two years.

The docket as the unit of BD analysis

The docket is the primary BD instrument for an IP litigation group. New filings at the UPC, national patent courts in Germany, the Netherlands, France, and Italy, the ITC and federal district courts in the United States, and the trademark and design tribunals all produce structured signals. Each filing tells you who is suing whom, in what venue, on what asset, with what counsel.

That information has three BD uses. First, it identifies parties who have just demonstrated they are willing to spend on litigation. Second, it identifies counsel relationships that are now visible and potentially shiftable. Third, it identifies adjacent parties — co-defendants, suppliers, customers — who are likely to be drawn into the dispute and will need their own representation.

Lexi reads the dockets across the venues that matter to the firm, tags new filings against the firm's prospect map and conflicts list, and surfaces the cases that warrant a partner's attention. She does not draft the strategy memo. She makes sure the partner sees the filing within hours rather than weeks.

Conflicts as a BD constraint

A litigation group cannot pursue every signal. Conflicts narrow the addressable pipeline more than most BD plans acknowledge. A serious litigation BD operation runs conflicts checks early, ideally before outreach, and treats the conflicts function as a partner to BD rather than an obstacle to it.

The practical consequence is that the BD pipeline for a litigation group should be smaller and more deliberate than for a transactional practice. Twenty live prospects that have cleared conflicts and have an identified path to a mandate are worth more than two hundred names in a spreadsheet.

Cycle length and how to think about it

A litigation mandate often originates from a relationship that was built over years. The BD investment is front-loaded and the payoff is back-loaded. That makes pipeline reporting unusually difficult — a partner who has done excellent BD for eighteen months may still have nothing to point to in a quarterly review.

The honest answer is to report on inputs, not just outputs. Meaningful inputs include depth and frequency of contact with target accounts, presence at the conferences where buyers congregate, visible authorship on the substantive issues the buyers care about, and timely outreach following docket events. A practice group leader who reports on these inputs and tracks conversion over multi-year windows will run a better litigation BD operation than one who chases quarterly numbers.

Conferences, judgments, and the slower channels

The slower BD channels matter disproportionately for litigation. Conferences such as AIPPI, INTA, and EPLAW are where reputations are reinforced. Published judgments are where expertise becomes visible. Speaking slots, panel appearances, and written commentary on significant decisions all build the kind of recognition that puts a name on a shortlist.

Lexi tracks the conference calendar, maps which target accounts will be present, suggests outreach windows ahead of each event, and prepares briefing notes that pull together the recent docket activity, prior contact history, and current matters for each meeting. The partner walks into the coffee with the right context.

What practice group leaders should actually do

Build the BD operation around the docket, the conflicts map, and the conference calendar. Accept that the pipeline will be small and the cycles will be long. Report on inputs honestly. And invest in the slower channels — they are slower for everyone, which is precisely why they are defensible.

Related: The Four Functions of Legal BD. Calendar as a BD Instrument. Practice-Group Leader BD Ownership.