Your First 30/60/90 Days as a New CSM

It's day 8. You inherited 25 accounts from a CSM who left for a competitor. You've never spoken to any of them. Three are flagged red in the health dashboard. One escalated to your VP this morning, and the email thread has 14 replies you don't fully understand. You don't know the product well enough to answer their question, and you don't know the account well enough to know why they're angry.

Welcome to customer success.

When I picked up my first book, the handover doc was a Confluence page with seven of 25 accounts described as "great customer, expanding." Two months later one of those "great customers" churned. In the exit call I learned they'd been threatening to leave for six months. Nobody had told me, or the previous CSM either.

This guide is built around that reality.

Why CS Ramp Is Harder Than Other GTM Ramps

A new sales rep starts with a clean pipeline. A new support agent picks up tickets one at a time. A new CSM inherits live relationships built by someone else, with all the promises, grudges, side deals, and unwritten context that came with them.

You can't reset. The renewal clock doesn't pause for your ramp, and neither does the "quietly evaluating a competitor" clock nobody told you was running. Your job in the first 90 days isn't to invent strategy. It's to catch up to where the relationships already are, then move them forward.

Days 1–30: Learn the Inputs

The first 30 days are about absorbing inputs, not generating outputs. You'll be tempted to start "adding value" in week one. Resist it. The value you add in week one is almost always wrong, because you don't yet know what these specific accounts care about.

Master the product to demo-ready depth

You need to run a demo blindfolded by end of week three. Not because you'll demo to existing customers (you won't, much), but because customers will ask product-specific questions, and "let me get back to you" is the wrong answer four times in a row.

Block 10–12 hours a week for product immersion in weeks 1–3. Build something yourself. Break it. Ask a product manager to walk you through the three features that get the most edge-case questions.

Read the inputs from sales and RevOps

Before you talk to any customer, you should know the official ICP, the deal sizes and segments your book covers, the top 3 reasons deals close and lose in your segment, and the product roadmap themes for the next two quarters.

Schedule 30 minutes each with the lead AE who covers your segment, a sales engineer, and someone in RevOps. These three conversations are higher-leverage than any internal training deck.

Schedule intros with all 25 accounts

Yes, all of them, including the quiet green ones. Especially those, actually. Quiet green accounts are where churn lives, because nobody's been paying attention.

25 intro calls in 30 days is about 6 per week. Block them in the first two weeks of your calendar before anything else fills up. The accounts you put off until week 4 are the ones you'll still be putting off in week 8.

Before each intro call: account-discovery checklist

Read these items in this order before every single intro call. No exceptions, even when you're behind on prep:

Contract terms: what they bought, what tier, term length, renewal date, custom commitments
Original sales notes: what problem they were solving, who was the economic buyer, what objections sales handled
Last 3 QBRs (if they exist): what was committed, what landed, what slipped
Open and recent tickets: last 90 days, especially anything escalated or still open
Usage trend: up, flat, or down over the last 90 days, and which features
Exec map: champion, economic buyer, user, skeptic

If any of these are missing or unclear, that's also a finding. Note it.

Intro-call agenda (15–20 minutes)

You don't need 60 minutes for an intro call. You need 15–20, used well:

"Hi, I'm [name], I'm taking over as your CSM from [previous]. I have four questions: What's working well that I shouldn't accidentally break? What's not working? What would great look like in the next 90 days? Who else on your team should I know?"

Four questions. Don't pitch. Don't explain the new feature you saw in product training. Don't promise anything. Just listen.

The biggest mistake new CSMs make is treating intro calls as status updates instead of discovery. You have permission in week 2 to ask basic questions you'll never get permission to ask in month 6.

Build a personal account map

By end of week 4, you should have one row per account with: champion, economic buyer, primary use case, biggest risk, biggest expansion opportunity, last contact date. Update it weekly. If you can't fill in all six fields for an account by week 4, that account tops week 5's call list.

Days 31–60: Deepen and Diagnose

By day 30 you've met everyone. Now the work shifts from discovery to diagnosis.

