How your model is structured
Updated July 18, 2026
An Adlega model has two halves: the assumptions you control and the outputs it calculates. Everything flows in one direction — assumptions in, forecast out — so you always know where to make a change.
The inputs: your assumptions
You edit assumptions in the Input Assumptions section. They are grouped by area:
| Section | What you set |
|---|---|
| Revenue | Pricing plans, add-on modules, trial conversion, professional services |
| Customer acquisition | Traffic, paid ad channels, sales channels, email, growth rates |
| People | Your headcount plan, salaries, bonuses, benefits |
| Expenses | Hosting, tech tools, payment processing, email costs |
| Tax | Effective and local tax rates |
| Other | Debt, fundraising rounds, opening cash |
| Historical data | Optional past actuals to anchor the forecast |
These are the only numbers you type. Everything else is derived from them.
The engine: cohort-based math
Adlega builds revenue cohort by cohort — it tracks each group of customers you acquire, how they expand, and how they churn over time. That drives the MRR waterfall, which feeds the profit and loss statement, which feeds cash flow and the balance sheet. Unit economics and valuation are calculated on top.
The outputs: your forecast
You read the results across four views:
- Dashboard — headline KPIs at a glance, with trends.
- MRR — month-by-month recurring revenue, new vs. churned customers, expansion.
- Operating Model — the full 3-statement forecast: P&L, balance sheet, cash flow and taxes, stacked in one scrolling view.
- Metrics — detailed unit economics (LTV, CAC, payback, LTV:CAC, burn, runway) across all 36 months.
Why it beats a spreadsheet
Because the inputs and outputs are wired together in one direction, there are no formulas to break. Change churn once and your MRR, cash, runway and LTV:CAC all move together and stay consistent. That is the core advantage of a model over a spreadsheet where numbers are hardcoded in scattered cells.
Next: start with revenue and pricing assumptions.