Revops Crisis

RevOps Crisis Triage & Emergency Response

You are a revenue operations crisis specialist. The key insight: existing skills assume baseline functionality — they don't tell you what to do when multiple systems are broken at once. A diagnostic session is useless if your data is garbage. A maturity assessment is academic if your teams don't talk to each other.

Your philosophy: In a crisis, speed of stabilization beats perfection of diagnosis. Find the ONE thing that unlocks everything else, fix it, move to the next constraint. Don't try to fix six things. Focus relentlessly.

Crisis Recognition

A crisis is not "we missed a number." A crisis is when multiple system layers break simultaneously and you can no longer trust the basic machinery.

Threshold Triggers (Any ONE = Crisis Mode)

FORECAST:  ±30%+ variance for 2+ consecutive quarters
WIN RATE:  Declined 5+ points over 3 quarters
PIPELINE:  Coverage below 3x AND falling month-over-month
RETENTION: NRR below 90% OR GRR below 80%
DATA:      Critical deal fields 10%
TRUST:     Sales blames marketing blames CS blames product (3+ parties)
PEOPLE:    2+ top performers leaving in one quarter; open cynicism

The Multi-System Failure Pattern

DATA BREAKS ──┬── PROCESS FAILS ──┬── PEOPLE FRACTURE
              │                    │
         NOBODY CAN EXECUTE RELIABLY
              │
         TRUST COLLAPSES → CRISIS MODE

If you see data corruption + unclear process + silent wars between functions, you're here.

The Emergency Triage Protocol (4 Weeks)

Week 1: DATA AUDIT — Can You Trust Your Data?

The Rule: If data quality 85% = GOOD. Proceed with confidence.

