Why Sales Coaching Arrives Too Late (And What To Do About It)
The CRM knows the moment something changes. The calendar decides when anyone responds — and that gap is where most underperformance quietly happens.
Take a rep we'll call Sam. Sam is an illustration, but you'll recognise the month.
On the 3rd, Sam books a meeting with an account that has ignored your team for a year. The CRM records it that afternoon.
On the 9th, Sam's calls drop by a third. A big renewal has landed on their desk and it's eating the week. The CRM records that too.
On the 17th, Sam's 1:1 comes round. The manager opens the month's numbers, says well done on the new logo, asks about the dip and hears about the renewal. By then the renewal is signed, the dip is a hole in next month's pipeline, and the new-logo meeting is a line on a list.
Nothing went wrong that month. Everyone did their job. But the praise arrived two weeks after the moment that earned it, and the help arrived after the problem had already cost something.
01Why coaching runs on the calendar
Coaching isn't late because managers don't care. It's late because of how it's organised.
A manager with eight or ten reps can't sit with each of them every time something changes. So conversations get batched into a recurring 1:1, and the 1:1 reviews what has already happened. Most of that time goes on the numbers: what closed, what slipped, what's in the pipeline.
The manager is also carrying a number of their own. When the week gets busy, coaching is the first thing to give.
The result is a system built around the calendar. The work it's meant to shape isn't.
02What a late conversation costs
Two things, mostly.
The moment to help passes. Say a rep's call volume drops by a third on a Tuesday. Maybe they've been pulled onto a renewal. Maybe a new segment is throwing objections they haven't heard before. A short conversation on Wednesday could help either way. Two weeks later, in the 1:1, it's a trend to explain and a gap to make up.
The good stuff goes unnoticed. A rep tries something new and books a meeting they'd usually miss, and nobody mentions it until it's history. Anyone who has run a team knows the difference between praise on the day and praise in the review. One reinforces the habit. The other reinforces the review.
Add those up across a team and you find where most underperformance actually lives. Not in the rep who was never going to make it, but in the ones who drifted for a few weeks before anyone said anything.
03One root cause
Put the two side by side and the pattern is hard to miss.
Recognition
- What happens — A rep does something well
- Where it's recorded — The CRM, the same day
- When someone acts — The next 1:1 or team meeting
- Usual delay — Often a week or more
Coaching
- What happens — A rep's activity changes
- Where it's recorded — The CRM, the same day
- When someone acts — The next 1:1
- Usual delay — Often a week or more
The event is in the CRM on the day. The response waits for the calendar.
That's why more 1:1s rarely fix it. The problem isn't how often you meet. It's the gap between the moment and the response, and a calendar can't close it.
04What changes when coaching starts from the moment
If the CRM already knows when something happens, the response can start there.
When a rep's activity drops, the first conversation happens that week, about what changed, not in the review. When a rep does something well, they hear about it while it's fresh, and the recognition names the result: "12 meetings booked, your best week this quarter." And instead of a list of six things to improve, the rep works on one small change at a time, with a date to check whether it moved.
Most of the time that's enough, and the 1:1 becomes the place to review progress rather than discover problems.
05Where PraiseLoop fits
Doing this by hand, for every rep, every week, is the part that doesn't happen. That's the gap PraiseLoop is built for. It's an AI coach for sales teams: it works from the data your team already has in the CRM, compares each rep with your top performers and with their own normal, and works out where the gap is. Each rep gets a coach that works on one specific behaviour at a time and checks whether it's moving against the rep's own normal. Managers approve the plan, see what's already been tried, and step in where a conversation matters. When a rep improves, the coach names the result.
You don't need any software to test the idea, though.
06A test you can run this month
Pick one number every rep already logs. Meetings booked works well, because it changes often and the rep usually knows why.
For one month, ask each manager to spend five minutes on Monday looking at what changed for each rep against their usual week. Where something moved, have one short conversation that week, outside the 1:1. Agree one small change and a date to look again. And when something goes well, say so within a day or two, naming the number.
For what to say in those short conversations, see coaching a rep who's behind target, without killing their morale.
Then compare the month with the one before. Look at the number you picked, how many problems came up in 1:1s that you already knew about, and what came out of those short conversations.
If it makes a difference, you'll know the gap is worth closing properly. If you'd like to see what that looks like on your own data, book a 20-minute demo.