Running a Pre-Renewal Discovery Call (Not a Check-In)

I lost a $340K renewal last year that I should have saved. The account was healthy by every metric we tracked. Usage was strong. NPS was an 8. The champion told my CSM three months before renewal that she didn’t “anticipate any issues.”

The renewal came back as a 40% downgrade. Their new CFO, who had joined seven months earlier and who nobody on my team had ever spoken to, had run a vendor consolidation review and decided our platform overlapped with a tool they’d bought through an acquisition. We were single-threaded — our entire relationship ran through one champion, and we had no visibility into the broader decision-making unit. Our champion tried to fight for us internally. She lost. She didn’t tell us any of this was happening because, from her perspective, she was handling it.

We found out at the procurement stage. By then, the decision was made and we were negotiating how much we’d lose, not whether we’d keep the deal.

The problem wasn’t that we had a bad relationship. The problem was that our pre-renewal touchpoint was a check-in, not a discovery call. A pre-renewal discovery call is a structured, forward-looking conversation — held 90 to 120 days before the renewal date — that re-qualifies account fit, surfaces unstated objections, maps the current decision-making unit, and stress-tests the internal business case for renewal. We weren’t doing any of that. We asked “how are things going?” and got the only answer that question ever produces: “fine.”

The Check-In Is the Problem

I’ve sat in on dozens of pre-renewal calls across my team, and the pattern is remarkably consistent. The CSM opens with some version of “wanted to connect ahead of your renewal and see how things are going.” The champion says things are good, maybe mentions a feature request or two. The CSM asks if they anticipate any issues with the renewal. The champion says no. The call ends. Everyone feels like progress was made.

Nothing happened on that call. The CSM learned nothing they didn’t already know. The champion wasn’t asked anything that would surface a real problem. And the renewal outcome was no more certain than it was before the call started.

The check-in fails because of what it doesn’t do. It never probes for changes in the customer’s organization or budget dynamics. It never identifies who else will influence the decision. And it completely misses the gap between “we like your product” and “we’re going to renew at the same level.” Those are two very different things, and the space between them is where downgrades and churns live.

One Head of CS at a fintech company we interviewed described it this way:

“My team was running pre-renewal check-ins like wellness visits. They’d ask the patient how they feel, hear ‘fine,’ and move on. Nobody was ordering the blood work.”

That stuck with me. The check-in asks how you feel. The discovery call runs the tests.

What a Pre-Renewal Discovery Call Actually Looks Like

The shift isn’t about being more aggressive or treating the customer like a prospect. It’s about applying the same rigor to keeping a customer that you applied to winning them. When a sales rep runs discovery on a new deal, they’re qualifying fit, mapping stakeholders, understanding budget, and identifying objections — the same elements you find in frameworks like MEDDIC or MEDDPICC. A pre-renewal discovery call applies that same discipline to the renewal, because the variables have changed since the original sale and nobody has rechecked them. This is where net revenue retention lives. The difference between 87% and 91% gross retention is meaningful, but the real impact shows up in fewer surprise downgrades and more expansion conversations.

I run these calls around four areas. Not as a rigid checklist — more as a mental framework that ensures I cover the ground that check-ins don’t.

Re-qualifying ICP fit

ICP re-qualification is the process of reassessing whether a customer still fits your ideal customer profile at renewal, rather than assuming the fit from the original sale still holds. This is the one most CSMs skip entirely because it feels strange to question whether a paying customer is still a good fit. But customers change. The team that bought your product 18 months ago might have restructured. The use case that justified the spend might have been deprioritized. The champion who understood your value might have shifted focus to a different initiative.

The question I ask is some version of: “When we started working together, the primary use case was [X]. Is that still where you’re getting the most value, or has it shifted?” The answer tells me whether the original business case is still intact. About a third of the time, it has shifted meaningfully, and the customer hasn’t told anyone because nobody asked.

