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 autonomous AI SDR just automated the old mistake and made it cheaper to run at scale.

The BDR is not dead. Most companies just run the function in a way that slowly kills it. A business development team is one of the highest-impact things a B2B company can build and one of the easiest to wreck, and it usually gets wrecked in three specific ways: it is measured on the wrong thing, handed the wrong inputs, and paid on a plan that changes the moment a quarter looks shaky. Fix those three and most of the rest follows. Get any one of them wrong and no amount of activity or fresh tooling will save the number.

This is the blueprint we use when we build or rebuild one, in the same order we would build it inside a client’s CRM. It is opinionated on purpose, because a BDR function that tries to please everyone ends up measuring everyone’s favourite vanity metric and producing none of the pipeline any of them actually wanted. The diagrams below are live too, so tap the rungs of the metric chain, flip the cycle toggle, and run your own team through the health check at the end. Read it through for the argument, then use the interactive pieces to pressure-test it against your own team.

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 the lane, well before the script or the sequence: 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, or the enterprise tier of one product, or 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 and the trigger events actually worth a call.

Focus is what makes a BDR good in the first place. A rep who calls the same kind of buyer all week learns how that buyer thinks, which questions open them up and which ones close them down, what a real buying signal looks like in that world as opposed to a polite brush-off. A rep who calls a manufacturer on Monday and a fintech CFO on Tuesday learns none of that. They learn to read a script, which is a different and much less valuable skill, and it happens to be the one skill an AI already has. The ICP work is what draws the lane; the lane is what makes the ICP operational, the difference between a slide that says who you sell to and a rep who can recognise them on the phone.

There is a limit in the other direction as well. A lane has to hold enough addressable accounts to keep a full-time rep busy without burning the entire list inside a month, which is a capacity question, and capacity comes down to arithmetic. It also has to match the motion you have actually chosen. An outbound lane and an inbound lane are different jobs with different metrics, and running one rep across both is a fast way to end up running four go-to-market motions and none of them well.

Watch, too, for lanes that look identical on a slide and behave nothing alike in the field. Nordics, DACH and North America each carry their own idea of what a qualified conversation even is, which is why a global number built from three local definitions of “qualified” tends to be expensive fiction. Draw the lane around how buyers actually behave, not around how the org chart is coloured in.

Once the lanes are drawn, the manager’s job is to protect them. 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 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

The same failure 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 the rep treats it as four things to come away knowing and not a script to interrogate someone with. Read it out like a checklist and the rep sounds like a form. Keep it in the back of the mind and it just becomes good listening with a purpose.

Notice what the four have in common: not one is reliably answered on a first cold call, and pretending otherwise is where a lot of so-called qualified pipeline goes wrong. So be honest about how qualification actually happens in your motion. 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 ways to clear the bar. What is not valid is leaving the bar undefined, because then every rep sets their own, and the reps who set it lowest look like the top performers right up until the AEs revolt.

So write it down, and write it down with the people who receive the work. A qualified conversation is one where these specific things are known and recorded, agreed with the AEs who have to act on it, not handed down by a manager who never takes the meeting. That agreed line is your sales-accepted lead, and it only means something if both sides signed it. Give the qualification its own field in the CRM rather than smuggling it into the deal stage, because a stage doing two jobs is exactly why the pipeline report lies. Everything below the bar is still 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

Changing the owner field does not hand a lead over. The handover happens when a human on the other side has accepted it and started work. The gap between those two moments is where BDR-sourced pipeline 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 in the buyer’s own words, 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, which is a poor way to start asking someone to buy. Half of that record only exists if the BDR actually logged the call, a discipline problem we will come back to.

Give the pass a clock, the way you would any handoff worth trusting. If the AE has not accepted and actioned the lead inside a defined window, it escalates or reassigns on its own instead of sitting in a queue nobody owns. Without a deadline the trigger is just a suggestion, and leads cool while they wait on suggestions.

Then close the loop. The AE accepts or rejects the handover, with a reason, in the CRM. The number that matters is accepted-and-worked, not thrown-over-the-wall. A rejected handover is worth more than it looks, because it shows precisely where the BDR’s bar and the AE’s bar have drifted apart, which is the most useful thing a BDR can learn. A BDR function with no accept-or-reject loop is a team flying blind, hitting a target nobody downstream has agreed to, which is how you get a BDR team celebrating a record quarter while the AEs grumble that none of it was worth working.

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. They are the numbers that were easy to count, which is not the same thing, and the gap between easy-to-count and worth-counting is where a whole function can waste a year.

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. Tap a rung to see which is which, and use the toggle, because the honest answer genuinely changes with the length of your sales cycle.

Calls and emails are pure activity. They earn their keep as a diagnostic when something is clearly broken, but set them as a target and you just 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 happily book ones that never happen; move the pay to held meetings and the no-shows dry up on their own.

For a long cycle, this is the part that actually answers the 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. That is one number to move and a couple to keep it honest. Pile on any more and you end up measuring everything, which gets you the same visibility as measuring nothing.

One more trap hides inside the long cycle: attribution. A deal the BDR sourced in March closes in November, long after everyone has stopped thinking about who started it, so the pull is to fall back on activity, because at least activity happens this week. That pull is worth resisting. Stamp the sourcing BDR on the deal at creation and let the credit travel with it, so a rep can see, months later, that the meeting they booked became real revenue. Keep sourced and influenced pipeline separate and be honest about which is which, and make sure the stages underneath are clean enough to trust, because a stage that means five different things turns every one of these numbers back into a guess.

