The Workflow Library

Library / Renewal and expansion / renewal-expansion-011

Renewal deal owner auto-assignment to current CSM/AM

Renewal and expansionDealSales Hub ProfessionalSimple~20 min to buildFull spec

Outcome. A renewal deal is owned by whoever currently manages the account, not whoever happened to be the deal creator or the original sales rep, the moment the deal is created.

Workflow map Enrollment, branches and actions at a glance renewal-expansion-011
flowchart TD
    A[Deal Type = Renewal, owner does not match company CSM Owner] --> B[Copy CSM Owner from company to deal owner]
    B --> C[Notify new deal owner]
action or delay branch public on every spec, paid or not

When to use it, when not to

  • UseUse it whenever renewal deals get created (manually, or by renewal-expansion-001) and the account's day-to-day owner is a CSM or AM tracked in a separate property from the original sales owner.
  • UseUse it as a companion to renewal-expansion-001; that fiche creates the deal, this one makes sure ownership is correct at creation and stays correct if the CSM changes later.
  • SkipDo not use it if the same person is both the original sales owner and the ongoing account manager. In that case the default deal owner is already correct and this workflow adds no value.
  • SkipDo not use it as a substitute for fixing incorrect CSM assignments upstream; this workflow copies whatever the CSM property says, it does not decide who the right CSM is.
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.2 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 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.