agentleFS
stephenroganstephenrogan/csm-skills/skills/territory-transition-planner/SKILL.md

territory-transition-planner

Skill0 starsChanged 8 months agoMITView on GitHub

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.

The file

We split this skill into the rules it gives an agent

1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    If the outgoing CSM is available, cover these in your sessions:

    line 106

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Territory Transition Planner

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.

How to Use

Provide:

  • Your new book of accounts (names, ARR, health if known, renewal dates)
  • What handoff materials exist (account briefs, CRM notes, outgoing CSM context)
  • Upcoming critical events (renewals in next 90 days, active escalations, scheduled QBRs)
  • Your capacity (how many accounts, what segment, do you have other responsibilities during ramp?)
  • Whether an outgoing CSM is available for knowledge transfer (and for how long)

The 30-60-90 Framework

Days 1-30: Triage and Protect

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:

  • Accounts renewing in the next 60 days (you must own the renewal conversation)
  • Accounts with active escalations or open P1/P2 tickets (customers in pain)
  • Accounts flagged as at-risk or critical by the outgoing CSM
  • Accounts with scheduled QBRs or executive meetings in the next 30 days

Priority 2: High-value accounts These need introduction in weeks 2-3:

  • Top 10 accounts by ARR (your highest-value relationships)
  • Accounts with active expansion opportunities
  • Strategic accounts (logo value, reference potential, board-level visibility)

Priority 3: Stable portfolio These can wait until month 2:

  • Healthy accounts with no upcoming events
  • Accounts with a recent touchpoint from the outgoing CSM

Actions for Days 1-30:

ActionWhenPurpose
Read every account brief / CRM note for Priority 1 accountsWeek 1Cannot engage without context
Introduction emails to all Priority 1 and 2 accountsWeek 1-2Establish yourself as the new contact
Deep-dive calls with Priority 1 accountsWeek 2-3Understand their current situation from their perspective, not just from CRM notes
Knowledge transfer sessions with outgoing CSM (if available)Week 1-2Get the context that is not in the system: relationship dynamics, political landscape, personal preferences
CRM audit of your bookWeek 2-3Verify data accuracy. Outgoing CSM's notes may be outdated
Identify single-threaded accountsWeek 3-4Know 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.

Days 31-60: Depth and Relationship Building

Goal: Build genuine relationships beyond the introduction. Establish your cadence.

Actions for Days 31-60:

ActionWhenPurpose
First substantive touchpoint with all Priority 2 accountsWeek 5-6Move past introduction to actual partnership
Introduction to Priority 3 accountsWeek 5-8Complete coverage
Establish regular cadence for all accountsWeek 5-8Set the rhythm that will sustain the book
Identify and begin multi-threading on single-threaded accountsWeek 6-8Reduce relationship concentration risk
First QBR or business review you leadWeek 6-8Prove you can deliver value, not just introduce yourself
Success plan review with top 10 accountsWeek 5-7Validate 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.

Days 61-90: Strategy and Optimisation

Goal: Shift from reactive management to proactive strategy. Identify where you can create the most value.

Actions for Days 61-90:

ActionWhenPurpose
Build 90-day strategic plans for your top 5 accountsWeek 9-10Move from "managing the book" to "growing the book"
Identify expansion opportunities across the portfolioWeek 9-10Start building your commercial pipeline
Assess where your book's adoption gaps areWeek 10-12Identify where customers are leaving value on the table
Have the first honest conversation with your manager about your bookWeek 10-12Share what you have learned, what you are worried about, and what you need
Identify 2-3 accounts where you can deliver a quick winWeek 9-10Build 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.

Triage Matrix

For initial account prioritisation:

Renewal < 90 daysRenewal 90-180 daysRenewal 180+ days
At Risk / CriticalImmediate -- protect revenueThis month -- investigate and interveneMonitor closely -- early intervention
HealthyEngage within 2 weeks -- prepare for renewalIntroduce by month 2 -- standard cadenceIntroduce by month 2-3 -- standard cadence
StrongEngage within 2 weeks -- renewal should be smoothIntroduce by month 2 -- look for expansionSchedule for month 2-3 -- lowest urgency

Knowledge Transfer Checklist

If the outgoing CSM is available, cover these in your sessions:

TopicWhat to AskWhy 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

Output Format

## 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]

Quality Gates

  • Are the highest-risk accounts identified and scheduled for week 1? Any renewal under 60 days or active escalation that you do not personally engage in week 1 is a potential loss
  • Is the knowledge transfer captured in writing? Verbal-only knowledge transfer evaporates within days. Write it down
  • Is the plan realistic given your capacity? A 50-account book cannot be deeply engaged in 30 days. The triage matrix ensures you focus where it matters most, not where it is easiest
  • Does the Day 90 deliverable set you up for the long term? A transition plan that ends at Day 90 with "now manage the book" is incomplete. It should end with strategic plans, an expansion pipeline, and a cadence

Principles

  • The first 30 days are about protection, not impression. Do not try to be brilliant in month one. Try to be reliable. Show up, follow through, remember what was said. Brilliance comes in month three
  • Customers do not want a new CSM. They want continuity. Your job is to provide continuity with a fresh perspective -- honour what was built before you while bringing your own judgment
  • The outgoing CSM's assessment is a starting point, not the truth. They may have optimistic views of accounts they liked and pessimistic views of accounts that frustrated them. Form your own assessment by day 30
  • Speed of introduction matters. Every day without a CSM is a day the customer feels unowned. Even a brief email on Day 1 -- "I am your new CSM, I will be in touch within a week with a proper introduction" -- closes the gap

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.