Connor Wright
Growth at Yoodli
Building a Manager-Led Coaching Program Beyond Ride-Alongs
September 25, 2026
•
8 min read
How to Build a Manager-Led Sales Coaching Program Without Ride-Alongs
Ride-alongs are the default coaching motion in most sales organizations. A manager sits in on a live call, takes notes, and debriefs afterward. The coaching that comes out of it is good. It also burns the scarcest resource in the revenue org, a frontline manager’s attention, at a bad exchange rate. A manager-led sales coaching program that holds up has to answer one question: where does a manager’s hour produce the most change in rep behavior? Ride-alongs usually lose that comparison.
Where a Sales Manager’s Week Actually Goes
Start with the real calendar, because coaching programs get designed against an imaginary one.
A frontline sales manager spends their week on forecast calls and pipeline inspection, one on ones, deal desk and approvals, escalations from reps who are stuck, interviewing for open roles, their own leadership’s reporting requests, and whatever fire started that morning. Coaching is the only item on that list with no external deadline, which is why it is the first thing that moves when the week gets compressed.
Now price a ride-along. The manager blocks the call itself. They block time before to get context on the account. They block time after to write up feedback and hold the debrief. One coaching interaction, covering one call, for one rep, costs a meaningful fraction of a day. Multiply by a full team and the arithmetic stops working long before every rep gets coached.
Coaching still happens under that load, just unevenly. The distribution turns accidental. The reps who get coached most are the ones whose calls happened to fall in an open slot, or the ones the manager already enjoys working with, or the ones in deals large enough to demand attention. The rep missing quota with a fixable discovery problem gets coached least, because nothing on the calendar forces it.
Snowflake’s Version of This Math
Snowflake ran the numbers on their own manager coaching load and saved 1,200+ hours of manager coaching time after moving practice and initial evaluation off manager calendars.
Two things about that figure matter. It is counted in hours because hours are the binding constraint. And those hours did not vanish from the business. They moved from listening and evaluating toward the part managers are uniquely good at: judgment on specific situations with specific reps.
Harness is the same pattern from the review side. The team cut sales training review time by 75% with Yoodli. Review time is the hidden cost in every certification program. Someone has to watch the attempt, and that someone is usually a manager.
For scale on what a manager hour is worth, The Bridge Group publishes an annual AE metrics and compensation benchmark covering quota, on-target earnings, and ramp across B2B SaaS sales teams. Pull the current median quota figure from it if you are building the business case internally. A manager’s hour touches a team carrying several multiples of that quota, which is the argument for spending it deliberately.
The Structure That Replaces the Ride-Along
The design principle is separation. Split coaching into evaluation and intervention, then automate the first and protect the second.
Evaluation answers the question of where each rep currently stands. It requires consistency more than insight, which means it does not need a manager sitting on a live call. Reps run scored practice against defined scenarios, and AI roleplays produce a comparable score for every rep on the team against the same rubric. Yoodli scores each attempt against criteria you define, so the rubric reflects how your team is supposed to sell rather than a generic checklist. That gives a manager something ride-alongs never provided: a view of the whole team scored the same way, instead of a handful of impressions from whichever calls they happened to attend.
Intervention is the coaching conversation itself, and that stays with the manager. The difference is that it now starts from evidence. Instead of opening a one on one with “how’s the pipeline,” the manager opens with a specific behavior the rep demonstrated across multiple practice attempts.
A working weekly rhythm looks like this:
- Reps complete assigned practice scenarios on their own time, scored automatically.
- The manager reviews the team dashboard once, looking for patterns and outliers rather than listening to every session.
- Coaching time goes to the reps whose scores or trend lines flag them, plus one deliberate session with a strong rep on something advanced.
- Real call review continues, sampled rather than exhaustive, to confirm that practice behavior is showing up live.
That last item is the one teams skip, and skipping it is how a practice program drifts into AI roleplays nobody validates against real conversations. Post call coaching from real calls is what keeps the practice honest, and connecting practice to real conversations through a call recording integration removes the manual step of matching the two.
How to Roll Out a Manager-Led Sales Coaching Program in One Quarter
Run it on one team before you run it everywhere. A single team gives you a clean before-and-after and a manager who can tell the story to the rest of the org.
Weeks 1 and 2: baseline. Pick one scenario the whole team faces, such as discovery against your most common competitive objection. Assign it to every rep with a deadline. Change nothing about how the manager spends their week yet. At the end of week two, look at the score distribution. That spread is your baseline, and it usually surprises the manager, because the reps they assumed were fine rarely all land in the top half.
Weeks 3 and 4: first coaching cycle. The manager holds one 45-minute dashboard review, then books coaching conversations with the three lowest-scoring reps and one high performer working on an advanced skill. Four 30-minute conversations. Each one opens with a specific moment from the rep’s practice attempts. Reps rerun the same scenario after their conversation.
Weeks 5 through 8: validate transfer. Assign a second scenario. Pull two live calls per coached rep and score them against the same rubric the practice used. If the reps who improved in practice also improved live, the scenarios are doing their job. If they did not, rewrite the scenarios before adding more reps.
Weeks 9 through 12: expand. Add a second team and a certification bar for the first scenario. Write down the manager’s weekly hours on the program so far, then set that against the ride-along cost you priced earlier. That comparison is the slide for your leadership.
How Many Reps Can One Manager Coach This Way?
More than they can coach with ride-alongs, because evaluation no longer grows with headcount. Ten reps or twenty produce one dashboard review either way. The coaching conversations still scale with the team, and those are the hours you have to protect.
A practical ceiling: if a manager cannot hold a coaching conversation with every rep at least once a month, either the span of control is too wide or the practice cadence is too heavy for the manager to keep up with. Cut the number of assigned scenarios before you cut the conversations. Two well-chosen scenarios a month, coached properly, beat six that nobody discusses.
The Objections a Skeptical Enablement Leader Should Raise
If you have run enablement, you have watched a coaching program get announced and then stop. Take these objections seriously:
Managers will treat the dashboard as the coaching. This is the most likely failure mode. A manager who reads scores and never has the conversation has automated the easy half and dropped the half that matters. Guard against it by making the coaching conversation the thing you inspect in your own manager one on ones. Dashboard review on its own gets no credit.
Reps will game the practice. Some will, especially if practice scores are tied to compensation or visible rankings. Keep practice scores diagnostic and keep the stakes on certification bars and real call performance. A rep gaming a practice score is telling you the incentive design is wrong.
Practice does not transfer to live calls. This is a legitimate concern and it is testable. Sample real calls from reps who scored high in practice and reps who did not, score them against the same rubric, and see whether the ordering holds. If it does not, the scenarios are wrong, and you should fix the scenarios rather than abandon the program.
Managers were never good at coaching to begin with. Often true, and freeing up hours does not by itself create skill. Manager coaching skill is its own practice problem, and roleplays for manager training exist for the same reason rep roleplays do.
What to Measure
Measure the program on manager behavior first, because that is what you are actually changing.
Track coaching conversations held per rep per month, and specifically the spread across the team. A healthy program shows every rep getting coached, with more going to the ones who need it. An unhealthy one shows the same distribution you had with ride-alongs and a new dashboard on top. Track manager hours spent on evaluation versus intervention if you can get at it, even roughly.
Then use the revenue metrics you already report. Ramp time and time to first closed deal for new hires. Quota attainment distribution across the team, watching the middle rather than the top. Certification pass rate and attempts to pass. Win rate and stage conversion, which move last and should be treated as confirmation rather than early signal.
The real test of the program is whether the rep who was struggling in month two got coached in month two. Guidance on how to measure sales coaching effectiveness covers the reporting side in more depth.
Pick one scenario, assign it to every rep on one team, and look at the score distribution before you change anything about how managers spend their week. The spread will tell you where the coaching hours should have been going all along. The sales coaching page covers how teams usually structure the rest.
Bring Yoodli to your team