The Sales Org Health Check Reboot — 60-Min Training

The outcome you should expect

The measurable outcome of this Training is not a feeling — it is a scored artifact. When the hour ends, three things should exist that did not exist at 0:00. First, a filled 12-row rubric with a numeric score on every dimension and a total out of 36, written where the whole leadership team can see it. Second, a ranked list of the three lowest-scoring dimensions, re-ordered for upstream dependency rather than raw score. Third, three calendar invites already sent, each naming a follow-on Reboot training, an owner, and a date inside the next 60 days.

What you should *not* expect is agreement. The most common first-run result is a two-point spread between how the CRO scores coaching cadence and how the RevOps lead scores it. That spread is the finding. A CRO scoring coaching at 2 while the person who reads the CRM every day scores it at 0 is not a rubric problem — it is a visibility problem, and it usually means the executive layer is consuming manager self-reports rather than observing the work. Capture both numbers. Do not average them and move on; the gap is more diagnostic than the score.

The second expected outcome is a reduction in initiative count. Most Sales orgs run two to three major initiatives a year — a methodology rollout, a hiring sprint, a tooling migration — with no formal diagnostic upstream of any of them. Each is defensible alone; together they thrash the team, because a rep who is learning a new qualification framework while onboarding into a new CRM while covering an open territory is learning none of the three. The Health Check exists to cut that number to one sequenced track: one dimension per month, one training per month, re-score quarterly.

Expect the total score to land lower than leadership guessed. That is normal and it is the point. A team that scores itself 31 on the first pass has almost always awarded 3s it cannot defend with data. The recovery move is the "teach it" test described later — if you could not teach this dimension to a peer org tomorrow, it is not a 3.

Finally, expect the artifact to have a shelf life. Scores drift. A dimension that was a 3 when a strong enablement lead ran the function drops to a 1 the quarter after they leave, and nothing in the CRM will tell you that. Re-scoring is what converts a one-time exercise into a trend line, and the trend line is what you actually manage against in year two.

What drives that outcome

Twelve dimensions, each scored 0 (broken), 1 (inconsistent), 2 (working), 3 (best-in-class). No half points — half points are how a room avoids a decision. The rubric below is the whole instrument; the discipline is that every score has to be defensible from data the group can see in the room.

Pipeline coverage. Weighted pipeline divided by remaining quota at quarter start. The classic bar is 3x–4x. A 0 is under 2x or no visibility at all. A 3 is 3.5x-plus with stage-weighted forecast variance staying inside roughly 10%. If you cannot compute this in under five minutes, you are a 0 or 1 by definition — the inability to produce the number *is* the score.

Process discipline. Stage definitions, exit criteria, mandatory fields. A 0 means reps freelance and "Stage 3" means whatever the rep wants it to mean. A 3 means qualification fields are complete before a stage advances, and someone audits that weekly rather than at quarter-end.

Methodology adoption. One methodology showing up in the *language* of deal reviews — MEDDPICC, Command of the Message, Challenger, SPICED, pick one. A 0 is nobody using one. A 3 is roughly 80% of reps using it unprompted, in their own words, without a manager asking "what's the metric?"

Coaching cadence. Structured coaching on deals and skills, distinct from status updates. A 0 is none, or "coaching" that is really a forecast interrogation. A 3 is a weekly 30-minute skill session plus a separate pipeline review, with the coaching topic tracked over time so you can see whether a rep's discovery actually improved.

Tool usage. CRM hygiene, call-recording adoption, engagement-platform usage. A 0 is a CRM nobody trusts. A 3 is weekly call review as a habit and data clean enough that you would pay commission off it without a manual reconciliation.

Hiring quality. Structured interviews, calibrated scorecards, a defined loop. A 0 is vibes-based hiring where the loudest interviewer wins. A 3 is a scorecard-driven loop with regretted attrition holding under roughly 10%.

Ramp time. Start date to 80% of full quota. A 0 is over nine months, or untracked — and untracked is far more common than leaders admit. A 3 is under four months against a written, week-by-week ramp plan.

Attainment distribution. Not average attainment — *distribution*. A 0 is under 40% of reps at quota, or a top-three-reps-carry-most-of-the-number shape. A 3 is 60%-plus at quota with no single rep owning an outsized share of total revenue. A healthy org has a fat middle, not two heroes and a long tail.

Retention. Trailing-12-month voluntary AE attrition. A 0 is above 30%. A 3 is under roughly 12% with regretted attrition under 8%. Split voluntary from involuntary before scoring — an org that managed out five underperformers on purpose is not the same as one that lost five good reps.