From intro calls to working sessions

Intro calls were 15–20 minutes of listening. Working sessions are 30–45 minutes focused on something specific the customer mentioned: a use case they want to expand, a feature they're stuck on, a metric they're trying to move.

A useful rule: every customer should leave a month-2 conversation with one concrete next step that you own. Not them. That's how you start being useful instead of just present.

Run the churn-risk triage on every account

By end of week 8, scan every account against six churn-risk signals. Score each red/yellow/green:

Usage drop: are weekly active users or core-feature usage down vs. 90 days ago?
Champion change: has your champion left, changed roles, or gone quiet?
Escalation pattern: more than one escalated ticket in the last 90 days?
Value gap: is the customer using less than 60% of what they're paying for?
Exec disengagement: has the executive sponsor missed the last two QBRs or stopped replying?
Competitor mentions: has a competitor's name come up in any call, ticket, or email in the last 90 days?

Three or more reds means churn-risk territory and an action plan logged this week. One red plus one yellow is a watch-list account. The triage doc gets updated monthly for the rest of your tenure on the book.

Spot expansion signals too

On a healthy book, expansion is where NRR comes from. Scan for: new use cases mentioned, new teams using the product, adjacent pain points the customer brings up unprompted, hiring growth, and the champion getting promoted.

Expansion signals decay fast. A customer who mentions a second use case in March and gets ignored will have built a workaround by June.

Shadow your peers and build internal relationships

Pick the two best CSMs on your team and sit in on three of their QBRs each. Not to copy their style. To see how they handle the awkward moments: "this isn't working," the exec who clearly doesn't remember why they bought the product, the defensive champion when usage is down. Sitting in three live QBRs is worth more than 50 articles about them.

Then go wider. The AE who sold the account knows things no CRM field will ever capture: side deals, verbal commitments, which exec was a no on the original deal. The support engineer who triaged your customer's last six tickets knows whether they're a healthy power user or a serial complainer.

Buy them coffee. Ask what they'd want a CSM on this book to know. Most of the answer isn't in any system. This relational work pays off most when an account goes red. The CSMs who save the most accounts can mobilize a sales engineer, a PM, and an exec sponsor in 48 hours because they invested before the fire started. Avoiding the CSM Firefighting Trap goes deeper on the operating model that makes this scalable instead of reactive.

Days 61–90: Own the Outcomes

By day 60 you've met everyone, you've diagnosed the book, and you've started being useful in working sessions. Day 61–90 is when you start owning real outcomes.

Run your first solo QBR

Pick a stable, friendly account for your first solo QBR. Not the easiest one, the one where you're confident enough to handle a curveball. Prep it three times harder than you think you need to. Send the deck the day before. Have a clear ask: a renewal commitment, an expansion conversation, or a champion intro to one more team.

By your third solo QBR you should be running it as a working session, not a presentation.

Execute your first save play

By day 90, at least one red account should have moved to yellow because of something you specifically did. Not because the situation improved on its own. Because you intervened.

A save play: identify the root cause (champion turnover, low adoption in one team, a feature gap with a workaround nobody showed them), run a structured intervention (exec sponsor reset, adoption workshop, custom training), and measure the change in the next 30-day window. The first save is the hardest. Once you've done one, you have a template.

Contribute to NRR

By end of day 90, you should have at least one of: a renewal saved that was at risk, an expansion signed (even small), or a churn prevented and documented in your save log. NRR on your book should be flat at minimum, ideally positive.

You should also know which renewals are coming up in the next 90 days and which need an intervention now. The renewal 60 days out gets an intervention this week, not next month. For the metrics behind all this, CSM Metrics That Matter: NRR, GRR, and Health Scores is the one I send every new CSM I onboard.

Define your personal cadence

Decide how often each tier of account gets a touch:

Tier 1 (top 5–7 accounts): Bi-weekly working session, monthly exec check-in, quarterly QBR
Tier 2 (mid-book, 10–12 accounts): Monthly working session, quarterly QBR
Tier 3 (remainder): Quarterly check-in, ad-hoc on signals

