Building a BD engine that doesn't rely on the founder

Most BD pipelines are clogged with deals nobody should be chasing. Before any outbound or partnership work begins, write a one-page ideal-customer profile: industry, size, trigger event, who signs the check, and the specific outcome they hire you to deliver. Then build a do-not-pursue list that's just as specific. Half of BD discipline is the willingness to say no to plausible-looking deals that don't fit the motion.

Founders fail at BD because they try to do both inside the same hour. Sourcing is a daily, low-emotion activity — research, list-building, warm intros, follow-ups. Closing is a high-attention, low-volume activity — conversations, proposals, negotiation. Block sourcing in the mornings, closing in the afternoons, and never let one bleed into the other. The two activities require different headspaces and rarely co-exist well.

Pick three channels and run them for a quarter before adding a fourth. Typical winners: warm intros via a curated partner network, targeted outbound to a tight ICP list, and visible expertise (podcast appearances, written teardowns, conference talks). Each channel gets a named owner, a weekly KPI, and a written sequence. If the channel can't be handed to someone else inside a year, it isn't a channel — it's a personality trait.

Every deal should sit in exactly one stage at any time, and the criteria to move between stages should be black-and-white. 'Discovery → Scoping' might require a written problem statement and budget confirmation. 'Scoping → Proposal' might require a signed mutual action plan. Without exit criteria, deals rot in pipeline purgatory and forecasts become fiction.

Thirty minutes, same time every week, three questions per deal: what's the next concrete step, who owns it, and when does it happen. Kill anything that hasn't moved in 30 days unless there's a written reason. This single meeting — done with discipline — is more valuable than most CRM implementations.

Closed revenue is a lagging indicator. Conversations booked, proposals sent, and qualified pipeline created are leading indicators. A BD engine that only watches revenue is driving while looking in the rearview mirror. Track the leading metrics weekly and the lagging ones monthly.

The right time to bring in a BD hire is when the playbook is written and a clear role can be handed over — not when the founder is already drowning. Hiring under duress almost always produces a mis-hire. Build the system first, then bring in the operator to run it.