Comp competitiveness. OTE benchmarked against a real survey for your stage and ACV, not against what you paid last year. A 0 is below market with no plan. A 3 is at or above the 60th percentile with functioning accelerators reps can actually explain.

Enablement maturity. Onboarding curriculum, ongoing skill work, content mapped to stages. A 0 is nothing. A 3 is a named owner, a published calendar, and some measurement of impact beyond attendance.

Leadership bench. Could you promote a frontline manager to director next quarter without an external search? A 0 is no successor anywhere. A 3 is a named successor for every frontline role.

The dependency logic matters as much as the scores. Process discipline sits upstream of methodology adoption: a methodology layered onto undefined stages evaporates within a quarter, because there is no moment in the deal where the framework is enforced. Coaching cadence is the multiplier on everything else — if managers cannot coach what you teach, teaching something new adds noise. Pipeline coverage and process discipline are foundational; if either scores 0 or 1, they go first regardless of what else is lower.

Benchmarks and realistic ranges

Scores are only useful against external reference points, and the reference points below are the ones this rubric leans on. Where you do not have a credible benchmark for your segment, score conservatively rather than guessing.

Pipeline coverage: 3x–4x. This is the durable B2B benchmark and it holds across most segments, though it flexes with win rate. An org converting at 30% needs materially less coverage than one converting at 12%. Compute your own required coverage as roughly 1 ÷ win rate, then compare to the 3x–4x default. If your math says you need 8x, your problem is win rate, not pipeline generation — and that redirects your prescription entirely.

AE ramp: roughly 5 months as a common SaaS median. Under four months is strong; past nine months you are effectively paying a full-year salary for a partial year of production. Ramp is also the dimension most often scored from memory. Pull the actual start dates and first-close dates for every hire in the last twelve months before anyone scores it — the number is usually a month or two worse than leadership believes.

Attainment: 60%-plus of reps at quota is the healthy shape. Below 40% and the quota itself is suspect, not the reps. Also check concentration: if the top three reps carry the majority of revenue, you have a hero problem, and hero problems break the quarter one resignation lands. This dimension frequently scores 1 in orgs where average attainment looks fine, because the average is masking a bimodal distribution.

Voluntary AE attrition: under 18% is a reasonable healthy band; under 12% is strong. Above 30% you are in turnaround on this dimension alone regardless of the total. Separate regretted from unregretted before scoring, and check tenure at exit — reps leaving inside twelve months usually indicates a hiring or ramp failure, while reps leaving at 24–30 months more often indicates a comp or career-path failure. Same number, entirely different prescription.

Comp: benchmark to a real survey at your stage and ACV. The 60th percentile with working accelerators is a defensible 3. Paying at median with no accelerator ceiling is a 1 or 2 in most competitive markets, because your best reps are the ones who notice.

Forecast variance. If you want one number that summarizes process discipline and pipeline coverage together, use stage-weighted forecast variance against actuals over the last four quarters. Consistently inside 10% is a strong signal. Swinging 25% quarter to quarter means the stages are not doing work — they are labels, and the forecast is being produced by manager intuition regardless of what the CRM says.

Realistic total ranges. A Series A org running founder-adjacent Sales typically lands 14–20; the gaps are enablement, bench, and process, and that is expected, not alarming. Series B/C lands 20–27, usually strong on tooling and weak on coaching and ramp. A mature org at 28–33 is defending a lead and should be scoring quarterly to catch drift. Scores above 33 are rare and should be re-audited — in practice a 34+ on a first run almost always means the room graded itself generously.

Risks, edge cases, and failure modes

Score inflation is the dominant failure. Teams round up to avoid uncomfortable conversations, especially when the person who owns a dimension is in the room. Counter it structurally: assign one person — the RevOps lead or an outside facilitator — to hold the rubric and challenge every 3. The working test is "a 3 means you could teach this dimension to another org next week." When the room debates between two scores, take the lower one. Debate itself is evidence the higher score is not clearly true.

The founder or CRO scoring first. If the most senior person states a number before anyone else, the rest of the room anchors to it. Run four minutes of silent individual scoring before any discussion, then reveal simultaneously. This one procedural change does more for score honesty than any amount of facilitation skill.

Attacking the lowest score. The instinct is to fix the 0 first. Often the 0 is downstream of a 1. Methodology adoption at 0 with process discipline at 1 is a sequencing trap: run the methodology Training first and it fails, because there is no enforced stage gate where the framework gets used, and now the team has learned that Reboot trainings do not stick. Order by dependency, not by severity.