I had an account last year where the answer was illuminating. The VP of Revenue Operations said: “Honestly, the team that used it most has been folded into a different org. The new team lead hasn’t really figured out how it fits into their workflow yet.” That account was at full price, showing decent aggregate usage numbers, and had a green customer health score. This is where traditional health scoring fails — it measures activity, not fit. Without that question, we’d have sent a renewal contract and been surprised by the pushback.

When the fit has drifted, you have a window to reposition. But you need to know it’s drifted first.

Surfacing unstated objections

Unstated objections are the renewal risks a champion knows about but does not volunteer — not out of dishonesty, but because they are advocating for you internally and minimizing friction in the vendor relationship. Champions don’t tell you their objections unprompted. Not because they’re dishonest, but because they’re advocates. They’re rooting for the renewal to go through. They minimize internal friction when they talk to you because they’re on your side. The person most likely to hide bad news from you is the person you trust most. That’s not a bug in the champion relationship. It’s how it works.

Direct questions about objections almost never work. “Are there any concerns about the renewal?” gets “no” 90% of the time. Even when there are significant concerns.

The approach that works better is asking about expansion rather than renewal. “If you were going to double your investment in us next year, what would need to be true?” The gap between their answer and reality is where the objections live. If they say “we’d need to see better reporting,” they’re telling you reporting is a problem. If they say “we’d need to get the data team using it,” they’re telling you adoption is narrower than you think. If they hesitate and say “I’m not sure we would,” you’ve just learned the most important thing you’ll hear all quarter.

Another indirect question that works: “If I were sitting in your CFO’s review meeting and had to defend this line item, what would I need to say?” This externalizes the objection. They’re not telling you they have a concern. They’re telling you what a hypothetical skeptic would say. It’s the same information with none of the relational risk.

Mapping current stakeholders

Your sales rep mapped the decision-making unit during the original deal. That map is probably wrong now. People change roles, new leaders join, reorgs happen. In a typical 12 to 18 month renewal cycle, at least one person who will meaningfully influence the renewal wasn’t part of the original deal. This is where multi-threading — building relationships with multiple stakeholders beyond your primary champion — becomes critical. Single-threaded accounts, where your entire relationship runs through one contact, are the most common source of surprise churn and downgrades at renewal.

One question: “Who else will weigh in on the renewal decision that wasn’t involved last time?” Follow up with: “Have they seen what we do?” If the answer is no, you have a stakeholder who will form an opinion about your product without ever having talked to you.

On the $340K account I mentioned earlier, this single question would have uncovered the new CFO and his vendor consolidation review — one of the most common drivers of surprise churn in B2B SaaS, where a new finance leader rationalizes the tech stack and eliminates overlapping tools. Seven months of runway. Instead, he made his decision in a vacuum, and our champion lost a fight we didn’t even know was happening.

Building the internal business case

This is the part that most post-sales teams leave entirely to the champion, and it’s a mistake. A quarterly business review (QBR) or executive business review (EBR) can lay the groundwork, but the pre-renewal discovery call is where you pressure-test whether the champion can actually articulate the case. Your champion has to justify the renewal internally. They need to walk into a budget meeting or a procurement review and explain why this spend is worth continuing. If you haven’t given them the ammunition for that conversation, they’re improvising.

The question I ask: “When you go to bat for us internally, what’s the story you tell?” If they can articulate it clearly, you’re in decent shape. If they stumble, you have work to do.

The best move I’ve found is to co-build the business case during the call. Not a formal ROI document — those feel like vendor marketing and get ignored. Instead, collaboratively articulate three or four specific outcomes: “Your team was doing [X manually] before, now they’re doing [Y with our product], and the result is [Z measurable outcome].” When your champion can say that in their own words, the internal conversation is dramatically easier.

I started doing this after losing a renewal where the champion shared afterward: “I knew it was valuable but I couldn’t explain it to my VP in a way that competed with the other budget requests.” She wasn’t wrong. We’d been delivering value for 14 months and never once helped her translate that value into language her leadership would respond to. That was our failure, not hers.

