Why Templates Lose in Business Development

A template can be sent to a hundred prospects in an afternoon. Almost none of them reply, and the ones who do rarely convert into anything worth the effort of sending the other ninety-nine.

What a recipient notices immediately

A senior contact at a public company receives dozens of pitches. The ones that get deleted without a second look are the ones that could have been sent to any company in the sector, generic praise, a generic pain point, a generic call to action. The recipient does not need to know it was templated to feel that it was.

What makes an outreach note land

A note that references something specific and true about the recipient's company, a recent leadership change, a detail from the latest filing, a specific number from their own numbers, signals that someone did the work of looking at them specifically. That signal is worth more than any line of persuasive copy a template can offer.

The real cost of templates

The apparent efficiency of a template is an illusion once response rate is factored in. Sending one hundred generic notes to get two replies is more expensive, in time per useful conversation, than sending twenty specific notes to get four replies. Volume without specificity is not actually efficient, it just moves the wasted time from writing to sending.

A quick way to audit your own last batch

Pull the last twenty outreach notes the firm sent and read only the first two sentences of each. If more than a few of those openings could be swapped between notes without anyone noticing, the firm has a template problem regardless of how the notes were produced, by hand or with AI assistance. The fix is the same either way: ground the opening in a specific, verifiable fact about that one recipient before anything else is written.

A short reframe for anyone who resists the audit

Team members sometimes resist this kind of audit because it can feel like a critique of their writing. Framing it instead as a check on whether enough specific research went into the note before drafting began, a process question, not a writing-quality question, tends to reduce defensiveness and keeps the conversation focused on the actual fix, which is upstream research, not sentence-level editing.

A final distinction worth keeping in mind

Efficient outreach and generic outreach are not the same thing, even though they can look similar from the outside at a glance. The test is always whether the recipient, reading closely, would conclude someone looked specifically at their company. Everything else, how the note was produced, how quickly, with what tools, is secondary to that one outcome.

Where this leaves a firm

None of this is complicated in principle, which is exactly why it gets skipped under deadline pressure. The question worth returning to before treating automating business development without hollowing it out as settled is what a careful reader would actually notice if the firm got it right. On the point raised above under “what a recipient notices immediately,” the answer is usually specific rather than clever: recipients recognize generic outreach even without being told it was templated. Firms that build this expectation into how they train new associates find it easier to sustain once experienced staff move on, because the standard lives in a documented habit rather than in one person's memory. The gap between a firm that talks about automating business development without hollowing it out and a firm that actually practices it shows up over several quarters, not in any single engagement, and it tends to show up most clearly in the small, unglamorous checks that a client never sees directly but benefits from anyway.

It also helps to name, plainly, who is responsible for keeping this working once the novelty of a new tool wears off. Someone should own the point raised under “what makes an outreach note land,” check it periodically rather than assume it stays true on its own, and be the person a colleague asks when a new situation does not fit the pattern described here. Put simply: fewer, specific notes usually outperform more, generic ones on a time-per-reply basis. That kind of ownership, named and specific, is a small addition to a firm's process, and it is usually the difference between a good idea that is followed for a month and a standard that actually holds up over a year of real client work.

None of this needs to be elaborate to be effective. A short, dated note in a shared file, reviewed at the next quarterly check-in, is usually enough to keep the responsibility from quietly disappearing when the person who first cared about it moves on to something else.

Key takeaways

  • Recipients recognize generic outreach even without being told it was templated.
  • Specific, verifiable details about the recipient's own company are what earn a reply.
  • Response rate, not send volume, is the right measure of BD efficiency.
  • Fewer, specific notes usually outperform more, generic ones on a time-per-reply basis.