Untracked dimensions scored as if tracked. If nobody can produce the data for ramp or regretted attrition, the honest score is 0 or 1 — not "probably a 2." Inability to measure is itself a maturity failure. Orgs consistently over-score exactly the dimensions they cannot instrument, which is how the rubric's most important signal gets erased.

Running it too often. Quarterly re-scores are for tracking the three dimensions you are actively working. A full 12-dimension re-run more often than annually produces noise from normal quarter-to-quarter variance and burns the room's patience. Annual in Q4, before planning, is the cadence that matters — the scores then feed headcount, quota, and enablement budget while those decisions are still open.

Running it too late in the planning cycle. If the Health Check happens in January after the plan is locked, the prescription competes with commitments already made. The diagnostic has to precede the plan or it becomes commentary.

Edge case: fewer than about 15 reps. Attainment distribution and retention become statistically meaningless at small scale — one departure is 20% attrition. Score those two dimensions qualitatively and weight process, coaching, and hiring more heavily. Note the adjustment on the rubric so next year's comparison is apples to apples.

Edge case: multi-segment orgs. An org running both SMB velocity Sales and enterprise field Sales should score the two segments separately. Blending them produces a meaningless middle: SMB will drag ramp down and enterprise will drag pipeline coverage up, and the composite describes nobody. Two rubrics, two prescriptions.

Edge case: post-acquisition or post-reorg. Score the org as it exists today, not as it existed pre-change. Historical attainment from a different territory model is not evidence about the current one. If less than a quarter has elapsed since the change, note it and treat the first run as a baseline rather than a verdict.

The commitment failure. Initiatives without a named owner and a date have very low completion rates. If the hour ends with "we should do a coaching Training soon," the Health Check produced nothing. Send the three calendar invites from inside the room, before anyone stands up.

A practical rollout plan

Pre-work (10–15 minutes, done before the room convenes). Pull four raw data sets into one shared doc: per-rep attainment against quota for the last four quarters; ramp velocity for every hire in the last twelve months, measured start date to first close and to 80% of quota; voluntary and involuntary turnover by quarter; and current weighted pipeline coverage. Raw numbers only, no synthesis, no commentary — the scoring works because everyone is looking at the same unfiltered facts. The act of gathering usually surfaces the first red flag on its own, most often that one of the four is not actually tracked anywhere.

0:00–0:05 — Frame it. State the premise: most Sales orgs do not have a sales problem, they have a diagnostic problem. They roll out a methodology because a conference said to, then a hiring sprint because attainment slipped, then a tool migration because the board asked. State the rule for the hour: diagnose first, prescribe second. Nothing new gets initiated until the rubric is scored.

0:05–0:20 — Walk the rubric. Read all twelve dimensions aloud with their 0 and 3 anchors so everyone is scoring against the same definitions. Do not score yet. Answer definitional questions now; a question asked during scoring costs three times as much time.

0:20–0:30 — Score live. Four minutes of silent individual scoring, then go dimension by dimension around the table. Cap each dimension at under four minutes with a visible timer — twelve dimensions at four minutes is already 48 minutes, so most need to land in one or two. Write every divergent score on the board rather than resolving it. Exposure, not consensus, is the goal of this block.

0:30–0:40 — Find the bottom three. Rank the low scores, then re-order for upstream dependency. Pipeline coverage and process discipline jump the queue if either is 0 or 1. Coaching cadence jumps if managers cannot deliver what you are about to teach. Write the three on the board in execution order.

0:40–0:55 — Prescribe. Map each of the bottom three to a specific follow-on Reboot Training in the library and commit to running it within 60 days. One dimension per month, one Training per month, everything else waits. Put dates in the calendar before leaving the room, with a named owner per line — not a team, a person.

0:55–1:00 — Close. Three commitments on the wall: dimension, training, owner, date. Set the 90-day re-score meeting now, same room, same people, same rubric. Progress is measured as dimension-level score lift, not as initiatives launched.

The twelve-month mechanic. Months 1–3 execute the three prescribed trainings. Month 3 re-scores only those three dimensions. Months 4–6 take the next tier, and so on. The full 12-dimension Health Check re-runs once a year in Q4, feeding the annual plan. Anything not on the list waits — that constraint is the entire value, because it is what stops the organization from running three unsequenced initiatives at once.

Related questions

How long should the whole cycle take before we see score movement?

Expect 90 days for the first measurable lift on a single dimension, and closer to two quarters for coaching cadence or ramp time, which are behavior-change dimensions rather than process-change dimensions. Tooling and process scores can move inside 30–45 days.

