war-room-setup-operations-guide.md
War Room Setup & Operations Guide
For: B2B scale-ups €15M–150M ARR
Operational checklist for activating and running an effective crisis war room.
WAR ROOM TRIGGER CRITERIA
Activate war room when:
- Pipeline coverage drops below 2x coverage (Q at risk)
- Forecast miss detected mid-quarter (>10% gap to guidance)
- Revenue-critical system fails (CRM outage, forecasting system down)
- Major customer churn event (>€250k/mo at risk)
- Rep attrition crisis (>3 reps departing in 30 days)
- Board-level notification required
Do NOT activate if:
- Single deal is lost (handle in regular weekly forecast)
- Routine month-end reconciliation issues
- Low-impact data quality issue (<€50k affected)
PHYSICAL/VIRTUAL WAR ROOM SETUP
Core Team (Non-Negotiable)
- CRO or VP Sales — Decision authority; crisis owner
- RevOps Lead — Data, analytics, reporting
- Finance/CFO — Revenue verification, board communication
- Sales Manager(s) — Territory intel, rep support
- Marketing Lead (if pipeline-driven) — Demand gen support options
Extended Team (Add as Needed)
- Product Lead (if churn/data crisis) — Customer needs, roadmap
- CS Lead (if churn crisis) — Customer health, retention strategies
- IT/Systems Admin (if data/system crisis) — Data integrity, backups
- CEO (if forecast miss) — Board strategy, capital decisions
Physical War Room Setup
- Location: Dedicated space with large displays, whiteboard
- Duration: 1–2 week daily standups; then 3x weekly
- Technology:
- Laptop/desktop per core team member
- Large screen(s) showing live dashboards
- Whiteboard for playbook tracking
- Phone/video for remote participants
- Shared spreadsheet accessible to all (live deal tracker)
Virtual War Room Setup (If Remote)
- Dedicated Slack channel: #crisis-warroom-[crisis-type]
- Daily standup: Scheduled same time daily (e.g., 8 AM CET)
- Shared documents: Google Sheet with live deal pipeline tracker, metrics dashboard
- Video: 30 min daily standup, cameras on
- Tools: CRM open on shared screen; live metric updates
- Async updates: Slack thread with 6 PM CET end-of-day update
DAILY STANDUP STRUCTURE
Duration: 15 minutes (strict)
Attendees: Core team only; optional observers on mute
Agenda (Fixed Order):
- Metric update (2 min): Pipeline coverage | Pipeline value | Forecast variance | Churn status
- Green/yellow/red status for each metric
- Deal updates (5 min): Top 10 deals by revenue impact
- Status change since yesterday? Probability shift?
- Anything blocking that war room can unblock?
- Action items (5 min): What changed since yesterday?
- Who owns what by EOD today?
- Any escalations needed?
- Wins to celebrate?
- Forecast revision (2 min): New forecast based on last 24 hours
- Did we move the needle?
Standup artifacts:
- One-page metric snapshot (emailed 6 PM previous day)
- Deal tracker updated by 8 AM before standup
- Action item log tracked in Slack/spreadsheet
Discipline rules:
- Start and end on time
- No long discussions (take to side conversation)
- Decisions made by CRO in real-time; no "let me check and get back"
- Decision log updated immediately (Slack thread)
METRICS TO TRACK DURING CRISIS
Hourly (First 48 Hours)
- Pipeline coverage: Current vs. 2x benchmark
- Top 20 deal status: Green/yellow/red per deal
- Forecast variance: Current forecast vs. guidance
- Blockers identified: Number of deals stuck; by reason
Daily (Weeks 1–2)
- Pipeline coverage: Movement toward 2x
- New pipeline generated: Outbound meetings set, partner pipeline activated
- Deal acceleration: Deals moved up in timeline
- Forecast confidence: Forecast variance to guidance
- Action item completion: % of previous day's actions done
- Churn rate (if churn crisis): New churns identified; save plays activated
Weekly (Weeks 2+)
- Pipeline recovery trajectory: On track to 2x by target date?
- Demand gen output: Inbound meetings scheduled; quality
- Rep activity: Calls, meetings, proposals by rep (if attrition)
- Customer retention: Save play outcomes; win-back results
- Board narrative: What we'll tell CEO/board this week
Dashboard Display
- War room screen: Live Salesforce/reporting dashboard
- Pipeline coverage chart
- Top 50 deals with status, probability, value, close date
- Forecast variance to goal
- Weekly inbound meeting count
- Physical board (if in-person): Playbook checklist with checkmarks
- Week 1: [ ] Deal acceleration [ ] Outbound blitz [ ] Partner activation
- Week 2: [ ] Demand gen running [ ] Rep support [ ] Rep hiring started
ESCALATION PATHS
Daily Escalation (During Standup)
- CRO makes decision on: Deal-level authority, rep compensation, pricing discounts
- CFO decides: Forecast disclosure, revenue recognition, contingency planning
- Marketing lead decides: Ad spend increase, campaign timing
CEO Escalation (When to Involve)
- Forecast miss (>5% of annual guidance): Brief CEO immediately; daily updates
- Major customer churn (>€500k): Executive-level save play required
- Board notification required: CEO + CFO decide timing and disclosure
- System/data crisis (data integrity loss): CEO briefed same day; stakeholder comms
Board Escalation (When to Notify)
- Missed guidance: CFO notifies board chair; structured update in next call
- Forecast revision (>10% down): Included in next earnings call or special notice
- Timeline: If crisis detected mid-month, notify board by week 1 if miss likely
External Escalation
- Investor/board relations: CFO leads; RevOps provides data
- Customer communication: CEO/CRO determines if board-level customers need heads-up
- Financing impact: CFO assesses if revenue miss triggers covenant questions
CRISIS WAR ROOM EXIT CRITERIA
War room transitions to "watch mode" when:
- Pipeline coverage recovers to 2x+ (sustained for 3 days)
- Forecast variance closes to <5% of goal
- All Tier 1 deals have clear status (closed, delayed to next quarter)
- Daily standup no longer needed (shift to 3x weekly, then weekly)
War room is formally closed when:
- Full month of normalized operations without crisis triggers
- All playbook actions completed or embedded into normal process
- Post-crisis retrospective completed and shared
POST-CRISIS RETROSPECTIVE TEMPLATE
Date: [Date war room closed] Crisis type: [Pipeline / Forecast / Churn / Rep attrition / Data] Duration: [X days active] Revenue impact prevented/recovered: [€XXX]
What We Did Right
- Quick escalation and war room activation
- Clear decision-making authority
- Transparent communication (team + board)
- [Add specific wins]
What We Didn't Anticipate
- [Root cause #1]: We should have seen this because...
- [Root cause #2]: Early warning system needed for...
Process Changes to Prevent Recurrence
- [Change #1]: Implement [control] by [date] → [owner]
- [Change #2]: Modify [process] to [new approach] → [owner]
- [Change #3]: Add [metric/dashboard] to early warning system → [owner]
Process Changes Already Made
- [What changed during crisis that we'll keep]
- [New metric or dashboard we'll maintain]
- [Communication cadence or process improvement]
Team Feedback
- What helped most: [Quote from team member]
- What was hardest: [Challenge during crisis]
- What we'd do differently: [Improvement for next time]
Knowledge Capture
- Playbook refinement: [Updates to crisis playbook based on actual experience]
- Tools/processes to keep: [Anything new that worked well]
- Training needed: [What would help team prepare for next crisis]
Retrospective facilitator: [RevOps lead] Date completed: [Date] Shared with: [CEO, CFO, leadership team]
Last updated: 2026