skills/territory-transition-planner/SKILL.md
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.
npx skillsauth add stephenrogan/csm-skills territory-transition-plannerInstall 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.
Builds the 30-60-90 day plan for a CSM taking over a new book. The first 90 days on a new portfolio determine your success for the next 12 months. This skill structures that critical period so nothing falls through the cracks and the most important accounts get attention first.
Provide:
Goal: Identify and protect the accounts that cannot wait. Build the foundation for the rest.
Priority 1: Immediate attention accounts These need your engagement in week 1:
Priority 2: High-value accounts These need introduction in weeks 2-3:
Priority 3: Stable portfolio These can wait until month 2:
Actions for Days 1-30:
| Action | When | Purpose | |--------|------|---------| | Read every account brief / CRM note for Priority 1 accounts | Week 1 | Cannot engage without context | | Introduction emails to all Priority 1 and 2 accounts | Week 1-2 | Establish yourself as the new contact | | Deep-dive calls with Priority 1 accounts | Week 2-3 | Understand their current situation from their perspective, not just from CRM notes | | Knowledge transfer sessions with outgoing CSM (if available) | Week 1-2 | Get the context that is not in the system: relationship dynamics, political landscape, personal preferences | | CRM audit of your book | Week 2-3 | Verify data accuracy. Outgoing CSM's notes may be outdated | | Identify single-threaded accounts | Week 3-4 | Know where your biggest relationship risk sits |
Deliverable at Day 30: You have personally engaged every Priority 1 account, introduced yourself to every Priority 2 account, and have a complete picture of your book's health, risks, and opportunities.
Goal: Build genuine relationships beyond the introduction. Establish your cadence.
Actions for Days 31-60:
| Action | When | Purpose | |--------|------|---------| | First substantive touchpoint with all Priority 2 accounts | Week 5-6 | Move past introduction to actual partnership | | Introduction to Priority 3 accounts | Week 5-8 | Complete coverage | | Establish regular cadence for all accounts | Week 5-8 | Set the rhythm that will sustain the book | | Identify and begin multi-threading on single-threaded accounts | Week 6-8 | Reduce relationship concentration risk | | First QBR or business review you lead | Week 6-8 | Prove you can deliver value, not just introduce yourself | | Success plan review with top 10 accounts | Week 5-7 | Validate or rebuild the success framework the outgoing CSM had |
Deliverable at Day 60: You have a relationship (not just a name) with the primary contact at every account. You are running your own cadence, not inheriting someone else's.
Goal: Shift from reactive management to proactive strategy. Identify where you can create the most value.
Actions for Days 61-90:
| Action | When | Purpose | |--------|------|---------| | Build 90-day strategic plans for your top 5 accounts | Week 9-10 | Move from "managing the book" to "growing the book" | | Identify expansion opportunities across the portfolio | Week 9-10 | Start building your commercial pipeline | | Assess where your book's adoption gaps are | Week 10-12 | Identify where customers are leaving value on the table | | Have the first honest conversation with your manager about your book | Week 10-12 | Share what you have learned, what you are worried about, and what you need | | Identify 2-3 accounts where you can deliver a quick win | Week 9-10 | Build confidence and momentum with early results |
Deliverable at Day 90: You own the book -- not just manage it. You have strategic plans for the highest-value accounts, a pipeline of expansion opportunities, and a clear view of where your time creates the most impact.
For initial account prioritisation:
| | Renewal < 90 days | Renewal 90-180 days | Renewal 180+ days | |---|---|---|---| | At Risk / Critical | Immediate -- protect revenue | This month -- investigate and intervene | Monitor closely -- early intervention | | Healthy | Engage within 2 weeks -- prepare for renewal | Introduce by month 2 -- standard cadence | Introduce by month 2-3 -- standard cadence | | Strong | Engage within 2 weeks -- renewal should be smooth | Introduce by month 2 -- look for expansion | Schedule for month 2-3 -- lowest urgency |
If the outgoing CSM is available, cover these in your sessions:
| Topic | What to Ask | Why It Matters | |-------|-----------|---------------| | Relationship dynamics | "Who is the real decision-maker? Not on paper -- who actually decides?" | CRM titles do not capture political reality | | Communication preferences | "Does this customer prefer email, calls, or Slack? Formal or casual?" | Matching their style from day one signals competence | | History that matters | "What happened that I need to know about but is not in the CRM?" | Every account has unlogged context that shapes the relationship | | Landmines | "What should I avoid? Any sensitive topics, past failures, or ongoing frustrations?" | Stepping on a landmine in your first call erases all goodwill from the introduction | | Quick wins | "Where is the easiest opportunity to demonstrate value in my first 30 days?" | Early wins build confidence with the customer and with your manager | | Personal details | "Anything personal I should know? Family, hobbies, communication quirks?" | Personal connection accelerates relationship building |
## Territory Transition Plan: [CSM Name]
**Accounts:** [Count] | **Total ARR:** [Amount] | **Start Date:** [Date]
### Triage Classification
| Priority | Accounts | ARR | Key Events |
|----------|----------|-----|-----------|
| Immediate | [count] | [ARR] | [renewals, escalations, QBRs] |
| High-value | [count] | [ARR] | [expansion, strategic] |
| Standard | [count] | [ARR] | [stable] |
### Days 1-30 Action Plan
[Prioritised action list with dates]
### Days 31-60 Action Plan
[Relationship building actions]
### Days 61-90 Action Plan
[Strategy and optimisation actions]
### Knowledge Transfer Notes
[Key context from outgoing CSM]
### Review Dates
Day 30 review: [date]
Day 60 review: [date]
Day 90 review: [date]
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 mutual success plan with the customer that defines what success looks like, how it will be measured, who is responsible, and what the timeline is. Produces a shared document that both sides reference throughout the engagement. Use when asked to create a success plan, build a customer outcome framework, define success criteria with a customer, structure mutual goals, or when a CSM needs to align with a customer on what they are trying to achieve together. Also triggers for questions about success planning, outcome definition, customer goal alignment, mutual accountability frameworks, or how to ensure both sides know what success looks like.