Timing: 120 Days, Not 90

Most teams start renewal motions at 90 days out. That’s too late.

By day 90, procurement is often already aware that a renewal is approaching. In larger organizations, they’ve already flagged it in their review cycle. The conversation has started to shift from “is this valuable?” to “what are we paying?” Once that shift happens, you’re negotiating, not selling. And you’re negotiating without having done the discovery work that tells you what your leverage actually is.

At 120 days, you’re upstream of procurement. The renewal conversation should start at 120 days for mid-market accounts and 150 days for enterprise accounts — anything later and you’re negotiating price instead of demonstrating value. The conversation is between your CSM and the customer’s operational team. You can talk about fit, value, and future plans without a purchasing manager in the room optimizing for discount percentage.

The 30-day difference matters more than it seems. I compared our renewal outcomes for deals where the discovery call happened at 120+ days versus 90 days. The sample is small enough that I won’t pretend the numbers are statistically rigorous, but the pattern was clear: earlier discovery calls correlated with higher retention rates and, more importantly, with fewer surprise downgrades. The downgrades at 90 days were surprises. The downgrades at 120 days were things we saw coming and had time to address, even when we couldn’t fully prevent them.

For enterprise accounts with complex procurement, 150 days isn’t unreasonable. I know that feels aggressive. But the alternative is finding out about a CFO’s vendor consolidation review at the procurement stage, and I can tell you from experience that the conversation goes very differently when you’re 60 days ahead versus 30.

The Five Questions

I’ve tried to keep this practical. If you take nothing else from this article, take these five questions and use them in your next pre-renewal call. They’re not magic. Some will land better than others depending on the account. But collectively, they cover the ground that a check-in never will.

1. “When we started working together, the main use case was [X]. Is that still where you’re getting the most value, or has it shifted?” (ICP re-qualification)

2. “If you were going to double your investment in us next year, what would need to be true?” (Surfaces unstated objections)

3. “Who else will weigh in on the renewal that wasn’t involved last time?” (Stakeholder mapping)

4. “When you go to bat for us internally, what’s the story you tell?” (Business case readiness)

5. “What would make this renewal easy for you?” (Opens the door for the champion to tell you what they need)

That fifth question is the one I added most recently, and it’s become the most valuable. It reframes you as a partner in the renewal process rather than a vendor waiting for a signature. The answers are often operational: “If you could send me a one-page summary of what we’ve accomplished,” or “If I could show my VP a demo of the new feature.” These are things you can do. And doing them before the champion asks is the kind of proactive support that turns a renewal into an expansion conversation.

What This Doesn’t Solve

I want to be honest about the limits of this approach. A discovery call doesn’t save an account where the product genuinely doesn’t fit anymore. It doesn’t overcome a champion who has completely disengaged. And it doesn’t work if the CSM doesn’t have the relationship depth to ask these questions without it feeling like an interrogation.

The discovery call works best when there is a real relationship and real value, but the renewal is at risk because of organizational changes, unstated concerns, or internal dynamics that nobody has surfaced. That describes, in my experience, somewhere around half to two-thirds of at-risk renewals. The rest are either genuinely at risk because of product-market fit issues or genuinely safe because nothing has changed. For the ones in the middle, the difference between a check-in and a discovery call is often the difference between a save and a surprise.

I’ve been running pre-renewal discovery calls for about two years now. My team’s renewal rate hasn’t changed dramatically — it went from 87% to 91%, which matters but isn’t transformative. What changed more was the nature of the losses. We stopped being surprised. The accounts we lost, we saw coming. The downgrades we took, we negotiated from a position of understanding rather than scrambling. And the expansions we landed came out of discovery conversations where we learned what the customer actually needed next, not what we assumed they wanted.

The worst pre-renewal call is the one where you learn nothing. The check-in guarantees that outcome. The discovery call doesn’t guarantee a different one, but it makes it possible.