The Workflow Library

Library / Deal hygiene / deal-hygiene-036

Missing deal description flag at negotiation stage

Deal hygieneDealSales Hub ProfessionalSimple~20 min to buildFull spec

Outcome. A deal reaching Negotiation with a blank description gets a task for the owner to fill it in, so anyone picking up the deal later, including a manager reviewing forecast or a rep covering for absence, has context instead of a blank field.

Workflow map Enrollment, branches and actions at a glance deal-hygiene-036
flowchart TD
    A[Deal enters Negotiation, description blank] --> B[Create task for owner]
    B --> C[Notify owner]
    C --> D[Delay 3 business days]
    D --> E{Description still blank?}
    E -->|yes| F[Send reminder notification]
    E -->|no| G[Exit, description was filled in]
action or delay branch public on every spec, paid or not

When to use it, when not to

  • UseUse it once a deal is far enough along that "what is this deal actually about" should be answered in a sentence or two, not still unclear.
  • UseUse it as a light nudge, not a hard gate, unless paired with the native required-property-per-stage setting.
  • SkipDo not use it at earlier stages where the description genuinely may not be settled yet, for example right after a deal is created from a form submission.
  • SkipDo not use it if your team already fills in the description automatically from a call transcript or deal-creation template, check the actual field population rate before assuming this gap exists.
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.2 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.6 numbered actions
Known pitfallsTraps seen in production, each with what breaks and what to do instead.4 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.