■ SDR Coaching

SDR coaching that turns 1:1s from status updates into behavior change

SDR coaching is the weekly operating rhythm that turns call inspection into changed behavior: a manager listens to real calls, gives structured feedback, defines the next behavior, and re-inspects it the following week. It is not an occasional training event, and it is not a pipeline review with a coaching label. The SD Lab installs this rhythm inside your team and builds your managers' capability to run it — because the manager is the multiplier.

When coaching is the real gap

The 1:1s happen. The behavior doesn't change

Most SDR teams have 1:1s on the calendar and call recordings in a folder. What they lack is the loop between them: inspection that produces feedback, feedback that produces a defined next behavior, and re-inspection that checks whether it happened. These are the signals.

  • 1:1s are pipeline status updates, not skill conversations
  • Dashboards get reviewed; actual calls do not
  • Coaching quality varies wildly from manager to manager
  • Reps repeat the same mistakes for quarters because nobody re-inspects
  • Feedback is vague — 'be more consultative' — with no defined next behavior
  • New managers inherit a team but no coaching system to run
  • Training happened, felt good, and decayed within a month

Two resources go deep on the mechanics: the 10-2-1 SDR coaching framework and proactive coaching through inspection.

What the coaching work covers

Inspection, feedback, next behavior, re-inspection

Coaching that sticks is a loop, not an event. The work builds each part of the loop with your managers, inside their real week, until they run it without help. The SDR Leadership hub carries the full discipline.

SDR Leadership & Coaching

The full discipline

The hub for the manager layer: inspection cadence, coaching structure, ramp and the weekly operating rhythm.

Go deeper
Framework

The 10-2-1 coaching framework

A concrete structure for the coaching week: what to inspect, how much, and how the feedback conversation runs.

Go deeper
Guide

Proactive coaching through inspection

How to coach from what calls actually show, before the dashboard tells you something is wrong.

Go deeper
Call inspection

Listening as a management skill

What to listen for, how to score a call against the system, and how to pick the one behavior worth coaching this week.

Feedback structure

Feedback that defines the next behavior

Moving from vague advice to a specific, observable next behavior the rep commits to — and the manager can re-inspect.

Manager capability

The multiplier layer

Building the managers' own coaching skill, because one coach per team does not scale and a dependency is not a system.

Coaching as rhythm vs coaching as event

Why the occasional training day keeps failing

Most teams have tried the event version: a trainer comes in, the team energy spikes, and within a month the old behaviors are back. The difference is not the trainer. It is whether a weekly inspection loop exists to catch the drift.

 Coaching as operating rhythm (The SD Lab)Coaching as occasional event
CadenceWeekly inspection and feedback, built into the manager's calendarA session when someone books one
Source materialThe rep's own recorded calls from this weekGeneric examples and roleplays
FeedbackOne defined next behavior, re-inspected the following weekBroad advice, rarely revisited
Who runs itYour managers, with their capability deliberately builtAn outside trainer, until the budget line ends

This is sales-development execution coaching — calls, pipeline behaviors and the manager rhythm. It is not personal or career coaching, and it is not therapy.

Evidence

Coaching systems installed in real teams

The Field Reports document what changed and what the team kept. Where results are client-reported, the reports say so.

How the work happens

Installed inside the Revenue Rebuild

Coaching work happens inside Revenue Rebuild, scoped after diagnosis — because a coaching rhythm cannot fix messaging or targeting that is broken underneath it.

  1. Phase 01

    Observe

    Sit inside the current rhythm: the 1:1s, the call reviews that do or don't happen, the feedback reps actually receive. The gap between the calendar and the reality is the diagnosis.

  2. Phase 02

    Build

    Install the loop with your managers: what to inspect, how to structure feedback, how to define the next behavior. Run it together on real calls until it is theirs.

  3. Phase 03

    Hand off

    Managers run the rhythm alone, with the inspection structure documented. The engagement ends when the loop runs without the consultant in it.

Fit

For leaders who want managers that multiply

■ Good fit
  • SDR managers who want a real coaching system, not more dashboards
  • Directors and VPs whose coaching quality varies by manager
  • Enablement leaders tired of training that decays in a month
  • Teams with call recordings nobody systematically inspects
  • Leaders who want the capability inside their own managers
Not a fit
  • Looking for someone to coach the reps so managers don't have to
  • Wanting a motivational speaker for kickoff
  • Personal, career or executive coaching
  • Teams unwilling to put call inspection on the manager calendar
Adjacent scopes

If the gap is bigger than coaching

Questions managers actually ask

SDR coaching, answered plainly

What is SDR coaching, concretely?
A weekly loop: the manager inspects a rep's real recorded calls, gives structured feedback, defines one specific next behavior, and re-inspects that behavior the following week. Repeated consistently, it compounds. Done occasionally, it does nothing.
Do you coach our reps directly?
During the engagement, yes — but the point is to build your managers' capability to run the loop themselves. A team that depends on an outside coach has rented the skill, not installed it. The work ends when your managers run the rhythm alone.
We already do 1:1s. What changes?
Most 1:1s are pipeline status updates. The change is source material and structure: the conversation runs off the rep's actual calls, produces one defined next behavior, and opens next week by checking whether that behavior happened.
How is this different from enablement or training?
Training delivers knowledge to a room; coaching changes one rep's behavior at a time, against their own calls, week over week. Enablement builds the material; the coaching rhythm is what makes the material show up on calls.
What if our managers have never been trained to coach?
That is the normal starting point, not an exception. Most SDR managers were promoted for being good reps. Building their inspection and feedback capability is a core part of the work — the manager layer is the multiplier.

The manager is the multiplier. Build the multiplier.

If your 1:1s are status updates and the same mistakes keep repeating, start with the evidence or go straight to the engagement.

Prefer proof first? Read the Field Reports.