Sales Forecasting Agent
Forecasts revenue from pipeline stage and velocity.
- Industry
- Procure AI
- Department
- Sales
- Team
- Deal Conversion
- Kind
- Decision-maker
- Approver
- Sales Lead
- Code
- SAL-17
It forecasts new and expansion fee revenue for the period from each open deal's stage, age and velocity against historical win rates, accounting for the long procurement buying cycle and the client's own tender and board approval dates. It sets commit, best case and pipeline numbers with the deals behind each and compares its call with the reps'.
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, age, value, ramp and client decision dates..
- 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 Sales Lead with its reasoning before anything goes out.
- 07Acts
Once approved, it acts in the CRM: it submits the forecast to the forecast module. and records what was done.
What it works with
Your knowledge, your systems, your people.
Knows
The stage probabilities, historical win rates and cycle lengths by deal type, the submission calendar and the revenue recognition rule for fee ramps.
Reads from
the CRM: open opportunities with stage, age, value, ramp and client decision dates.
Acts in
the CRM: it submits the forecast to the forecast module.
Hands back
An object with period, commit, best_case, pipeline, deals (a list with opportunity, stage, probability, value_in_period and flag) and variance_percent.
Asks a person when
Its commit differs from the reps' by more than 10 percent, or the forecast goes for a period with an approval in the submission calendar.
Settings
Your limits, set by your managers.
| Setting | Default | What it controls |
|---|---|---|
| Stage probabilities | Discovery 10, Assessment 20, Proposal 35, Tender shortlist 55, Negotiation 75, Commit 90 | Probability by stage. |
| Commit probability (%) | 75 | Deals at or above this are commit. |
| Velocity lookback (days) | 365 | Long cycles need a year. |
| Slip flag (days) | 30 | Deals aged this past stage norm are flagged. |
| Variance alert (%) | 10 | A gap larger than this with the reps is flagged. |
Limits are settings, not code: a manager changes them without a developer.
Rules it always follows
- Weight deals by Discovery 10, Assessment 20, Proposal 35, Tender shortlist 55, Negotiation 75, Commit 90; commit is 75 percent or more.
- A deal whose client tender or board date is after the period is not commit.
- Flag deals 30 days past the stage norm, using 365 days of history.
- Recognise fees on the contract's ramp, not the total contract value.
- Flag a gap above 10 percent with the reps.
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.