Can a frontline manager run this instead of the CRO?

Partially. A manager can score their own team on coaching, process, tools, and methodology. Comp competitiveness, leadership bench, and enablement maturity require authority over budget and headcount, so those dimensions need the CRO or VP present to score honestly.

What if two leaders cannot agree on a dimension score?

Record both numbers and take the lower one for the total. The disagreement is the more useful output — it usually means one person is reading self-reported manager summaries while the other is observing the actual work. Investigate the gap before the next re-score.

Do we score the whole company or one segment at a time?

One segment at a time whenever the motions differ. SMB velocity and enterprise field selling produce opposite readings on ramp and coverage; blending them yields a composite that describes neither. Run two rubrics and issue two prescriptions.

Is a low total score a reason to replace leadership?

No. A low total identifies where the system is under-built, which is usually a resourcing and sequencing story rather than a personnel one. Use it to fund the next three trainings. If scores do not move after two honest cycles with real investment, that is a different conversation.

FAQ

What exactly happens during the 60-minute Training?

You walk a 12-dimension health rubric, scoring each dimension 0 to 3 against your org's actual data. The total out of 36 places you in a band — under 24 is turnaround, 24–30 is a tune-up, 30-plus means defending your lead. The hour ends with a prescription linking your lowest scores to specific follow-on trainings, each with an owner and a date.

Do I need to prepare anything before the training?

Yes. Bring four quarters of attainment data, ramp velocity for the last twelve months of hires, voluntary and involuntary retention, and current pipeline coverage. The exercise depends on real numbers rather than optimistic recall — you cannot fix what you will not measure. Without the pre-read the scores are opinions, and opinions do not produce a usable prescription.

Who is this training designed for?

CROs, VPs of Sales, and RevOps leads with authority over process, headcount, and budget. Frontline managers and individual contributors are not the audience — the rubric measures systemic health, not daily execution. A manager can score the subset of dimensions they control, but comp, bench, and enablement need someone who can act on the result.

How is this different from the other Reboot trainings?

Every other training fixes one symptom — pipeline gaps, weak qualification, thin coaching. This one tells you which symptoms you actually have. It is the index, not a chapter. Running it first is what keeps you from spending a quarter on a methodology rollout when your real constraint was ramp time or forecast discipline.

How often should we run this health check?

Fully, once a year in Q4 before planning, so the results feed quota, headcount, and enablement budget while those are still open. Re-score only the three dimensions you are actively working every 90 days. More frequent full runs generate noise from normal quarterly variance; less frequent runs miss gradual decline.

What if our scores come out low — is that bad?

Low scores are the useful outcome. The instrument is built to surface honest mediocrity, because that is what tells you where to spend the next two quarters. A total under 24 is a clear, actionable signal that foundations need building before anything sophisticated gets layered on top. Inflated scores are the genuinely bad result — they hide the work.

Sources

1. Roberge, Mark. *The Sales Acceleration Formula.* Wiley, 2015 — https://www.wiley.com/en-us/The+Sales+Acceleration+Formula-p-9781119047070
2. Jordan, Jason and Michelle Vazzana. *Cracking the Sales Management Code.* McGraw-Hill, 2011 — https://www.mhprofessional.com/cracking-the-sales-management-code-the-secrets-to-measuring-and-managing-sales-performance-9780071765732-usa
3. Bertuzzi, Trish. *The Sales Development Playbook.* — https://www.thebridgegroupinc.com/sales-development-playbook
4. The Bridge Group — SaaS AE and SDR metrics research — https://www.thebridgegroupinc.com/research
5. Winning by Design — SPICED framework and revenue architecture resources — https://winningbydesign.com/resources/
6. Force Management — Command of the Message — https://www.forcemanagement.com/command-of-the-message
7. Harvard Business Review — sales management and forecasting research — https://hbr.org/topic/subject/sales
8. Gartner — sales practice research and CSO guidance — https://www.gartner.com/en/sales
9. Pavilion — GTM leadership community and operating benchmarks — https://www.joinpavilion.com/

Related on PULSE

• [The Annual Sales Planning Reboot — 60-Min Training](/knowledge/st226)
• [The Customer Health Scoring Reboot — 60-Min Training](/knowledge/st208)
• [The Founder-Led Sales Transition Reboot — 60-Min Training](/knowledge/st236)
• [The PLG Sales Motion Reboot — 60-Min Training](/knowledge/st237)
• [Hospice and Home Health Admissions — 60-Min Training](/knowledge/st291)
• [Group Health Benefits Broker Selling — 60-Min Training](/knowledge/st332)