The conversation almost always starts the same way. A managing partner, or a head of business development, or someone with a title that includes the word “growth,” gets in touch and says something like: “We want to automate our follow-up.” It sounds like a reasonable, well-defined request. It sounds like something that has a beginning, a middle, and a deliverable at the end. It is, in fact, the beginning of a much more interesting and occasionally uncomfortable conversation - because the first question you have to ask is: “What is your follow-up?”
The answer, more often than not, is silence. Or a version of silence dressed up as a sentence. “Well, we send them something after the meeting.” What do you send? “Depends on the partner.” When? “Fairly soon after.” What happens if they don’t respond? “We chase.” When? “When we remember.” What does the chase look like? “It depends.”
This is not a criticism. This is the normal state of affairs in professional services firms that have been operating successfully for years, sometimes decades, without ever needing to write down how their business development actually works. The work came in, the clients were served, the partners did what they did, and it was fine. The follow-up process lived inside people’s heads, and heads were sufficient.
Until you try to automate it. At which point you discover that what you thought was a process is actually a collection of habits, instincts, and individual preferences that differ between every partner in the firm, and that nobody has ever reconciled.
The algorithm that lives in someone’s head
There is usually a senior partner - sometimes more than one - who is genuinely excellent at business development. They seem to know when to call, what to say, how long to wait, when to push and when to back off. They win work that other partners don’t, and the firm regards them with a mixture of admiration and mild bewilderment.
What this person is doing, whether they realise it or not, is running an algorithm. It is a sophisticated one. It takes into account the type of prospect, the nature of the initial conversation, the signals given during the meeting, the sector, the likely decision timeline, the competitive landscape, and a dozen other variables that the partner processes without conscious effort. They have built this algorithm over twenty years of practice, refinement, and pattern recognition. It works extremely well. It is also completely undocumented, entirely non-transferable, and will leave the firm the day they do.
When someone says “automate our follow-up,” what they often mean, without knowing it, is “replicate what David does, but for everyone, and without needing David.” This is a perfectly reasonable ambition. It is also impossible to achieve without first understanding what David actually does - which David himself may not be able to explain.
The gap between instinct and instruction is where most automation projects stall. Not because the technology is inadequate, but because the thing you are trying to automate has never been described with enough precision to be automated. You cannot build a sequence for something that has never been a sequence. You cannot set triggers for a process that has no defined triggers. You cannot write the rules for a game that has always been played by feel.
The mirror effect
This is the part that firms rarely expect and almost always find valuable, even when it is uncomfortable. The act of trying to automate something forces you to describe it. And the act of describing it forces you to confront what is actually happening versus what you assume is happening.
When you sit down to map a follow-up workflow - what happens after an initial enquiry, after a meeting, after a proposal is sent - you have to answer questions that the firm has never formally asked itself. What constitutes a qualified lead? At what point does an enquiry move from “interested” to “engaged”? Who is responsible for the next action? What is the next action? How long do you wait before a second touch? What changes if the prospect is in financial services versus property versus private client? What happens when nobody responds for three weeks - do you keep going, or do you stop?
These questions sound basic. They are basic. That is precisely why they have never been asked - they feel too obvious to require a formal answer. Everyone assumes the answers are understood. They are not. Ask three partners in the same firm to describe the follow-up process and you will get three different descriptions. Sometimes the differences are minor. Sometimes they are structural. One partner follows up within twenty-four hours; another waits a week. One sends a tailored email referencing the conversation; another sends a generic capabilities document. One chases three times before stopping; another chases once and moves on. None of them is wrong, exactly. But they are not the same process, and the firm has been operating as though they are.
Automation acts as a mirror. It reflects back to the firm the reality of its own operations, stripped of the comfortable ambiguity that allows everyone to believe they are doing roughly the same thing. The reflection is not always flattering, but it is always useful.
The mapping exercise is the product
There is a tendency, when firms engage with automation, to treat the mapping phase as a preliminary step - the admin you have to get through before the real work begins. The real work, in this framing, is the technology: the CRM configuration, the email sequences, the triggers and workflows and integrations. The mapping is just preparation.
This is backwards. The mapping exercise - the process of defining, in explicit and agreed terms, what the firm’s business development follow-up actually looks like - is the most valuable thing the firm will get out of the entire project. If you stopped after the mapping and never touched a piece of software, the firm would still be materially better off than it was before.
Because what you end up with is not just a document. You end up with a shared understanding. For the first time, the firm has a common language for how it develops business. The partners have agreed - actually agreed, in a room, with specifics - on what happens after a meeting. On what a good follow-up looks like. On when to escalate, when to pause, and when to let something go. On what information needs to be captured, and where, and by whom.
This shared understanding changes behaviour even without automation. Partners who previously operated in isolation begin to operate with a degree of consistency. Junior staff who had no framework for follow-up now have one. The firm’s approach to business development becomes something that can be taught, measured, and improved - rather than something that exists as folklore.
Why instinct doesn’t scale
The senior partner running their internal algorithm is not a problem when they are the only person who needs to do business development. It becomes a problem when the firm wants to grow, when it hires laterals who need to develop their own clients, when it promotes associates who have never been taught how the work actually arrives.
Instinct is, by definition, personal. It is the product of one person’s experience, applied in one person’s context, and refined by one person’s feedback loops. It cannot be shared by sending a memo. It cannot be onboarded. It cannot be quality-controlled. When a firm relies on instinct for a function as critical as business development, it is making a structural bet that the people who have the instinct will always be there, will always be available, and will always be right. This is not a bet most firms would consciously choose to make, but it is the bet they are making by default.
Automation forces the conversion of instinct into instruction. It requires you to take the thing that David does by feel and express it as a series of decisions, conditions, and actions that someone else - or something else - can execute. This is not about removing David’s judgment. It is about making the baseline transferable. David’s instinct can still override the system. David’s experience can still add nuance. But the firm is no longer dependent on David being in the room for the basics to happen.
The firms that resist this exercise often do so because they believe their business development is too nuanced, too relationship-driven, too human to be reduced to a workflow. They are usually right that it is nuanced. They are wrong that documenting it reduces it. Documenting the process does not flatten the nuance - it creates a foundation on which nuance can be applied deliberately rather than accidentally.
What the technology actually does
Once the mapping is done - once the firm has described, in concrete terms, what its follow-up process should be - the technology becomes almost straightforward. A CRM configured to reflect the actual stages of your pipeline, not a generic template. Email sequences that trigger based on defined events: a meeting was held, a proposal was sent, a period of silence has elapsed. Task assignments that ensure someone is always responsible for the next step. Reporting that shows where prospects are getting stuck, where follow-up is falling off, and where the process is working.
None of this is exotic. The technology to do all of it has existed for years and is, by the standards of what technology can do in 2026, relatively simple. The reason most firms have not implemented it is not that the tools are expensive or complicated. It is that the tools require you to tell them what to do, and the firm has never decided what that is.
This is the real bottleneck. It was never the software. It was never the budget. It was never even the time. It was the absence of a defined process to automate. The technology was waiting. The firm was not ready.
The uncomfortable admission
Saying “we don’t have a process” feels like an admission of failure for firms that have been operating successfully for a long time. It shouldn’t. Having an undocumented process is not the same as having no process - it means the process exists but has never been made explicit. Every firm that has been winning work for years is doing something right. The question is whether they know what that something is, and whether they can do it reliably when circumstances change.
The firms that engage honestly with this exercise - that sit down and say “we actually don’t know what happens between the first meeting and the instruction, and we’d like to” - are the ones that get the most out of automation. Not because the technology transforms their business overnight, but because the conversation transforms how they think about business development. It moves from being something that happens to being something that is managed.
Automation does not replace your process. It does not even improve your process, not initially. What it does is hold up a mirror and say: describe this. And in the act of describing it, you build the thing you thought you already had.