Outcome. Every open deal carries a live aging bucket, 0-30, 31-60, or 61-90+ days since creation, so a list view or dashboard can segment the pipeline by age without anyone computing days-open by hand.
Workflow map
Enrollment, branches and actions at a glance
deal-hygiene-042
flowchart TD
A[Deal created, open] --> B[Set bucket = 0-30 days]
B --> C[Delay until create date + 30 days]
C --> D{Deal closed by now?}
D -->|yes| E[Exit]
D -->|no| F[Set bucket = 31-60 days]
F --> G[Delay until create date + 60 days]
G --> H{Deal closed by now?}
H -->|yes| I[Exit]
H -->|no| J[Set bucket = 61-90-plus days]
When to use it, when not to
- UseUse it when pipeline reviews need a quick "how much of our pipeline is getting old" view and the native deal age is not already surfaced the way the team wants it.
- UseUse it alongside deal-hygiene-021's days-in-current-stage tracker, the two answer different questions: this fiche measures total time open since creation, deal-hygiene-021 measures time in the current stage specifically.
- SkipDo not use it if the native
Time in current stageor a similar built-in metric already available in list views and reports covers this need (check in your portal: exact native properties or report types your portal exposes for deal age, some of this may already exist without a custom build). - SkipDo not expect a live day-count number out of this fiche, workflows do not do arithmetic between "today" and a date property, this fiche produces a bucket label at defined checkpoints, not a continuously updating number of days.
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.8 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.
