3-Year SaaS Business Model Template

The constraints

What made this hard?

Three constraints. The first was input/output discipline. A model where any cell can be a formula or an input is a model that breaks the first time somebody types a number into the wrong place. The blue-cell convention had to be visually obvious and structurally enforced; everywhere not blue is calculated.

The second was the SaaS-specific revenue layer. Generic three-statement models don't handle SaaS revenue correctly. New MRR plus expansion minus churn, with cohort effects, with monthly versus annual contracts, with payment timing, is a different shape from "sales line goes up". The template had to handle that without making it the only thing the founder could think about.

The third was the headcount-to-burn link. Most founder financial models have headcount as a separate exercise from burn, which means changing a hire date requires updating multiple tabs and the runway calculation goes wrong. Headcount had to feed burn directly, with hire-date inputs flowing into salary, employer costs, and cash position automatically.

The approach

How did Tincture frame the problem?

A single workbook with four sheets: Assumptions, Revenue, Headcount, and the Three-Statement Output (Income, Cash, KPIs).

The Assumptions sheet holds every input: starting MRR, new logo close rate per month, expansion rate, churn rate, ACV per segment, gross margin, hiring plan (role, function, start month, salary, employer cost multiplier), opex categories, starting cash. Every blue cell in the workbook is on this sheet (or echoed from it).

The Revenue sheet calculates monthly MRR and ARR with new logos, expansion, and churn modelled as separate flows, summed to total MRR per month and rolled forward across thirty-six months.

The Headcount sheet lists every hire by month, with salary plus employer cost multiplier rolling into total monthly people cost. The hire dates are blue cells; the cost calculation is automatic.

The Output sheet renders the income statement, cash flow, and the cash position month by month for thirty-six months. Plus a KPI row: ARR, runway months, gross margin, net new MRR per month, burn multiple. Conditional formatting flags the month cash goes negative if the assumptions produce that result.

The build

What was shipped?

A Google Sheets workbook (Excel-compatible) with the four sheets, the blue-cell convention, the linked formulas across sheets, conditional formatting on the cash row, and a starter set of plausible assumptions for an early-stage SaaS business.

A README tab inside the workbook explaining the colour convention, how to update the assumptions, what the KPIs mean, and how to add hires or modify the revenue model. Documentation lives inside the workbook because that's where the founder needs it.

A worked example column for the first six months populated with sample data, so the founder can see what a filled-in version looks like before zeroing it out for their own numbers.

The whole workbook is downloadable as both Excel and Google Sheets. No add-ons required. No macros. Standard formula library only.

The outcome

What were the results?

Live and free. Founders download the template, fill in their assumptions, and walk away with a three-year financial model they can credibly bring to a board meeting or a raise.

The compounding outcome is the founder's relationship with their own model. Most founders treat their financial model as a thing they have to update when somebody asks. After this template, the model becomes a working surface; updating a hire date or a churn assumption takes thirty seconds and the runway recalculates. The model goes from theatre to tool.

The strategic outcome is the credibility shift. Investors, board members, and operating partners read financial models with a quick eye for whether the founder built it or somebody else built it for them. The template walks the line: structured enough to be credible, simple enough that the founder clearly owns it.

What it took

What tools and methods were used?

Google Sheets and Excel as the dual delivery format. Linked formulas across the four sheets, conditional formatting for the cash position row, the blue-cell convention for inputs versus outputs. No add-ons, no macros, standard formula library only.

The methodological underpinning is the practice's pattern for founder-facing financial tooling: structured but editable, credible but ownable, monthly granularity but quarterly readable. The template sits in the gap between "spreadsheet that's too simple to defend" and "model that's too complex to update".

The other move worth naming: documentation inside the workbook. Most templates ship with a separate PDF guide that nobody reads. The README tab inside the workbook means the documentation is one click from the cell the founder is trying to update, which is the only place documentation actually gets read.

The takeaway

What's the transferable principle?

Most founder financial models fail one of two ways. Either they're too simple to defend in a serious conversation (one tab, four lines, no SaaS-specific revenue) or they're too complex to maintain (eight tabs, fifty dependencies, breaks on the first edit). The work that lands sits in the middle: enough structure to handle SaaS revenue and headcount-to-burn correctly, simple enough that the founder owns it.

For the template, that meant four sheets, a strict blue-cell convention, linked formulas across the workbook, and documentation inside the file rather than alongside it. Founders update the model themselves on a Tuesday and it doesn't break.

The other transferable principle, broader than financial modelling: ownership versus precision. A model the founder builds (or genuinely owns) is more useful than a more-precise model an analyst built that the founder won't update. Build for ownership; precision compounds where it can be maintained.

Read more on this in Cash Flow Management for SaaS Startups: The Rolling 4-Week Forecast