How I run a
BDR org.

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.

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.

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.

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.

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.

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.

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.

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.

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.