From Rainmaker to Rainmaking Team: Building BD Capacity Beyond One Partner

Most intellectual-property boutiques have a partner whose retirement is a strategic problem. She originated twenty percent of the firm's revenue, knows fifty inside counsel by first name, and remembers the personal context of every relationship she built over thirty years. None of that lives anywhere a successor can read.

This is the rainmaker succession problem, and every firm we have worked with has some version of it. It is not solved by a retirement party or a one-day handover. It is solved by distributing relationship capital across the partnership over several years, deliberately, while the rainmaker is still active.

Why it does not happen on its own

Rainmakers do not naturally distribute their relationships. Three reasons, none of them malicious.

First, the compensation model usually rewards them for keeping the relationships. A partner who introduces a junior colleague to her best client is, in many firms, slowly reducing her own origination credit.

Second, the relationships are partly tacit. The rainmaker does not consciously know what she knows about a contact — the daughter's law school, the running grudge with the in-house IP director two companies ago, the preference for phone over email. She cannot dictate it because she does not know it as a list.

Third, succession is uncomfortable to talk about. The rainmaker knows retirement is coming; she does not want to spend her last active years systematically training a replacement. Most managing partners avoid the conversation until it is overdue.

What "distributing relationship capital" actually means

Two things. The relationships themselves — meaning the contacts know multiple partners at the firm, not just one. And the context — meaning what the firm knows about each contact lives in a system the next generation can read.

Both have to happen. Knowing the names without the context produces a partner who calls and has nothing to say. Having the context without the relationship produces a partner who knows everything about a contact who has no reason to take her call.

The five-year arc

We have seen this work when it is approached as a multi-year project with explicit milestones, rather than as a vague intention.

Year one: map the book. Catalog the relationships systematically. Not from memory — from email, calendar, billing, CRM, every available data source. The rainmaker reviews the map and adds what the data does not capture: who matters most, who is fragile, who is dormant, who is genuinely strategic.

Year two: pair on the warmest accounts. The rainmaker brings a designated successor partner into every meeting with the top twenty contacts. Not as a junior in the room — as a second partner being explicitly introduced as the next point of contact.

Year three: rotate the lead. The successor partner runs the next matter for those contacts, with the rainmaker still in the relationship but no longer the primary. The contact learns to call the successor first.

Year four: extend to the next tier. Repeat the pairing-and-rotation pattern with the next forty contacts. By now, several other partners are involved, not just one successor.

Year five: rainmaker steps back to strategy. She is in the firm, she remains involved with the most strategic accounts, but the day-to-day relationships have been handed off.

This arc compresses or extends depending on the rainmaker's timeline. The key is that it is an arc, not an event.

The role of the firm system

Distributing relationships at this scale is impossible without a system that holds the context. The rainmaker cannot remember to brief the successor on every contact. The successor cannot ask every question that needs asking before each meeting.

A BD platform that captures the relationship history — what was discussed, who else is involved, what matters are open, what the contact cares about — turns the implicit knowledge into something the firm owns. When the rainmaker eventually leaves, what stays is not just a list of names but the working context behind each one.

LeadLex is built for this. Lexi maintains the account history across partners, surfaces the dormant relationships before they cool, and queues the introductions that move a contact from one partner's book to two. The compensation politics still have to be worked out at the partnership level. The infrastructure that makes distribution possible should not also be the bottleneck.

The firms that handle succession well start the project a decade before they need it. The firms that handle it badly start it the year the rainmaker announces her retirement, and watch a quarter of their revenue walk out with her.

Related: In-House Counsel Moves Are the Most Underused BD Signal. What a Relationship Strength Score Actually Measures. The Managing Partner Adoption Playbook.