Financial models an investor can follow without a call
Clear input sheets, one calculation per row, no hard-coded numbers hidden inside formulas. Models are read by other people, so we build them to be read.
Models we build
We follow standard modelling conventions: inputs, calculations and outputs on separate sheets, consistent formulas across each row, colour coding for hard inputs, and checks that flag when the balance sheet stops balancing.
Scenarios are switchable from one cell. Change the case, and every output updates — no duplicate tabs to maintain.
Three-statement models
P&L, balance sheet and cash flow linked properly, with a balance check that cannot be ignored.
Cash flow forecasts
13-week or rolling monthly, with sensitivity on collections and payment terms.
Budgets and reforecasts
Departmental build-up rolling into a consolidated view, with variance against actuals.
Valuations and returns
DCF, LBO and simple return models with clean assumption pages.
What we fix in models we inherit
- 1Numbers typed inside formulasEvery assumption gets pulled out to a labelled input cell.
- 2Rows where the formula changes halfwayThe classic source of silent errors. We make each row consistent.
- 3Scenario tabs copied and pastedReplaced with a single switchable case driver.
- 4No checks anywhereWe add balance, cash tie and integrity checks that flag loudly.
Everything that ships with this
- A documented model with an assumptions page
- Switchable scenarios from a single cell
- Built-in integrity checks
- A summary output page ready for a board pack
- A walkthrough call with your finance team
Fixed price, quoted after we have seen the file or the brief. Nothing is billed until you approve the scope in writing. See pricing.
Yes, and it is often the better route. We review it, list what needs fixing, and rebuild only the parts that need it.
We follow widely used conventions — consistent rows, separated layers, no hard-coding, visible checks. If your investor or lender requires a specific standard, tell us and we will build to it.
Yes, always, and before any file is sent.
Often booked alongside this
Send the file. Get a straight answer.
A 20-minute call, or just email the workbook with a note on what is wrong. Either way you will know the cause and the cost before you commit.