6 questions CSMs ask before a contested renewal
When a customer says they're looking at someone else, the answers live on the competitor's public pages, not in your gut.
A customer says they're evaluating a rival before renewal. Six questions customer success should answer from the competitor's public surfaces first.
"We're taking a look at a couple of other options before we renew."
Every CSM has heard that sentence. Most respond with a discount before they respond with a question. That's backwards. The customer has almost certainly already read the competitor's pricing page, its migration guide, and maybe a sales deck. You should know what they read before you pick up the phone.
Here are the six questions customer success teams ask us most often when a renewal turns contested, and how we'd answer each one.
Which competitor, and how do I find out without asking directly?
Ask directly first. Customers usually tell you if you ask plainly: "Who are you looking at?" It's a normal question, and dodging it makes you look nervous.
If they won't say, look at the signals you already own. Did their admin recently export data in bulk? Did someone file a ticket asking about API rate limits or SSO config they've never touched? Those requests often mirror a competitor's onboarding checklist. Your support queue tends to know first, as we wrote in Support heard about the competitor before we did.
What will the competitor's price actually be for this account?
Not the list price. The price for an account of this size, on this plan, with these seats.
Pull the competitor's pricing page and read the fine print: seat minimums, annual-only discounts, which features sit behind "Contact sales." Then check whether that page changed recently. A competitor that quietly dropped a seat minimum last month is a different threat than one whose page hasn't moved in a year. The Wayback pricing archaeology method works here, though it's slow when the renewal is in nine days.
This is where Seeto earns its keep for CS teams: it watches competitor pricing and plan pages continuously and records each change as a dated event, so "did they change anything recently?" becomes a lookup instead of an afternoon in the Wayback Machine.
Do they have a migration path from us specifically?
This is the question that matters most and gets asked least.
Search the competitor's docs and help center for your product's name. A dedicated "Migrating from [you]" guide, an import tool that reads your export format, or a landing page with your logo on it means they've invested in taking your customers. That changes the conversation. The customer isn't comparing features; they're comparing switching costs, and the competitor has been working to lower them.
No migration path? Say so, honestly. Switching cost is a legitimate part of the decision.
Which of their claims should I take seriously?
The ones with a link behind them. "40% faster" on a homepage is marketing. A changelog entry from last Tuesday describing the feature your customer asked you for in Q2 is a fact.
Separate what's shipped (changelog, docs, release notes) from what's promised (roadmap boards, webinar slides, "coming soon" badges). Customers mix the two constantly. Your job is to un-mix them, with sources. We've argued before that every competitor claim needs a source link, and a renewal call is where that rule pays off.
Should I match their price?
Usually not on the first call. A price match tells the customer the competitor set your price. It also teaches them that "looking around" is worth a discount every year.
First find out whether price is the real reason. Often it's a missing feature, a bad support experience, or a new stakeholder who used the competitor at a previous job. A discount fixes none of those. We almost matched a competitor's price cut once, before noticing that SSO and audit logs had quietly moved up a tier. The "cut" was a repackage.
What do I bring to the renewal call?
One page. Three things on it:
- What changed on the competitor's side recently, with dates and links.
- What the customer would give up, in specifics: integrations, data history, workflows their team has built.
- What you're shipping next that addresses their actual complaint, if anything. If nothing, don't invent it.
Leave the feature comparison grid at home. The customer has already seen the competitor's version of that grid, and theirs looks better.
The CSMs who save contested renewals aren't the best negotiators. They're the ones who walked in already knowing what the customer had read.