Thursday, 4:00 p.m. The rep opens Salesforce.
There is a renewal that slipped. A proposal is waiting on finance. One champion has gone quiet. The manager suggests an email for the renewal, offers to join the finance call, and asks for another attempt at the quiet account before Friday.
Forty minutes later, three deals have new tasks. Nothing else has changed.
The rep will need the same help next Thursday.
This kind of one-to-one feels useful because real deals move while everyone is in the room. It is also how coaching gets replaced by rescue work. The manager becomes an extra pair of hands; the rep never gets much better at making the call without them.
Deal help matters and needs somewhere to live. Protect a small part of the week for actual practice.
Get the pipeline update out of the meeting
If the rep spends the first fifteen minutes narrating the CRM, the coaching session is already in trouble.
Ask for four lines beforehand:
- what the rep wants to get better at;
- the customer conversation where it showed up;
- the exact moment they would take back;
- what they have tried so far.
A four-line pre-read is more likely to be used than a seven-page coaching form or slide deck.
Current stages, next steps, and deal risks should already be readable. If something needs pricing approval or an executive introduction, handle it as a management decision outside the coaching block.
HubSpot's sales one-to-one guidance treats the meeting as the salesperson's development time and asks the rep to help set the agenda. Gong makes a similar point: the one-to-one belongs to the rep. That sounds obvious. Calendars have a way of proving otherwise.
Pick the ten seconds that mattered
Skip the sixty-minute playback. Find the ten seconds where the rep had to choose.
Maybe the buyer gave a vague answer and the rep moved on. Maybe a new stakeholder objected and the rep began defending the product. Maybe the call ended with "I'll send something over" when nobody had agreed what should happen next.
For a field meeting, the recording may not exist. Fine. Use the notes while the exchange is still fresh:
Buyer: We need to think about whether the team will actually use it.
Rep: We have a full onboarding program, weekly support, and a knowledge base...
There it is. The buyer voiced uncertainty. The rep heard a request for product information.
Salesforce recommends reviewing real calls and working on one area at a time. The "one" matters. Marking twelve mistakes is an assessment. Coaching one repeatable decision gives the rep a chance to change it.
Let the rep go first
Play the clip once. Or read the exchange aloud.
Then ask, "What were you trying to make happen?"
Wait.
The pause can feel awkward, especially when the manager already knows what they want to say. Keep it anyway. You need to hear how the rep read the moment.
Two reps can use the same weak phrase for completely different reasons. One missed the objection. The other heard it, got nervous, and reached for a familiar feature dump. Giving both of them a polished script only fixes the surface.
A few questions are usually enough:
- What did you notice from the buyer?
- Where did the conversation depart from your plan?
- What would you keep?
- What would you try again?
The manager adds evidence and avoids verdicts. "Listen to the buyer after you mention implementation" gives the rep something to inspect. "You lost control of the call" gives them a label.
Sometimes the rep will not see the problem. Narrow the question. Sometimes they will spot it immediately and say something better than the manager had in mind. Let them.
Learning to diagnose a conversation is part of the job.
Run the moment again
The manager takes the buyer's line: "We need to think about whether the team will actually use it."
The rep gets another go. Perhaps this time they ask:
Which part worries you most: getting people started, changing the current workflow, or seeing enough value to keep using it?
The question may still need work. It already beats three minutes of onboarding detail because it lets the buyer locate the concern. Training, behavior change, and business value are different problems.
Try it twice. Three times if the words still sound borrowed.
This is where a lot of coaching sessions stop too early. The manager gives good advice, the rep agrees, and both leave feeling productive. Agreement alone leaves the rep unpractised. The first clumsy replay is usually where the work begins.
Keep the replay to the decision. The rep gets another chance at the part that mattered.
Write down something you can see
"Improve discovery" gives nobody an action they can observe. "Be more confident" is worse.
Use a cue, a behavior, and a place to look for evidence:
On the next two discovery calls, when a buyer names a problem, ask for the most recent example before discussing the product. Put the example and its consequence in the opportunity note.
Next week, nobody has to debate whether confidence improved. Open the call, transcript, or meeting note. Did the moment happen? What did the rep do? What did the buyer say next?
Revenue is too distant to judge one coaching cycle. Start with the behavior. Over several calls, watch whether it improves discovery, objection handling, next steps, or buyer commitments.
Choose the next conversation before the rep leaves. Otherwise "we'll check next week" becomes a scavenger hunt five minutes before the meeting.
A 30-minute agenda that survives a real calendar
| Time | What you do |
|---|---|
| 0-4 minutes | Name the skill and the customer moment |
| 4-10 minutes | Hear the clip or reconstruct the exchange |
| 10-17 minutes | Let the rep diagnose it; add observations |
| 17-25 minutes | Replay the moment and adjust |
| 25-28 minutes | Write the cue, behavior, and evidence |
| 28-30 minutes | Pick the next conversation to review |
Thirty minutes is enough for one moment. Coaching, a forecast inspection, career planning, and a performance conversation need separate calendar space.
Split those jobs. The rep can tell when you have not.
Keep a short coaching record
The record can be tiny:
- the moment you reviewed;
- what the rep noticed;
- the behavior they will try;
- where they will try it;
- the evidence you will inspect.
Link the source conversation beside it. That saves the next session from beginning with two competing memories of what happened.
This is also where conversation software is genuinely useful. It can surface moments involving pricing, competitors, objections, and next steps. It can attach the note and remind the rep what they agreed to try. The manager still has to decide which behavior matters. Software cannot make that judgment worth having.
Over time, the notes reveal patterns. A rep may keep explaining before they understand the objection. Another may run good discovery and lose direction at the close. Those are coaching plans grounded in actual work, not traits assigned from a dashboard.
The meeting should make the manager less necessary
That is the test I would keep.
A deal review asks, "What should we do with this opportunity?"
A coaching session asks, "What will you be able to do the next time this happens?"
Both conversations belong on a sales manager's calendar under different names.
Help with the deal when the deal needs help. But if every one-to-one ends with the manager writing the email, joining the call, or prescribing the next move, the rep is borrowing judgment rather than building it.
Take one real moment, let the rep read it, run it again, and check what happens in the next conversation.
Quick answers
What is a sales coaching one-to-one?
It is a private working session where a manager helps one rep improve a selling behavior. A recent customer conversation supplies the evidence; diagnosis, practice, and a follow-through commitment do the work.
How often should sales coaching happen?
Weekly is useful while a rep is building a skill or needs close support. Experienced reps may need a longer interval. Keep the cadence steady long enough to inspect the same behavior in later conversations.
Is coaching the same as a pipeline review?
No. A pipeline review decides what to do with current opportunities. Coaching improves how the rep handles a situation that will happen again. A deal can supply the example without taking over the session.
What should a rep bring?
One call clip, transcript excerpt, or fresh meeting note. Bring the moment that felt difficult and the result the rep wanted instead.
Can AI automate sales coaching?
AI can find conversation moments, summarize context, and draft notes or tasks. The manager should own the diagnosis, the feedback, and the judgment about whether a response fits the buyer and the rep.
Research note: This article draws on current coaching guidance from HubSpot, Salesforce, Gong, and LinkedIn Sales. LogicNotes added the ten-second coaching workflow, the evidence-based 30-minute agenda, and the connection between conversation context and CRM follow-through.
Keep the coaching moment beside the call.
LogicNotes turns sales conversations into structured CRM context and follow-up tasks, so managers can coach from what happened instead of asking reps to reconstruct it.
See LogicNotes for teams