Coaching a Full Team When You Only Have Hours for Two
Every sales manager runs the same silent triage. There are eight reps, there is time to genuinely coach two, and the other six get a pipeline review and encouragement. Nobody designed it that way and everybody does it, because the arithmetic does not leave an alternative. The useful question is not how to find more hours — it is which parts of coaching actually need you.
Sales managers and trainers coach teams and review performance, and are measured on ramp time and team performance. The structural constraint is that coaching consumes one manager-hour per rep-hour, so most reps go uncoached. AI practice absorbs the repetitive drilling and reports per-rep readiness, which lets manager time move from delivering repetitions to reviewing exceptions.
Separating what needs you from what does not
A useful audit: list what you did in your last five coaching sessions. In most cases a meaningful share was running drills — listening to an opener, counting filler words, telling a rep they talk too much in discovery, playing a difficult buyer. None of that requires your judgement. It requires attention and a stopwatch, both of which are expensive when supplied by a manager and cheap when supplied by software.
What genuinely requires you is the other share: whether a deal is real, whether a rep is coachable or checked out, whether the territory is the problem, how to have a hard conversation with someone who has stopped trying. That work does not compress and should not be the part that gets squeezed out.
Running a coaching programme on exception review
The operating model that emerges is exception-based. The team runs standardised practice on a fixed cadence; you look at the scoreboard, not the sessions. Three reps flagged low on objection handling, one rep's talk ratio has drifted upward for two weeks, one rep's scores are excellent and their live numbers are not. Those are five specific, pre-diagnosed conversations, and they are a completely different use of Tuesday than listening to eight calls hoping something jumps out.
- Set one fixed scenario per month that everyone runs, so scores are comparable across the team.
- Track score delta, not session count. Volume without improvement is activity, not progress.
- Review transcripts only where the score flags a problem — the flashlight, not the verdict.
- Keep practice scores out of performance reviews for the first quarter, or reps will practise defensively and stop experimenting.
- Let reps see their own scores before you do. Adoption depends on the tool feeling like theirs.
What to do about the rep who scores well and sells badly
This is the most informative pattern a readiness system surfaces, and it is invisible without one. A rep who performs cleanly in practice and poorly on live calls does not have a skill gap in the conversation — they have a gap somewhere else: nerves that only appear with a real buyer, a list quality problem, a territory problem, or a mismatch between the practised scenario and the real one.
Each of those has a different fix and none of them is more drilling. Before readiness data existed, this rep looked identical to a rep who simply could not sell, and got coached the same way. Being able to distinguish them is one of the clearest returns on measuring practice at all.
What DUODIAL gives a manager
Standardised practice scenarios run across the team without consuming your calendar, scored on a consistent rubric — talk-to-listen ratio, pacing, filler words, confidence, questions asked, objections handled. Progress tracking accumulates history per rep so a trajectory is visible rather than a snapshot, and transcripts are available where you want to verify a score rather than trust it.
Because the Call Analyzer applies the same rubric to recorded real calls, practice performance and live performance are directly comparable — which is what makes the diagnostic above possible at all.
Practise this, don't just read about it
DUODIAL runs voice-based sales conversations against adaptive AI buyers and scores every session, so the next attempt is better than the last one.