The playbook
Sales Forecasting: Worked Examples
The following sales forecasting examples illustrate how to move from an observed problem to a practical decision. They are hypothetical operating scenarios, not customer results or performance benchmarks. The central question is whether the work helps improve forecast error by period without losing the context needed to judge it.
Put the task in context
For each included deal, review the expected close period and the evidence behind its stage. Compare forecast assumptions with historical outcomes, while allowing for changes in deal mix. Keep committed revenue separate from weighted estimates and upside scenarios.
Example 1: establish a usable starting point
A team begins working on sales forecasting but cannot consistently describe opportunity and value for the same item. The immediate task is define the forecast period and included opportunities. The team records the current state, identifies the source of each value, and resolves conflicting information before making a broader change.
The useful output is a customer or opportunity record that another person can interpret. This example does not require assuming an uplift. Success at this stage means the next decision can be made using a shared set of facts, with missing information explicitly identified.
Example 2: correct a specific failure
In a second situation, the team observes treating every open deal's full value as expected revenue. It proposes the correction: use realistic assumptions and disclose uncertainty. Before applying that correction everywhere, the owner checks whether the same cause is present in other affected items. A common symptom alone does not prove that all items need the same repair.
| Decision | Illustrative reasoning |
|---|---|
| Observation | Treating every open deal's full value as expected revenue |
| Likely correction | Use realistic assumptions and disclose uncertainty |
| Verification task | Review stage evidence close dates and historical conversion |
| Result to inspect | Compare forecasts with actual closed outcomes |
After the change, the owner repeats the relevant task and records what happened. If the condition remains, the team returns to the evidence rather than declaring the process complete. The example illustrates a repair cycle; it does not claim a particular commercial result.
Example 3: extend a process after it works
A third team already has reliable records for a small scope and wants to expand. It compares the next group with the first: are opportunity, value, close period defined in the same way, and does the intended outcome remain forecast error by period? Differences are written down before the earlier process is reused.
Expansion is appropriate when the assumptions still hold and an owner can review exceptions. Where the new group has different needs, the team adapts the process and tests again. Reusing the structure is useful; reusing a conclusion without checking its conditions is much less reliable.
Apply the examples to your own work
- Write the current problem in observable terms using opportunity.
- Choose which of the three examples matches the stage of the work.
- Complete this action first: define the forecast period and included opportunities.
- Keep the resulting evidence and review forecast error by period on a consistent basis.
Distinguish a person, an organization, and an opportunity. One contact can participate in several buying decisions, and one company can have several contacts. Keep identifiers and relationships clear when reviewing counts or moving records.
Skip the manual steps. Let AgentixCRM run this for every client.
Start now