How Do I Score My Managers on Coaching Cadence?

The job a coaching-cadence score is hired to do

Most sales orgs already grade managers. The grade is usually one number: did the team hit quota. That number is honest about outcomes and silent about method, which is why it fails as a management tool. Two managers land at 104% of plan. One got there by running a weekly one-on-one with all seven reps, sitting in on twelve calls a month, and pulling two struggling reps from 40% to 85% attainment. The other got there by personally closing the three largest deals in the territory while five reps quietly did nothing. The quota number cannot tell them apart. Next quarter, when the second manager's heroics run out or they take another job, the team collapses, and leadership acts surprised.

The job a coaching-cadence score is hired to do is make that difference visible *before* the collapse. It is a leading indicator sitting upstream of attainment, ramp time, and voluntary rep attrition. You are not measuring coaching because coaching is virtuous. You are measuring it because the behaviors that produce a durable team are invisible in revenue reporting until it is far too late to correct them.

There is a second, less-discussed job: cadence scoring gives your middle-of-the-bench reps a defense. Left ungoverned, manager attention follows either the top rep (fun, high-yield, easy conversation) or the rep about to be fired (urgent, documented, HR-adjacent). The rep at 78% of quota — the one whose four-point improvement would swing the whole team's number — gets nothing. Scoring one-on-ones *per rep* rather than in total is what exposes that gap. A manager who ran fourteen sessions last month looks diligent until you split it by rep and see eleven of them went to two people.

The third job is contractual clarity. Front-line manager is the least-defined role in most revenue orgs. People get promoted for selling, receive a title, and then invent the job. A published cadence matrix is the closest thing most companies have to a written job description for that role: here are the six behaviors, here is what a 3 looks like, here is what a 5 looks like. New managers stop guessing. Tenured managers stop arguing that their style is different.

What the score is *not* hired to do matters just as much. It is not a productivity surveillance tool, and the moment reps believe their one-on-ones exist to generate a manager's score, the sessions become theater. It is also not a replacement for the attainment line — it is a second line that sits beside it. A manager scoring 4.8 on cadence with a team at 61% of plan has a coaching-quality problem, not a coaching-quantity problem, and the matrix should surface that contrast rather than hide it.

Building the matrix: KPIs, weights, and levels

Start with six to eight lines. Fewer than five and the composite is too coarse to guide anyone; more than nine and managers cannot hold it in their head, which defeats the purpose.

A workable default set:

One-on-ones held per rep per month. The foundation line. Score it on coverage, not volume: a 5 means every rep on the team got the target number, a 3 means most did, a 1 means the manager ran sessions with whoever asked. Weekly is the common benchmark for front-line sellers; biweekly is defensible for tenured enterprise reps carrying six-month cycles. Pick your standard and hold it.

Deal reviews completed. Structured inspection of a named opportunity — MEDDIC, MEDDPICC, whatever your qualification frame is — with next steps written down. Biweekly per rep is a reasonable bar. This line is the one that catches "coaching" that is really pipeline interrogation: if every deal review ends with a forecast number and no rep skill takeaway, the behavior is happening but the development is not.

Call reviews logged. Recorded calls listened to and commented on. Conversation-intelligence platforms make this countable and timestamped, which is why it is one of the more gameable lines — a manager can scrub to minute 30, drop a comment, and generate a data point. Score depth where you can: comments per review, or whether the review fed into a documented plan.

Ride-alongs or live shadows. In field, industrial, and services sales this is the highest-signal line and often deserves the heaviest weight. For inside teams the equivalent is live call listening or joint demo participation.

Documented coaching plans. Does each rep have a written development focus with a stated skill gap and a date to reassess? This is the line that separates coaching from checking in. Two per rep per year is a low bar most orgs fail.

Team attainment trend. Not raw attainment — *trend*, quarter over quarter, and ideally the movement of the middle third of the team rather than the average. This is the anti-gaming line.

Ramp time to first quota month. For teams hiring at any volume, this is the cleanest proof that coaching works. If a manager's new hires consistently ramp two months faster than the org average, the cadence is real regardless of what the activity counts say.

