---
name: "Build a sales forecast"
description: "Produces a sales forecast the team can defend: three independent views (deal categories, stage-weighted pipeline, run rate) reconciled into one number with a range, the deals that decide it and the assumptions written down. Used when you need a number for next month or quarter for the owner, board or bank."
version: 2
verified_on: 2026-10-28
reverify_by: 2027-10-28
sources:
  - id: t1-hs-forecast
    title: "Set up the forecast tool (HubSpot Knowledge Base)"
    url: https://knowledge.hubspot.com/forecast/set-up-the-forecast-tool
    tier: T1
    accessed_on: 2026-10-27
  - id: t1-hs-pipelines
    title: "Set up and manage object pipelines (HubSpot Knowledge Base)"
    url: https://knowledge.hubspot.com/object-settings/set-up-and-customize-pipelines
    tier: T1
    accessed_on: 2026-10-27
---

> **How to use this file:** attach it to ChatGPT, Claude, Gemini or Copilot, replace every [PLACEHOLDER] with your details, and add any data or Deepstory evidence files the method needs.

**Best with:** Any chat AI that can analyse a spreadsheet; attach the open deals export and last year’s closed deals, with customer names removed if needed.

## Quick start

1. Clean your pipeline first: mark dead deals as lost (do not delete them, because your win rates come from closed deals) and fix close dates that have passed.
2. Sort deals into three groups: very likely (commit), possible (best case) and early (pipeline).
3. Use your own history: of the deals that reached each stage last year, how many did you win?
4. Multiply each deal by that win rate and add them up. Then compare with what you usually sell in a period.
5. If the numbers disagree a lot, find out why instead of averaging them.
6. Give a range: low, likely and high, and name the few deals that decide it.
7. At the end of the period, compare the forecast with what really happened.

## Before you start

