The Workflow Library

Library / Deal hygiene / deal-hygiene-020

Deal stage regression alert (moved backward)

Deal hygieneDealSales Hub ProfessionalIntermediate~30 min to buildFull spec

Outcome. The deal owner and manager get notified when a deal moves backward in the pipeline, so a regression gets a reason logged instead of vanishing quietly into the stage history.

Workflow map Enrollment, branches and actions at a glance deal-hygiene-020
flowchart TD
    A[Deal stage changes] --> B[Set Stage Order from stage mapping]
    B --> C{Stage Order less than Stage Order Snapshot?}
    C -->|yes| D[Set Stage Regression Flag = true]
    D --> E[Create task for owner]
    E --> F[Notify owner and manager]
    C -->|no| G[Set Stage Regression Flag = false]
    F --> H[Copy Stage Order into Stage Order Snapshot]
    G --> H
action or delay branch public on every spec, paid or not

When to use it, when not to

  • UseUse it on pipelines with a clear linear stage order where moving backward is unusual and worth a manager's attention.
  • UseUse it as the branching companion to deal-hygiene-011's stage-order mapping. This fiche reuses the same stage-to-number pattern to detect direction of movement.
  • SkipDo not use it on pipelines where reps regularly move deals back and forth by design, for example a "requalify" step that is a normal loop. The alert becomes noise.
  • SkipDo not expect this fiche to explain why the deal regressed. It flags the fact, a human still records the reason.
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.5 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.16 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.