A BDR function is a machine for producing qualified pipeline. Most are machines for producing meetings.

Every few months someone declares the BDR dead, replaced by an AI that fires ten thousand emails before lunch. Then you look at the pipeline that machine built, and it is the same pipeline the spray-and-pray teams built a decade ago: enormous, busy, and empty.

The BDR is not dead. The way most companies run the function is. A business development team is one of the highest-leverage things a B2B company can build and one of the easiest to wreck, because it gets measured on the wrong thing, handed the wrong inputs, and paid on a plan that changes the moment a quarter looks shaky. This is the blueprint we use when we build or rebuild one. It is opinionated on purpose, because a BDR function that tries to please everyone ends up measuring everyone’s favourite vanity number and producing none of the pipeline any of them actually wanted.

Start with the lane, not the script

A BDR with no lane is a BDR pointed at the whole market, which is the same as being pointed at nothing. The first decision is not the script or the sequence or the tool. It is the lane: the specific slice of the world this person is responsible for knowing better than anyone else in the building.

A lane can be an industry, a product line, a segment, a geography, or a motion. Agricultural equipment in the DACH region. The enterprise tier of one product. Inbound demo requests from healthcare. What matters is that it is narrow enough for the BDR to build real pattern recognition: the language these buyers use, the objections that come up every week, the trigger events actually worth a call.

Focus is not a constraint you impose on a BDR. It is the thing that makes them good. A rep who calls the same kind of buyer all week learns how that buyer thinks. A rep who calls a manufacturer on Monday and a fintech CFO on Tuesday learns how to read a script, which is a different and much less valuable skill. The ICP work is what draws the lane; the lane is what makes the ICP operational.

The manager’s job is to protect it. Every “can you also just cover this” is a small tax on the pattern recognition you were trying to build. Say yes to enough of them and you have turned a specialist back into a switchboard. We have watched exactly that happen: a capable operator quietly re-tasked into a generic BDR seat, measured on volume, producing pipeline that fell apart the moment anyone checked it against the recordings.

Define a real conversation before you count one

Here is the failure that turns up in almost every audit. The team is measured on meetings or conversations, and nobody ever wrote down what a real one is. So the count climbs and the pipeline does not, because a good share of what got counted was a polite five-minute call that was never going anywhere.

Before you count a single conversation, define the bar it has to clear. That is a qualification standard, and BANT (budget, authority, need, timing) is still a perfectly good frame, as long as you treat it as a list of what the rep needs to learn, not a script to interrogate someone with.

Then be honest about how qualification actually happens in your motion, because it is rarely all four on the first call. Sometimes need and timing surface in the first conversation and budget and authority get confirmed by email before the meeting. Sometimes the cleanest signal is the buyer qualifying themselves: booking through a link, answering three questions on a form, replying to a specific question in a way only a real buyer would bother to. All of those are valid. What is not valid is leaving it undefined, because then every rep sets their own bar, and the reps who set it lowest look like the top performers right up until the AEs revolt.

So write it down. A qualified conversation is one where these specific things are known and recorded. Everything else is a conversation, which is fine, and often useful, but it is not the thing you forecast on or pay for.

The handover is an event, not a field change

A lead is not handed over when the owner field changes. It is handed over when a human on the other side has accepted it and started work. The gap between those two things is where BDR-sourced pipeline quietly dies, and it is the same crack that swallows leads at every other handoff in the funnel.

A complete handover is documented and measurable, which means the record carries everything the AE needs and nothing they have to go back and ask for: who the person is, what was said, the qualification you confirmed, the specific pain, and the next step already on a calendar. If the AE has to re-interview the prospect, the handover failed, and the prospect feels it as a company that does not talk to itself.

Then close the loop. The AE accepts or rejects the handover, with a reason, in the CRM. Accepted-and-worked is the number that matters, not thrown-over-the-wall. A rejected handover is not something to punish; it is the single most useful piece of feedback a BDR can get, because it shows precisely where their bar and the AE’s bar have drifted apart. A BDR function with no accept-or-reject loop is a team flying blind, hitting a target nobody downstream has agreed to.

Measure the outcome, not the motion

This is the heart of it, and the question most teams get wrong: what is the real KPI? The honest answer is that most of the numbers a BDR team reports on are not it.

Walk the chain a lead travels and ask, at each step, whether it is a leading indicator worth a target or a vanity number that will be gamed the moment you attach one to it.

