Skip to content

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.

Deal9 stepsUpdated for HubSpot seat pricing
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
Deal stage = Closed Lost, reason unknown leads to Notify owner. Notify owner leads to Create task: log loss reason. Create task: log loss reason leads to Delay 1 business day. Delay 1 business day leads to Reason still unknown?. Reason still unknown? leads to yes: Notify manager + escalation task; no: Reason = Competitor?. Notify manager + escalation task leads to Reason = Competitor?. Reason = Competitor? leads to yes: Create task: log competitor name; no: Exit. yes no yes no Deal stage = Closed Lost, reason unknown Notify owner Create task: log loss reason Delay 1 business day Reason still unknown? Notify manager + escalation task Reason = Competitor? Create task: log competitor name Exit
Deal stage = Closed Lost, reason unknown leads to Notify owner. Notify owner leads to Create task: log loss reason. Create task: log loss reason leads to Delay 1 business day. Delay 1 business day leads to Reason still unknown?. Reason still unknown? leads to yes: Notify manager + escalation task; no: Reason = Competitor?. Notify manager + escalation task leads to Reason = Competitor?. Reason = Competitor? leads to yes: Create task: log competitor name; no: Exit. yes no yes no Deal stage = Closed Lost, reason unknown Notify owner Create task: log loss reason Delay 1 business day Reason still unknown? Notify manager + escalation task Reason = Competitor? Create task: log competitor name Exit

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

Prerequisites · 4 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 · 9 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 · 6 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