Hey {{first_name | CS Pro}},
The day you sign an offer letter with an NRR target on it, your entire career changes.
You are no longer paid to make customers happy, you are paid to make a number move.
And those renewals landing in your first quarter? They were won or lost months before you ever walked in the door.
This week I am handing you the operating plan I wish someone had given me the first time I owned a retention number. What to do in your first 30 days, your first 60, and your first 90. The four mistakes I watch new CS leaders make again and again, including the one that drained my credibility in front of a CFO during my second week in seat. And the exact system I built to dig myself back out of it. So keep reading, because whether you have just landed the VP seat, you are interviewing for one, or you are a CSM who wants to understand how your leader thinks, this one is your playbook.
But first, today’s sponsor
↓
When to build AI agents, when to buy, and how to sequence both
Most CS teams have proven they can adopt AI. The harder question is operationalizing it. Knowing when to build custom agents, when to buy pre-built ones, and how to sequence both without stalling.
Gainsight built a practical guide on exactly that.
Download the guide to learn about:
The three stages CS teams move through to operationalize AI
The warning signs that a custom agent is adding technical debt instead of results
Where pre-built analyst agents close the gaps first: handoffs, risk, expansion
The scoreboard was written before you arrived
Two numbers should make every CS leader sit up.
➡ The chief customer officer is the youngest seat in the C-suite, with an average tenure of just 29 months, and data floating around LinkedIn puts VPs of CS even lower, around 18 months. My own last two VP roles ran two years and 18 months.
➡ Meanwhile, benchmark data from more than 2,000 SaaS companies puts median net revenue retention at 106%, with best in class running 130 to 135%. Anything under 100% means your company is shrinking before sales books a single new logo.
Put those together and you have about two years to move a number you did not create.
It reminds me of football, and since I live in London, I mean actual football. (Soccer for my Americans reading). ⚽
A manager hired mid-season inherits the squad, the injuries and the league position, but from day one the results sit on their record. That is the VP of CS seat. NRR is a lagging indicator, so it is the final score of a game that started long before you showed up.
The four mistakes I keep seeing (and made myself)
Accepting the number without doing the math yourself. Companies calculate NRR wildly differently... trailing 12 months or annualized monthly, contraction at renewal or every downgrade, professional services in or out. I have watched leaders present retention wins and get corrected by finance in the room. That is career damage you never recover from.
Boiling the ocean. New leaders launch everything at once: health scores, a new CS platform, resegmentation, comp plans, playbooks. That is activity, and NRR does not respond to activity. It responds to two or three levers pulled hard and consistently.
Operating like a super CSM instead of an operator. You got the seat because you are brilliant with customers, so you keep jumping into every escalation. That is your team's job, and nobody else will build your retention operating system.
Letting other people write your narrative. Stay silent for 90 days and sales decides CS is a cost center, finance builds its own version of your metric, and your CEO wonders who they hired. Say it out loud early: I am here to protect and grow revenue to 120% NRR through renewals and upsell motions.
The operating plan
In my second week in seat, my CFO asked for my renewal forecast for the quarter. I gave the classic CS answer. Relationships are strong, sentiment is high, I feel really good about it.
Then a sales leader said 92% to commit with two deals at risk worth $500,000. Nobody was unkind, which was almost worse, they simply moved on to the people with numbers.
Here is what I built. I rebuilt the number by hand with the finance manager, line by line, and found my dashboard and my CFO's spreadsheet were not the same model. I ran a listening tour with structure: my top 10 accounts by ARR, every CSM naming which accounts worried them, and my CRO, CFO and VP of Product on what CS needed to do to hit their numbers. I walked my CEO through the churn already baked into the book, so when it landed six months later it was a known event, not a surprise on my record. I put three meetings in the calendar and never cancelled them: a weekly renewal forecast run like a sales pipeline review, a weekly risk review, and a weekly expansion review. Then I picked two levers, onboarding time to value and multi-threading, and parked six other initiatives.
My team hated that forecast call at first. Six to eight weeks later they walked in with dollar amounts and probabilities instead of gut feel.
This week's challenge
Build your NRR bridge. One page: starting ARR, minus churn, minus downsell, plus expansion, equals ending ARR.
Break it out by segment and take it to finance to pressure test your math. \
If you are a CSM or team lead, do not wait for the title. Build it for your own book, then walk into your next meeting and say here is where my book is growing, here is where it is leaking, here is my plan. That conversation gets people promoted.
You do not inherit an NRR number. You earn it, forecast by forecast, with a system that works.
Have a listen to the full episode on Spotify, Apple Podcasts or YouTube.
I hope you enjoyed this week’s newsletter.
If you have any questions or suggestions, please feel free to contact us.
Cheers to your CS success,
Anika
