Require and capture win/loss reason on Closed Lost
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.
OutcomeNo deal reaches Closed Lost without a standardized loss reason on file, so loss analysis is based on real data instead of guesswork.
Workflow mapdeal-hygiene-004
When to use it, when not to
Use it
- Use it as soon as leadership asks "why are we losing deals" and the honest answer is "we don't know, the field is empty on 80% of them."
- Use it alongside the native required-property-per-stage feature for a stronger, non-bypassable control (see Known pitfalls).
Read more on when to use itShow less
Skip it
- Do not use it if you have not yet agreed on a finite, mutually exclusive list of loss reasons with sales leadership. Building the workflow before the taxonomy exists means rebuilding it later.
- Do not extend this same workflow to also capture Closed Won reasons. Keep that as a separate, parallel workflow (see Variants) so the branch logic and reporting stay clean.
Read more on when to skip itShow less
The rest of this spec
Not the workflow you needed?
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.
Here it is. Download the pack now (.zip) The link is in your inbox too.
Read the free Deal hygiene spec