Calls and emails are pure activity. Useful as a diagnostic when something is clearly broken, useless as a target, because measure them and you get more of them, which is not the same as more pipeline. Conversations are better, but only against the written bar from the section above; otherwise they are calls wearing a nicer name. Qualified meetings booked is the first number a BDR can be proud of and an AE can use. Meetings held is the first fully honest one, because booked and held differ by exactly the no-show rate, and the no-show rate tells you how real the booking was. A team paid on booked meetings will book meetings that do not happen. A team paid on held meetings books meetings that do.

Here is the part that matters for a long cycle, which was the real question. If your deals take six or nine months to close, you cannot run a BDR team on closed-won, because the feedback lands two quarters after the work and half the reps who did it have moved on. So you measure the best available leading indicator of that lagging outcome, and for most considered B2B sales that is qualified meetings held that the AE accepted and that advanced to a genuine next step. You keep the lagging number, sourced pipeline and eventually sourced revenue, as the scoreboard you check the leading indicator against, so the two never drift apart unnoticed. That drift, incidentally, is one of the reasons a forecast built on activity is always wrong.

Pick one primary metric, the one closest to the outcome that the BDR still genuinely controls. Then wrap it in two or three guardrails so it cannot be gamed: an acceptance-rate gate, so meetings held cannot be padded with junk, and a volume floor, so quality never becomes an excuse for doing nothing. One number to move, a couple to keep it honest. Any more than that and you are measuring everything, which is the same as measuring nothing. The reports and metric definitions for this are laid out, by business type, in the sales ops cheat sheet.

And the oldest rule in operations, worth saying plainly: the moment a measure becomes a target, it stops being a good measure. That is not cynicism about your team. It is how incentives work on everyone, you included. Which is exactly why the metric has to sit as close to the real outcome as you can get it, so that gaming the number and doing the job become the same activity.

Pay for results, and do not move the goalposts

A BDR works a hard, repetitive, high-rejection job for two things: to get good, and to get paid. The comp plan is not an HR detail bolted on afterwards. It is the strategy, written in the only language that survives a bad week.

Keep it straightforward. A base someone can actually live on, plus a variable tied to the primary outcome metric from the section above, not to raw activity. Pay for dials and you will get dials. Pay for accepted, held, qualified meetings that turn into pipeline and you will get those. Reps optimise for exactly what the plan pays, every single time, and that is not a character flaw. It is the plan working as designed.

Then the rule almost nobody honours and everybody should: do not change the plan without a real reason, and never change it retroactively. A real reason is a budget cut, a pivot, a genuine product change. A quarter that came in light is not a real reason; it is usually the plan telling you the truth about the strategy. And whatever you change going forward, anything a rep already earned under the old plan gets paid under the old plan. Full stop. The first time a BDR watches a commission they earned get clawed back by a rule invented after the fact, you have not saved money. You have taught the entire team that the number on the plan is a suggestion, and every one of them has quietly repriced their effort to match.

Comp stability is not generosity. It is the cheapest retention and motivation lever you own, and it costs you nothing right up until the moment you are tempted to break it.

Policy and transparency, or the team works against you

This is the one most managers learn too late, often on their way out the door.

When a go-to-market strategy is failing, there is a strong pull to change the rules on the people executing it: raise the quota, move the definition of a qualified meeting, reshuffle the territories, bolt on an activity minimum. It feels like decisive action. It is almost always a manager trying to fix a strategy problem by squeezing the layer beneath them, because that layer is the only one they control.

It does not work, and it fails in one of two ways. Either the team was capable and the strategy was the problem, in which case you have just demoralised or fired people who would have succeeded with a better plan, and sent the real cause out the door with them. Or the team senses that the goalposts move whenever the numbers are inconvenient, stops trusting anything you say, and a group that could have been on your side quietly starts working around you. Both roads end in the same place: the strategy still fails, and now you have failed as a manager on top of it.

The alternative is not softness. It is a clear policy, published, applied evenly, and changed only for reasons you are willing to say out loud. Transparency is a control system, not a nicety. A team that knows the rules, and trusts that the rules are stable, will tell you the truth about what is happening in the market, and that truth is the only thing that actually fixes a failing strategy. A team that has learned the rules are whatever this quarter needs them to be will tell you what keeps them safe, and you will be the last person in the building to know your strategy is already dead.

The inputs decide the output