- You need to clean up or inspect the pipeline itself first (stale deals, missing steps). See: Run a sales pipeline review (https://deepstoryresearch.com/method/pipeline-review)
- You need a cash forecast (when money arrives and leaves), not a bookings forecast. See: Build a 13-week cash-flow forecast (https://deepstoryresearch.com/method/cash-flow-forecast-13-week)
- You have no deal pipeline (a shop, website, walk-in or appointment business, or subscriptions that renew automatically): forecast units and demand instead. If only part of your sales goes through deals (for example a few wholesale accounts), use this method for that part and the demand method for the rest, then add the two. See: Forecast product demand (https://deepstoryresearch.com/method/demand-forecasting)
- Other CRMs: the rules apply to any CRM, but category names and the stage-to-category mapping differ by platform. Map your CRM’s categories to commit, best case and pipeline before you start.

## Intake questions

Ask me these first:

1. **Do you track sales as deals in a CRM or spreadsheet, with a stage and amount for each?**
   Why: The category and weighted views need a deal pipeline.
   If unknown, assume: No pipeline: use the run-rate view only and follow the routing in Before you start.
2. **What is being forecast: new bookings, revenue, or number of deals, and for which period?**
   Why: Bookings (the value of signed deals, not appointments or orders), invoiced revenue, recognised revenue and cash fall in different periods; annual subscriptions invoiced upfront are booked on signing, recognised monthly and paid after the payment term. Ask who will read the forecast: a bank usually wants revenue or cash.
   If unknown, assume: Forecast new bookings (signed deals) for the period asked.
3. **Can you export open deals with stage, amount, close date, owner, created date and last activity?**
   Why: Stage, amount and dates drive every view; age and activity show stale deals.
   If unknown, assume: No deal-level view: forecast from the run rate or the funnel, and list the export fields needed.
4. **What share of deals reaching each stage were eventually won in the last 12 months?**
   Why: Stage-weighted forecasts must use your own conversion, not generic percentages.
   If unknown, assume: Calculate from closed deals if exported; otherwise use early (first meeting or qualified demo) 10%, middle (proposal or trial) 25%, late (negotiation or verbal yes) 50%, labelled ASSUMPTION (rule of thumb), and show low and high at half and double these rates.
5. **What were bookings in each of the last 4 to 6 periods, and how much is already closed this period?**
   Why: The run-rate view checks the pipeline against history.
   If unknown, assume: Annual sales / 12 a month, flat, labelled ASSUMPTION, with known peaks named.
6. **What is the typical sales cycle from first meeting to signed deal?**
   Why: Deals created too late to close within the cycle are unlikely this period, and a period longer than the cycle will also close deals not yet in the CRM.
   If unknown, assume: The midpoint of the range the user gives, or 30 days if none, labelled ASSUMPTION; do not confuse the sales cycle with payment terms.
7. **What is the target for the period, and what are your financial year and quarter dates?**
   Why: The forecast is judged against the target, and quarter names differ between April to March and calendar years.
   If unknown, assume: No target; name the period by its months (for example January to March 2027), not by quarter number.
8. **Which CRM and plan do you use, and should new customers, expansions and renewals be forecast separately?**
   Why: Forecast tools need specific plans and settings, and renewals and expansions close at very different rates from new deals.
   If unknown, assume: Work from the export; forecast new bookings only and list other deal types separately.
9. **How do reps decide that a deal is "commit"?**
   Why: Categories mean nothing without written rules.
   If unknown, assume: Use: commit = buyer confirmed budget, decision maker and date, and the next step is booked.

## Decision rules

| If | Then | Threshold | Type | Source |
|---|---|---|---|---|
| You set up forecast categories in HubSpot. | HubSpot groups deal stages into Not forecasted, Pipeline (low likelihood), Best case (moderate likelihood), Commit (high likelihood, committed to the forecast) and Closed won. Categories can update automatically when a deal changes stage, and users can override a deal’s category on the deal record. Category meaning follows the order of the values in the Forecast category property, not their names. | - | Platform rule | [t1-hs-forecast] |
| You use HubSpot’s forecast tool. | It needs Sales Hub or Service Hub Professional or Enterprise, and Super Admin to set up. Its Forecast deal amount defaults to Weighted amount (amount x deal probability); the other options include Total amount. Check which one is set before reading category totals, and export the plain Amount field when you apply your own win rates. Changing the forecast period resets revenue goals and forecast submissions. | - | Platform rule | [t1-hs-forecast] |
| You use a weighted pipeline in HubSpot. | Weighted amount = deal amount x deal probability for the stage. Set each stage’s probability in the pipeline settings (the default Sales Pipeline comes with generic probabilities), and include both Won and Lost stages so reports process deals correctly. | - | Platform rule | [t1-hs-pipelines] |
| You set stage probabilities. | Replace default probabilities with your own: for each stage, won deals that passed through it divided by all closed deals that passed through it, over the last 12 months. | - | Heuristic (rule of thumb) | - |
| A deal’s close date is in the past, its age is more than about 1.5 times the median sales cycle of won deals, or it has had no logged activity for more than about a third of the cycle (30 days at most). | Treat it as stale: move it out of commit and best case until the owner updates the date and books the next step. | 1.5 x cycle age; one-third of cycle inactivity (rules of thumb) | Heuristic (rule of thumb) | - |
| A deal is marked commit. | Require written evidence: confirmed budget, decision maker involved, agreed close date, and a booked next step. Without these, it is best case. | - | Heuristic (rule of thumb) | - |
| You set the likely number. | Likely = closed + weighted view of normal deals + big deals you call in + the allowance for deals not yet in the CRM. Compare likely with the run-rate view. If they differ by more than about 15% of the run-rate view, do not average; explain the gap (a big deal called out, a slow start, stale deals) and keep the view whose assumptions you can defend. Once you have 3 or more periods of forecast accuracy, prefer the view that was closest. | 15% (rule of thumb) | Heuristic (rule of thumb) | - |
| The period has not started, the period is longer than your median sales cycle, or a deal was created recently. | Add one allowance, shown as its own line, for deals not yet in the CRM: the average value of deals created and won inside the same period over the last 4 periods, multiplied by the share of the period still to come (weeks left / weeks in the period). If that history is unknown, use the funnel instead: expected new qualified opportunities in the rest of the period x your own win rate from that stage x average deal amount (without a known amount, forecast the number of deals). Use one of the two, never both. Keep deals created later than (period end minus median cycle) out of commit unless the buyer has confirmed a signing date. | median cycle; share of period left (rules of thumb) | Heuristic (rule of thumb) | - |
| A few deals make up most of the forecast. | Forecast those deals one by one (in or out) and apply weighting only to the rest; a probability on a single large deal is misleading. | - | Heuristic (rule of thumb) | - |
| You report the forecast. | Give a likely number with a low (closed plus commit) and high (plus best case) range, and track forecast accuracy each period (actual / forecast) to improve the rules. If there is no commit category (no pipeline, or the period has not started), set low and high from the same calculation with the lowest and highest win rate or monthly sales of the last 12 months; if those are unknown, write "Low and high: not computable" and never use a fixed percentage band. | - | Heuristic (rule of thumb) | - |

## Procedure

Copyable checklist:

- [ ] Clean: Mark dead deals Closed lost with a reason (never delete them), update past close dates, fill missing amounts, merge duplicates only after checking with the owner.
- [ ] Categorise: Commit, best case, pipeline using the written rules; note any rep overrides.
- [ ] Weighted view: Sum of amount x your own stage win rate for deals closing in the period.
- [ ] Run-rate view: Closed so far + (average bookings per week in past periods x weeks left), adjusted by (same period last year / average period last year); if last year is unknown, say "no seasonal adjustment" and name the known peaks or dips in the period.
- [ ] Big deals: List the deals that make up most of the gap to target, each in or out with a reason.
- [ ] Reconcile: Likely = closed + weighted (normal deals) + big deals called in + allowance for deals not yet in the CRM (scaled to the share of the period left); compare with run rate; if more than about 15% apart, explain and choose; low = closed + commit, high = closed + commit + best case.
- [ ] Write assumptions: Win rates used, period of history, deals excluded and why.
- [ ] Review and learn: Weekly check against the forecast; at period end record accuracy.

## Output template

```
## Sales forecast: [PERIOD]

Target: [ ] | Closed so far: [ ] | Open deals in period: [n], [total]

### Clean-up
Deal | Issue | Action | Amount removed

### Categories
Commit: [ ] | Best case: [ ] | Pipeline: [ ]

### Views
Categories low (closed + commit): [ ] | Categories high (+ best case): [ ] | Weighted (own win rates, big deals separate): [ ] | Run rate: [ ] | Deals not yet in the CRM (history or funnel, and which): [ ] | Likely and how it was chosen: [ ]
If a section does not apply, write "Not applicable: [reason]".

### Deals that decide the period
Deal | Amount | Stage | In or out | Next step | Owner | Date

### Forecast
Low: [ ] | Likely: [ ] | High: [ ] | Gap to target: [ ]

### Assumptions and review
[win rates, history used, exclusions] | Review: [dates]
```

## Failure modes

| Mistake | Symptom | Fix |
|---|---|---|
| Weighting with default stage percentages. | Forecast consistently too high. | Use your own win rates by stage. |
| Leaving stale deals in the pipeline. | Big pipeline, missed forecast. | Take deals with past dates or long inactivity out of the forecast: mark them lost or ask the owner to update them; never delete them. |
| Commit based on optimism. | Commit deals slip every month. | Written commit rules with evidence. |
| Applying a probability to one huge deal. | Forecast swings on a single decision. | Forecast large deals in or out individually. |
| Averaging views that disagree. | A number nobody can explain. | Explain the gap and choose. |
| Counting the same deal in two periods or categories. | Totals add up to more than the pipeline. | One deal, one period, one category. |
| Applying your own win rates to an already weighted amount. | Weighted view far below every other view. | Export the plain Amount field, or set Forecast deal amount to Total amount, before weighting. |
| Using "ever won" stage rates for a single period. | Volume is right but deals land a period late. | Measure what share of deals in each stage at the start of past periods closed won within that period, or discount by your usual slip rate. |
| Deleting dead deals instead of marking them lost. | Win rates look higher than they are. | Mark them Closed lost with a reason. |
| Never measuring accuracy. | The same mistakes every quarter. | Record actual / forecast each period. |

## Verification

- [ ] Stale and dead deals were taken out of the forecast (marked lost or updated, never deleted), with a list.
- [ ] Win rates are your own, or labelled ASSUMPTION.
- [ ] All three views are shown with their numbers.
- [ ] The forecast has low, likely and high values, or says why low and high cannot be computed.
- [ ] Large deals are forecast individually.
- [ ] Assumptions and the review date are written down.

## Agent mode

If an AI agent is operating a browser or API on your behalf:

**May do without asking:**
- Analyse exported deal data and calculate the three views.
- Draft the forecast summary and the list of deals that decide the period.
- Read CRM pipeline and forecast settings in a read-only session.

**Must stop before (the user decides and does these):**
- Editing deal stages, amounts, close dates, owners or forecast categories in the CRM.
- Deleting, merging or marking deals Closed lost.
- Changing pipeline stages, stage probabilities or the Forecast deal amount setting.
- Changing the forecast period (in HubSpot this resets all forecastable revenue goals and forecast submissions).
- Turning Automate forecast categories on or off, or creating or editing workflows.
- Creating, editing or deleting forecast goals, or submitting or deleting a forecast in the CRM forecast tool.
- Sending the forecast to investors, lenders or the board.
- Exporting customer data outside the business.
- Buying, upgrading or starting a trial of a CRM plan, add-on or seat, or accepting any terms.
- Assigning seats or changing user permissions.
- Importing, bulk-updating or uploading deal data, or connecting a new app or integration.
- Editing the Forecast category property (adding, renaming or reordering its values).

**Setup advice:**
- Let reps update their own deals after the clean-up list, rather than editing them for them.
- Keep a forecast log with the number, date and actual result each period.

## Worked example

The figures below are illustrative. Never reuse them: use only the user’s own numbers and facts, and label anything they have not given as an ASSUMPTION.

**Scenario:** An Indian B2B SaaS company forecasting new bookings for January to March 2027 (Q4 of its April to March financial year), on 5 January 2027 (week 1 of 13 complete).

**Input:** Target INR 1.2 crore. Open deals: 38, total INR 2.1 crore; 32 of them (INR 1.8 crore) have close dates from January to March 2027, and 6 (INR 0.3 crore) have close dates in December 2026 and no activity for 80 days. Own win rates from the last 12 months: demo 18%, proposal 35%, negotiation 62%. Median sales cycle 45 days. Last 4 quarters, oldest first (January to March 2026 to October to December 2026): INR 1.05, 0.95, 0.9 and 1.1 crore, so the same quarter last year was INR 1.05 crore. Deals created and won inside the same quarter averaged INR 0.25 crore a quarter. Already closed this quarter: INR 0.12 crore. One deal of INR 0.4 crore is in negotiation; its legal review is not booked.

**Output excerpt:** Clean-up: the 6 deals with December close dates and no activity for 80 days (more than a third of 45) are stale: moved out of the forecast and the owners asked to update or mark them lost, leaving 32 deals worth INR 1.8 crore, all closing this quarter. Categories: commit INR 0.45 crore (4 negotiation deals with budget, decision maker and signing date); best case INR 0.75 crore (proposal deals INR 0.35 crore plus the INR 0.4 crore deal); pipeline INR 0.6 crore (demo). Weighted view, big deal treated separately: 0.6 x 18% + 0.35 x 35% + 0.45 x 62% = INR 0.51 crore; plus closed INR 0.12 crore = INR 0.63 crore. Big deal: out until the legal review is booked. Deals not yet in the CRM: 0.25 x 12 / 13 weeks left = INR 0.23 crore. Run rate: average quarter 1.0, so 0.12 closed + (1.0 / 13 weeks x 12 weeks left) x seasonal factor (1.05 / 1.0) = INR 1.09 crore. Likely: 0.63 + 0.23 = INR 0.86 crore, 21% below the run rate; the gap is explained because the run rate assumes a typical large deal closes and this quarter’s only one is out, so likely stays at 0.86. Forecast: low INR 0.57 crore (closed + commit), likely INR 0.86 crore, high INR 1.32 crore (closed + commit + best case). The 1.2 crore target is reachable only if the INR 0.4 crore deal signs (0.86 + 0.4 = 1.26). Review every Monday; record actual / forecast at quarter end.

## References

### Platform settings

| Platform | Path | Setting | Note | Source |
|---|---|---|---|---|
| HubSpot | Settings > Objects > Forecast > Pipelines | Forecast categories per deal stage (Not forecasted, Pipeline, Best case, Commit, Closed won); Automate forecast categories | - | [t1-hs-forecast] |
| HubSpot | Settings > Objects > Forecast | Forecast deal amount (Weighted amount by default, or Total amount); forecast period (monthly or quarterly) | Changing the forecast period resets revenue goals and forecast submissions. | [t1-hs-forecast] |
| HubSpot | Settings > Data Management > Objects > Deals > Pipelines | Deal probability per stage; Won and Lost stages | Weighted amount = amount x deal probability. | [t1-hs-pipelines] |

### Sources

| ID | Title | Tier | Accessed on | URL |
|---|---|---|---|---|
| t1-hs-forecast | Set up the forecast tool (HubSpot Knowledge Base) | T1 | 2026-10-27 | https://knowledge.hubspot.com/forecast/set-up-the-forecast-tool |
| t1-hs-pipelines | Set up and manage object pipelines (HubSpot Knowledge Base) | T1 | 2026-10-27 | https://knowledge.hubspot.com/object-settings/set-up-and-customize-pipelines |

---
Deepstory methods are process guidance for AI tools. Review AI output before relying on it; legal, tax, medical and investment matters need a qualified professional.
