Crisis War Room

Crisis War Room

The startup crisis command center. Not theory — executable battle-tested protocols for the 14 crisis types that kill startups. Every protocol has severity scoring, escalation triggers, communication templates, and recovery playbooks.

Keywords

crisis, emergency, fire, disaster, failing, dying, shutdown, wind down, pivot, runway, burn rate, cash crisis, co-founder conflict, co-founder breakup, PR disaster, reputation, data breach, security incident, layoff, RIF, workforce reduction, down round, churn spike, customer loss, regulatory action, legal threat, lawsuit, product failure, outage, recall, key person risk, bus factor, investor conflict, board crisis, market crash, competition threat, acqui-hire, zombie startup, bridge to nowhere, death spiral, turnaround, restructuring, insolvency, bankruptcy, dissolution, India, NCLT, MCA, SEBI, RBI, GST notice, labor dispute

How to Use This Skill

This skill operates in 5 modes based on crisis urgency:

Chain with existing skills:

• fundraising-command-center for cash crisis → emergency fundraising
• legal-ip-fortress for legal/regulatory crises
• founder-resilience for founder mental health during crisis
• talent-os for layoff/team crisis management
• governance-compliance-shield for board/regulatory crisis
• india-business-law for India regulatory crises

1. Crisis Classification Matrix

The 14 Crisis Types That Kill Startups

Severity Scoring (1-10)

Score 1-3: WATCH — Monitor, no immediate action
Score 4-5: YELLOW — Proactive mitigation needed
Score 6-7: ORANGE — Active management, weekly war room
Score 8-9: RED — Daily war room, all-hands response
Score 10: BLACK — Existential, 72-hour decision cycle

Crisis Severity Calculator

Assess each factor (1-5), multiply by weight:

Total Score = Weighted average × 2 (to get 1-10 scale)

