Business Development Representative (BDR)

A Business Development Representative (BDR) is a quota-carrying prospector whose job is to manufacture pipeline from cold accounts. The BDR researches target companies, runs outbound sequences across email, phone, and social, and converts strangers into booked meetings for an account executive. At most companies the distinction from an SDR is sourcing: BDRs work outbound into accounts that have never raised a hand, while SDRs work inbound leads that marketing already warmed. The line is blurry and org-dependent, but the BDR is the one dialing into silence.

It is the hardest entry-level job in software, and the most data-rich. A BDR's entire output is countable.

How a BDR Is Measured

BDRs carry an activity-and-outcome quota, not a revenue quota. The standard scorecard runs top to bottom of a small funnel:

The outcome that matters is the last row. Activities are an input, meetings are a promise, and opportunities are the only thing finance can put a dollar on. A BDR booking 25 meetings that produce 3 opportunities is worse than one booking 12 that produce 8.

How a BDR Generates Pipeline

The work is account selection plus persistence. A BDR builds a list against the ICP, identifies a buying trigger — funding round, exec hire, new tech in the stack — and runs a multi-touch cadence over two to three weeks. Reply rates on cold outbound sit around 1–3%, so a BDR working 1,200 touches a month is mathematically buying roughly 15–30 conversations. Everything else is volume math and message quality.

When the prospect agrees to a meeting, the BDR hands off to an AE. A clean handoff includes the pain, the trigger, and the next step, so the AE walks into discovery instead of starting from zero.

When Sales Orgs Rely on BDRs

VP Sales staffs a BDR team when the addressable market is large enough to prospect but the AEs are too expensive to spend their day dialing. Finance models BDRs as a pipeline factory: each rep is expected to source 3–5x their fully loaded cost in closed-won revenue. RevOps watches the BDR-to-AE ratio, usually somewhere between 1:1 and 1:3, to keep AEs fed without flooding them.

Recruiters treat the BDR role as the proving ground. The metric they actually trust is opportunities-created-to-closed-won, because it shows whether the candidate sourced pipeline that survived contact with a real buyer, not just meetings that no-showed.

Common BDR Gaming Patterns

The booked-meeting metric is the one that gets bent. A BDR under quota pressure books meetings with anyone who says yes — wrong title, no budget, no intent — to hit the number, then the meeting no-shows or the AE disqualifies it in five minutes. The activity count gets gamed too: 1,200 "touches" can be 1,200 identical templated emails to a scraped list, which moves the input metric while generating nothing.

The honest counter is to pay and measure on AE-accepted opportunities, not raw meetings booked. The moment a second human has to agree the meeting was real, pass-through junk stops counting. A BDR's meeting count tells you they were busy. The opportunity count tells you whether any of it was worth an AE's calendar.