Pipeline Automation
For firms that win work through referrals and relationships, we build the pipeline and relationship machinery that turns ad-hoc partner effort into a managed business-development process, capturing signals automatically so partners are not doing data entry.
For most firms above a certain size, new work does not come from a web form. It comes from relationships: referrals, repeat clients, cross-selling between practice groups, and the slow cultivation of prospects a partner has known for years. Managing that is a different discipline from intake, and a different kind of system. We build the pipeline and relationship machinery that turns ad-hoc partner effort into a managed business-development process, as part of our CRM & Sales Pipelines practice.
Intake CRM and relationship CRM are not the same tool
This is the distinction firms get wrong. Intake software like Lawmatics is built to convert inbound leads. Relationship CRM like Nexl, or a configured Salesforce, is built to grow the relationships a firm already has. A partner-driven practice that buys an intake tool to manage referrals will be disappointed, and vice versa. We start by being honest about how the firm actually wins work, then pick the tool that fits that, not the one with the best demo.
| Growth driver | What the pipeline tracks |
|---|---|
| Referrals | Who refers, what converts, who to thank |
| Cross-selling | Which clients use one group and could use another |
| Key relationships | Last contact, next step, owner |
| Pursuits | Open opportunities, stage, and value |
The hard part is relationship intelligence
The genuinely valuable, genuinely difficult capability is knowing who at the firm knows whom. That intelligence lives in inboxes and calendars, and harvesting it without becoming a surveillance tool partners resent is the art. Done well, a managing partner can see every touchpoint the firm has with a target client across every office. Done badly, it is a database nobody updates, which is exactly how InterAction installs end up dormant, a pattern we wrote about in why InterAction installs go dormant.
Adoption, again, is the whole game
A pipeline system only works if partners keep it current, and partners will not do data entry. So the design has to pull relationship signals automatically from email and calendar wherever it can, ask for the minimum manual input, and give partners something back, a clearer view of their own book, before it asks anything of them. The same adoption discipline we apply to matter management applies here, doubly, because the users are the busiest and least patient people in the firm.
A worked example
A mid-sized firm had bought a respected relationship CRM and watched it go stale within a year, because it relied on partners logging contacts they never logged. We reconfigured it to capture relationship signals automatically from Outlook, stripped the manual fields back to almost nothing, and gave each partner a simple view of their own relationships and lapsed contacts. Usage recovered because the system finally gave more than it asked, and the firm could see its cross-selling opportunities for the first time.
Common pitfalls we are brought in to fix
- Wrong tool class. An intake CRM for a referral-driven firm, or vice versa. Match the tool to how work is won.
- Manual data entry. Partners will not do it. Capture signals automatically or the system dies.
- No value to the user. A CRM that only serves management gets ignored. Give partners a reason to open it.
- Surveillance feel. Harvest relationship data with transparency, or you lose the room.
What good looks like
A firm with a working pipeline can see its referral sources, its cross-selling opportunities, and the state of every key relationship, without nagging partners for data entry. Business development stops being a black box of individual effort and becomes a managed process the firm can actually steer, and the data feeds genuine reporting on what the pipeline is worth.
From pipeline data to BD decisions
Visibility is the start, not the end. Once the firm can see its relationships, referrals, and open pursuits, the value is in acting on them: which lapsed clients to re-engage, which referrers to thank and feed, which cross-sell is one introduction away, which pursuit has stalled and needs a partner’s attention. We set up a light business-development cadence around the pipeline, a short regular review where the data drives who does what next, so the system changes behaviour rather than just recording it.
The trust-and-transparency line
Relationship intelligence works by reading signals from email and calendar, which makes partners nervous, rightly. The line between useful and intrusive is real, and crossing it loses the room permanently. We design for transparency: clear about what is captured and why, scoped to firm relationships rather than personal correspondence, and framed as a tool that serves the partner first. Get that right and adoption follows. Get it wrong and you have an expensive database nobody will touch, the same failure mode behind most dormant CRM installs.
Connecting BD to the rest of the firm
A pipeline system delivers most when it is not an island. The relationships it tracks should connect to the matters those clients actually run, so a partner pursuing a prospect can see the firm’s full history with them, and the intake that converts a lead should feed the relationship record rather than starting a separate one. We connect the pipeline to practice management and to intake, so business development sees one continuous picture from first contact through active matter to repeat instruction, instead of three disconnected views that each tell half the story.
That connection is also what makes cross-selling real rather than aspirational. When the pipeline knows which clients are active with which practice groups, the opportunity to introduce another service is visible and specific, not a vague exhortation at a partners’ meeting. The firm can see that a litigation client has never used the corporate team, route that to the right partner, and track whether the introduction happened. Cross-selling stops being a slogan and becomes a managed motion with an owner and a number attached.
How we engage
We map how the firm wins work, select the relationship CRM that fits, configure it to capture signals automatically and ask partners for almost nothing, give each user a view worth opening, and set the light cadence that keeps it alive. Run on retainer or handed over owned.
Business development as a system
A pipeline is most powerful when it is wired into the firm rather than kept as a partner’s private spreadsheet. It begins where intake ends, it informs who the communications programme should reach, and its data feeds the reporting that lets leadership see business development as a managed process rather than a black box. The firms that grow deliberately are the ones that treat BD as a system with inputs, stages, and measurable outcomes, not as a series of individual heroics that vanish when a rainmaker leaves. We build the pipeline as that system, connected to the rest of the firm and owned by someone accountable, so the relationships that drive the business are visible, maintained, and not dependent on any one person remembering to keep them alive.