Use when an org role acts as sales coach and must improve rep performance through ongoing call reviews, skill-building and habit reinforcement. Covers weekly rubric-based review loops, one or two skills per session, GROW 1:1s, objection libraries and tracking behavior change. For discovery calls specifically, use discovery-coach.
Installs into .claude/skills of the current project.
Are you the author of Sales Coach?
Add the live security badge to your README. It updates with every re-scan.
[](https://www.skillsdirectory.com/skills/monoes-sales-coach)
---
name: sales-coach
description: "Use when an org role acts as sales coach and must improve rep performance through ongoing call reviews, skill-building and habit reinforcement. Covers weekly rubric-based review loops, one or two skills per session, GROW 1:1s, objection libraries and tracking behavior change. For discovery calls specifically, use discovery-coach."
tags: ["sales","people","leadership"]
tools: []
license: Apache-2.0
source: https://github.com/monoes/monomind
---
# Sales Coach — Best Practices
## Focus
Improves rep performance through structured, ongoing coaching — call reviews, skill-building, and habit reinforcement — rather than one-off feedback or deal rescue.
## Best practices
- Run a consistent weekly loop: review a call against a rubric, identify one or two coachable moments, co-create a fix with the rep, schedule the follow-up review.
- Coach one or two specific skills per session, not a laundry list of everything that went wrong — focus compounds, noise dilutes.
- Separate coaching time from pipeline/deal-review time; mixing the two turns coaching into deal interrogation and reps disengage.
- Adapt coaching style to the rep's skill level and confidence (situational coaching) rather than applying one method to everyone.
- Coach in the moment where possible — right after a call, during a live pipeline review, or shadowing a customer conversation — not weeks later from memory.
- Build and maintain an objection-handling library from real call reviews: track recurring objections, document how top performers respond, and standardize the response.
- Use a defined framework (e.g., GROW: Goal, Reality, Options, Will) to structure 1:1 coaching conversations so they produce a concrete next action, not just discussion.
- Track whether coaching is actually changing behavior on subsequent calls — coaching that doesn't show up in later performance isn't working.
## Common pitfalls
- Giving generic "good job, keep it up" feedback instead of specific, actionable, skill-level observations tied to what happened on the call.
- Trying to fix everything at once in a single session, overwhelming the rep and producing no lasting change.
- Coaching only underperformers while ignoring mid-tier reps who have the most room for incremental, high-leverage improvement.
- Treating coaching as a compliance checkbox (logged but not followed up) instead of a loop with accountability for the next call.
## Tools & techniques
- Call scorecards/rubrics aligned to the team's sales methodology (MEDDIC, SPIN, etc.) for objective, repeatable review.
- Conversation intelligence tools to surface coachable moments (talk ratio, objection handling, question quality) at scale.
- GROW model (or similar) as the structural skeleton for every 1:1 coaching conversation.
- Objection library maintained and updated from real call transcripts, shared across the team.
