The Workflow Library

Library / Renewal and expansion / renewal-expansion-020

Multi-year contract mid-term check-in task

Renewal and expansionDealSales Hub ProfessionalSimple~25 min to buildFull spec

Outcome. A deal owner gets a check-in task at the halfway point of any multi-year renewal contract, so a two- or three-year deal does not go silent between signature and its eventual renewal date.

Workflow map Enrollment, branches and actions at a glance renewal-expansion-020
flowchart TD
    A[Deal Closed Won, term 24+ months, check-in not completed] --> B[Calculate and set Mid-term Check-in Date]
    B --> C[Wait until check-in date]
    C --> D{Check-in already completed?}
    D -->|No| E[Create task for deal owner]
    E --> F[Notify deal owner]
    D -->|Yes| G[No action]
action or delay branch public on every spec, paid or not

When to use it, when not to

  • UseUse it on any Closed Won renewal or new-business deal with a contract term of 24 months or longer.
  • UseUse it as a lightweight relationship touchpoint, separate from the executive business review cadence in renewal-expansion-024, which targets the period right before renewal rather than the middle of the term.
  • SkipDo not use it on month-to-month or annual contracts. A 12-month or shorter term does not need a mid-term milestone; renewal-expansion-002's reminder cascade already covers the run-up to those renewals.
  • SkipDo not use it if Contract Term Months is not populated on the deal; there is no midpoint to calculate without it.
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.3 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.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.