The Workflow Library

Library / Renewal and expansion / renewal-expansion-018

Renewal deal auto-move to Closed Lost on confirmed non-renewal

Renewal and expansionDealSales Hub ProfessionalSimple~25 min to buildFull spec

Outcome. A renewal deal moves itself to Closed Lost with a reason attached the moment someone confirms the account will not renew, so stale renewal deals stop sitting open in the pipeline and skewing forecast.

Workflow map Enrollment, branches and actions at a glance renewal-expansion-018
flowchart TD
    A[Deal Type = Renewal, Renewal Confirmed Lost = true, not yet closed] --> B{Non-renewal Reason set?}
    B -->|Yes| C[Set stage = Closed Lost]
    C --> D[Copy reason to Closed Lost Reason]
    D --> E[Notify deal owner]
    B -->|No| F[Create task: add reason first]
action or delay branch public on every spec, paid or not

When to use it, when not to

  • UseUse it on renewal deals created by renewal-expansion-001 or built manually, once a rep or CSM has a confirmed non-renewal to record.
  • UseUse it to keep forecast and pipeline reports honest: an open renewal deal for an account that already told you no is a forecasting risk, not a pending opportunity.
  • SkipDo not use it to guess at non-renewal from inactivity alone. This workflow reacts to an explicit confirmation field, not to silence or a missed close date.
  • SkipDo not use it on new-business deals. It is scoped to Deal Type equal to Renewal.
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.5 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 renewal and expansion 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.