Financial Contingency Planning Three-Deep: Never Running Out of Options
In military planning, we have a doctrine called "three-deep planning"—for every critical operation, you develop three contingency plans: Plan B if Plan A fails, Plan C if Plan B fails, and Plan D if everything goes to hell.
When I was managing $33 billion in funding in Iraq, this wasn't academic theory. Supply chains failed. Security situations changed hourly. Political priorities shifted overnight. Currency volatility was constant. If you only had Plan A, you were perpetually in crisis mode.
The teams that succeeded weren't the ones with perfect execution of Plan A. They were the ones who never ran out of options—who had thought through branches and sequels, who had pre-positioned alternatives, who could pivot without panic because they'd already gamed out the contingencies.
Later, as CFO of the 341st Comptroller Squadron supporting nuclear ICBM operations, the same principle applied. When you're managing financial operations for systems that must maintain 24/7 readiness, you don't get to say "we ran out of options." You build depth into every critical financial process.
Now, working with growing businesses as a fractional CFO, I see companies operating with Plan A only. They have a budget, a forecast, a growth plan. And when reality deviates—when a major customer churns, when a key hire doesn't work out, when market conditions shift—they're reactive and scrambling because they never built contingency depth.
Three-deep financial planning isn't pessimism. It's operational readiness. And it's the difference between companies that navigate uncertainty with confidence and companies that get crushed by it.
What Three-Deep Planning Actually Means
This isn't about building three separate financial plans and maintaining them in parallel. That's impractical and wasteful. Three-deep planning is about identifying critical dependencies in your financial model and pre-planning responses if those dependencies fail.
The framework is simple:
Plan A: Expected Case — Your base plan built on reasonable assumptions about revenue, costs, market conditions, and execution capability. This is your budget, your forecast, your growth trajectory. It's what you're working toward and what you communicate externally.
Plan B: Primary Contingency — What happens if one major assumption breaks? Your top revenue source underperforms, your key product launch delays, your primary growth channel becomes more expensive than expected. You've identified the trigger conditions and pre-decided the response.
Plan C: Secondary Contingency — What happens if multiple assumptions break simultaneously or if Plan B doesn't stabilize the situation? This is deeper retrenchment, more significant pivots, mobilization of reserves. You're no longer optimizing for growth—you're prioritizing survival and stabilization.
Plan D: Emergency Protocol — What happens if everything fails at once? This is your break-glass plan for existential threats. You've already identified what gets cut, who makes decisions, what the communication plan is, and what the minimum viable business looks like.
The value isn't in the specific plans—circumstances will always differ from what you anticipated. The value is in having thought through the decision trees before you're in crisis, having identified the levers you can pull, and having pre-positioned the capability to execute alternatives.
Identifying Your Critical Financial Dependencies
You can't build contingencies for everything—that's paralysis. Three-deep planning focuses on critical dependencies: the elements of your financial model that, if they fail, create material impact.
Start by asking:
Revenue dependencies:
What's your largest customer concentration? (If we lost our top customer, what happens?)
What's your primary revenue channel? (If this channel performance degrades 30%, what happens?)
What product/service drives majority of margin? (If demand shifts away from this, what happens?)
What seasonal patterns are we dependent on? (If peak season underperforms, what happens?)
Cost structure dependencies:
What's your largest fixed cost commitment? (Long-term leases, debt service, salaried headcount?)
What costs are most vulnerable to external factors? (Commodity inputs, regulatory compliance, labor market inflation?)
What operational leverage are we assuming? (If volume drops 25%, does our cost structure flex or stay fixed?)
Capability dependencies:
What critical roles are single-person dependencies? (If this person leaves, what breaks?)
What systems/platforms are we dependent on? (If this platform fails or prices increase 3x, what happens?)
What vendor/supplier relationships are critical? (If this vendor exits or becomes unreliable, what happens?)
Capital dependencies:
What's our cash runway at current burn? (If revenue stopped today, how long could we operate?)
What credit facilities are we dependent on? (If our line of credit gets reduced, what happens?)
What funding events are we planning around? (If the next capital raise delays 6 months, what happens?)
For each critical dependency, you're not trying to prevent failure—you're identifying what you'll do when it happens.
Building Plan B: Primary Contingencies
Plan B addresses single-point failures in your critical dependencies. The discipline is pre-decision: don't wait for the dependency to fail to figure out your response.
Here's how I work through this with fractional CFO clients:
Identify the trigger condition: What specific event or metric signals that Plan A is failing and Plan B needs to activate?
Example: "If monthly revenue drops below $X for two consecutive months" or "If customer concentration with Client Y exceeds 40% of total revenue" or "If our primary sales channel CAC increases above $Y."
The trigger should be specific and measurable. Vague triggers ("if things get bad") don't help. Precise triggers allow you to detect problems early and respond decisively.
Define the response actions: What specific actions do you take when the trigger hits?
Example trigger: "Monthly revenue drops below $400K for two consecutive months"
Plan B response:
- Freeze all non-essential hiring (saves $15K/month)
- Reduce discretionary marketing spend by 30% (saves $8K/month)
- Extend payment terms with flexible vendors to 45 days (improves cash flow timing)
- Activate backup revenue channels (outbound sales, partnership deals we've scoped but not executed)
- Communicate revised targets to team with transparent context
Notice these aren't panic moves. They're pre-planned adjustments that reduce burn, extend runway, and activate alternative growth paths. You're not cutting to the bone—you're trimming discretionary spending while maintaining core operations.
Pre-position the capability: Don't just document what you'd do—make sure you can actually do it when needed.
If Plan B includes "activate backup revenue channels," have those channels scoped and relationships established. If it includes "extend vendor terms," have those conversations before you're desperate. If it includes "reduce specific cost categories," make sure you're not locked into contracts that prevent flexibility.
In Iraq, we pre-positioned contingency funding authorities, alternate vendors, and backup logistics routes before we needed them. When primary plans failed (and they did, regularly), we didn't scramble—we executed pre-planned alternatives.
Building Plan C: Secondary Contingencies
Plan C addresses either multiple simultaneous failures or the failure of Plan B to stabilize the situation. This is deeper retrenchment focused on survival and capital preservation.
The trigger for Plan C is typically: "Plan B has been active for X period (60-90 days) without stabilizing trajectory" or "Multiple critical dependencies have failed simultaneously."
Plan C responses are more aggressive:
Significant cost restructuring:
- Reduce headcount to minimum viable team (pre-identify what "minimum viable" means)
- Exit or renegotiate major contracts (office leases, service agreements, SaaS platforms)
- Cut or pause all growth investment (focus shifts from growth to survival)
- Reduce founder/executive compensation (leadership shares the pain)
Business model pivot:
- Shift from growth mode to profitability mode (different operational priorities)
- Exit underperforming product lines or markets (concentrate resources on what works)
- Change pricing models or customer segments (pursue faster cash conversion)
Capital mobilization:
- Draw down strategic reserves (the reason you built them)
- Activate credit lines or alternative financing (pre-arranged, not scrambling)
- Pursue strategic capital from existing investors or partners (from position of planned action, not desperation)
- Consider asset sales or strategic partnerships
Plan C is not comfortable. But having it pre-planned means you're executing a strategy, not flailing in crisis.
Building Plan D: Emergency Protocols
Plan D is your break-glass protocol for existential threats: major customer bankruptcy, catastrophic market collapse, critical regulatory change, competitive disruption, or any scenario where the business as currently configured is no longer viable.
Most businesses never build Plan D because it's psychologically uncomfortable to contemplate total failure. But that's exactly why you need it—when you're in existential crisis, clear thinking is hardest. Pre-decision is what saves you.
Plan D should document:
Minimum viable business definition: What's the smallest configuration of the business that's still worth operating? What revenue level, what cost structure, what team size, what customer base?
Rapid wind-down sequence: If we determine the business isn't viable, what's the orderly shutdown process? What gets communicated to whom, in what order? How do we protect employee interests, customer commitments, and vendor relationships while minimizing legal and financial exposure?
Asset preservation and deployment: What assets have value that could be sold, licensed, or redeployed? Customer lists, IP, technology platforms, brand assets, physical equipment?
Decision authority: Who makes the call to activate Plan D, and what's the decision process? This shouldn't be unilateral panic—it should be defined governance (board vote, ownership consensus, specific triggers).
You may never use Plan D. I hope you don't. But having it means that if the worst happens, you have a map. And maps matter most when you're in unfamiliar territory.
The Three-Deep Review Cadence
Building contingency plans once and filing them away is useless. Business conditions change. Dependencies shift. Plans become obsolete.
Implement a quarterly three-deep review:
Q1 Review (15-30 minutes):
- Are our critical dependencies still the same, or have new ones emerged?
- Are our trigger conditions still relevant, or do they need adjustment?
- Have we taken actions that reduce contingency optionality (e.g., locked into long-term contracts, increased fixed costs beyond what contingencies can handle)?
Q2 Review (deeper, 60-90 minutes):
- War-game one scenario: pick a critical dependency and actually walk through Plan B and Plan C activation. What works? What doesn't? What have we not thought through?
- Update response actions based on current cost structure, team composition, and market conditions
- Validate that pre-positioned capabilities still exist (vendors haven't changed, credit lines still available, relationships still active)
Annual Deep Review:
- Complete refresh of three-deep framework
- War-game multiple scenarios with leadership team
- Update all documentation
- Ensure new team members understand the framework
This isn't bureaucratic planning theater. It's operational readiness maintenance. Your contingency plans are like emergency equipment—they only work if you maintain them.
When to Activate Contingency Plans
The hardest leadership decision is when to pull the trigger on contingency activation. Pull too early, and you're cutting unnecessarily. Pull too late, and options have already evaporated.
The military trains us to use defined trigger conditions precisely because human psychology resists action until crisis is undeniable—by which point you've lost optionality.
Disciplines for contingency activation:
Respect your triggers: If you defined specific metrics or conditions that activate Plan B, honor them. Don't override your triggers with optimism or hope. You set those thresholds for a reason when you were thinking clearly. Trust past-you.
Bias toward early activation: It's easier to scale back up from Plan B than to try activating it from a position of crisis. If you're debating whether conditions warrant Plan B, that's usually a signal to activate it.
Communicate transparently: When you activate contingency plans, explain why to your team. "We're not in crisis, but we're seeing these specific indicators that tell us we should shift to our contingency mode. Here's what that means, here's what we're doing, and here's how we'll know when to adjust again."
Transparency builds trust. Mystery breeds panic.
Monitor for plan effectiveness: Set review points after activating contingency plans. Plan B should stabilize trajectory within 60-90 days. If it's not working, don't wait—move to Plan C. Holding onto a failing plan is how you run out of runway.
Three-Deep Planning as Competitive Advantage
Here's what most people miss about contingency planning: it's not just defensive, it's offensive.
Companies without contingency depth make reactive decisions under pressure. They cut the wrong things because they haven't thought through what's essential. They miss opportunities because they're in survival mode. They lose talent because changes feel chaotic rather than strategic.
Companies with three-deep planning make confident decisions quickly. When market conditions shift, they're not figuring out what to do—they're executing pre-planned responses. That speed and confidence is competitive advantage.
In Iraq, the units that succeeded weren't the ones with the best Plan A. They were the ones who could pivot to Plan B or C without losing momentum, because they'd already thought through the branches.
In business, the same dynamic applies. Market downturns create opportunities for companies with contingency depth. While competitors are panicking and cutting blindly, you're executing strategic adjustments. While they're losing talent through chaotic layoffs, you're making thoughtful reductions with severance and dignity. While they're desperately seeking capital from position of weakness, you're selectively deploying reserves or accessing pre-arranged facilities.
The market rewards companies that can navigate uncertainty without panic. Three-deep planning is how you build that capability.
Start Building Your Contingency Depth Today
Don't wait for crisis to think about contingencies. Don't wait for Plan A to fail before developing Plan B. The time to build three-deep planning is when you don't need it—because by the time you need it, it's too late to build it.
Start simple:
This week: Identify your top 3 critical financial dependencies
This month: Define trigger conditions and Plan B responses for your #1 dependency
This quarter: Build out full three-deep framework for all critical dependencies
Ongoing: Quarterly reviews and annual deep updates
This isn't a one-time project. It's an operational discipline. And like all disciplines, it compounds over time.
The first time you face a major disruption and respond with a pre-planned contingency instead of panic, you'll understand the value. Your team will see leadership under pressure. Your investors will see professional risk management. You'll see that you still have options when others are running out.
That's the power of three-deep planning. Not preventing problems—problems are inevitable. But ensuring you never run out of moves.
Because in combat and in business, the side that runs out of options first loses. Build your depth now, and you'll never be that side.
Gabriel Denny Financial Services, LLC