Outcome. A contact whose only open deal is marked Closed Lost, or has gone quiet past your stale threshold, gets moved back from Sales Qualified Lead to Marketing Qualified Lead automatically, keeping funnel reporting honest instead of carrying dead SQLs forward indefinitely.
Workflow map
Enrollment, branches and actions at a glance
marketing-ops-013
flowchart TD
A[Associated deal marked Closed Lost or flagged stale] --> B{Contact still Sales Qualified Lead?}
B -->|No| Z[No action]
B -->|Yes| C{Another open deal associated?}
C -->|Yes| Z
C -->|No| D[Set lifecycle stage: Marketing Qualified Lead]
D --> E[Set demotion reason]
E --> F[Notify sales rep and marketing ops]
F --> G[Remove from SQL-only lists]
When to use it, when not to
- UseUse when Sales Qualified Lead is meant to reflect an active, open deal in progress, and you have seen contacts stay tagged SQL long after their deal died.
- UseUse alongside deal-hygiene-001 (stale deal alert), which is what actually marks a deal stale in the first place; this fiche reacts to that state on the contact side.
- SkipDo not use this if a contact can have several deals over time and staying SQL while one deal closes is expected and correct. The suppression rule below handles the common case of another open deal, but confirm it matches your actual sales process before enabling.
- SkipDo not use this for company-level qualification tracking; that needs the same pattern built on the company object with company-associated deals instead.
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.5 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 marketing ops 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.
