THE SCORECARD
Three Head of RevOps OKRs that defend the seat at 200-500 SaaS.
You're not the Salesforce admin. You're not the forecasting analyst. You're not the deal-desk approver. You also don't only own forecast accuracy — you own forecast, pipeline conversion math, territory and quota planning, comp plan administration, GTM data architecture, and win/loss analytics on top of that. Three objectives show up on every RevOps scorecard that holds at this stage — picked specifically because they cover the full motion, not just forecast season. None of them is "improve forecast accuracy" (that's an outcome of upstream discipline, not something you can directly enforce). These are the three that actually hold.
| Objective | Key Result | Benchmark / Threshold | Target |
|---|
| Hold forecast accuracy in ±10% across all 13 weeks of the quarter O1 · Variance that narrows toward quarter-end, not widens — the seat-defining metric for RevOps at 200-500 |
Weekly forecast variance ≤ ±10% from week 4 forward±10% because that's Gartner's top-quartile benchmark1; widening past 10% mid-quarter means the upstream stage discipline is broken |
±15-25% typical1 Threshold | ≤ ±10% |
| Forecast variance trends DOWN week-over-week from week 6 onwardDirection matters more than absolute number — variance widening through quarter close is the structural failure signal |
Variance widens 60% of qtrs Threshold | Trend down |
| Pipeline conversion rates (MQL→SQL, SQL→Opp, Opp→Won) reviewed monthly with CRO and CMO — drift > 15% triggers root-cause reviewConversion-rate drift is the leading indicator forecast variance can't catch — when MQL→SQL drops 22% and nobody flags it, the forecast is wrong 6 weeks later |
No cadence typical Threshold | Monthly |
| Catch CRM hygiene drift before it shows up as forecast variance O2 · The leading indicator that prevents O1 from blowing up — required-field discipline + stage-aging discipline |
CRM required-field completeness ≥ 90% across active opportunities90% because at 70-80% the data is unusable for forecasting; at 90%+ the rep behavior is enforced |
60-70% typical Threshold | ≥ 90% |
| Stage-aged opportunities (90+ days in stage) ≤ 10% of pipeline at any time10% because the rest distorts coverage math and cumulates into the quarter-close cleanup spike |
25-35% typical Threshold | ≤ 10% |
| Run the major GTM motions on cadence — not on emergency O3 · Territory and quota planning, comp plan rollout, GTM definitions — the operating rhythms that actually run RevOps when forecast season isn't burning |
Annual GTM data model + territory + comp plan all signed by CRO + CFO + CMO before quarter startsBefore because mid-quarter changes break forecast modeling, AE motivation, and CMO attribution simultaneously |
Mid-quarter drift typical Threshold | Pre-Q sign-off |
| All exec dashboards reconcile to ±2% on weekly revenue numbers; territory + comp data refreshed monthly±2% accounts for legitimate timing differences (booked vs. recognized); wider gaps signal definition drift or stale territory mappings |
±5-15% drift typical Threshold | ≤ ±2% |
How to start in week 1 of the quarter
Don't migrate Salesforce. Don't hire a forecasting analyst. Do these five things:
→ Pull last quarter's forecast variance week-by-week. If it widened from week 6 onward, that's your Q3 priority — not better dashboards.
→ Define the 5 CRM required fields that absolutely have to be populated for forecasting (close date, amount, stage, next step, decision-maker). Anything else is optional. Communicate the list to all VPs.
→ Run a 1-hour stage-aging audit. Pull every opportunity 90+ days in stage. Either move them, mark them dead, or escalate. Your baseline number for the quarter.
→ Get CRO + CMO in a 30-minute meeting to sign the MQL/SQL/Opportunity/Closed-Won definitions. Document, share, never debate again.
→ Set a Friday 4pm deadline on weekly pipeline updates. AEs who miss it surface to their VP — not to you. Enforcement is at the function, not the seat.
Why O2 is the seat-defining objective
O1 is what the CFO watches. O3 is what the CRO and CMO fight over. O2 is what makes O1 and O3 actually possible. If your CRM hygiene is at 60% with 30% of pipeline aged, no forecast model will hold ±10%, and no shared MQL definition will survive contact with the data. O2 is the leading indicator that the seat is working — when CRM hygiene is at 90%+ and stage aging below 10%, forecast variance and definition drift both narrow on their own.
STRATEGIC BETS
The three bets inside every RevOps OKR stack — and the dozen your team runs without you.
Your Salesforce admin runs the field-management. Your data analyst runs the dashboard refresh. Your sales-ops manager runs deal desk. You don't. Your job is the three bets that make forecast variance hold, CRM hygiene self-enforce, and the GTM data model survive contact with the CRO and CMO who don't agree on what an opportunity is.
Strategy 1 — Make forecast variance narrow toward quarter-close, not widen
→ O1
1.1
Weekly forecast call: AEs commit deals, VPs approve commits, RevOps owns variance reporting — Friday 4pm deadline enforced at the VP layer, not the seat
All VPs + AEs
1.2
Stage-aging audit weekly — opportunities 60+ days in stage flagged, 90+ days require action (move, kill, or escalate to VP)
RevOps + VPs
1.3
Forecast call methodology: AEs provide commit / best-case / pipeline confidence — variance trended week-over-week, not just to quarter close
Internal
1.4
Quarter-end cleanup limit: if mass Closed-Lost events exceed 5% of pipeline at quarter-close, root-cause review with the affected VP within 14 days
VPs
Strategy 2 — Make CRM hygiene self-enforce at the function, not at the seat
→ O2
2.1
Required field list — minimum 5 fields per stage, communicated to all VPs, enforced via stage-progression validation rules
RevOps + Salesforce admin
2.2
Weekly hygiene scorecard by team — VP gets the score, not the AEs. Below 80% triggers VP-level conversation, not a RevOps reminder.
All VPs
2.3
Field deprecation discipline — annual audit of which CRM fields are required, optional, dead. Anything not used in reporting gets deleted or hidden.
Internal
2.4
Onboarding rep playbook — every new AE/SDR/CSM gets the 5-required-fields walkthrough in week 1 with their VP, not as a self-serve doc
All VPs + Enablement
Strategy 3 — Lock GTM definitions before the next quarter's planning
→ O3
3.1
Annual GTM data model document — MQL/SQL/Opportunity/Closed-Won/Expansion definitions with explicit examples, signed by CRO + CMO at FY start
CRO + CMO + CFO
3.2
Mid-year refresh — definitions reviewed at H2 planning, drift checked against actual data, signed off again
CRO + CMO
3.3
Dashboard reconciliation cadence — monthly check that CRO + CFO + CMO dashboards show same revenue numbers within ±2%
RevOps + Finance
3.4
Definition-change process — any function wanting to change MQL/SQL/Opp definition mid-year submits a change request reviewed by all three function heads
Internal
ENFORCEMENT LAYER
Enforcement for RevOps OKRs — the cadence layer above your CRM and forecasting tools.
Salesforce stores deals. Clari forecasts on top of them. HubSpot tracks marketing leads. Each tool runs in one lane and reports what's there. None of them enforces whether the inputs were updated on time, whether the upstream definitions match, or whether the cross-functional handoffs happened. That's the cadence layer above your CRM stack — where ShiftFocus runs.
How this works in practice: your RevOps team computes the KR values where you already do — forecast variance in Clari or Excel, hygiene scores in Salesforce, conversion rates in your data warehouse. Each week, the team enters those values into ShiftFocus as KR updates. ShiftFocus runs the cadence and triggers ON those values: when variance crosses ±10%, Trigger 4 fires; when an upstream feed dependency from CRO is overdue, Trigger 6 fires. We don't pull data from Salesforce. We make the KRs your team already maintains run on a cadence that catches problems at week 5 instead of week 12.
Six of the seven triggers fire on RevOps KRs. Two define daily pain: KPI Drift (Trigger 4 — forecast variance crosses threshold) and Dependency SLA Breach (Trigger 6 — upstream data feeds skipped). One catches the variance before quarter-close. The other catches the upstream cause before the variance shows up.
The two that fire hardest at the RevOps layer
Trigger 4 · KPI Drift — when forecast variance crosses the threshold
⚡ Fires whenWeekly forecast variance KR crosses ±10% from week 4 onward, OR CRM hygiene score drops below 80%, OR stage-aged opportunity ratio crosses 15%. Threshold
▎ Why this matters
Forecast variance is the lagging indicator that determines whether the seat survives the quarter. By the time the CFO shows the board "we missed by 18%," the recovery window has closed. Trigger 4 fires the moment any of the three input KRs crosses threshold — variance, hygiene, or aging — so the conversation happens at week 5, not week 12.
▎ Why ShiftFocus catches it
Salesforce reports pipeline. Clari forecasts variance. Each views one slice. ShiftFocus runs all three RevOps input KRs (variance + hygiene + aging) through one cadence — when any one crosses, the trigger fires with which one and which function. The conversation in Friday's exec meeting is "Mid-Market hygiene dropped to 73% in week 5; that's why variance is widening" — not "the forecast is off, let's investigate."
▎ Example scenario
Week 5 of Q3. Your "Forecast variance ≤ ±10%" KR ticks past threshold — week 4 was ±9%, week 5 is ±13%. Trigger 4 fires. Same week, your hygiene KR for Mid-Market shows 76% (below the 90% target). The brief lands with both KRs called out. You walk into Friday's exec meeting with "Mid-Market hygiene dropped — that's why variance is widening" and a 7-day plan to recover hygiene before the quarter compounds.
Trigger 6 · Dependency SLA Breach — when upstream data feeds get skipped
⚡ Fires whenAn upstream data dependency tracked as a KR — weekly pipeline update from a Sales VP, monthly MQL definition refresh from CMO, quarterly comp-plan-feed from Finance — misses its SLA by more than 48 hours. Threshold
▎ Why this matters
Every RevOps KR depends on upstream functions feeding the data on time. When the CRO doesn't sign off on the weekly pipeline by Friday, your forecast variance Monday isn't real — it's the previous week's number. ShiftFocus tracks the upstream feeds as KR-level dependencies. When a feed is skipped, the breach attributes to the function that owed it — not to RevOps for "the dashboard is wrong."
▎ Why ShiftFocus catches it
Lattice doesn't track data feeds. Salesforce doesn't know the CRO didn't sign off on commits. Clari assumes the inputs are current. ShiftFocus runs the cadence layer where every upstream feed is a tracked dependency on a RevOps KR — and where missing the feed fires a trigger that attributes upstream, not to the seat that owns the report. The conversation on Tuesday is "the CRO's commit feed is 72 hours overdue, here's the impact on Friday's forecast call" — not "RevOps' numbers don't match."
▎ Example scenario
CRO's "Weekly commit sign-off" tracked as an upstream dependency on your "Forecast variance ≤ ±10%" KR. Friday: commit not submitted. Monday morning: dependency 72 hours overdue. Trigger 6 fires to CRO + Chief of Staff. The Tuesday exec meeting starts with "the commit-feed dependency is breached — let's resolve it before Friday's forecast call," not with a RevOps explanation of why the variance number is stale.
The other 4 that also fire on your KRs
Trigger 1 · Missed Cadence
⚡ WhenA scheduled RevOps cadence skips: weekly data sign-off, monthly definition refresh, quarterly territory review, monthly comp-plan reconciliation. The cadence itself is the KR; missing it is the trigger.
▎ Example scenario
Monthly MQL definition refresh with CMO scheduled for first Tuesday. Skipped two months in a row. Trigger fires — not to RevOps, to the function that owed the meeting.
Trigger 2 · Velocity Drop
⚡ WhenPipeline velocity (avg deal age in stage) drops below 50% of plan for 2 consecutive weeks across a segment.
▎ Example scenario
Mid-Market deals avg 45 days in Discovery. Plan was 30. By week 3, velocity 0.4. Trigger fires — segment review.
Trigger 5 · Owner Absence
⚡ WhenOpportunity has no AE owner, or 30%+ of pipeline is owned by RevOps as the default fallback.
▎ Example scenario
Q3 audit: 22 opportunities show RevOps team as primary contact. Trigger fires — owner reassignment review.
Trigger 7 · Projected Miss
⚡ WhenProjected end-of-quarter forecast variance > ±15% at week 6, with cross-functional attribution to which input KRs are driving it.
▎ Example scenario
Week 6 projection: ±18% variance. Brief fires to CRO + CFO + RevOps with breakdown by segment and KR.
Why this works alongside your existing GTM stack
Each of your tools runs in one lane: Salesforce is your CRM, Clari handles forecasting, HubSpot tracks marketing leads, Outreach handles sequences. They each do their job well. ShiftFocus is the cadence and trigger layer above them — where forecast variance, CRM hygiene, and stage-aging KRs are reviewed in one weekly cadence; where the upstream data feeds from CRO/CMO/Finance are tracked dependencies; and where threshold breaches and dependency SLAs both fire to RevOps before the forecast goes wrong. Your team keeps using whatever GTM stack you have. ShiftFocus adds the cadence layer that makes RevOps predictive instead of explanatory.
ESCALATION DESIGN
The Head of RevOps escalation chain — 5 levels, all on a 48-hour clock.
Every trigger feeds into this ladder. The ladder climbs on time, not on judgment. Below is a single upstream dependency breach (Sales VP missed Friday commit sign-off) threaded through all five rungs.
L1
Auto-Nudge — to the upstream owner
Friday 4pm: Sales VP's weekly commit sign-off dependency hasn't completed. Trigger 6 fires. Sales VP gets Slack + email: dependency overdue, 48h SLA breached, sign-off required for Monday's forecast variance KR. Initiative flags yellow.
Immediate
L2
Peer Flag — Chief of Staff + RevOps + CRO see it
Monday morning: dependency still unresolved. Chief of Staff and CRO see the flag in the weekly dashboard. Peer pressure resolves it without RevOps becoming the chaser.
+48h
L3
CRO Review — VP-level commit conversation
Tuesday: still stuck. CRO directly asks the Sales VP for the commit sign-off and an explanation. The conversation is between CRO and VP — RevOps stays out of it, owning the consequence-tracking, not the chase.
+48h
L4
Pattern Brief — recurring breach surfaces
Week 6 auto-check: 3 weekly commit sign-offs missed this quarter. Pattern goes to CRO + CFO + RevOps — not the individual instance. "Sales VP commit-feed reliability dropping" is a CRO-level operating problem, not a RevOps cleanup task.
Week 6
L5
Intervention — operating-cadence review
3 weeks before quarter close. Forecast variance projecting >±20% with multiple upstream feeds breaching. Full GTM exec team in the room. Decision: enforce the cadence with sign-off requirements, or accept the structural variance and re-baseline forecast methodology.
T-3 weeks
What this kills
The RevOps failure mode where you spend Q3 chasing 12 AEs and 4 VPs for pipeline updates, present a clean forecast Monday morning that's already stale by Wednesday, and absorb the blame at the QBR for variance you flagged in week 4 that nobody acted on. Trigger 6 fires the moment a feed dependency is breached. Same facts, same week, with the chase happening at the function — not the seat.
EXECUTION INTELLIGENCE
How the 5 ShiftFocus metrics read on your RevOps KRs.
ShiftFocus runs five health metrics on every KR — same five whether the KR is "Forecast variance ≤ ±10%" or "CRM hygiene ≥ 90%" or "Stage-aged opportunities ≤ 10%." You don't need to compute them. The point is reading them. Here's what each one tells you on a RevOps KR.
What this looks like at week 6 of Q3
$40M ARR SaaS, 320 employees. Head of RevOps has three OKRs running. Here's how the metrics read across them, mid-quarter:
What the leakage actually costs
RevOps failures don't compound across headcount, but they compound across every revenue function — and they show up as forecast variance, missed expansion, and discount drift simultaneously. Numbers sourced; scenarios illustrative for a $40M ARR SaaS with 320 employees, 7 AEs in each of 3 segments, median ACV $50K.
Forecast variance compounding into mid-quarter — board surprise
Variance widens from ±9% week 4 to ±18% week 12. Real-dollar surprise on $10M quarterly target = $1.8M off plan vs. ±$900K expected. Variance gap modeled at ~$900K of unforecast risk.
1−$900K
Discount drift — AEs close at 18% off list to hit number
When variance is climbing mid-quarter, AEs discount harder to close. 18% avg discount on 40 deals × $50K ACV = ~$360K margin drag. Multiplied across 3 segments = ~$700K quarterly.
2−$700K
Mass quarter-close cleanup — 12% of pipeline marked Closed-Lost in week 13
Rather than the 5% normal-discipline target, 12% means ~$1.2M in pipeline that should have been Closed-Lost weeks earlier. Distorts win-rate metrics, AE comp, and next-quarter forecast assumptions.
−$600K
RevOps team time absorbed by reconciliation, not strategy
3-person RevOps team × 50% time on dashboard reconciliation × $130K fully-loaded comp ÷ 4 quarters = ~$240K per quarter of strategic capacity not deployed.
−$240K
CRO/CMO disagreement cost — exec time on definition fights
When MQL/SQL/Opp definitions drift, CRO + CMO + their VPs lose ~6 hours/quarter to reconciliation meetings. Fully-loaded exec time × 8 people × 6 hrs = ~$180K. Plus opportunity cost of the strategic conversations not happening.
−$180K
Quarterly cost band of running RevOps without enforced data discipline
$3M – $5M
1 Gartner 2024 Sales Forecasting Benchmark — fewer than 50% of B2B forecasts within ±10%; top-quartile cost-per-miss benchmarks.
2 Everstage 2024 SaaS Sales Compensation Benchmarks — discount-drift and ACV compression patterns at quarter close.
Cost range reflects modeled variance across $20M–$60M ARR band; upper end assumes compounding of forecast variance, discount drift, and quarter-close cleanup in the same quarter.
The ROI math for a Head of RevOps buying this internally
Modeled quarterly leakage: $3M–$5M (range scales with ARR, segment count, and how many upstream feeds are routinely missed). Annual: $12M–$20M. The single highest-value moment for the seat is converting "RevOps missed the forecast" into "the CRO's commit-feed dependency was breached 4 of 13 weeks; the CMO's MQL definition drifted in May; here's the variance attribution by week and function" — before the next QBR. The business case is making upstream data discipline an enforceable cadence, not a hope — not "another forecasting tool on top of Salesforce."