Weights are set with leadership, not by RevOps alone, and they should sum to 100 so the composite reads as a percentage. A common opening distribution: one-on-ones 25, deal reviews 20, call reviews 15, ride-alongs 10, documented plans 10, attainment trend 20. Then score each line 1-to-5 and compute composite = Σ(weight × level). With weights summing to 100 and levels capping at 5, the theoretical maximum is 500; publish scores as a percentage of that so a 340 reads as 68% and everyone understands the scale immediately.

Define the levels in writing before the first scoring cycle. A 1-to-5 scale with undefined anchors becomes a 3-to-4 scale within two quarters, because no scorer wants to give a 1 and no scorer wants to defend a 5. Write it out: level 5 on one-on-ones means 100% rep coverage at the target frequency for all three months; level 3 means 70-89% coverage; level 1 means under 50%. That specificity is the difference between a scorecard and a vibe.

Where the score lives in the RevOps stack

Coaching cadence is a RevOps data problem before it is a management problem. Every input already exists somewhere in your systems; the work is pulling it into one place and refreshing it on a schedule someone trusts.

The activity data comes from three or four sources. One-on-one occurrence lives in calendar data or an HRIS one-on-one module. Deal reviews live in the CRM as logged activities or opportunity-stage notes. Call reviews live in your conversation-intelligence tool. Ride-alongs usually live nowhere, which means you either add a CRM activity type for them or accept a manually entered number and label it as such. Attainment and ramp come from the commissions or reporting layer.

The instinct is to automate all six lines. Resist it for the first two cycles. Instrument the two or three that are genuinely reliable, hand-score the rest, and publish anyway. A matrix that is 60% automated and shipped beats a fully automated one that arrives in Q3.

Ownership is the part teams get wrong. The scorecard must be owned by RevOps or enablement — a neutral party — and not by the VP whose managers are being scored. When the scored population also controls the data pipeline, the definitions drift toward whatever makes the numbers look acceptable. RevOps owns the calculation; sales leadership owns the weights; enablement owns the level definitions. Those three roles disagreeing in a room is the system working.

Refresh cadence should be monthly, with quarterly formal review. Weekly refreshes create noise — a manager on vacation shows a bad week — and annual refreshes arrive too late to change anything. Monthly gives managers three data points before their quarterly review, which is enough to self-correct.

One implementation warning: whatever you use to compute this, keep the weights editable by a human without an engineering ticket. The entire value of the weighted approach is the ability to re-aim the bench in a day. Ramp times stretch from four months to six, you push the one-on-one and documented-plan weights up, republish, and every manager knows by Monday where the priority moved. If changing a weight requires a sprint, you have built a report, not a management instrument.

Pricing, engagement models, and typical ranges

The cost question splits three ways: build it in what you already own, buy a coaching-orchestration layer, or hire the capability in.

Build in existing tools. A spreadsheet or a CRM dashboard costs nothing in license and roughly 15-30 hours of RevOps time to build, plus two to four hours a month to maintain. This is where most teams under 30 reps should start and where many should stay. The real cost is staleness — a scorecard nobody updates is worse than no scorecard, because it gives leadership false confidence. Budget the maintenance hours explicitly or don't start.

Buy a platform layer. The market splits by which line you most need instrumented. Sales-scorecard and coaching-orchestration platforms like Ambition schedule and track coaching sessions directly, usually on custom quote. Enablement and coaching platforms like SalesHood and Mindtickle run structured coaching programs and tie sessions to skill assessments — SalesHood publishes per-user pricing, Mindtickle quotes custom. Conversation intelligence like Gong gives you hard call-review counts and the substance behind them, generally custom-priced and landing in five figures annually for a real team. Performance-management platforms like Lattice and HRIS tools like BambooHR give you clean one-on-one records at low per-person cost, without any sales specificity. Gamification tools like Spinify put a manager leaderboard on coaching activity, which drives visibility more than rigor.

Confirm current pricing directly with each vendor — published tiers move, and most of this category negotiates.

Hire or contract the capability. Sales-enablement managers and RevOps analysts are the internal owners. Fractional RevOps contractors and sales-effectiveness consultants will build the matrix in a defined engagement, typically a four-to-eight-week scope covering KPI definition, weight-setting workshops with leadership, data plumbing, and a first scoring cycle. This is worth it when the political work — getting the VP of Sales to accept that cadence is scored — is harder than the technical work, which it usually is.

