Scenario planning for freelancers: three projections worth keeping
Forecasts get unwieldy fast. For most freelancers, three named scenarios cover the decisions that actually come up.
Forecasts get unwieldy fast. It is tempting to model every plausible future, and then to spend more time maintaining the model than acting on it. For most freelancers, three named scenarios cover the decisions that actually come up, and the rest is noise.
Why three
Two scenarios — "best case" and "worst case" — are too binary to plan around. You will spend most of your time in neither.
Five or more scenarios are hard to keep in your head. You will not re-run them often, and a forecast you do not re-run is decorative.
Three scenarios are enough to bracket the realistic range and force you to put a name on what each one means.
Scenario 1: Baseline
The baseline assumes nothing exciting happens.
- Existing recurring inflows continue at the cadence they have shown for the last 90 days.
- Existing recurring outflows continue.
- No new clients, no churned clients, no surprises.
This is your "current trajectory" forecast. If you do nothing different, this is what your cash looks like in 30, 60, 90 days. It is the most boring scenario and usually the most informative one.
The baseline is what you compare everything else to. If your baseline runway is 120 days, that is the number that "doing nothing" costs you.
Scenario 2: Lean
The lean scenario assumes a slowdown that is plausible but not catastrophic.
- A specific recurring inflow reduces or ends. Pick the most likely candidate; do not abstract.
- A specific late-paying client lands an invoice 30 days later than usual.
- One-off project income you were vaguely counting on does not show up.
The point is not pessimism. The point is to identify the scenario where things are slower than baseline but still recognizable. Then you ask: in the lean scenario, when does the runway cross 60 days? That date is when you would need to act, and "act" usually means new business development or trimming expenses.
If lean and baseline give very similar answers, your business has more buffer than you think. If they diverge sharply, you have concentration risk worth naming.
Scenario 3: Stretch
The stretch scenario is the upside.
- A pipeline opportunity lands.
- An existing client expands engagement.
- A one-off that is realistic, not aspirational.
This scenario is not for celebration; it is for planning. If stretch lands, what does the cash look like? Does it free up a hire, a tool, a longer contract for office space, time off?
A common failure mode is to treat stretch outcomes as available before they arrive. The scenario lets you make conditional plans without spending the money in advance. "If stretch lands, then X" is a different commitment from "X."
How to keep the scenarios honest
Three habits keep this from drifting into fiction.
- Name the events, not just the outcomes. "Lean" is not a 20% haircut on inflows. It is "Client A reduces retainer to half" and "the November invoice slips to December."
- Re-run monthly. A scenario you wrote three months ago that has not been touched is not a scenario; it is a memory. Re-run when the month closes.
- Compare runway, not income. Scenarios are decision tools. The thing you compare across them is the runway date and the date you cross 60 days, because those are the dates that change behavior.
Using scenarios in Vitsis
In Vitsis, scenarios are first-class. The forecast page lets you add named adjustments — a delayed inflow, a one-time outflow, a recurring change — and see them on the projection chart.
A practical setup is to keep three scenarios named "Baseline," "Lean," and "Stretch," and to update them on the same day each month. Five minutes per scenario is usually enough. The chart does the rest.
When to add a fourth scenario
The case for a fourth is rare and specific: you are weighing a deliberate, large change. A move, a hire, a new business line. In that case, model it as its own scenario alongside the three above and compare. Once the decision is made, retire the scenario; do not let it linger.
The discipline is to keep the standing set at three. Scenarios that proliferate stop being read.
Takeaway
Forecasting is not about modeling the future. It is about giving yourself enough structure to make better decisions now. Three named scenarios — Baseline, Lean, Stretch — are usually enough. Update them monthly, compare the runway dates, and let the rest go.