Financial Model Assumptions Builder

Document startup financial model assumptions for revenue, costs, and growth

Build a financial assumptions document for a startup model — ARR growth rate, churn, CAC, LTV, headcount plan, infrastructure costs, and revenue recognition notes — with the LTV/CAC ratio computed for you.

Why document model assumptions separately?

A spreadsheet shows numbers but not the reasoning behind them. An assumptions document records the inputs and the logic so reviewers can challenge the drivers, not just the outputs, and so future-you remembers why a growth rate was set where it was.

Make the thinking behind your model explicit

A financial model is only as credible as its assumptions. Investors and finance reviewers spend most of their time interrogating the inputs — growth rate, churn, CAC, headcount — not re-checking your formulas. This builder turns your key inputs into a clean assumptions document and computes the derived SaaS ratios (LTV, LTV/CAC, CAC payback) so you can pressure-test the model before anyone else does.

How it works

You enter the core drivers and the tool computes the standard unit-economics outputs:

LTV = (ARPA × gross margin) ÷ monthly churn rate
LTV/CAC = LTV ÷ CAC
CAC payback (months) = CAC ÷ (ARPA × gross margin)

Dividing by the monthly churn rate approximates the average customer lifetime in months, and multiplying ARPA by gross margin keeps LTV on a contribution basis so it is directly comparable to CAC. The document also captures the assumptions that do not reduce to a single number — the headcount plan, infrastructure cost trajectory, and revenue recognition policy — because those drive the cost side of the model.

Tips and example

  • Use conservative churn. A small change in churn swings LTV dramatically because it sits in the denominator.
  • Keep ARPA and CAC in the same currency and period; mixing monthly and annual figures is the most common modelling error.
  • State your revenue recognition basis explicitly (e.g. recognise annual contracts ratably over 12 months) — it changes when revenue appears in the model.
  • Treat the computed ratios as directional sanity checks, not precise forecasts; pair them with cohort data once you have it.