How I run a BDR org.

Prologue. The job changed. Most operating models didn’t.

The BDR role a company hired for in 2019 does not exist anymore. The metrics on the dashboard still look the same. The comp plan still looks the same. The interview loop still asks about grit. But the actual behavior a modern rep needs to survive, and the behavior a leader needs to coach for, is not the one the org chart was designed around.

Every rebuild I’ve done, from a 64-rep global BDR org to a from-scratch 16-rep team, has come back to the same nine things. This document is those nine things. It is not a framework. It is not a course. It is what I believe, in writing, so nobody has to guess.

If you’re a leader running an org that isn’t producing what it should, start at the principle that made you flinch. That’s usually where the leak is.

Hire for judgment, not enthusiasm.

Every broken BDR org I’ve walked into hired the same way: energy, coachability, a story about grit from a lacrosse tournament. That gets you a team that shows up. It does not get you a team that thinks.

The rep who wins in 2026 is the rep who can look at 200 accounts and tell you which 30 matter this quarter and why. That’s an AE skill. We used to wait until year two to develop it. That was fine when the phones worked. It is not fine anymore.

The interview loop should have a case. A real one. Give them ten accounts, a product one-pager, and ninety minutes. Score how they think, not how they present. If the top of the funnel is judgment work now, judgment is what you’re hiring.

Onboarding ends. Ramping doesn’t.

Most companies confuse onboarding with ramping and then wonder why month four looks like month one. Onboarding is the thirty-day download. Ramping is the six-to-twelve-month behavior build that produces a rep who prints pipeline without a manager in the room.

I run three gates. Thirty days: can they run the motion. Six months: can they own the motion. Ten to twelve months: can they teach the motion. Each gate has a rubric, a manager script, and a clear “you’re behind” conversation attached to it.

The gate is not a review. It is a decision. Pass, coach up, or move. Companies without gates end up with a floor full of month-eight reps still being coached like it’s week two, and a bench that never earns the promotion.

Coach the pattern, not the moment.

One bad call is data. Fifteen bad calls of the same type is a pattern. Coaching the moment feels responsive. It’s actually noise. The rep hears feedback on Tuesday, hears different feedback on Thursday, and by Friday has stopped listening.

Every 1:1 opens with a one-page scorecard filled in before the meeting. Same seven fields. Every week. The scorecard is the coaching conversation. The manager’s job is to point at the pattern, not to freestyle for thirty minutes about the last dial.

This is also how you find out your best manager is coaching the wrong thing. If every rep on their team has the same weakness in month five, the weakness lives in the coach. That’s a signal you can only see when the pattern is on paper.

Enablement builds behavior. Not slides.

Most enablement is designed to transfer knowledge. Most business outcomes require behavior change. Those are different jobs. If the training ends and nothing on the phone changes, the training didn’t work. It doesn’t matter how well it was received.

Before I build anything, one question: what does Apply look like. If I can’t describe the behavior a rep will do differently on Monday morning after this training, the training doesn’t get built. It gets sent back.

Two drills fix most of it. A five-minute pre-call rehearsal. A three-minute post-call replay. Attached to real calls, not a Zoom classroom. That’s the whole compound. Managers defend the eight minutes. Reps do the reps. Behavior actually changes.

Forecast the leading indicators. The lagging ones are already true.

By the time SQL count is bad, it’s been bad for six weeks. The board finds out in the QBR. The CRO finds out in the forecast call. The BDR floor knew in real time and nobody asked them.

I run a twelve-signal pipeline health scan every month. Six leading, six lagging. The leading ones are the whole game. Reply rate on tier-one accounts. First-meeting hold rate. Meetings that survive to opportunity. Time from booking to first stage advance.

If any leading indicator moves the wrong direction two weeks in a row, we intervene that week. Not next month. Not in the QBR deck. This week. That is what “operating” actually means.

AI is a workflow, not a purchase.

The tools exist. Nobody has translated the actual BDR motion into the workflows that use them. So companies buy the tools, adoption dies at 12%, and the CRO concludes the tools don’t work. The tools are fine. The workflows aren’t there.

Governance layer first. A vetted prompt library, a data policy, and a review cadence. Then two manager tools (account tiering, pipeline pattern read) and three rep tools (research brief, message rewrite, objection response). That’s the whole stack.

AI adoption is a leading indicator now. Reps who use it well are the ones who get promoted. Reps who won’t touch it are the ones we’re going to have a hard conversation with in twelve months. Neither of those is about the tools. Both are about judgment.

Managers are the product. Everything else is packaging.

You can have a beautiful onboarding, a slick tech stack, and a comp plan designed by consultants. If your frontline manager is coaching the wrong version of the job, none of it matters. The manager is the operating system. Everything else is UI.

New managers get a ninety-day plan the same way new reps do. Same gates, different rubric. Can they run a coaching 1:1 the enablement team would sign off on. Can they defend a promotion decision in front of the CRO. Can they read a pattern in a rep’s book and name it before the rep does.

The org rebuilds I’ve done all had the same first move: recalibrate the managers before touching anything on the rep floor. You can’t build a 4.0 BDR team with a 1.0 coaching model. Fix the ceiling first.

The operating rhythm is the strategy.

Every leader I know has a strategy doc. Almost none of them have a rhythm doc. The strategy is the aspiration. The rhythm is what actually happens. If the rhythm is broken, the strategy is theater.

Weekly: 1:1s with scorecards, pipeline pattern read, one live coaching moment per rep. Monthly: gate check on ramping reps, tier-one account review, comp check-in. Quarterly: hiring bar recalibration, org design pressure test, manager review.

Print it. Pin it. Run it. The best BDR orgs I’ve seen aren’t the ones with the smartest playbook. They’re the ones where a rep on their worst day still knows exactly what happens on Monday at nine.

Build for the rep who’s still here in two years.

Half of everything I’m arguing for gets easier if you stop optimizing for eleven-month rep turnover and start optimizing for the ones who make it. The eleven-month rep is a symptom. The system that produces them is the disease.

Design the ramp for a rep you want to promote. Design the coaching for a rep who will one day be the manager. Design the tooling for a rep who has AI in their workflow, not one who’s afraid of it. Design the operating rhythm for the rep who will still be on this floor two years from now, running someone else’s onboarding.

You will get better tenure as a side effect. You will get better pipeline as a side effect. What you’re actually building is a farm system. Everything else is downstream of that.

One more thing. None of this works without the reps.

Every principle here assumes you have a floor full of people who want to be good at this. If you don’t, none of the operating rhythm in the world will save you. Hire for that, protect it once you have it, and treat every promotion decision like the tell it actually is.

That’s the whole system. The rest is defending the eight minutes.