CHURN IS DEAD

Stop Calling Yourself Strategic — You're Just Expensive

9 min read · Strategy & Impact

# CHURN IS DEAD

*Issue: Stop Calling Yourself Strategic — You're Just Expensive*

The QBR That Changed Nothing

I sat in on a QBR last quarter. Not my account — a colleague asked me to observe and give feedback.

It was a masterclass. In the wrong way.

The CSM spent four days preparing the deck. Forty-two slides. Executive summary. Usage trends with colorful graphs. Feature adoption heatmap. Support ticket analysis. Competitive landscape overview. A roadmap preview that product had approved for external sharing. Appendix with benchmark data.

The customer's VP of Engineering attended. So did their Director of Security Operations. Two senior analysts dialed in. This was a serious audience.

The CSM presented for 35 minutes. The slides were polished. The data was accurate. The delivery was professional.

Then the VP of Engineering said: "Thanks. This is helpful context. What do you think we should actually do differently?"

Silence. Three seconds. Five seconds.

"Well, I think you're on a really strong path. Maybe we could look at expanding the SOAR integration?"

That was it. Four days of prep. Forty-two slides. And the recommendation was "maybe look at expanding the SOAR integration" — something the customer had already been evaluating independently.

The VP nodded politely. The call ended five minutes early. Nothing changed.

That CSM would describe themselves as strategic. They had executive meetings. They delivered data-driven QBRs. They used words like "business outcomes" and "value realization."

But here's the uncomfortable question: what decision did that customer make differently because of that conversation?

The answer is: none. Zero. Not one.

The Strategic Inflation Crisis

Somewhere in the last five years, "strategic" became the most overused word in Customer Success. And its meaning inflated to the point of worthlessness.

What "strategic" actually means: you change how someone thinks about their business, their priorities, or their approach — and they make a different decision as a result.

What "strategic" has come to mean in CS: you talk to executives, you use data in your presentations, and you avoid discussing support tickets.

These are not the same thing. Not even close.

Here's the test I've started running: after every customer interaction, ask one question.

"What will this customer do differently as a result of this conversation?"

If the answer is "nothing different" — if the customer will continue operating exactly as they were before your call — then the interaction wasn't strategic. It was informational. And informational interactions are what AI does for free.

I've asked this question to dozens of CSMs about their most recent customer meetings. The majority — not some, the majority — cannot point to a single customer decision they influenced in the last 30 days.

They had meetings. They shared data. They maintained relationships. They checked in. But they didn't change anything. And that's the gap between expensive and strategic.

The Four Levels of CS Impact

Not all customer interactions are equal, and the industry has been lazy about distinguishing between them. Here's a hierarchy I've been developing based on the patterns I see in teams that actually earn the "strategic" label versus teams that just claim it.

Level 1: Information Delivery (Low Impact, Highly Automatable)

This is where most CS interactions live. You're delivering information the customer could access themselves — usage reports, feature updates, roadmap previews, support summaries. The customer smiles, says thanks, and moves on exactly as before.

A dashboard does this. An AI-generated email does this. A self-serve portal does this. If your "strategic" contribution is presenting data the customer could pull themselves, you're not strategic. You're a newsletter with a face.

Level 2: Insight Generation (Moderate Impact, Partially Automatable)

This is one level up. You're not just delivering data — you're interpreting it. "Your adoption of module X is 40% below peers in your segment, and here's why that matters for your security posture." You're adding context that the customer doesn't have because you see patterns across your entire customer base.

This is genuinely valuable — but it's increasingly what AI does well. Pattern recognition across large datasets is literally the thing generative AI excels at. The shelf life of "insight generation" as a human competitive advantage is short.

Level 3: Recommendation Delivery (High Impact, Hard to Automate)

Now you're changing behavior. You're not just saying "here's what we see" — you're saying "here's what you should do about it, and here's why." The customer hears your recommendation, evaluates it, and adjusts their approach because your judgment carries weight.

This requires trust. It requires technical credibility. It requires understanding the customer's business well enough to make recommendations that are relevant, not generic. AI can suggest — but a customer doesn't restructure their security operations because a chatbot said so.

Level 4: Decision Architecture (Highest Impact, Impossible to Automate)

This is where genuinely strategic CSMs operate. You're not just recommending an action — you're reshaping how the customer frames the decision itself. You're changing the criteria they use to evaluate options. You're introducing considerations they hadn't thought of. You're building the business case that goes to their CFO.

