It was scoped as a systems project
The statement of work has configuration milestones and no capability milestones. Enablement becomes one line called "training" in week eleven.
We build the layer most implementations skip: buyer-verified stage gates, a qualification scorecard wired into HubSpot, and a manager inspection cadence that holds past week six.
Five failures show up in almost every stalled rollout. Each one is diagnosable from the CRM before the quarter is lost.
The statement of work has configuration milestones and no capability milestones. Enablement becomes one line called "training" in week eleven.
Enablement designs the methodology, RevOps builds the fields, and nobody owns whether managers inspect them. 87% of enablement teams already carry seven or more responsibilities.
Managers deliver about 36 minutes a week per direct report against an effective threshold of 3–5 hours a month. Poor coaching hurts roughly twice as much as good coaching helps.
"Sent the proposal" is an activity. "Proposal reviewed by the decision committee" is a fact. 76% of organisations say less than half their CRM data is accurate and complete.
A date creates pressure to declare victory at go-live. Gates create pressure to prove capability. Only one of those produces adoption.
If quota credit does not depend on the process, the process is optional. Reps are rational. If comp and process disagree, comp wins every time.
No new headcount, no extra leads. Move the four inputs to your team's reality and the arithmetic stays visible.
+3 to +8 points by month 6–9 is what this play targets. The 16-point figure is the measured spread between random enablement (39.2%) and a formal function with a written charter (55.1%).
From the same pipeline, on a win rate moving 24% → 32%.
Model, not a forecast. Attribute against a trend line across multiple cycles, never a single prior quarter — and agree the baseline, the window and the confounds in writing before launch.
Select a layer to see who owns it, what gets built, and how you know it broke.
The highest-leverage artefact in enablement and the one most often absent. A written charter settles mandate, scope, decision rights, funding and the metrics enablement is accountable for. Only 15.8% of organisations have one.
Worth 6.7 points of win rate over formal-without-charter. It costs a day to write.
The sequence matters. Training before instrumentation produces reps who know the right behaviour and have nowhere to record it. Instrumentation before design produces beautifully validated fields that encode the wrong process. Measurement before reinforcement produces a dashboard that documents failure in real time and changes nothing.
Eight MEDDPICC ratings, each paired with an evidence field, each meaning verified — not named. Set a rating to see the Commit gate respond.
"Champion: Green" must mean the champion took a verifiable action for us — not that a name is in the field. That single distinction is the difference between a scorecard and a wish list.
Gating stage movement hard produces sandbagging — reps park deals early to dodge the paperwork. Gating entry to Commit is where forecast accuracy actually lives.
Every field we add is matched by a field we delete or a named manager who will inspect it. Organisations with simplified seller roles were 4.5x more likely to be top sales organisations.
Pipeline rules, conditional logic and validation rules are all bypassed by workflows and the API. On Enterprise, the deal approval process is the only control that survives automation bypass.
We say this in the SOW. Any design that promises "enforced" stage discipline through the other three mechanisms is over-promising.Thresholds we hold engagements to, drawn from the measured ranges in the playbook. Pull each number from your own portal before the first workshop.
| Metric | Weak | Acceptable | Strong |
|---|---|---|---|
| Process adoption — open deals meeting stage exit criteria | Under 50% | 50–75% | Above 75% by day 90 |
| Stage-required field completeness | Under 70% | 70–95% | Above 95% |
| Open deals carrying a current next step | Under 60% | 60–90% | Above 90%, weekly |
| Forecast variance — submitted versus closed | Above 15% | 10–15% | Under 10% by month 6 |
| Coaching coverage — reps with one call reviewed weekly | Under 50% | 50–80% | 100% |
| Manager coaching time per rep, per month | Under 1 hour | 1–3 hours | 3–5 hours |
| Closed-lost deals with a usable loss reason | Under 70% | 70–90% | Above 90% |
| Green ratings backed by a written evidence field | Under 85% | 85–95% | Above 95% |
Benchmarks above 5 hours of coaching per rep per month show no further benefit — the effect plateaus. More is not the answer; consistency is.
Four weeks of design and build, one cohort proving the design, then three scheduled decisions: advance, or hold and remediate.
Interview three top reps, three average reps and every manager. Map the process that actually happens, not the one on the wiki. Select the methodology stack against the motion, then build it in sandbox.
There is no launch. A baseline you did not capture cannot be reconstructed, and every ROI claim made later becomes unfalsifiable and contested.
If you cannot point to an observable number, we will tell you not to run it. "Leadership wants better data" is a wish, not a trigger.
"87% of sales training is forgotten within 30 days" has no publication, no sample size, no year and no methodology. The citation trail runs blog to blog.
The 87% figure and its cousins — 84% at 90 days, 70% in a week, 80% in two days. The learning-pyramid retention percentages, classified as pseudoscientific. "90% of marketing content never gets used" (the traceable figure is 80%, from the CMO Council). "70% of change efforts fail," which traces to a 1995 impression rather than a study.
Thalheimer's review across 69 experimental conditions and 1,000+ learners: forgetting ranged from 0% to 94%, determined by the material, the context, and whether the learner ever used the thing again. That makes retention an operating-cadence question, not a course-design question — so we design reinforcement against behaviour decay in your own CRM telemetry, not a borrowed percentage.
Tier A for primary research with disclosed methodology, Tier B for vendor-published work where the methodology is at least visible. Predictions are labelled as predictions.
Where the pricing page and the knowledge base disagree on a tier gate, we show both figures and name the conflict rather than picking the convenient one.
Three material platform changes shipped in the first eight months of 2026 alone. We re-verify tier gates in your portal before they enter a runbook.
We will pull your adoption, hygiene and coaching-coverage numbers, place them against the bands above, and tell you which of the five layers is broken. If the answer is that you should not run this play yet, we will say so.
Contact us No obligation, and no pitch deck. A working session against your own numbers.
We engineer growth systems. JayOh builds the RevOps architecture, GTM execution and data infrastructure that turn messy revenue operations into predictable pipeline for B2B SaaS and PE-backed teams.
