revops-crisis

Run a four-week emergency revenue operations triage protocol for simultaneous forecast, pipeline, retention, and data failures.

40|18|Updated Apr 2, 2026
One-click install
npx skills add https://github.com/NEON-Rutger/B2B-revops-skills --skill revops-crisis
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: revops-crisis
Source: https://github.com/NEON-Rutger/B2B-revops-skills/tree/main/revops-crisis
Command: npx skills add https://github.com/NEON-Rutger/B2B-revops-skills --skill revops-crisis

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

RevOps crisis triage helps you recover when multiple revenue system layers fail at once and you can no longer trust forecasting, pipeline, retention, or the underlying data.

Core Features & Use Cases

  • Crisis recognition & trigger thresholds: Detect crisis mode using clear signals like forecast variance, win-rate drop, pipeline coverage falling below 3x, NRR below 90%, data incompleteness, and cross-functional trust collapse.
  • Emergency triage protocol (4 weeks): Run a speed-first stabilization sequence that starts with a data audit, then immediate cash risk diagnosis, then fast root-cause checks, and finally constraint identification for the next unlock.
  • Crisis-specific playbooks: Execute targeted procedures for forecast misses, pipeline coverage collapse, churn/NRR crashes, and trust breakdown across sales, marketing, CS, and product.
  • Operational war-room cadence: Establish a daily standup and leadership action loop to stop chaos propagation and drive measurable progress.

Use cases include “everything is broken,” “forecast is ±30% wrong,” “pipeline coverage at 2.1x and falling,” “NRR crashed below 90%,” or “I can’t trust our data—where do we even start?”

Quick Start

Tell the AI: “We’re in a revops crisis and multiple systems are failing—run revops-crisis to stabilize us this quarter.”

Frequently Asked Questions about revops-crisis

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I stabilize revenue operations when forecasting, pipeline, and retention fail at the same time?

Stabilize revenue operations by executing a four-week emergency triage protocol: run a data audit, diagnose immediate cash risk, perform fast root-cause checks, and identify constraints to halt multi-system failures.

What triggers a revenue operations crisis that requires emergency triage?

Revenue operations crisis triggers include forecast variance, win-rate collapse, pipeline coverage falling below 3x, NRR dropping below 90%, critical CRM field incompleteness, and cross-functional trust breakdown.

How do I fix pipeline coverage collapse when it drops below 3x?

Fix pipeline coverage collapse by deploying crisis-specific playbooks alongside a daily war-room standup cadence to stop chaos propagation, identify root causes, and drive measurable pipeline recovery progress.

What is the best way to diagnose NRR crashing below 90% during a RevOps crisis?

Diagnose NRR crashes by applying the emergency triage protocol's fast root-cause checks alongside targeted churn and retention playbooks to identify systemic retention failures and stabilize net revenue retention.

Can I use a war-room cadence to fix cross-functional trust breakdowns in sales and marketing?

Use a war-room cadence to fix cross-functional trust breakdowns by establishing a daily leadership action loop that aligns sales, marketing, CS, and product teams to restore data integrity and drive measurable progress.