Skip to content

Auto-set forecast category based on deal stage

One of 565 written HubSpot workflow specs, by a collective of independent HubSpot consultants.

Professional

Seat pricing: Professional edition. To build it, a GTM Seat or an Ops Seat (an Ops Seat cannot create marketing emails or sequences). Per-hub plans: Sales Hub Professional.

Deal6 stepsUpdated for HubSpot seat pricing
OutcomeThe forecast category updates automatically as a deal moves through the pipeline, so forecast rollups reflect actual stage progress instead of a manually maintained rep field that drifts out of sync.
Workflow mapdeal-hygiene-005
Deal stage changes, pipeline matches leads to Which stage?. Which stage? leads to Qualified to Buy: Set forecast category = Pipeline; Proposal Sent: Set forecast category = Best Case; Negotiation: Set forecast category = Commit; Closed Won: Set forecast category = Closed Won; Closed Lost: Set forecast category = Closed Lost. Deal stage changes, pipeline matches Which stage? Qualified to Buy Set forecast category = Pipeline Proposal Sent Set forecast category = Best Case Negotiation Set forecast category = Commit Closed Won Set forecast category = Closed Won Closed Lost Set forecast category = Closed Lost
Deal stage changes, pipeline matches leads to Which stage?. Which stage? leads to Qualified to Buy: Set forecast category = Pipeline; Proposal Sent: Set forecast category = Best Case; Negotiation: Set forecast category = Commit; Closed Won: Set forecast category = Closed Won; Closed Lost: Set forecast category = Closed Lost. Deal stage changes, pipeline matches Which stage? Qualified to Buy Set forecast category = Pipeline Proposal Sent Set forecast category = Best Case Negotiation Set forecast category = Commit Closed Won Set forecast category = Closed Won Closed Lost Set forecast category = Closed Lost

When to use it, when not to

Use it

  • Use it when the sales manager currently asks reps to manually tag every deal's forecast category and half of them forget.
  • Use it as the default, system-of-record mapping, with a manual override property reserved for genuine exceptions (see Known pitfalls).
Read more on when to use itShow less

Skip it

  • Do not use it if the team relies on HubSpot's native Forecast tool with manual category overrides as the primary input; decide up front which property is the source of truth to avoid the two fighting each other.
  • Do not use it across multiple pipelines with reused stage labels without adding an explicit pipeline filter to each branch, or deals in the wrong pipeline get mapped incorrectly.
Read more on when to skip itShow less

The rest of this spec

Prerequisites · 3 items

Every property with its label, internal name, type and options, plus the assets the workflow needs.

Enrollment · 4 parts

The trigger, the criteria as ticked in the UI, the re-enrollment rule and the suppression list.

Steps · 6 numbered actions

Each action in order with its parameters, branches and delays.

Known pitfalls · 5

Traps seen in production, each with what breaks and what to do instead.

Test plan and UAT script · 8 cases, 3 variants

How to prove it works in a test portal, one case per branch, and a sign-off sheet.

Files · PDF, Markdown, JSON, CSV

The properties JSON creates the fields in one call. The workflow JSON documents the build.

Install · 1 click, switched off

The installer creates the properties and the workflow, switched off, then opens a task for what it cannot create. Nothing is deleted, enabled or enrolled.

Unlock all 565 specs, 149 EUR

One-time, excl. VAT. 30-day refund. Installs in 3 portals. Founding price until 30 November.

Read the free Deal hygiene spec

Read 12 complete specs before you pay.

One per category, same format as the paid ones. Email only, no card.

We email the link, then a short note when specs change. Nothing else.

149 EUR199

Full library, 565 specs
Get the full library