Financial Forecasting Agent
Forecasts revenue, costs and profitability.
- Industry
- Procure AI
- Department
- Finance
- Team
- Planning and Compliance
- Kind
- Decision-maker
- Approver
- CFO
- Code
- FIN-10
It forecasts the company's revenue, delivery costs and operating profit from contracted retainers, transaction fee volumes, the gain-share savings pipeline weighted by validation rates and the new-client pipeline, and tests scenarios such as a client renewal lost, a sourcing wave delayed or a new e-invoicing mandate raising volumes. It saves the forecast as a version with its assumptions and a base, upside and downside case.
How it works
7 steps, and a person signs off before step 7.
- 01Looks it up
Finds the record the request is about in the spend analytics warehouse: monthly actuals by account, contracted fees, invoice and PO volumes by client, identified and validated savings, the new-client pipeline and the last published forecast..
- 02Reads the request
Works out what is being asked and what a complete answer needs.
- 03Checks the facts
Checks figures, dates and rules against the source records, not from memory.
- 04Forecasts, when it decides
Projects what each option will cost or return before it recommends one.
- 05Works it through
Prepares the draft, match, recommendation or reply, with its sources.
- 06Asks a person
Hands the work to CFO with its reasoning before anything goes out.
- 07Acts
Once approved, it acts in the planning system: it saves the forecast as a new version with its cases and assumptions, marked draft or official. and records what was done.
What it works with
Your knowledge, your systems, your people.
Knows
The forecasting method: revenue drivers by fee type, historical savings-to-validation conversion, seasonality of invoice volumes, delivery cost per unit, new-client ramp curves and the scenario templates.
Reads from
the spend analytics warehouse: monthly actuals by account, contracted fees, invoice and PO volumes by client, identified and validated savings, the new-client pipeline and the last published forecast.
Acts in
the planning system: it saves the forecast as a new version with its cases and assumptions, marked draft or official.
Hands back
An object with horizon, cases (a list for base, upside and downside, each with case, months (a list, each with month, retainer_revenue, transaction_revenue, gain_share_revenue, delivery_costs, operating_costs and operating_profit) and totals), scenarios (a list, each with name, change_in_operating_profit and key_driver), assumptions (a list, each with driver, value, source and verified) and last_forecast_error_percent.
Asks a person when
The forecast would become the official version and off is false, a scenario changes headcount or fee rates, or base-case operating profit moves more than 5 percent from the last official version.
Settings
Your limits, set by your managers.
| Setting | Default | What it controls |
|---|---|---|
| Weigh the new-client pipeline by | stage probability | How open opportunities count towards forecast revenue. |
| Share of identified savings expected to validate (%) | 65 | Gain-share revenue is forecast on this share of identified savings, unless a client's own history says otherwise. |
| Months of actuals used | 24 | How much history sets seasonality and cost behaviour. |
| Downside cut to pipeline and gain-share (%) | 20 | The downside case reduces weighted pipeline and gain-share revenue by this much. |
| Acceptable forecast miss (%) | 5 | A last forecast that missed actuals by more is recalibrated and explained. |
| Publish as official without review | Off | When off, a forecast stays a draft until the approver makes it official. |
Limits are settings, not code: a manager changes them without a developer.
Rules it always follows
- Base revenue on contracted retainers and transaction fee volumes first, then gain-share on identified savings at 65 percent validation, then the new-client pipeline weighted by stage probability; never count a deal twice.
- Forecast gain-share in the month savings are expected to validate, not when they are identified.
- Use 24 months of actuals for seasonality, including month-end and year-end invoice volume peaks, and split delivery cost into fixed and per-unit before applying volume changes.
- Show a base, an upside and a downside case; the downside cuts weighted pipeline and gain-share by 20 percent.
- A last-forecast miss above 5 percent is reported with its cause and the drivers recalibrated.
- State every assumption with its source; an assumption only from the request is marked unverified, and a forecast becomes official only when off is true or the CFO approves.
See the Financial Forecasting Agent agent on your own work.
We’ll run it on a sample of your work and show you what your approver would see.