Extensions

Opt-in modules that layer extra modelling power onto the Core App.

3 min read

Extensions are opt-in modules that add modelling capability on top of the Core App. Enable only what you need; each one adds its controls to the relevant pages and changes nothing you have not turned on.

How extensions work

Extensions are organised into three layers — recommended, quality, and advanced. Turning one on adds its controls; turning it off hides them again. Your underlying actuals are never modified either way, so trying one is reversible.

The layers

Improve data base (recommended). The ones most forecasts benefit from: driver-based revenue and cost, and contracts. These replace a historical projection with something that knows why a line moves.

Improve quality and accuracy. One-time purchases and sales, advertising budgets, project labour, employment contracts. These sharpen specific lines where the default is predictably wrong.

Advanced customisations. Custom projections, growth trends, formula display, the advanced simulator. Expert controls for people who already know exactly what shape a line should have.

The ones most founders turn on first

•Driver-Based Revenue — forecast revenue from orders, customers or ad spend rather than its own history.

•Contracts & Subscriptions — model committed revenue and recurring costs on their real dates.

•Acquire / Dispose — book one-off purchases and sales into the forecast on their own date.

•Advertising Budgets — make ad spend and its return editable levers.

Turning one off

Extensions have dependencies: one that builds on another cannot run without it, so switching off a lower-layer extension will also switch off what depends on it. Foreqast shows what will be affected before you confirm. Because none of this touches your actuals, the forecast simply reverts to the default projection for the lines involved.

PreviousDecision simulator Next Driver-Based Revenue