skills/renewal-conversation-opener/SKILL.md
Frames the initial renewal conversation by leading with value delivered, transitioning to forward-looking partnership, and anticipating likely objections based on account context. Produces multiple opening approaches calibrated to the account's health, relationship, and commercial situation. Use when asked to prepare for a renewal discussion, draft a renewal email, frame a renewal conversation, open a retention dialogue, or when a CSM needs to move from relationship management to commercial conversation. Also triggers for questions about renewal preparation, retention conversation strategy, renewal email drafting, or how to start the renewal discussion with a customer.
npx skillsauth add stephenrogan/csm-skills renewal-conversation-openerInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Frames the opening of the renewal conversation. The goal is not to "close" the renewal in one interaction -- it is to set the right tone, lead with value, and create the conditions for a productive commercial discussion.
The renewal conversation starts the moment the CSM first mentions renewal. That moment shapes the customer's framing of the entire process. Lead with what they have gained, not with what you are asking for.
Provide:
The skill produces 2-3 opening approaches because renewal conversations are not one-size-fits-all. The right approach depends on the relationship, the account health, and the commercial context.
Best for: Healthy accounts with strong value evidence. The renewal should be straightforward.
Structure:
Tone: Confident, consultative, forward-looking. The renewal is a natural continuation, not an event.
Example framing: "Your team saved an estimated 340 hours this quarter through automated workflows -- up 22% from last quarter. As we approach [renewal date], I wanted to discuss how we build on that momentum next year and make sure you have everything you need. Can we set aside 30 minutes next week to talk through the renewal and what the next 12 months could look like?"
Best for: Accounts where the relationship is strong but value evidence is thin. Or accounts where the personal relationship matters more than the data.
Structure:
Tone: Warm, relationship-first, collaborative. The renewal is a conversation about where you go together.
Example framing: "We have been working together for [X months/years] and I have genuinely valued the partnership -- especially [specific moment: launching the API integration, navigating the Q3 migration, supporting the team expansion]. With the renewal coming up in [X days], I would love to hear what your priorities look like for the next 12 months so we can make sure we are set up to support them. Can we schedule a conversation?"
Best for: At-risk accounts, accounts with known concerns, or accounts where addressing the elephant in the room is more credible than ignoring it.
Structure:
Tone: Honest, accountable, forward-looking. The renewal is a chance to get things right.
Example framing: "I know the last quarter has not been smooth -- the API performance issues affected your team's workflow and I understand the frustration. We have [specific action: deployed the fix, restructured your support escalation path, brought in a dedicated technical resource]. With the renewal in [X days], I want to have an honest conversation about where we stand and what we need to commit to for you to feel confident going forward. What would that conversation need to cover?"
Based on the account context, the skill identifies likely objections and prepares responses:
| Likely Objection | Trigger Signal | Prepared Response Framework | |-----------------|---------------|---------------------------| | "It is too expensive" | Budget pressure, pricing mentioned in prior conversations | Lead with value delivered (ROI > cost). Then explore: is it a budget issue or a value perception issue? Each has a different path | | "We are not using it enough" | Low adoption, underutilised features | Acknowledge the gap. Offer an adoption plan. Frame the renewal as the commitment to fix this, not a reward for the current state | | "We are looking at alternatives" | Competitive signals, evaluation language | Do not panic. Understand the trigger. Address the root cause, not the competitor | | "We need a discount" | Prior negotiation history, budget cycle timing | Establish value before discussing price. Ask what is driving the request. Never discount without understanding why | | "The timing is not right" | Budget cycle mismatch, internal reorganisation | Offer flexibility on timing (if your contract allows). The goal is renewal, not renewal on your preferred date | | "I need to involve [new person]" | Stakeholder change, champion departure | Good -- you want the decision-maker in the conversation. Ask for an introduction. Do not view this as a delay; view it as alignment |
| Situation | Channel | Why | |-----------|---------|-----| | Healthy account, straightforward renewal | Email opener, then call | Email sets the frame. Call has the discussion | | At-risk or complex renewal | Call first, then email to confirm | Difficult conversations should happen in real-time, not in writing | | Expansion included with renewal | Meeting (not just a call) | Expansion requires a proper discussion with data. A phone call is too brief | | Executive involved | Executive-to-executive outreach from your leadership, supported by your preparation | Executives respond to peers. Your prep arms your leader; their leader receives the outreach |
For each approach, the skill produces:
development
Structures the CSM's week based on their portfolio status, upcoming events, overdue items, and strategic priorities. Produces a time-blocked plan that balances reactive demands with proactive account management. Use when asked to plan a week, structure daily priorities, build a weekly schedule, allocate time across accounts, manage a busy week, or when a CSM feels overwhelmed and needs to determine where to focus. Also triggers for questions about time management, weekly planning, account prioritisation for the week, daily priority setting, or how to balance competing demands across a portfolio.
development
Constructs a compelling value narrative for a customer account by connecting product usage to business outcomes in the customer's language. Produces different versions for different audiences -- the champion, the CFO, the board. Use when asked to build a value story, articulate ROI, create a business case for the customer, prepare value evidence for a renewal or QBR, or when a CSM needs to translate usage metrics into business impact the customer will recognise. Also triggers for questions about value articulation, ROI storytelling, customer business case, value evidence, or how to prove the product is worth the investment.
data-ai
Takes raw usage data -- even a spreadsheet export or pasted metrics -- and identifies patterns, risks, and opportunities. Translates product analytics into account intelligence a CSM can act on. Use when asked to interpret usage data, analyse product metrics, make sense of a usage report, identify trends in customer behaviour, flag usage-based risks, or when a CSM has data but does not know what it means for the account. Also triggers for questions about usage analysis, product analytics interpretation, behavioural pattern detection, usage-based risk identification, or turning raw metrics into actionable insight.
development
Builds a structured 30-60-90 day plan for a CSM taking over a new book of accounts or joining a new team. Prioritises accounts by risk and value, identifies immediate relationship actions, and structures the ramp to full productivity. Use when asked to plan a book transition, create a new CSM onboarding plan, structure a territory takeover, build a 30-60-90 plan for a new role, or when a CSM is inheriting accounts and needs a systematic approach to getting up to speed. Also triggers for questions about account transitions, new book ramp-up, CSM onboarding to a portfolio, territory planning, or how to take over accounts from another CSM.