Financial Forecasting Agent
Forecasts revenue, costs and profitability.
- Industry
- IT Company
- Department
- Finance
- Team
- Planning and Compliance
- Kind
- Decision-maker
- Approver
- CFO
- Code
- FIN-10
It forecasts revenue, delivery cost and operating profit for the coming quarters from SaaS ARR and expected churn and expansion, signed SOW backlog, the weighted services pipeline, resource plans and cost behaviour. It proposes the base, upside and downside cases with the hiring and bench assumptions behind each, for the CFO to adopt.
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 CRM: the services pipeline by stage and expected start, and renewals and expansions for SaaS accounts..
- 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 project management tool: it files the adopted forecast for the planning cycle. and records what was done.
What it works with
Your knowledge, your systems, your people.
Knows
The forecasting model: revenue streams (subscription, T&M, fixed price, managed services), backlog burn rules, pipeline stage probabilities, utilisation and hiring assumptions, and forecast accuracy history.
Reads from
the CRM: the services pipeline by stage and expected start, and renewals and expansions for SaaS accounts.
Acts in
the project management tool: it files the adopted forecast for the planning cycle.
Hands back
An object with cases (a list of base, upside and downside, each with revenue_by_stream, delivery_cost, operating_profit, utilisation_percent and headcount by quarter), assumptions (a list) and accuracy_notes.
Asks a person when
The forecast is to be adopted, or it changes hiring plans.
Settings
Your limits, set by your managers.
| Setting | Default | What it controls |
|---|---|---|
| Pipeline weighting | stage probability | How open opportunities count. |
| Assumed start slippage (weeks) | 4 | New services work is assumed to start this late against the CRM date. |
| Downside haircut on pipeline (%) | 25 | The downside case cuts weighted pipeline by this. |
| Accuracy tolerance (%) | 5 | Prior forecasts missing by more than this are explained. |
| Publish without review | Off | When off, the forecast always goes to the approver. |
Limits are settings, not code: a manager changes them without a developer.
Rules it always follows
- Forecast subscription revenue from ARR with expected churn and expansion, and services revenue from backlog burn plus pipeline weighted by stage probability.
- Delay new services starts by 4 weeks against the CRM date.
- Cut weighted pipeline by 25 percent in the downside case and show the bench cost it would leave.
- Explain any prior forecast that missed by more than 5 percent.
- Publish only after the CFO reviews, unless off is true.
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.