The honest sequencing: build the matrix in a spreadsheet first, run two scoring cycles, find out which lines actually correlate with team performance in *your* org, and only then buy tooling to automate the lines that survived. Buying first means you automate a scorecard you haven't validated, and vendor-default KPIs become your KPIs by accident.

Wiring the score to consequences without breaking it

A published score with no teeth is a newsletter. A published score with too many teeth becomes a gaming exercise within a quarter. The band between those failure modes is narrower than most people expect.

Start with visibility only. Run one full quarter where the matrix is computed, published to every manager, and attached to nothing. This does two things: it surfaces the data-quality problems before anyone's pay depends on them, and it lets managers argue about the definitions while the argument is still cheap. Expect the first cycle to produce genuine disputes — "those four one-on-ones were logged as team meetings" — and treat every dispute as a definition bug to fix rather than an attack to deflect.

In cycle two, attach the composite to the performance review narrative. Not to money yet. The manager's quarterly review now opens with attainment *and* composite cadence score, and the conversation covers both. This is where most of the behavior change actually happens, because managers are more sensitive to being discussed than to marginal comp.

By cycle three or four, if the data holds, put a portion of the manager's variable compensation on the composite. A common structure puts the majority of manager variable on team attainment and a meaningful minority — often 10-25% — on the leadership composite. Percentages vary widely by org and by how much of total comp is variable in the first place; the principle is that it must be large enough to notice and small enough that nobody rationally trades a deal for a checkbox.

Guard against gaming with a small set of structural defenses. Score per rep, never in total, so attention distribution is visible. Pair every activity line with an outcome line — attainment trend, ramp time — so pure volume cannot carry the composite. Sample for quality: pull three random coaching sessions per manager per quarter and read the notes; if the documented plan says "keep it up" three times, the count is real and the coaching is not. And build a floor rule — a manager whose team attainment trend scores a 1 cannot post a top-decile composite regardless of activity, because that combination means the activity isn't working.

The failure mode to watch for is *displacement*: a manager who was already coaching well now spends time logging coaching instead of coaching. If logging a session takes more than 60 seconds, the instrumentation is the problem. Every field you add to the coaching-plan template is a tax on the behavior you're trying to encourage.

Also consider what the score does to rep trust. Reps figure out fast when a one-on-one exists to generate a manager's metric. The tell is a session that opens with the manager checking the agenda template rather than asking a question. Enablement should coach the coaches on session structure at the same time RevOps instruments the count — otherwise you get perfect cadence and worthless conversation.

Decision framework: choosing your approach

The right implementation depends on team size, how much of the data already exists cleanly, and whether your bottleneck is measurement or motivation.

Read the framework with a bias toward the cheapest branch that closes your actual gap. If managers are holding sessions and nobody can prove it, you have a records problem and a CRM activity type solves it for the cost of an admin's afternoon. If sessions genuinely are not happening, no amount of instrumentation fixes that and you need the orchestration layer plus real consequences.

Three adjacent situations worth naming, because they change the answer:

Player-coach managers. In teams under about 25 reps, the front-line manager usually carries a bag. Scoring them on the same cadence standard as a pure people-manager guarantees a low composite and a demoralized manager. Either set a lower frequency target for player-coaches and label it explicitly, or accept that the coaching line carries a lower weight for that role tier. Do not pretend the roles are the same.

Distributed and field teams. Ride-alongs cost a day, not thirty minutes. A field manager covering four states cannot match an inside manager's session count, and weighting them identically punishes geography. Weight ride-alongs heavily and one-on-one frequency lightly for field roles, and consider quarterly rather than monthly targets for the travel-dependent lines.

Managers of managers. Second-line leaders should be scored on whether *their* managers are coaching — the composite of their direct reports' composites — plus their own cadence with those managers. Skipping this level is the most common structural gap. Front-line managers who are scored on coaching while their director is scored purely on revenue will get exactly the message the director sends in their weekly, and it will not be about coaching.

The last consideration is timing. Introduce this at the start of a fiscal period, never mid-quarter, and never in the same month as a comp-plan change or a territory redraw. Managers absorb one structural change at a time. Land the matrix in a quiet month, run it silent for a cycle, and it becomes furniture. Land it alongside a comp cut and it becomes the thing everyone blames.