And the oldest rule in operations, worth saying plainly: the moment a measure becomes a target, it stops being a good measure. That has nothing to do with cynicism about your team. It is just 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 the strategy itself, written in the only language that survives a bad week. Anyone who treats it as an HR detail bolted on afterwards has already lost the plot.

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

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 or a genuine product pivot. A light quarter is not one of those; more often it is 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, no exceptions. 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 at all. You have taught the entire team that the number on the plan is a suggestion, and every one of them has repriced their effort to match.

Picture the version that actually happens. A rep spends a quarter building a book of accepted meetings under a plan that pays a set amount for each. The quarter lands light for reasons that have nothing to do with them, a new leader arrives, and the plan is rewritten after the fact so that only meetings which converted to pipeline count, applied backwards. The rep opens a commission statement to find that work they were told was worth paying for is suddenly worth nothing. You saved one quarter of variable comp. In exchange, every rep who hears the story now treats every future target as provisional, holds their best accounts back for a job that will honour the deal, and starts taking recruiter calls. That is a terrible trade, and managers make it constantly, because the saving is visible this month and the cost only shows up over the next three.

Comp stability 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 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.

There is an ownership problem underneath all of this. When nobody is clearly accountable for the whole system, every local fix looks reasonable and the sum rots, which is how a system nobody owns the shape of ends up squeezing the layer with the least power to change it. The fix is a stable operating rhythm: a weekly, monthly and quarterly cadence where the numbers get looked at the same way every time, so a bad month reads as information instead of an emergency, and the reflex to move the goalposts never gets the chance to fire.

The alternative to squeezing is not going soft. It is a clear policy, published, applied evenly, and changed only for reasons you are willing to say out loud. Transparency here does real work; it is a control system. 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.

Start with the list and the data behind it. A rep working records riddled with wrong titles, dead numbers and duplicate accounts spends half the day on data entry and the other half apologising to the wrong person, and no amount of coaching fixes that. This is where a CRM carrying hundreds of half-empty fields stops being an abstract hygiene problem and becomes a rep staring at a record that tells them nothing they can use. Clean it at the source. A bloated stack leaks the margin you were trying to protect, and every extra tool bolted on is one more door for the mess to come back through. Enrichment only helps once the base is clean; run it over garbage and you get confident guessing dressed as fact.

Then the message. A lane deserves a real point of view, the kind a merge field can never carry. A good BDR beats a spray-and-pray sequence because they can say something true about this buyer’s world that a template never could, and that only happens when the lane is narrow enough to have taught them something worth saying.

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, whatever the board wishes the number could 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 a matter of arithmetic. 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.

The arithmetic is not hard, and doing it out loud settles a surprising number of arguments. Start from how many qualified meetings the number actually needs, work back through your own held-to-booked, conversation-to-meeting and touch-to-conversation rates, and you arrive at a daily load. If that load is humane, you have a plan. If it asks a rep to hold more live conversations in a day than the hours allow, the target has crossed from ambitious into imaginary, and imaginary targets get met by cutting corners on the exact qualification bar you spent the first half of this piece defining.

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 the team, not just to keep tabs on it.

A manager who spends the week inside dashboards instead of call reviews is really just managing a spreadsheet. The dashboard tells you the number is down; the recording tells you why, and only the recording is coachable.

There is a compounding bonus in doing it properly. The library of real, recorded calls that weekly coaching produces is the best training material your whole go-to-market owns, far better than anything generic, because it is how your deals actually sound. It is the raw material for onboarding the next hire, for sharpening the qualification bar as the market shifts, and, when you are ready for it, for teaching a model on your real conversations rather than the internet’s. Do the coaching well and the instrumentation comes for free, because they are the same work.

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. This is not about beating the team with a stick. A BDR function you cannot see is one you cannot coach, cannot pay fairly, and cannot defend when someone senior asks whether the pipeline is real. It is also why marketing fails when sales do not use the CRM: no logged activity, no timeline, no idea what actually happened.

You get logging without a running battle by fixing the CRM so it does not punish the person filling it in. If entering a call takes eight fields and three clicks, reps will skip it and you are back to the phantom pipeline; if the record is built for the person doing the work rather than the person who bought the software, logging becomes a by-product of the job instead of a chore piled on top. Discipline that leans on willpower tends to fail without warning, so design it into the tool and it mostly holds.

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 the job working as intended, not disloyalty. The mistake is pretending otherwise and acting 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, was never a promise that 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.

The path is a recruiting tool before anyone is ever promoted. A candidate choosing between two BDR jobs takes the one that can show them where it leads and point to someone who walked the road. So the visible path pays twice: it keeps your best people through the grind, and it makes the grind easier to hire into in the first place. The alternative, treating the seat as disposable, is a decision to re-run onboarding forever and to watch the knowledge of the lane walk out every twelve months with the person who had finally understood it.

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. Treat it as a mirror, not a scientific instrument.

Wherever you landed, the order of repair is the same, and it is not the order most teams reach for. Do not start with more activity. Start at the top of this piece: the lane and the qualification bar, then the handover and the single metric you run on, then the comp plan that pays for it. Motion is the last lever to pull, because motion aimed at an undefined target is only a faster way to fill the pipeline with things nobody downstream will accept. If the score stings a little, that is rather the point; a mirror only helps if you believe what it shows you.

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 what half the market is building right now: a very fast machine for producing meetings nobody wanted, run by a team already updating their CV.

And if you would rather not assemble it from a blog post, that is precisely the sales operations work we do: the lane, the bar, the handover, the one metric and the comp logic, wired into HubSpot or Salesforce so the function runs on a system instead of on whoever happens to remember what.

Common questions