Quick Summary: The protection conversation — what you’re doing to defend revenue you’ve already earned — is where most CS teams are most exposed. Discover seven principles for defending revenue, reducing churn, and protecting the growth you generate, with ChurnZero VP of customer success Lukas Alexander.
Revenue protection, what you’re doing to defend the revenue you’ve already earned, is far more consequential than many leaders want to admit.
“Sales fills up the bucket. CS controls how fast it empties—and the more ARR you get, the more you have to lose,” says ChurnZero VP of CS Lukas Alexander.
If you’re not deliberate about stopping those leaks, the math will never work in your favor.
Lukas joined Jennica Dixon on Revenue Unscripted this month for an execution-level conversation on what actually drives revenue in complex B2B environments. Listen here, and scroll down for the top takeaways.
Seven customer success principles stood out from Lukas and Jennica’s conversation on revenue protection.
1. Recognize that competitors are always circling.
Collectively, your company’s instinct after closing a deal is to acknowledge the win, then shift to delivery mode. You should appreciate, however, that your competitors move into hunting mode at the same time.
“The moment you sign the contract,” Lukas says, “your best customer is listed on somebody else’s forecast.”
This reality should raise an immediate question for every CS team. If your top competitor called a customer tomorrow with a strong pitch, what would make them stay?
Any customer who hasn’t received real and visible value recently is liable to take that call seriously, which means that if the answer isn’t clear, the account isn’t protected. It’s simply quiet for now, which isn’t the same thing at all.
2. Implementation is a retention asset. Treat it like one.
The most durable defense of revenue is depth of implementation, which is also something that companies consistently get wrong.
“Where I see a lot of teams struggle is really investing in that upfront setup,” Lukas says. “That technical help is essential if customers are to crush the barrier to entry and get full value.”
The question he asks about every account: “Are the hooks in? Are the anchors in that make the product so hard to rip out that your customers will continue to renew?”
If your product demands significant technical guidance to deliver value, you need to invest in the roles that can provide it: technical account managers and implementation specialists. Letting CSMs carry it on their own is one of the most common failure points.
3. CSMs can’t be helpdesks and business partners simultaneously.
On the same note, don’t hire CSMs to own strategic relationships only to let them become the person a customer calls when something breaks. It’s more expensive than it might appear.
When a customer sees their CSM as a helpful troubleshooter, they don’t see them as a strategic advisor, and now the relationship is replaceable. At renewal time, a replaceable relationship becomes a negotiation over price, not value.
Lukas’s prescription: use AI to strip out the admin burden pulling CSMs toward operational firefighting, pair them with the right technical resources, and invest in training them as business partners.
“The best CSMs that companies will hire are going to be CSMs that possess the skills AI can’t replace,” he says. “Renewals, discovery, expansion negotiation, relationship building, or working with a procurement team.”
4. Quid pro quo works best in the long term.
Short-term quid pro quos are endemic in CS. References are traded for conference tickets. Case studies traded for service hours.
Long-term value exchanges have a more lasting impact in defending revenue. Take the example of a customer slightly over their user count, where the instinct might be for you to charge immediately.
“Should you ding them with these extra two users now,” Lukas asks, “or should you invest in that customer for the long term?”
Remember: the accounts that are hardest for your competitors to take are those with a long history of your team going to bat for the customer. To build that history, keep a long-term view.
5. Diagnose before you prescribe.
Jumping to answers before the real problem is visible is one of the most consistent revenue-protection failures Lukas sees at the CSM level.
“Imagine you went to the doctor,” he says, “and they just opened up all of the medication—the big medication cabinet—without diagnosing the pain properly.”
The cost of this is twofold. You miss the actual problem, then you miss the revenue opportunity sitting underneath it.
“I see a lot of post-sales teams go right into ‘solutioning’ without doing the right discovery,” Lukas says. “There could be a bigger revenue opportunity that you’re leaving tucked under the rug because you didn’t just ask the customer the right questions.”
His advice here is simple: “CSMs should speak mostly in questions here. Let the customer talk about the problems, the challenges, or the priorities that they’re being asked to focus on.”
When the customer articulates the pain themselves, the path to the right solution becomes clearer, faster.
6. Match your best CSMs to your most critical accounts.
Resource allocation is one of the most important ways to defend revenue, and yet many CS leaders let it happen by default.
“If 80% of your revenue is made up from 50 customers, you should be investing in the CSMs that are on those accounts,” says Lukas. “Are you paying them enough? Are they going to stick around?”
That last question matters. CSM turnover on a high-value account is a disruption that competitors can exploit, so match your strongest people to the accounts that need them and make sure they stay.
“The last thing you want is tons of turnover,” Lukas says. “It’ll frustrate your customers.”
When your budget is limited, look to scale with technology instead. “With, say, $100,000, you’re not going to hire 50 CSMs,” he says. “Instead, get the right AI tools and the right digital motion in place.”
7. AI revenue is slippery. Watch it differently.
If any revenue stream requires heightened protection right now, it’s AI. The market conditions Lukas describes are not subtle.
“There are fewer multi-year deals,” he says. “Everyone wants to try everything, and no one wants to commit long-term. You could sell as much as you want, but if you don’t retain all these AI dollars, it can go downhill pretty fast.”
His concern isn’t just retention mechanics, but complexity that makes AI ARR structurally harder to defend.
“It’s not just about the selling and the retaining,” he says. “It’s about how do we keep up with the pricing and packaging of AI—all the different credit models and platform models—and how we contract it.”
And finally… a CCO comeback story?
In one further observation, Lukas points to an organizational shift that’s already underway: the return of the CCO. After years of post-sales teams being moved under the CRO to fuel growth, he is seeing the CCO role reemerging.
“Over the past two years,” he says, “there’s been a real shift to moving post-sales teams under the chief revenue officer and gearing them up for growth. Now, more and more, as companies ask who is going to retain all those dollars, I’m seeing the CCO role start to re-emerge.
“We need experienced leaders whose bread and butter is retention.”
Want to hear more from Lukas? Learn what AI needs from you to make it work, how to lead your CSMs to success, and why adopting a customer success mindset helps your whole company.
Thank you to the Revenue Unscripted podcast—we appreciate you!
