The Workflow Library

Library / Deal hygiene / deal-hygiene-012

Closed-lost reason categorization with competitor capture

Deal hygieneDealSales Hub ProfessionalIntermediate~30 min to buildalso needs Marketing Hub ProfessionalFull spec

This spec is filed under Sales Hub Professional, and one of its steps belongs to another subscription: add to static list needs Marketing Hub Professional. Both are required to build it as written.

Outcome. Every logged loss reason rolls up into a small set of reporting categories automatically, and a competitive loss triggers a dedicated capture step, so leadership gets a clean loss-category trend instead of reading through a long list of granular reasons every quarter.

Workflow map Enrollment, branches and actions at a glance deal-hygiene-012
flowchart TD
    A[Deal Closed Lost, reason known, category unknown] --> B{Reason?}
    B -->|Competitor| C[Set category = Competitive]
    C --> D[Add to Competitive Losses list]
    D --> E[Create task: confirm competitor name]
    B -->|Price / No budget| F[Set category = Commercial]
    B -->|Timing / No response| G[Set category = Process]
    B -->|Feature gap| H[Set category = Product]
    B -->|Other| I[Set category = Other]
action or delay branch public on every spec, paid or not

When to use it, when not to

  • UseUse it once Closed Lost Reason is actually being captured on most Closed Lost deals, this fiche categorizes and routes data, it does not chase reps to fill in the field (see deal-hygiene-004 for that).
  • UseUse it when leadership specifically wants a top-level split (commercial, competitive, process, product) rather than the full list of granular reasons.
  • SkipDo not build this before deal-hygiene-004 or an equivalent reason-capture process exists, the categorization has nothing to categorize without a populated source field.
  • SkipDo not merge this workflow's logic into deal-hygiene-004, keep reason capture and reason categorization as separate workflows so either can be edited without breaking the other.
The preview ends here. Six sections are in the library. counted, not blurred
PrerequisitesEvery property with its label, internal name, type and options, plus the assets the workflow needs before you start.4 items
EnrollmentThe trigger, the criteria exactly as they are ticked in the UI, the re-enrollment rule and the suppression list.4 parts
StepsEach action in order with its parameters, its branches and its delays, written as you tick them.11 numbered actions
Known pitfallsTraps seen in production, each with what breaks and what to do instead.5 pitfalls
Test plan, variants and build specHow to prove it works in a test portal, where to look when it does not, the variants for other objects or tiers, and the YAML build spec.3 variants, 3 sections
FilesThe properties JSON creates the fields in one API call, the workflow JSON documents the build.PDF, Markdown, JSON
Install1 click. The installer creates the properties this spec declares and the workflow itself, switched off, then opens a task for the prerequisites that are assets rather than properties, such as a team, a static list or a marketing email. What it created is listed on the install page.1 click, switched off
Unlock the full library, 149 EUR

or the deal hygiene pack, 39 EUR

One-time, excl. VAT. 30-day refund, no questions asked. Founding prices until 31 October, then 199 and 59 EUR. Includes every spec added later, up to the full 500, and the one-click installer on the full library. Building on client portals? The agency licence at 449 EUR covers unlimited client portals.