Outcome. Every deal carries a probability percentage that updates automatically as it moves through the pipeline, giving forecast rollups a consistent input instead of a field reps forget to touch.
Workflow map
Enrollment, branches and actions at a glance
deal-hygiene-011
flowchart TD
A[Deal stage changes, pipeline matches] --> B{Which stage?}
B -->|Qualified to Buy| C[Set probability = 20]
B -->|Demo Scheduled| D[Set probability = 40]
B -->|Proposal Sent| E[Set probability = 60]
B -->|Negotiation| F[Set probability = 80]
B -->|Closed Won| G[Set probability = 100]
B -->|Closed Lost| H[Set probability = 0]
When to use it, when not to
- UseUse it when the team needs a probability value on the deal record itself, for a report or dashboard that native pipeline-level forecasting does not expose per record the way you need.
- UseUse it as a documented, agreed mapping between stage and probability, built with the sales manager, not guessed.
- SkipDo not build this if your pipeline stages already have win probabilities configured natively (Settings > Objects > Deals > Pipelines > stage > probability) and the native Forecast tool already meets the reporting need, check first, this fiche may be unnecessary work.
- SkipDo not treat the resulting number as more accurate than the stage-probability mapping it is built on, it reflects the agreed assumption, not measured close rates, unless the mapping is reviewed against real win-rate data periodically.
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.13 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.
