Available modeling methods
| Method / input | Behavior |
|---|---|
| Amount / growth / absolute change | Enter an annual amount, grow the previous value or add a signed change. |
| Price × volume / customers × ARPU | Model price and activity separately; ARPU is revenue per customer for the modeled year. |
| Percentage of a reference | Choose an eligible model reference and a percentage. Circular references are rejected. |
| Revenue per FTE | Link personnel groups and set a revenue-per-FTE rate for each relationship. |
Build the revenue schedule
In Advanced, expand Revenue → Model and add named lines. Select a method for each forecast year and use Apply Forward when the same setup should continue. Actual values are entered separately. Simple instead applies one revenue-growth assumption across all forecasts. Editing an eligible modeled output directly switches that item to an Amount method.
Use shared personnel, not copied headcount
Revenue per FTE multiplies linked average FTE by the relationship rate and sums the links. The same personnel group can support multiple revenue lines with different rates. Edit staffing in its canonical Personnel model. A link back to revenue that would create a calculation cycle is not permitted.
Example workflow
Add a Services revenue line, select Revenue per FTE, link a delivery team and enter its annual productivity rate. Change average FTE and inspect revenue, COGS, profit and receivables. A scenario can change the productivity rate without duplicating the personnel group.
Documents the current implemented behavior. Example assumptions are not market data.