Skip to content

Champion departure detected triggers renewal risk flag

One of 565 written HubSpot workflow specs, by a collective of independent HubSpot consultants.

Professional

Seat pricing: Professional edition. To build it, a GTM Seat or an Ops Seat (an Ops Seat cannot create marketing emails or sequences). Per-hub plans: Sales Hub Professional.

Contact4 stepsUpdated for HubSpot seat pricing
OutcomeWhen the primary internal champion at an account shows signs of having left the company, the associated account gets flagged for renewal risk and the deal owner is notified, instead of the departure going unnoticed until the renewal conversation itself.
Workflow maprenewal-expansion-027
Champion = true, email hard bounce reason populates leads to Set Champion Departure Suspected = true. Set Champion Departure Suspected = true leads to Set company Renewal Risk Flag = true. Set company Renewal Risk Flag = true leads to Create high-priority verification task. Create high-priority verification task leads to Notify deal owner. Champion = true, email hard bounce reason populates Set Champion Departure Suspected = true Set company Renewal Risk Flag = true Create high-priority verification task Notify deal owner
Champion = true, email hard bounce reason populates leads to Set Champion Departure Suspected = true. Set Champion Departure Suspected = true leads to Set company Renewal Risk Flag = true. Set company Renewal Risk Flag = true leads to Create high-priority verification task. Create high-priority verification task leads to Notify deal owner. Champion = true, email hard bounce reason populates Set Champion Departure Suspected = true Set company Renewal Risk Flag = true Create high-priority verification task Notify deal owner

One of 565 written HubSpot workflow specs, by a collective of independent HubSpot consultants.

When to use it, when not to

Use it

  • Use it on contacts explicitly marked as a champion, where an email hard bounce with a departure-style reason is the practical signal HubSpot can detect natively.
  • Use it as an early warning, not a confirmed fact. A hard bounce suggests a departure; it does not confirm one, and this workflow's task step is there specifically to get a human to verify it.
Read more on when to use itShow less

Skip it

  • Do not use it as the sole way departures are tracked. Sales conversations and account notes are often the first place a departure surfaces; the flag on a checkbox depends on that being logged.
  • Do not use it on contacts who are not marked as a champion. Any contact's email can hard bounce for unrelated reasons, and flagging renewal risk on every bounce would be noise.
Read more on when to skip itShow less

The rest of this spec

Prerequisites · 4 items

Every property with its label, internal name, type and options, plus the assets the workflow needs.

Enrollment · 4 parts

The trigger, the criteria as ticked in the UI, the re-enrollment rule and the suppression list.

Steps · 4 numbered actions

Each action in order with its parameters, branches and delays.

Known pitfalls · 5

Traps seen in production, each with what breaks and what to do instead.

Test plan and UAT script · 2 cases, 3 variants

How to prove it works in a test portal, one case per branch, and a sign-off sheet.

Files · PDF, Markdown, JSON, CSV

The properties JSON creates the fields in one call. The workflow JSON documents the build.

Install · 1 click, switched off

The installer creates the properties and the workflow, switched off, then opens a task for what it cannot create. Nothing is deleted, enabled or enrolled.

Unlock all 565 specs, 149 EUR

One-time, excl. VAT. 30-day refund. Installs in 3 portals. Founding price until 30 November.

Read the free Renewal and expansion spec

Read 12 complete specs before you pay.

One per category, same format as the paid ones. Email only, no card.

We email the link, then a short note when specs change. Nothing else.

149 EUR199

Full library, 565 specs
Get the full library