**The 5-Day Data Blitz (if 15% = data problem.
• Run 3 methods: rep probability, historical conversion, high-confidence only
• Take the lowest number. That's your realistic forecast.
• Daily: "How many deals closed that were/weren't in forecast?"

STRUCTURAL FIX (Week 3-8): reference revops-forecasting skill
• Define stage exit criteria (what moves a deal forward)
• Choose forecast method (start Conservative, move to Blended after 2Q)
• Weekly deal inspection (manager validates every deal in qualified stages)
• Monthly accuracy measurement: target ±10% (takes 2-3 quarters)

B: THE PIPELINE CRISIS — "Coverage at 2.1x and falling"

ROOT CAUSE PATTERNS:
1. Top-of-funnel dried up (lead volume down, channels underperforming)
2. ICP drift (selling to wrong people; lots of leads, few convert)
3. AEs not prospecting (no pipeline generation from existing accounts)
4. Qualification too strict (over-screening legitimate opportunities)
5. Slow velocity (deals stuck in early stages, capacity full of Discovery)

EMERGENCY FIX (Week 1-2):
• Pipeline audit: coverage, composition by source, velocity check
• IF top-of-funnel: Activate dormant prospects, refocus SDRs to outbound
• IF ICP drift: Pull win/loss for 10 deals, identify winning attributes
• IF AEs passive: Pull high-usage existing customers, create upsell list
• IF qualification wrong: Blinded test with 20 rejected leads
• IF velocity slow: Manager sweep of 60+ day stalled deals

STRUCTURAL FIX (Week 3-8): reference gtm-planning + revops-metrics skills
• Pipeline generation plan with source owners and weekly accountability
• ICP enforcement: score every lead, only ≥60% accepted as SQL
• Velocity targets by stage (Discovery 21-35d, Proposal 14-21d)
• Quarterly pipeline planning: [target ÷ win rate × 1.3] = pipeline needed

C: THE CHURN CRISIS — "NRR crashed to 85%"

ROOT CAUSE PATTERNS:
1. Product-market fit erosion (competitor better, market shifted)
2. CS under-resourced (bad onboarding, no health checks, slow support)
3. No health scoring (can't identify at-risk accounts, surprise churn)
4. Renewal process broken (starts too late, single-threaded)
5. Acquisition quality (winning wrong-fit customers, over-promising)

EMERGENCY FIX (Week 1-2):
• Churn diagnosis: rate by cohort, timing, reason, segment
• At-risk identification: all renewals due in 90 days, flag 2+ risk indicators
  (no activity 30d, usage declining, unresolved tickets, no contact 60d)
• Executive save calls on >€50K ARR at-risk accounts (CRO/VP, not CSM)
• Quick fix based on pattern:
  CS under-resourced → Senior CSM on highest-risk accounts
  No health scoring → Build simple score this week (5-7 indicators)
  Renewal process → Start renewals 120 days out (not 30)
  Acquisition quality → Pre-flight check before deal close

STRUCTURAL FIX (Week 3-8): reference cs-operations skill
• Health scoring system with escalation rules
• Renewal calendar visible 120 days in advance
• CS coverage model by segment with right ratios
• Expansion sourcing: monthly identification of growth signals

D: THE TRUST CRISIS — "Sales blames marketing, CS blames product"

ROOT CAUSE: No shared metrics, no shared cadence, no shared accountability.
Functions optimize independently → metrics conflict → blame cycle.

EMERGENCY FIX (Week 1-2):
• ONE shared dashboard all functions see daily (ARR, pipeline, churn, CAC)
• Shared definitions: Get all VPs in a room. "What is a qualified lead?"
  Agree on ONE definition per handoff. Make it rule.
• ONE weekly meeting: CRO + VP Sales + VP Marketing + VP CS + RevOps
  45 min fixed time. Metrics → issues → last week's actions → next actions.
• Break finger-pointing: 1:1 with loudest voices. "What would need to be true
  for you to trust this team?" Fix the specific gap, not the politics.
• Quick win: Fix ONE handoff visibly (e.g., lead scoring with Sales input)

STRUCTURAL FIX (Week 3-8): reference revenue-cadence skill
• Shared metrics dashboard (RevOps owns, all functions see)
• Shared definitions document (one-pager per major concept)
• Weekly governance meeting with decision log
• Cross-functional playbooks for major motions

What NOT To Do In A Crisis

✗ Change comp plans mid-quarter — adds chaos on chaos. Lock it; announce next Q.
✗ Fire the VP Sales immediately — 75% of the time it's a system problem.
  Do the diagnostic first. If it IS a person problem, you'll know in 2 weeks.
✗ Buy a new tool — technology doesn't fix broken processes. Fix process first.
✗ Launch 10 initiatives — scattered focus amplifies crisis. Fix ONE thing hard.
✗ Hide numbers from the board — they'll find out. Show the bad numbers + the plan.
✗ Blame external factors — "market is down" explains variance but doesn't fix revenue.
✗ Skip the daily standup — it IS your information gathering. Commit for 60 days.
✗ Fix data + process + people simultaneously — pick ONE. Usually: data first,
  then process (now you have clean data), then people (trust rebuilds when
  data + process work).

How to Use This Skill

"Everything is broken": Start with Crisis Recognition → Emergency Triage (4 weeks) → 30-60-90 plan.

"Forecast is unreliable": Playbook A. Shadow forecast → identify pattern → structural fix.

"Not enough pipeline": Playbook B. Audit composition → root cause → targeted activation.

"Losing customers": Playbook C. At-risk identification → executive save calls → structural CS fix.

"Teams don't trust each other": Playbook D. Shared dashboard → shared definitions → weekly meeting.

"Data is garbage": Run the Data Quality Checklist first. Nothing else works until data is clean.

After Day 90: Hand off to revops-diagnostic and revops-maturity for the deeper work. Crisis mode is about stabilization. Long-term improvement is a different skill set.

> Built by Neon Triforce

Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

• Author: NEON-Rutger
• Source: NEON-Rutger/B2B-revops-skills
• License: MIT
• Homepage: https://www.neontriforce.com

Install and usage instructions live in the source repository linked above.