The Workflow Library

Library / Deal hygiene / deal-hygiene-008

Required "next step" field before a deal can sit idle

Deal hygieneDealSales Hub ProfessionalIntermediate~30 min to buildFull spec

Outcome. Every open deal that goes more than a few days without a written next step gets chased automatically, so pipeline reviews stop running into blank "what's next" answers.

Workflow map Enrollment, branches and actions at a glance deal-hygiene-008
flowchart TD
    A[Deal open, no next step, idle 5+ days] --> B{Flag already set?}
    B -->|yes| Z[Exit]
    B -->|no| C[Set flag = true]
    C --> D[Create task for owner]
    D --> E[Notify owner]
    E --> F[Delay 3 business days]
    F --> G{Next step still blank?}
    G -->|yes| H[Notify manager - escalation]
    G -->|no| I[Reset flag, exit]
action or delay branch public on every spec, paid or not

When to use it, when not to

  • UseUse it when pipeline review meetings keep hitting deals where the rep cannot say what the next action is.
  • UseUse it together with the native "information required to move a deal to this stage" setting on your key stages for a stronger, preventive control (see Known pitfalls).
  • SkipDo not use it on very short sales cycles (days, not weeks) where "next step" churns faster than any reasonable check interval can catch.
  • SkipDo not use it if your team already tracks next steps exclusively through open tasks rather than a dedicated property, that pattern needs a different enrollment filter (task count instead of property value).
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.9 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.