renewal-and-expansion-enablement

name	renewal-and-expansion-enablement
description	Build renewal and expansion plays for customer-facing teams. Use when the user asks for renewal motions, save plays, expansion qualification, health signals, or post-sale inspection. For QBR/EBR narrative outputs, use qbr-ebr-builder.

Renewal And Expansion Enablement

Create repeatable post-sale plays that connect adoption, value realization, and growth outcomes.

Confirm Inputs First

Confirm these minimum inputs:

• Whether a current revenue-enablement-context exists; if yes, use it as baseline assumptions, if no, capture only the highest-impact missing context.
• Business model and contract model (annual, multi-year, usage-based)
• Target segments and ownership model (CSM, AM, hybrid)
• Current renewal and expansion performance baseline
• Available product-usage and adoption signals
• Commercial governance states (legal, procurement, pricing approvals, deal desk)
• Common risk patterns and expansion blockers
• Desired reporting horizon (quarterly, half-year, annual)

If critical items are missing, ask for the smallest missing set or proceed with assumptions labeled in the output.

Read The Right Reference

• Read references/renewal-expansion-framework.md before defining lifecycle plays, qualification, and manager checkpoints.

Default Workflow

1. Define the renewal and expansion windows by segment. Set the timeframes when each motion starts, who owns it, and what counts as late.

2. Separate save motions from growth motions. Define the signals that indicate retention risk versus whitespace or expansion potential.

3. Build the signal map. Use adoption, product usage, stakeholder coverage, outcome attainment, and commercial timing as the core inputs.

4. Design the plays. Write specific plays for healthy renewals, at-risk renewals, and expansion opportunities.

5. Add talk tracks and next actions. Give CS, AM, Sales, and Support a clear playbook for what to say and do next.

6. Add commercial guardrails. Define discount authority, deal desk handoffs, legal/procurement states, and exception rules.

7. Define manager inspection points. Set weekly and monthly review prompts, owner follow-up, and escalation triggers.

8. Operationalize the cadence. Lock ownership, reporting cadence, and handoff rules into the team workflow.

Tool Notes

• Tool-agnostic default: run from account plans, renewal lists, and meeting cadences.
• Optional tools: CRM, CS platforms, and product analytics can automate risk and opportunity flags.
• Keep logic portable so teams with low tooling maturity can still execute.

Output Contract

Default output includes:

• Renewal and expansion play matrix by segment
• Risk and expansion trigger map
• Product-usage and adoption signal map
• Commercial governance-state map with owner by state
• Role-based talk tracks and action prompts
• Manager inspection checklist and cadence
• KPI set with baseline and target recommendations

Quality Bar

• Plays are tied to measurable account signals, not generic account management advice.
• Roles, handoffs, and escalation points are explicit.
• Inspection criteria are concrete and repeatable.
• Recommendations reflect real commercial constraints.
• Usage and adoption signals are translated into specific plays.
• Output supports immediate team rollout.