A customer was planning to consolidate from three security vendors to two. A Level 4 CSM doesn't just argue "keep us." They reframe the decision entirely: "Consolidation makes sense for cost, but here's the operational risk analysis I've built based on what I've seen when companies in your sector reduce monitoring coverage. The $300K you save creates a $1.8M visibility gap. Let me walk your CFO through this."

That's not a check-in. That's not a QBR. That's architectural influence on how the customer thinks about their business. And no AI is doing that.

The Strategic Impact Scorecard

I've built a scoring system that any CSM can use to honestly assess where they're actually operating versus where they think they are.

Dimension 1: Decision Count

In the last 90 days, how many specific customer decisions did you influence? Not conversations had. Not meetings attended. Decisions changed.

0 decisions: You're at Level 1. You're delivering information.
1–2 decisions: You're at Level 2–3. You have moments of impact but no consistency.
3–5 decisions: You're at Level 3. You're a consistent source of actionable advice.
6+ decisions: You're at Level 4. Customers are making structural changes based on your input.

Dimension 2: Decision Altitude

What level of decision are you influencing? There's a hierarchy.

Tactical decisions ("which feature to enable next") — Low altitude. Important but replaceable.
Operational decisions ("how to restructure their monitoring workflow") — Mid altitude. Requires expertise.
Strategic decisions ("whether to renew multi-year, how to present ROI to their board, whether to consolidate vendors") — High altitude. This is where you become uncuttable.

Dimension 3: Request Direction

Who initiates the strategic conversation?

If the customer only calls you when something breaks — you're support with a better title.
If you proactively bring insights and the customer engages — you're building toward strategic.
If the customer calls you before making major decisions and asks for your perspective — you're genuinely strategic. That's the gold standard.

Dimension 4: CFO Translatability

Can you express your impact in language a CFO would understand? Not "we deepened the relationship." Not "adoption increased." Can you say: "Our CSM's architecture recommendation saved this customer $400K in redundant tooling, which their CFO cited as the reason they renewed for three years"?

If you can't translate your work into financial language, you can't prove you're strategic. And what you can't prove, you can't protect.

The Uncomfortable Homework

Here's what I'd challenge every CSM reading this to do this week.

[ACTION]Step 1: List your last 10 customer interactions (calls, QBRs, emails — anything substantive).[/ACTION]

[ACTION]Step 2: For each one, write down what the customer did differently as a result.[/ACTION]

[ACTION]Step 3: Count the zeros.[/ACTION]

If more than half your interactions resulted in "nothing different," you have a Level 1–2 problem. You're working hard. You're well-liked. You're professional. But you're not strategic. And in 2026, "not strategic" increasingly means "not necessary."

The good news: this is fixable. It's a skill gap, not a character flaw. But fixing it requires honesty about where you actually are — not where your LinkedIn headline says you are.

Your Strategic Impact Playbook

I've turned the Strategic Impact Scorecard into a complete self-assessment and development tool.

The Strategic Impact Audit includes:

The Decision Impact Log — A 90-day tracker for documenting every customer decision you influenced, the altitude of that decision, and the financial impact
The QBR Transformation Template — How to restructure your QBRs from information delivery to decision architecture in 3 steps
The CFO Translation Worksheet — Templates for converting CS activity into financial language that executives understand
The Level-Up Development Plan — A 90-day roadmap for moving from Level 1/2 to Level 3/4 with specific weekly actions
The Strategic Readiness Self-Assessment — Score yourself honestly across all four dimensions with calibrated rubrics

*Strategic isn't a title you give yourself. It's an outcome your customers confirm. If they're not making different decisions because of you, you're just expensive.*

*— Kuber*

*P.S. — I ran the "last 10 interactions" exercise on myself last month. The results humbled me. Four out of ten were genuine Level 3+. Six were information delivery I could have automated. If you run it and want to share your results (anonymously), hit reply. I'll compile the data and share what "strategic" actually looks like across the CS community.*

Share this newsletter with a CSM who calls themselves strategic but hasn't changed a customer decision in 30 days. Tough love is still love.

Subscribe to Churn Is Dead at churnisdead.com for weekly enterprise customer success frameworks that replace hope with strategy.

By Kuber Sethi · All issues · Subscribe