Sales Forecasting Agent
Forecasts revenue from pipeline stage and velocity.
- Industry
- Banking
- Department
- Sales
- Team
- Deal Conversion
- Kind
- Decision-maker
- Approver
- Relationship Director
- Code
- SAL-17
It forecasts new lending, deposit balances and fee income from the relationship pipeline, by stage, credit approval rate and drawdown timing. It flags deals likely to slip and gives finance and treasury a committed figure for loan book growth and funding plans.
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: open opportunities with stage, amount, expected dates and history, and approvals from the loan origination system..
- 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 Relationship Director with its reasoning before anything goes out.
- 07Acts
Once approved, it acts in the risk data warehouse: it publishes the pipeline forecast for finance and treasury. and records what was done.
What it works with
Your knowledge, your systems, your people.
Knows
The forecasting method: stage probabilities, credit approval rates by segment, typical approval-to-drawdown times, utilisation assumptions and the reporting calendar.
Reads from
the CRM: open opportunities with stage, amount, expected dates and history, and approvals from the loan origination system.
Acts in
the risk data warehouse: it publishes the pipeline forecast for finance and treasury.
Hands back
An object with period, new_lending (commit, weighted and best_case), deposits (weighted), fees (weighted), slipping (a list with deal and days), variance_to_calls_percent and reasons.
Asks a person when
The forecast differs from the managers' commit by 10 percent or more, or it will be given to finance and treasury.
Settings
Your limits, set by your managers.
| Setting | Default | What it controls |
|---|---|---|
| Stage probabilities | Discovery 10, Proposal 25, Credit Submitted 50, Credit Approved 80, Documentation 90 | Stage and percent. |
| Probability that counts as commit (%) | 80 | Deals at this probability or more are committed. |
| Approval to drawdown (days) | 30 | Expected time from approval to first drawdown. |
| Flag slips over (days) | 14 | Deals with a close date pushed this far are flagged. |
| Variance to commit that alerts (%) | 10 | Forecasts this far from the commit are explained. |
Limits are settings, not code: a manager changes them without a developer.
Rules it always follows
- Weight deals by Discovery 10, Proposal 25, Credit Submitted 50, Credit Approved 80, Documentation 90; commit includes only deals at 80 percent or more.
- Count lending in the period it is expected to draw, 30 days after approval, at expected utilisation, not at the full limit.
- Flag deals whose dates slipped more than 14 days.
- Explain any gap of 10 percent or more between the forecast and the managers' calls.
See the Sales 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.