Sign in
Modelling
Financial Modelling · Guide

Building a business model that tells you something

A model is not a forecast in a spreadsheet. It is a set of relationships that lets you ask what happens if. Here is the structure, the formulas that carry most of the weight, and the checks that catch a model that has quietly stopped being right.

Reading time11 minutesForOwners, buyers and anyone building a forecastCoversArchitecture, drivers, core formulas, integrity checks
01

Four layers, kept separate

Almost every unusable model fails the same way: assumptions, calculations and presentation are mixed together, so nobody can find what drives what. The fix is architectural and costs nothing if you do it first.

Layer 1
Inputs
Every assumption, entered once, colour-coded. Nothing is calculated here and nothing is typed anywhere else.
Layer 2
Calculations
The engine. Every cell references inputs or other calculations. No hardcoded numbers, ever.
Layer 3
Statements
P&L, balance sheet, cash flow. Presentation of the calculation layer, not new arithmetic.

A fourth layer sits alongside: outputs and checks — the summary a reader sees, and the integrity tests that tell you when the model has broken. The discipline is simple. If you are typing a number into a formula, you are creating a bug that will be invisible in six months.

The colour convention

Blue for inputs, black for formulas, green for links to other sheets. It is a fifty-year-old convention and it survives because it works: anyone opening the model can see instantly which cells they are allowed to change.

02

Revenue is built, not assumed

A growth rate is not a model. It cannot be tested, and when the number misses you learn nothing about why. Build revenue from a volume, a rate and a value — three things you can observe monthly and act on.

BusinessVolumeRateValue
SubscriptionNew sign-upsRetention / churnMonthly price
RetailTraffic or sessionsConversionAverage basket
Professional servicesBillable capacityUtilisationHourly rate
PracticePatient visitsCase acceptanceRevenue per visit
ManufacturingCapacity in unitsUtilisationPrice per unit
E-commerceSessionsConversionAverage order value

The formulas that carry the weight

MetricFormulaWhy it matters
RevenueVolume × Rate × ValueEvery miss is attributable to one of three things
Contribution margin(Price − Variable cost) ÷ PriceWhat each incremental sale actually contributes
Break-even unitsFixed costs ÷ Contribution per unitThe volume below which nothing works
Customer lifetime valueARPU × Gross margin ÷ Churn rateThe ceiling on what acquisition may cost
Payback periodCAC ÷ (ARPU × Gross margin)Months until an acquired customer repays
Cash conversion cycleDIO + DSO − DPODays of working capital growth consumes
Churn is the assumption to test hardest

Lifetime value divides by churn, so small errors compound violently. Moving monthly churn from 3% to 4% cuts implied lifetime by a quarter and changes what you can afford to spend acquiring a customer. If one input deserves real data rather than an estimate, it is this one.

03

Costs move in three different ways

Modelling every cost as a percentage of revenue produces a business that is always profitable at scale. Nothing real behaves that way, and the error only shows up in the scenarios you built the model to test.

  • Variable — materials, merchant fees, direct labour where hours genuinely flex. Model per unit or as a percentage of revenue.
  • Step — a supervisor at fifteen staff, a second van, another machine. Flat, then a jump, then flat again. Model with a threshold formula, not a percentage.
  • Fixed — rent, insurance, core salaries, software. They do not care what you sold.

Headcount deserves its own schedule with role, start month, base salary and a loading for payroll taxes, benefits and workers' compensation. The loaded cost is commonly 25–40% above base, so a model using base salary understates its largest expense line by roughly a third.

Cost typeFormula shapeCommon error
VariableRevenue × rateApplying it to costs that are actually fixed
StepCEILING(volume ÷ threshold) × costModelled as a percentage, so it never steps
FixedConstant, with inflationForgetting inflation over a five-year model
HeadcountBase × (1 + loading)Base salary only, understating by a third
05

Scenarios and sensitivity

Vary the two or three assumptions that genuinely drive the outcome. Varying everything produces noise; varying one thing at a time tells you where the model is fragile.

Find the drivers before you build cases

Move each input by ten percent and record the effect on the output you care about. Most models have two or three inputs that dominate and a dozen that barely register. A tornado chart of those sensitivities is worth more than a third scenario.

CaseWhat it isWho reads it
BaseMost likely, not most hopefulYou, monthly, against actuals
UpsideGrowth funded and deliveredInvestors
DownsideRevenue misses, costs do notLenders — this is the one they underwrite
The upside case should show less cash

If your upside scenario has more cash in the bank than your base case, the statements are not properly linked. Growth consumes working capital — receivables and inventory are funded before they are collected. An upside case that is richer in every dimension is a model that has not connected its balance sheet.

01Related toolWorking Capital CalculatorCash conversion cycle and what growth ties up.→
06

A model is only useful if you reopen it

The value is not in the forecast. It is in the variance — the monthly comparison between what you expected and what happened, and the revision that follows. A model written once and filed taught you nothing.

  • Monthly actuals beside forecast, same rows, same order, with a variance column.
  • Explain variances above a threshold, not every line. Five percent or a set dollar amount.
  • Revise the assumptions, not the history. If churn is running at 4%, change the input rather than adding a fudge.
  • Keep a version dated, so you can see what you believed six months ago and how wrong it was.
  • Model monthly for two years, then annually. Annual periods hide seasonality and cannot show the month you run out of cash.
The modest model that gets used

A simple model compared against actuals every month beats a sophisticated one written once. The point was never predicting the future. It was learning how the business actually behaves, and that only happens when you check.