What-If Scenarios: How to Model Business Decisions Before Committing

What Scenario Planning Actually Does

Scenario planning is not forecasting the future perfectly.

It is stress-testing decisions against plausible outcomes so you can avoid preventable downside.

For freelancers, this means answering questions like:

• if I hire a subcontractor, how many weeks of runway do I lose?
• if my largest client churns, how quickly does cash get critical?
• if I raise rates by 10%, how sensitive is pipeline conversion?

You are not looking for certainty. You are looking for decision safety.

The Minimum Model You Need

You do not need a complicated spreadsheet with 40 tabs.

You need one model with six moving parts:

1. baseline monthly revenue 2. baseline monthly operating costs 3. variable costs linked to delivery 4. tax/VAT/social contribution assumptions 5. opening cash and reserve balances 6. payment timing (invoice-to-cash lag)

If these six are maintained, scenario planning becomes operational, not academic.

For the underlying cash structure, use the same approach as [Cash Flow Management for Belgian Freelancers](/en/news/belgian-freelancer-cash-flow-calendar-2026).

Core Assumptions To Define Before Testing

### Assumption 1: Time Horizon

Use 3 months for tactical decisions and 12 months for structural decisions.

• 3-month horizon: hiring timing, short-term spending, bridge decisions
• 12-month horizon: pricing strategy, service mix, major tooling shifts

### Assumption 2: Confidence Ranges

Do not model single values only. Use ranges:

• likely
• optimistic
• downside

A single-point model creates false confidence.

### Assumption 3: Payment Reality

Use realistic payment lag, not contract terms.

If terms are 30 days but average actual payment is 47 days, model 47 days.

### Assumption 4: Buffer Policy

Define minimum acceptable runway before running scenarios. Example: "I never let projected runway drop below 12 weeks."

This turns scenario outputs into clear go/no-go decisions.

Five High-Impact Scenarios To Run

### Scenario 1: Hiring a Subcontractor

Question: "Can I hire without putting the business at risk?"

Model inputs:

• monthly subcontractor cost
• expected billable capacity uplift
• expected utilization (not 100%)
• margin after subcontractor cost

Decision checks:

• break-even month
• worst-case runway impact
• downside if utilization is 50% of plan

If downside runway breaches your threshold, delay hiring or stage the contract.

### Scenario 2: Buying Equipment or Software Stack Upgrades

Question: "Should I buy now, lease, or delay?"

Model inputs:

• upfront spend or monthly payment schedule
• expected productivity uplift
• payback period
• impact on reserve balances

Decision checks:

• runway under downside revenue
• payback period under realistic assumptions
• effect on tax and contribution accrual planning

### Scenario 3: Losing Your Biggest Client

Question: "How fragile is my revenue concentration?"

Model inputs:

• revenue share of top client
• replacement lead time (in months)
• cost reduction options and timing

Decision checks:

• weeks until minimum cash threshold is hit
• immediate cost actions required
• target pipeline volume needed to recover

Every freelancer should run this scenario at least once per quarter.

### Scenario 4: Pricing Change

Question: "If I raise rates, what happens to margin and conversion?"

Model inputs:

• new rate options (+5%, +10%, +15%)
• expected conversion sensitivity per option
• project mix and sales cycle timing

Decision checks:

• gross margin improvement by option
• downside case if win rate drops more than expected
• net monthly cash impact after 3 months

Without this test, pricing changes become emotional decisions.

### Scenario 5: Tax and Social Contribution Shock

Question: "Can I absorb a higher-than-expected obligation?"

Model inputs:

• expected vs stress-level social contribution and tax outflows
• reserve coverage at current month-end
• shortfall amount and bridge timeline

Decision checks:

• reserve sufficiency under stress
• minimum invoice collection required to avoid crunch
• cost pause options if reserves are short

How To Interpret Outputs and Decide

A scenario model is useful only if outputs drive action.

Track these four outputs for every scenario:

1. Runway impact: how many weeks gained/lost versus baseline.
2. Break-even timeline: when the decision pays back.
3. Downside survivability: can you survive the stress case without emergency debt?
4. Execution complexity: how hard is implementation operationally?

Then apply a decision rule:

• proceed if likely and downside cases both stay above your minimum buffer
• proceed with constraints if likely is strong but downside is fragile
• defer if downside is unacceptable and mitigations are weak

This keeps decisions data-led.

A Practical Scenario Scoring Template

Use a simple scorecard before committing:

| Dimension | Weight | Score (1-5) | Weighted score | |---|---:|---:|---:| | Runway impact | 35% | | | | Margin impact | 25% | | | | Downside survivability | 25% | | | | Implementation complexity | 15% | | |

Define a minimum weighted score to execute (for example 3.5/5).

You can customize the weights, but keep them stable for comparability across decisions.

Common Scenario Planning Mistakes

### Mistake 1: Modeling Revenue as Certain

Pipeline is not booked cash. Use probability and timing assumptions.

### Mistake 2: Ignoring Payment Delays

Profitability and liquidity are not the same. Cash timing is the difference.

### Mistake 3: Forgetting Compliance Outflows

VAT and social contributions are not optional line items.

### Mistake 4: Updating the Model Too Late

A model updated only during stress is a report, not a decision tool.

### Mistake 5: Running One Scenario Once

Scenario planning is a repeatable operating system, not a one-time spreadsheet exercise.

A Monthly Scenario Rhythm

### Week 1: Refresh Baseline

• update trailing actuals
• refresh payment lag and reserve balances
• validate core assumptions

### Week 2: Run One Strategic Scenario

Pick one current decision and run likely/optimistic/downside outcomes.

### Week 3: Commit and Monitor

Choose an action and define leading indicators (runway, conversion, margin).

### Week 4: Review Variance

Compare projected vs actual outcomes and improve assumptions for the next cycle.

This 4-week rhythm makes scenario planning light enough to sustain.

Worked Example: "Can I Hire a Part-Time Subcontractor?"

Assume:

• opening cash: EUR 28,000
• baseline monthly inflow: EUR 9,000
• baseline monthly outflow: EUR 6,500
• proposed subcontractor cost: EUR 2,200/month
• expected incremental billed work: EUR 3,000/month at full utilization

Now stress utilization:

• likely: 75% utilization
• downside: 45% utilization

Output:

• likely case remains cash-positive with reduced buffer
• downside case pushes runway close to minimum threshold in month 3

Decision:

• proceed only with staged contract and explicit stop conditions
• re-evaluate after first 8 weeks

The model does not say "never hire." It says "hire with guardrails."

FAQ

### Is scenario planning only for larger businesses?

No. Freelancers benefit most because one decision can materially change their runway.

### How often should I run scenarios?

At minimum monthly, and always before major financial commitments.

### Do I need advanced finance skills to do this?

No. A simple structured model beats intuition-only decisions.

### What is the best first scenario to run?

Run the "loss of biggest client" scenario first. It reveals concentration risk quickly.

### Should I model taxes and social contributions even if uncertain?

Yes. Use ranges and stress assumptions. Ignoring uncertain outflows is riskier than estimating them.

Final Take

Scenario planning is the difference between reacting to surprises and designing outcomes.

Before any major hire, purchase, or pricing move, run the model. If the downside breaks your cash buffer, redesign the decision.

You do not need perfect predictions. You need disciplined pre-commitment checks.