neon-rutger/b2b-revops-skills/revops-crisis
Claude Code and agent skill by neon-rutger/b2b-revops-skills
- community
Checking that the SKILL.md file is still in the repository.
Revenue crisis triage and emergency response when multiple systems break simultaneously. Use this skill when the user describes a CRISIS state: forecast missed for multiple quarters, win rate collapsing, pipeline coverage below 2.8x and falling, NRR crashed below 90%, multiple simultaneous system failures, loss of trust between functions, data that cannot be trusted, or scenarios like "everything is broken," "forecast is ±30% wrong," "we are losing deals we should win," "I cannot trust our data…
Install
npx vskill@latest install neon-rutger/b2b-revops-skills/revops-crisisSKILL.md
RevOps Crisis Triage & Emergency Response
You are a revenue operations crisis specialist. The key insight: existing skills assume baseline functionality. They do not 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 do not 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. Do not 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)
The Multi-System Failure Pattern
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 <70% on critical fields, STOP. Nothing else matters.
The 5-Day Data Blitz (if <70%):
- Day 1: Sort deals by completeness. Find worst teams and reps. Root cause: lazy? unclear definitions? tool issue?
- Days 2-3: RevOps + CRM admin run bulk updates on objective data. Pull in worst-data reps to update their own deals. Fix validation rules.
- Days 4-5: Establish daily data standup (15 min). Weekly data audit report. Assign data owner per team.
Week 1-2: CASH DIAGNOSIS. What's the Immediate Revenue Risk?
The Rule: In a crisis, protect cash first. Assign senior people to the top 10 at-risk deals.
Start the Daily Cash Standup (Monday of Week 2): 15 minutes. Every day. CRO, VP Sales, VP CS, RevOps. One line per deal: status, next action, owner, date. This is a war room. Run for 60 days.
Week 2-3: ROOT CAUSE. Six Stages of Check in FAST Mode
Reference: For full methodology, see revops-diagnostic skill. For maturity assessment after stabilization, see revops-four-capability-maturity-assessment.
Output: One-Page Root Cause Summary
Week 3-4: CONSTRAINT IDENTIFICATION
Reference: For full framework, see revops-four-capability-maturity-assessment.
Score each 1-2 (crisis mode; nuance comes later):
Constraint Unlock Logic:
The 30-60-90 Crisis Response Plan
Days 1-30: STABILIZE
Days 31-60: DIAGNOSE & FIX
Days 61-90: REBUILD
AI & Automation for Crisis Response (2026)
The efficiency gap: Manual crisis response (spreadsheets, daily calls, human analysis) is fast, but reactive. 2026 crisis response augments humans with AI for speed and pattern detection.
Real-Time Data Monitoring & Alerting
Replace daily manual forecast calculations with automated flagging:
- Streaming data pipelines: Supabase or similar warehouse ingests CRM changes in real-time. Fivetran syncs from Salesforce, HubSpot, finance systems continuously.
- Anomaly detection: ML model flags when forecast variance exceeds thresholds (e.g. 3+ deals slip in one day; deal values drop 20%+; win rate shifts >2 points).
- Slack alerts: War room receives notifications when anomalies trigger, not when humans remember to check.
- Outcome: Detect crises 3-5 days earlier than manual weekly reviews.
AI-Driven Root Cause Analysis
Instead of humans debating root cause for 2 weeks:
- Claude API integration: Feed war room data (deal activity, stage transitions, person changes, win-loss reasons, forecast variance trends) into Claude for structured root cause analysis.
- Pattern extraction: Claude identifies what changed (e.g. "discovery duration extended from 18 to 31 days in the last 6 weeks"; "win rate collapsed specifically on deals with no C-suite contact").
- Constraint mapping: Maps findings to Governance / Enablement / Revenue / Insight framework automatically.
- Outcome: Root cause analysis moves from "opinions" to "data-driven facts" in 1 week instead of 2-3.
Predictive Health Scoring
Forecast deal health before it fails:
- Model inputs: Deal age, stage duration, activity cadence, champion engagement, competitive signals, budget confirmation status.
- Real-time scoring: Every deal in pipeline scored continuously. War room sees Red (high risk), Yellow (watch), Green.
- Automate actions: CRM workflow triggers outreach when deals fall to Red; escalates to rep manager if no response in 24 hours.
- Outcome: Identify at-risk deals on Day 1 of risk, not Day 20.
War Room Tech Stack (2026)
Minimum stack for crisis war room:
- Real-time dashboard: Supabase-backed analytics (Metabase or Superset) showing live pipeline coverage, forecast variance, deal health scores, top 20 deals by status. Refresh every 15 minutes, not daily.
- Slack as command center: War room receives alerts from data pipelines. Decisions logged as Slack threads (timestamped, searchable, shared context).
- Shared CRM view: Large screen or shared tab showing live Salesforce/HubSpot pipeline for deal-level discussions.
- Action tracking: Asana, Linear, or simple spreadsheet for action items; automated reminders every 6 hours for overdue actions.
Avoid: Spreadsheet-only tracking. By Day 3, spreadsheets diverge from reality. Centralize data in warehouse; surface via dashboard.
Four Crisis-Specific Playbooks
A: THE FORECAST CRISIS . "Missed 3 quarters in a row"
B: THE PIPELINE CRISIS . "Coverage at 2.1x and falling"
This is the start of the file. Read the full SKILL.md on GitHub.
Security
- Security scanPassed, 100 of 100Pattern checks on the skill's files.
- Model reviewNot runA model review is scheduled for the next rescan.
Quality evaluation
- Task evaluationNot runNo evaluation yet. Run one in Skill Studio.
Source
- SKILL.md in the repositoryCheckingrevops-crisis/SKILL.md
Popularity
- 7-day trend score
- 0
Not refreshed yet.
Works with
Any agent vskill installs to: 56 targets in all. These 39 have a page on this site.
- Claude Code
- Cursor
- GitHub Copilot
- Windsurf
- Codex
- Gemini CLI
- Cline
- Amp
- Roo Code
- Goose
- Continue
- Kilo Code
- Junie
- Trae
- OpenHands
- Qwen Code
- AI Agent
- Tabnine Chat
- Sourcegraph Cody
- Amazon Q
- Firebase Genkit
- Sweep
- Devin
- Phind
- Mentat
- Claude Desktop
- Aider
- GPT Pilot
- Plandex
- bolt.new
- v0
- Replit Agent
- Anse
- TypingMind
- BetterChatGPT
- LibreChat
- Warp AI
- Pieces
- Fig AI
Embed badge
[](https://verified-skill.com/skills/neon-rutger/b2b-revops-skills/revops-crisis)