A BDR is a processor, and a processor is only ever as good as what you feed it. Hand a brilliant rep a list scraped off the internet last year, with no ICP behind it and no message that fits the lane, and you will get a brilliant rep producing garbage, right up until they leave for a company that hands them something better.

The inputs are the list, the data behind it, the ICP that shaped it, and the words the rep goes in with. Get those wrong and no activity target will rescue you; you are just paying someone to work a bad list faster. Most “our BDRs are underperforming” conversations turn out, on inspection, to be “our BDRs are being handed bad inputs and blamed for the result” conversations. Clean the data and draw the lane before you touch the quota, or the enrichment will just be confident guessing dressed as fact.

Ramp and capacity are numbers too

Two measurements teams skip because they are less satisfying than a big activity dashboard.

Ramp, first. A BDR is not judged in week three. Set ramp milestones, learning the lane, first qualified conversation, first accepted meeting, full quota by a defined month, and measure against those, so you can tell the difference between a rep who is failing and a rep who is still learning. Fire the first kind without drama. Coach the second. Confusing the two is how you churn people who were three weeks away from good, and then wonder why hiring never gets ahead.

Capacity, second. The target has to come from the funnel math, not from whatever the board needs the number to be. If it takes a known volume of touches to earn a conversation, and a known number of conversations to earn a qualified meeting, then a BDR’s realistic capacity is arithmetic, not ambition. Targets set above what the math allows do not raise output. They raise the rate at which reps cut corners to hit a number that was never honestly reachable, and you are back to the empty pipeline you started with.

Coaching is the job, not the overhead

A BDR function with no coaching is a hiring treadmill. The role is hard and repetitive, the feedback from the market is mostly rejection, and the one thing that reliably turns a raw hire into a producer is someone sitting down with real calls every week and working through them. Conversation-intelligence recordings exist precisely so this is possible. Use them to coach, not only to check up.

The manager who spends the week inside dashboards instead of inside call reviews is managing a spreadsheet, not a team. The dashboard tells you the number is down. The recording tells you why, and only the second one is coachable.

Log it, or it did not happen

None of this works if the work is not in the system. The pattern we find over and over in audits is a team whose real activity lives in someone’s head, or in a meeting recorder, or buried in an inbox, sitting next to a CRM that shows a tidy, invented version of events.

We once matched a client’s call recordings against their CRM and found a large share of the open pipeline was attached to conversations that were never really meetings. The recordings existed. The discipline to log honestly did not, and the forecast was fiction as a direct result. That is the whole story of the phantom pipeline.

The rule is boring and non-negotiable: if it is not in the CRM, it did not happen. Not as a stick to beat the team with, but because a BDR function you cannot see is one you cannot coach, cannot measure, cannot pay fairly, and cannot defend when someone senior asks whether the pipeline is real. It is also why marketing quietly fails when sales do not use the CRM: no logged activity, no timeline, no idea what actually happened.

A path out, or you keep paying to hire

BDR is a starting role, and everyone in it knows it. The best ones are gone inside a year, either up into an AE seat or out to a company that offered them one. That is not disloyalty. It is the job working as intended. The mistake is pretending otherwise and being surprised on the same twelve-month cycle, every year.

Build the path in. A visible route to AE, or to ops, or to marketing, with criteria the rep can actually see, turns your BDR bench into the recruiting pipeline for every closing role you will need next year. Sustainable, the word that started all of this, does not mean nobody leaves. It means the people who leave the seat mostly stay in the building, and the hard-won knowledge of the lane stays with them instead of walking across the street.

A five-minute health check

The blueprint above is a lot to hold at once, so here it is as ten statements. Tick the ones that are already true of your team and read where you land. It is not a scientific instrument; it is a mirror.

The blueprint on one page

None of this is complicated, which is the genuinely frustrating part. Draw the lane and protect it. Define what a real conversation is before you count one. Make the handover an event you can measure, with an accept-or-reject loop behind it. Pick the one outcome metric that fits your cycle, guard it, and pay for it. Do not move the line, and honour what was earned. Keep the policy stable and the reasons honest. Feed the team good inputs, coach them off real calls, and give them somewhere to go.

Do that and a BDR function is one of the most reliable pipeline engines a B2B company can own. Skip it and automate the gaps instead, and you will build the thing half the market is quietly building right now: a very fast machine for producing meetings nobody wanted, measured by a number nobody trusts, run by a team already updating their CV.

Common questions