Related questions

How often should managers run one-on-ones with reps?

Weekly is the common standard for transactional and mid-market sellers. Biweekly is defensible for tenured enterprise reps on long cycles. What matters more than the interval is coverage — every rep, consistently — rather than a high total concentrated among a few favorites.

What's the difference between a deal review and a coaching session?

A deal review inspects an opportunity and produces next steps for the deal. A coaching session inspects the rep and produces a development action. Deal reviews are necessary and frequently mislabeled as coaching. Score them as separate lines so one cannot substitute for the other.

Should coaching cadence affect manager compensation?

Eventually, yes, but not in cycle one. Publish the score with no consequences for a quarter to shake out data problems, attach it to the performance review next, and only then place a minority slice of variable compensation on the composite once the inputs are trusted.

How do I score a manager who carries their own quota?

Set an explicitly lower cadence target for player-coach roles, or reduce the coaching weight for that tier. Applying the pure-people-manager standard to someone carrying a bag produces a guaranteed low score that teaches the manager the matrix is unfair rather than teaching them to coach.

What if a manager scores high on cadence but the team misses quota?

That is a coaching-quality problem, not a quantity problem. The sessions are happening and not working. Sample the session notes, sit in on two, and check whether the coaching addresses skill gaps or just re-forecasts pipeline. The contrast between the two lines is the diagnostic.

FAQ

What is a coaching cadence scorecard?

A weighted multi-KPI matrix that scores managers on specific coaching behaviors — one-on-ones per rep, deal reviews, call reviews, ride-alongs, documented plans, attainment trend — rather than on team results alone. Each line carries a weight and a 1-to-5 level, and the composite equals the sum of weight × level. It rewards repeatable development over quarterly heroics.

Which KPIs belong on the matrix?

Pick six to eight lines that prove a manager develops people: one-on-ones held per rep per month, deal reviews completed, call reviews logged, ride-alongs or live shadows, documented coaching plans per rep, team attainment trend, and ramp time to first quota month. Include at least one outcome line so activity counts alone cannot carry the composite.

How often should the weights change?

Set them with leadership and review quarterly, or whenever the operating priority shifts. If ramp times stretch, raise the weights on one-on-ones and documented plans and republish — managers re-aim within days. Keep the weights editable without engineering involvement, or you lose the ability to pivot at all.

How do I stop managers from gaming the score?

Score per rep rather than in total so attention distribution is visible. Pair every activity line with an outcome line. Sample three random coaching sessions per manager each quarter and read the notes for substance. Add a floor rule so a manager with a declining team cannot post a top composite on activity volume alone.

Does this replace the existing manager review?

No. It adds a dedicated cadence dimension beside attainment, forecast accuracy, hiring, and retention. The composite is one input to the review conversation, not the whole review. Its value is making a previously invisible behavior discussable with evidence rather than impression.

How do I get managers to buy in?

Publish the matrix and the level definitions so nobody is scored against a hidden standard. Run one full cycle with no consequences attached and fix every definition dispute that surfaces. Involve two respected front-line managers in setting the weights — they become the internal advocates, and their peers stop treating it as a RevOps imposition.

Sources

• https://hbr.org/2019/11/the-leader-as-coach
• https://www.gartner.com/en/sales/insights/sales-enablement
• https://www.salesforce.com/resources/articles/sales-coaching/
• https://www.gong.io/resources/
• https://www.mindtickle.com/blog/
• https://www.saleshood.com/resources/
• https://lattice.com/library
• https://www.bamboohr.com/blog/
• https://www.mckinsey.com/capabilities/growth-marketing-and-sales/our-insights
• https://www.shrm.org/topics-tools/topics/performance-management

Related on PULSE

• [How Many Attendants Should I Schedule Each Day at My Car Wash?](/knowledge/tl0067)
• [How Many Sales Reps Do I Need to Hire for My Logistics Company?](/knowledge/tl0058)
• [How Many Salespeople Do I Need to Hire for My Car Dealership?](/knowledge/tl0052)
• [How Many Producers Do I Need to Hire for My Insurance Agency to Grow My Book?](/knowledge/tl0015)
• [How Do I Figure Out How Many People to Schedule Each Day and at What Times for My Single Store?](/knowledge/tl0002)