Renew & Expand Account — renewal path and expansion, handled¶
Renewal path chosen explicitly, expansion opportunity framed commercially, or non-renew branch handled gracefully
The term is ending. And nobody has decided what happens next.
- Area: Sales & Clients
- Time savings: Typical run: 2-4 hours across prep, decision, and conversation follow-through
- Try it: "End of term approaching, continuity decision needed, or account shows credible expansion potential"
- Compounding: Each run refines templates and context — 5 automated steps improve with accumulated data
- Frequency: Per opportunity
- Published: 2026-06-29
Inputs¶
- 🏢 Client name and
client-id - 📋 Contract / renewal timing or milestone timing
- 📋 Current service scope
- 📝 Known renewal risk or expansion opportunity, if any
- 📋 Revenue at stake and strategic importance
What BOB does¶
- vault-preflight → verify client context completeness and confirm there is enough commercial context to make a continuity decision
- client-health-tracker → produce current health snapshot, including at-risk and expansion signals
- retention-check → prepare the renewal-readiness brief: value delivered, satisfaction pattern, renewal recommendation, and explicit risks
- Review readiness — decide whether the account is currently in one of three states:
renew,renew-expand, ornon-renew-risk - client-ascension → if state is
reneworrenew-expand, produce the continuity path: ascension map, renewal / expansion script, and recommended commercial structure - Review continuity path — decide the commercial ask: renew as-is, renew with expansion, restructure, or hold
- Conduct the renewal / expansion conversation or prepare the package for the account owner
- meeting-intelligence → debrief the continuity conversation: objections, stakeholder signals, pricing pressure, and next-step commitments
Outputs¶
- 📋 Renewal Readiness Brief.md
- 📁 Expansion Path Recommendation.md
- 📝 Renewal / Expansion Conversation Script.md
- 📋 Decision Log.md
- 📋 If no-renew: Offboarding Branch.md