2. Cash Crisis Protocol (The #1 Killer)

Runway Assessment Matrix

72-Hour Cash Crisis Protocol

Hour 0-24: TRIAGE

1. Freeze all non-essential spending immediately
2. Calculate exact cash position (bank balance, AR, AP, committed expenses)
3. Map every dollar of burn: fixed vs variable, essential vs discretionary
4. Identify immediate cuts (unused SaaS, office perks, contractor spend)
5. Call your attorney — understand fiduciary duties when approaching insolvency

Hour 24-48: COMMUNICATE

1. Inform co-founders and board (no surprises)
2. Draft 3 scenarios: survive, bridge, wind-down
3. Identify emergency funding sources (existing investors, revenue acceleration, debt)
4. Prepare bridge round terms (be ready to offer steep discount)

Hour 48-72: EXECUTE

1. Launch emergency fundraise or bridge conversation
2. Implement immediate cost reductions
3. Negotiate payment extensions with vendors (most will work with you)
4. Accelerate AR collection (offer discounts for early payment)
5. Evaluate asset sales, acqui-hire, or wind-down

Runway Extension Tactics (Ranked by Speed)

Burn Multiple Emergency Thresholds

3. Co-Founder Conflict Resolution

Conflict Severity Assessment

Resolution Framework

Level 1-2 Protocol:

1. Schedule dedicated "co-founder time" (weekly, no agenda pressure)
2. Establish decision rights matrix (who owns which domains)
3. Create escalation process (disagree → discuss → data → decide → commit)
4. Implement "disagree and commit" culture
5. Consider executive coach or YC-style group office hours

Level 3-4 Protocol:

1. Engage neutral third-party mediator (not a friend, not an investor)
2. Review operating agreement and shareholder terms
3. Document all agreements in writing
4. Define clear separation scenario and terms
5. Protect the company: ensure IP assignment, non-compete, vesting acceleration terms are clear

Level 5 Protocol — The Buyout

1. Determine fair value (409A or agreed formula)
2. Structure: cash buyout, accelerated vesting reversal, or equity swap
3. Negotiate transition period (typically 30-90 days)
4. Handle equity: unvested shares return to pool, vested shares may be repurchased
5. Communication plan: team, investors, customers (in that order)
6. Non-disparagement and confidentiality agreements

Vesting as Crisis Prevention

• Standard: 4-year vest, 1-year cliff
• Co-founder departure before cliff = all shares returned to company
• Post-cliff departure = unvested shares returned
• Acceleration clauses: single trigger vs double trigger (negotiate upfront)
• Reverse vesting for founders who already own shares

4. Product-Market Fit Loss Protocol

PMF Health Dashboard

PMF Recovery Protocol

Phase 1: Diagnose (Week 1-2)

1. Churn analysis: interview every churned customer from last 90 days
2. Cohort analysis: which customer segments retain vs churn?
3. Usage analytics: where do users drop off?
4. Competitive analysis: did something change in the market?
5. Win/loss analysis: why are deals being lost?

Phase 2: Hypothesis (Week 2-3)

1. Identify top 3 hypotheses for PMF loss
2. Score each by impact potential and speed to test
3. Design minimum viable tests for each
4. Set kill criteria: what result means the hypothesis is wrong?

Phase 3: Rapid Iteration (Week 3-8)

1. Run experiments in 1-2 week sprints
2. Measure leading indicators (not lagging)
3. Kill experiments that don't show signal by week 2
4. Double down on what works
5. Be willing to pivot ICP, pricing, or core product

Phase 4: Pivot Decision

Is the core value proposition validated?
├── Yes → Iterate on delivery/UX/GTM
└── No →
    ├── Can you find a new ICP for existing product?
    │   ├── Yes → Pivot market (cheapest pivot)
    │   └── No →
    │       ├── Can you solve a different problem for same ICP?
    │       │   ├── Yes → Pivot product
    │       │   └── No → Full pivot or wind down
    └── Is there enough runway for a pivot?
        ├── Yes (>6 months) → Execute pivot
        └── No → Bridge raise or wind down

5. Data Breach / Security Crisis Protocol

Incident Severity Classification

P0 Breach Protocol (First 72 Hours)

Hour 0-1: CONTAIN

1. Isolate affected systems (pull from network, don't shut down — preserve forensics)
2. Revoke compromised credentials immediately
3. Activate incident response team (CTO, legal, CEO minimum)
4. Begin forensic logging — document everything from this moment

Hour 1-4: ASSESS

1. Determine scope: what data, how many records, what systems
2. Engage forensics firm (have one on retainer or know who to call)
3. Determine regulatory obligations (GDPR: 72-hour notification, state laws vary)
4. Draft initial stakeholder communication

Hour 4-24: NOTIFY

1. Legal counsel first (attorney-client privilege protects investigation)
2. Board/investors
3. Affected customers (per legal requirements)
4. Regulators (GDPR DPA, state AGs, SEC if public)
5. Law enforcement (FBI IC3 if significant)

Hour 24-72: REMEDIATE

1. Patch the vulnerability
2. Enhanced monitoring on all systems
3. Customer support war room (dedicated breach response team)
4. Credit monitoring/identity protection for affected users
5. Public communication (be transparent, specific, and apologetic)

India-Specific Data Breach Obligations

• CERT-In: Report to CERT-In within 6 hours of discovery (mandatory since 2022)
• DPDP Act 2023: Notify Data Protection Board and affected individuals "without delay"
• RBI: Financial data breaches require RBI notification
• SEBI: Listed company material breaches require stock exchange disclosure
• Penalties: Up to INR 250 crore per breach under DPDP Act

6. PR / Reputation Crisis Protocol

Crisis Communication Framework (SCARF)

Communication Templates

Holding Statement (Hour 1-4): "We are aware of [situation]. We are actively investigating and will provide a full update within [timeframe]. [Immediate actions taken]. The safety/security of our [customers/users/team] is our top priority."

Full Response (Hour 4-24):

1. What happened (factual, specific)
2. Who is affected
3. What we've done immediately
4. What we're doing to prevent recurrence
5. How affected parties can get help
6. Named executive taking responsibility

Platform-Specific Playbooks

7. Regulatory/Legal Crisis Protocol

Response Tiers

Document Preservation (Litigation Hold)

When ANY legal action is threatened or filed:

1. Issue litigation hold notice to ALL employees immediately
2. Suspend auto-deletion policies (emails, Slack, logs)
3. Preserve all relevant documents, communications, and data
4. Engage e-discovery vendor if data volume is large
5. Failure to preserve = spoliation sanctions (can be case-ending)

India Regulatory Crisis Specifics

8. Layoff / Workforce Reduction Protocol

Decision Framework

Is layoff truly necessary?
├── Tried salary cuts (founders first)?
├── Tried voluntary separation packages?
├── Tried reduced hours / furloughs?
├── Tried contractor/vendor cuts first?
└── If yes to all above → Proceed with layoff planning

Execution Playbook

Week -2 to -1: PLAN

1. Determine exact headcount reduction needed (cut deep once, never twice)
2. Select affected roles based on business needs, NOT performance alone
3. Legal review: WARN Act (100+ employees), state mini-WARN acts
4. Calculate severance: 2-4 weeks per year of service (minimum)
5. Prepare separation agreements, COBRA info, reference letters
6. Brief managers who will deliver the news

Day of Layoff:

1. Schedule individual meetings (15-20 minutes each)
2. Manager + HR present (never via email or group call)
3. Be direct, compassionate, and brief: "Your position has been eliminated"
4. Provide packet: severance terms, benefits continuation, reference commitment
5. Allow dignity: immediate departure or brief goodbye (their choice)
6. IT: revoke access after meeting, not before

Day 1-7: AFTERMATH

1. All-hands meeting for remaining team (within 24 hours)
2. CEO speaks: why, what it means, path forward, no more cuts (if true)
3. Manager 1:1s with every remaining direct report (within 48 hours)
4. External communication: transparent, factual, respectful of departed
5. Offer outplacement support, alumni network, warm intros

India Layoff Compliance

• Industrial Disputes Act: Establishments with 100+ workers need government permission for layoffs
• Notice Period: As per employment contract (typically 1-3 months)
• Retrenchment Compensation: 15 days average pay × years of service
• Gratuity: Payable if >5 years service (Payment of Gratuity Act)
• PF/ESI: Final settlements must be processed
• Shop & Establishment Act: State-specific requirements
• IT/ITES Exemptions: Many states exempt IT companies from Industrial Disputes Act

9. Board/Investor Conflict Protocol

Conflict Types and Response

Protective Measures

• Maintain majority board control through Series B
• Ensure protective provisions require mutual agreement, not investor veto
• Keep detailed board minutes (they're legal documents)
• Build relationships with all board members individually
• Never surprise your board — they should know before the meeting

10. Graceful Shutdown Protocol

The Decision Matrix

Should you shut down?
├── Runway <3 months AND no funding path → Yes, plan shutdown
├── Runway <3 months AND active term sheet → Bridge, don't shut down yet
├── Team has lost conviction → Honest discussion, consider pivot or shutdown
├── Market has disappeared → Pivot or shutdown
├── Regulatory kill → Evaluate compliance path vs shutdown
└── All options exhausted → Graceful shutdown is the right and honorable choice

90-Day Shutdown Timeline

Month 1: DECIDE AND PLAN

• Week 1: Final board meeting — formal shutdown vote
• Week 1: Engage dissolution attorney
• Week 2: Notify investors (call each one personally)
• Week 2: Calculate final obligations (employees, vendors, taxes)
• Week 3-4: Notify employees with generous transition support

Month 2: EXECUTE

• Week 5: Customer notification and data migration support
• Week 6: Terminate vendor contracts (review termination clauses)
• Week 7: Process final payroll, severance, PF/gratuity settlements
• Week 8: Cancel subscriptions, domains, hosting (selectively — keep what has value)

Month 3: DISSOLVE

• Week 9: Final tax filings (federal, state, local)
• Week 10: Distribute remaining assets per liquidation waterfall
• Week 11: File dissolution documents with state/ROC
• Week 12: Close bank accounts, notify creditors, file final reports

Liquidation Waterfall (Standard Priority)

1. Secured creditors (banks with collateral)
2. Employee wages and benefits (super-priority in most jurisdictions)
3. Government (taxes owed)
4. Unsecured creditors (vendors, landlords)
5. Preferred shareholders (per liquidation preference in term sheet)
6. Common shareholders (founders, employees with exercised options)

India Shutdown Specifics

• Strike-Off (Section 248): For companies with no operations for 2+ years
• Voluntary Winding Up: Pass special resolution, appoint liquidator
• Fast Track Exit (FTE): For companies with nil assets/liabilities
• NCLT Route: For companies with creditor disputes
• ROC Filings: Form STK-2 for strike-off, multiple compliance forms
• Tax Clearance: Obtain tax clearance certificates before dissolution
• PF/ESI Closure: Deregister from EPFO and ESIC
• Timeline: Indian dissolution typically takes 6-24 months

11. Key Person Risk Mitigation

Bus Factor Assessment

Mitigation Protocol

1. Map dependencies: Who knows what? Who can only they do?
2. Forced vacation test: Key person takes 2 weeks off — what breaks?
3. Pair programming/shadowing: Every critical function has a backup
4. Documentation mandate: Runbooks for all critical systems and processes
5. Key person insurance: Consider for CEO/CTO (investors may require it)
6. Succession planning: Even at 10 people, know who steps up if someone leaves

12. Crisis Communication Templates

Investor Crisis Update (Template)

Subject: [Company] — Situation Update: [Brief Description]

[Investor Name],

I want to share a development that requires your attention.

SITUATION: [2-3 sentences — what happened, when, current status]
IMPACT: [Quantified — revenue, runway, customer, team impact]
ACTIONS TAKEN: [Bullet list of immediate responses]
PLAN FORWARD: [3-5 concrete next steps with timelines]
ASK: [Specific — intro, bridge capital, advice, nothing]

I'll provide an update on [date]. Happy to discuss anytime.

[Founder Name]

Team Crisis Communication (Template)

Team,

I need to share some difficult news with you directly and honestly.

[THE NEWS — direct, factual, no corporate speak]

HERE'S WHAT THIS MEANS:
- For the company: [impact]
- For you: [what changes, what doesn't]
- For our customers: [our commitment]

HERE'S WHAT WE'RE DOING:
1. [Action 1]
2. [Action 2]
3. [Action 3]

I know this raises questions. I'll hold an all-hands Q&A on [date/time].
My door/DM is open anytime before then.

[Founder Name]

13. Post-Crisis Recovery Framework

The RECOVER Model

Crisis Preparedness Checklist (Pre-Crisis)

• Emergency contacts list (attorney, PR firm, insurance, board members)
• Cash reserve: 2-3 months of burn in accessible account
• Key person documentation and cross-training
• Incident response plan (security, product, PR)
• Board-approved crisis communication policy
• D&O insurance current and adequate
• Key contracts have force majeure and termination clauses reviewed
• Quarterly tabletop exercise (pick a crisis type, simulate response)

Reference Files

For detailed crisis response templates and India-specific regulatory crisis guides, load:

• reference/crisis-response-templates.md — Communication templates for all 14 crisis types
• reference/india-regulatory-crisis.md — India-specific regulatory response protocols

Military Doctrine Layer

OODA Loop for Crisis Response

OBSERVE: What is actually happening? (facts, not rumors)
  → Assign 1 person to gather intel. 30-minute reporting cadence.
ORIENT: What does this mean for US specifically?
  → Does this threaten survival? Revenue? Reputation? Team?
DECIDE: Commit to ONE response action.
  → Reversible? Decide in <2 hours. Irreversible? 24-hour deliberation.
ACT: Execute. Set 48-hour checkpoint. Feed back into OBSERVE.
Key insight: Move faster than the crisis cycle.

Red Team Crisis Protocol

Before executing any major crisis response:
1. Assign 1-2 people to argue AGAINST the proposed response
2. Give them 30 minutes to build the strongest counter-case
3. Present counter-case BEFORE executing
4. Solo: List 5 assumptions. For each: "What if this is wrong?"

After Action Review (Post-Crisis)

Mandatory within 48 hours:
1. What was SUPPOSED to happen? (our crisis plan)
2. What ACTUALLY happened? (objective timeline)
3. WHY the gap? (root cause, not blame)
4. What will we CHANGE? (specific, assigned, time-bound)
Junior speaks first. No blame. Add to Learning Log.

Chaos Engineering for Business

Monthly "Chaos Day":
Scenarios: lose biggest customer, key engineer quits, 10x demand spike,
  primary vendor bankrupt, regulatory investigation, data breach
Team has 60 min to: assess impact → draft 72hr plan → identify weakness
"Fail deliberately in peace → survive accidentally in war"

Clausewitz Applied

Apollo 13 Problem-Solving Protocol

When crisis hits, don't focus on what's broken:

1. "What do we got that's good?" — inventory every working asset
2. Creative recombination — solve new problem with existing resources
3. One clear objective — communicate with zero ambiguity
4. Cross-functional sprint — everyone on the same problem
5. Constrained innovation — best solutions emerge under real constraints