CSMs without a cadence default to whoever's loudest, which means the squeaky-wheel account gets eight hours of your week and the quiet expansion opportunity gets zero. The day-to-day texture of running this cadence is in A Day in the Life of a CSM.

Present your book strategy to your manager

End of day 90: a 30-minute readout to your manager covering (1) triage summary with red/yellow/green rationale, (2) top 3 churn risks and your plan, (3) top 3 expansion opportunities, (4) NRR forecast for the next 90 days, (5) what you need from product, sales, or support to hit it.

Most new CSMs don't do this, and most managers don't ask. The ones who do it anyway get the next promotion conversation 6 to 12 months earlier than peers.

If any of your 25 accounts is in its first 90 days post-sale, your save-play playbook overlaps with onboarding. The deeper breakdown of that adjacent motion is in Customer Onboarding: The First 30 Days That Drive NRR, which most new CSMs find more useful in month 2 than month 1.

Common Pitfalls to Avoid

Overpromising in week 1 to be liked. "Yes, I'll get that fixed by Friday." You can't. You don't know the engineering backlog yet, and now you've burned trust on day 4. Replace it with: "I want to understand this before I commit. I'll come back within a week with a real answer."

Ignoring red accounts because they're scary. Red accounts don't get less red on their own. The instinct to start with friendly green accounts and "build confidence" is wrong. Pick one red account in week 2 and call them. It will go badly. It still helps.

Treating intro calls as status updates. Discovery in week 2 is free. Discovery in month 6 is awkward. Use the early window.

Living in the dashboard instead of in customer conversations. Health scores are a map, not the territory. A green score on an account whose champion just got laid off is a lagging indicator about to flip.

Forgetting your own ramp goals. You're so focused on the customer's situation that you forget your manager also has expectations of you. Schedule a weekly 15-minute check-in from week 1.

Success Metrics by Week

Concrete, measurable checkpoints:

By week 4

Account-coverage rate: real conversation (not email) with every one of your 25 accounts
Account map filled in for at least 20 of the 25 accounts
Demo-ready in the product

By week 8

Can name from memory each account's primary use case, champion, biggest risk, biggest expansion opportunity
Churn-risk triage complete for all 25 accounts
At least 3 customer working sessions logged with concrete next steps

By week 12

First save logged (a red moved to yellow, with documented intervention)
First solo QBR run
NRR delta on your book at minimum flat, ideally positive
Book strategy readout delivered to your manager

Soft signals you're tracking well

Your AE partners proactively loop you into deals
Customers ask for you by name when they email support
Your manager stops checking your account list daily

How Rework Supports a New CSM's Ramp

A new CSM juggles three surfaces in their first 30 days: an account-discovery log, a churn-risk triage doc, and a cadence calendar. Most ramp in spreadsheets that don't talk to the CRM and sticky notes that don't sync to QBR prep. Rework CRM gives you one surface for the customer relationship, so the next CSM doesn't inherit a Confluence page with seven one-line summaries. Pair it with Rework Work Ops to track save plays and cadence as real tasks with owners and dates, so the bi-weekly Tier-1 touch doesn't drift into "whenever I get to it." CRM starts at $12/user/month, Work Ops at $6/user/month.

What Comes After Day 90

Day 91 isn't a finish line. It's the start of the part of the job where customers expect you to know what you're doing. By day 90 you have a working operating model: a triage cadence, a save-play playbook, a QBR rhythm, and an internal network. The rest of the year is iterating on those four things while running the book.

The CSMs who plateau at the 12-month mark stop refreshing their inputs. The triage doc from day 60 is stale by day 180 if you don't redo it. The account map from week 4 is fiction by month 9 if you don't update it.

If you're earlier in the journey, still interviewing or benchmarking the role, the Customer Success Manager job description template gives a clean view of what the job is on paper, before 25 inherited accounts make it personal.

The best CSMs aren't the ones who walked in knowing everything. They're the ones who walked in admitting they didn't, and built their ramp around catching up.

Customer Success Manager Playbooks