The Workflow Library

Library / Deal hygiene / deal-hygiene-029

Deal type auto-classification (new business vs expansion)

Deal hygieneDealSales Hub ProfessionalIntermediate~30 min to buildFull spec

Outcome. A new deal gets classified as new business or expansion automatically, based on whether its associated company has a prior Closed Won deal, so pipeline reports split cleanly without a rep manually tagging every deal.

Workflow map Enrollment, branches and actions at a glance deal-hygiene-029
flowchart TD
    A[Deal created, company associated, Deal Type unknown] --> B{Company on Closed Won history list?}
    B -->|yes| C[Deal Type = expansion]
    B -->|no| D[Deal Type = new-business]
action or delay branch public on every spec, paid or not

When to use it, when not to

  • UseUse it at deal creation. This fiche classifies once and does not keep re-checking, since re-running the same logic after the fact could reclassify a deal mid-cycle if the company happens to win another deal concurrently.
  • UseUse it when "new business vs expansion" is a standing reporting need for sales leadership, not a one-off report someone can pull manually.
  • SkipDo not use it if a company can have a Closed Won deal that does not count as prior business for classification purposes, for instance a free pilot recorded as Closed Won. Exclude those from the active list definition below.
  • SkipDo not use it on a company-less deal. Classification depends entirely on the associated company's deal history, pair with deal-hygiene-017 first.
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.3 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.