Last week I wrote about a client team reaching the point where one rep was producing and the internal manager was beginning to solve the normal problems around the work.

That mattered. The result showed the outbound motion could work, and the manager stepping into the decisions showed the organization might actually be able to own it.

This week gave me a better look at what that ownership requires.

The internal manager sat down with nine substantive calls. Not nine pickups or routing events. Nine conversations with enough surface area to inspect what the rep actually did.

He reviewed them, scored them, saved examples, added notes and coached the rep around a small set of observable behaviors. That part was good.

The more interesting part was what happened one layer above him.

Leadership didn’t jump around the manager and start coaching the rep directly. They began inspecting the manager’s diagnosis: which evidence he selected, what behavior he chose to coach, why he chose it and what happened next.

That’s the layer I think a lot of sales handoffs miss.

A company teaches the rep, gives the manager a playbook and assumes the system transferred. But if nobody is developing the manager’s judgment, the operating system still depends on one person getting the diagnosis right.

A dashboard can tell you calls happened. It can show pickups, duration, dispositions and meetings. What it cannot tell you by itself is whether the manager knows how to turn those events into better rep behavior.

That requires judgment.

The manager has to separate bad data from a real conversation, decide which calls are worth inspecting and find the difference between a weak opener, shallow discovery, poor listening, bad problem fluency and a conversation that simply was never going anywhere.

Then they have to resist the urge to coach everything.

That’s where the nine-call review mattered. The goal wasn’t a giant scorecard full of criticism. It was to find a pattern the rep could actually work on.

In this case, the useful behaviors were practical: prepare with more intention, stay curious longer and ask one more useful question before jumping toward the pitch or the exit.

Those are coachable. “Be better at cold calling” isn’t.

Neither is “convert more connects” if the denominator includes interactions that were never real buyer conversations in the first place.

The manager’s job is to turn messy evidence into one clear next behavior. That’s a skill, not an administrative task.

I see this a lot in sales orgs. The rep gets onboarding. The manager gets the process. The CRM gets the fields. The team gets the dashboard. Everybody agrees on the KPI.

Then a real week happens.

The numbers look strange. A rep has a rough block. The call recordings are inconsistent. Inventory runs thin. Somebody asks an edge-case question the playbook didn’t anticipate.

The handoff becomes real in how the team handles those moments.

The rep executes. The manager inspects the evidence and coaches one behavior. Leadership inspects how the manager diagnosed and coached. Then the team remeasures.

That last layer matters because frontline managers can make the same kinds of mistakes reps do. They can coach the loudest problem instead of the most important one, mistake activity for evidence, overload the rep with six changes at once or solve the work themselves instead of building the rep’s judgment.

A manager title doesn’t remove the need for coaching. It changes what the coaching should be about.

The cleanest version of the loop we’re using looks like this.

Before coaching performance, confirm the underlying events are real. Were the “connects” substantive conversations? Was the person relevant? Was there enough context for the rep to demonstrate the skill you’re about to coach?

If not, fix the data, inventory or workflow first.

Use real calls, real records and real outcomes. The manager should be able to point to the exact moment where the behavior showed up, not a general feeling that the rep needs to improve.

Don’t turn one review into a full rebuild of the rep. Pick the behavior with the clearest evidence and the most leverage.

Maybe it’s staying in the conversation one question longer. Maybe it’s slowing down after the opener. Maybe it’s connecting the problem back to the buyer’s role.

One useful behavior is more likely to survive the next call block than seven pieces of feedback.

The rep should leave knowing what different sounds like. The manager should save the examples, the note and the expected behavior so the next review connects back to the first one.

That’s how coaching becomes part of the operating system instead of a motivational speech.

Did the behavior change? Did conversation quality improve? Did the rep create better next steps?

And just as important: did the manager choose the right thing to coach?

The remeasurement isn’t only evidence about the rep. It’s evidence about the quality of the manager’s diagnosis too.

Once the frontline manager owns the first coaching layer, leadership’s job changes. They don’t need to become the senior SDR or listen to every call. They need to inspect the quality of management.

Did the manager choose substantive conversations, or coach noise? Can they explain the pattern they saw across the evidence? Did they pick one observable behavior, or hand the rep a personality critique?

Did they preserve the rep’s selling time instead of turning every imperfection into another meeting? Did they document the examples and create a way to check whether the behavior changed?

Those questions create accountability at the right layer. Leadership is still involved, but the inspection is aimed at the manager’s judgment instead of taking the rep back over.

That’s the manager-of-manager layer I was missing.

This changes my role too.

Early in a rebuild, I’m deep in the work. We’re shaping targeting, messaging, inventory, workflows, call tracks, dashboards and coaching language together.

That involvement is useful while the system is being built. It becomes a problem if every normal decision still needs to come back through me.

The rep should bring normal friction to the internal manager. The manager should inspect, coach and consolidate what actually deserves escalation. Leadership should develop the manager and remove material blockers.

I should get pulled in for strategic decisions, system-level failure or the occasional inspection of whether the loop is actually working.

That’s a much smaller job.

Good.

The goal was never to leave behind a playbook that only works when the person who wrote it is still in the room. The goal is an org that can see what’s happening, decide what matters and improve the work on its own.

If you’re looking at your own sales org this morning, don’t only ask whether the manager is coaching the reps.

Ask who is coaching the manager.

When the manager reviews calls, can they show the evidence behind the diagnosis? Can they separate a data problem from a process problem from a rep-skill problem?

Do they choose one behavior the rep can actually practice, or unload every observation at once? Does leadership inspect the quality of that coaching without taking the rep back over?

And if the person who originally designed the system stepped away, would the coaching loop keep running?

Last week, the question was whether the organization could own the motion. This week, the mechanism became clearer.

The handoff isn’t the playbook. It’s the coaching loop.

The rep executes. The manager coaches from evidence. Leadership coaches the quality of that coaching. The team remeasures.

And fewer normal decisions need to travel back to the person who built the system.

That’s what I’m watching now.

Have a great Monday 🤙

Thanks for reading. See you again next week at 8 am MST!

- Tom Slocum ✌️

I help B2B founders and sales leaders build the targeting, messaging, process, coaching and inspection underneath qualified pipeline so the team can actually run it.

Open the hood with me →

Know a founder, sales leader or operator who would get value from this field note? Forward it to them.