Discovery Call Questions for SaaS: A 25-Minute Diagnostic Playbook for CROs, RevOps and Growth Buyers

1. 1

   0:00–2:00 — Frame (do not re-pitch)

   "Thanks for making the time. Quick frame so I don't waste it: when we traded messages you said expansion had gone quiet and renewals were coming back re-baselined on seats. That's the thing I want to dig into. I'm going to ask questions for most of this — probably the first fifteen minutes. I'm deliberately not going to show you anything until I know whether it's relevant. I'd rather tell you this isn't a fit than burn a demo slot on both of us. Still good for 25? And is there anything you want to make sure we get to, so I don't run us out of clock?" (If they say 'I mostly want to see pricing' or 'I need to know what comes out of my stack' — you are now managing a different call. Say so: 'Got it, I'll leave four minutes at the end for that. Can I get ten minutes of questions first?')

2. 2

   2:00–6:00 — Open the thread (pick ONE, then follow it)

   Choose one opener. Do not stack. "Tell me how a renewal runs today, start to finish — from when CS flags it to when the paper's signed." or "When you said expansion had stalled — what does that look like in a bad month? Which accounts, what happened?" or "What makes this the quarter you're looking at it, versus last year when NRR was still 118?" Then shut up. Their first answer is the symptom and it's worth almost nothing. You're listening for the noun you'll follow up on: the account, the system, the person, the meeting.

3. 3

   6:00–11:00 — Layer 2: the mechanism (three follow-ups before you change subject)

   "Walk me through the last account that re-baselined. What actually happened — who saw it coming, and when?" "Where does that live between Salesforce and the warehouse? Is the usage data in the renewal opportunity, or is CSM opening a separate dashboard?" "Who's doing that manually right now — is that the CSM, or is RevOps building the list?" "What's the workaround people have built? There's usually a spreadsheet." For an outbound thread instead: "Reply rate under 1% — is that across every sequence, or did it fall off a cliff on specific domains? Walk me through what your SDRs did the week you noticed." For a PLG thread: "When a free workspace crosses whatever your usage threshold is — what physically happens? Does it route, does someone get a Slack alert, or does it sit in a report nobody opens?"

4. 4

   11:00–14:00 — Layer 3: the cost, then 'how do you know?'

   "How many accounts came back down at renewal last quarter? Roughly." "What's that in dollars — is it seat reduction or a module coming out?" (Seat expansion versus price uplift are tracked separately; ask which one moved.) "So NRR went 118 to where, exactly? And is GRR holding, or is that moving too?" Then the beat that most reps skip: "How do you know? Is that coming out of the warehouse or is it CS reporting it up?" If they can't answer 'how do you know,' that is a finding. It means the problem is invisible internally and you will be helping them build the case, not just selling them a tool. Write that down in their words. Other cost probes, depending on the thread: "What's CAC payback sitting at now versus a year ago?" "What's real pipeline coverage going into next quarter — and how much of that 3x has a next step actually booked?" "How many of your reps are at quota right now? Out of how many carrying?"

5. 5

   14:00–16:00 — Layer 4: the stake (the layer that moves deals)

   "Who's feeling this most — is it you, or is CS carrying it?" "Whose number does this land in when the board asks?" "What did you tell the board you'd have fixed, and by when?" "If NRR is still where it is two quarters from now, what's the conversation you're having — is that a product answer, a coverage answer, or a headcount answer?" Then count to three. Do not fill the gap. This is where you get the sentence they weren't sure they'd say — the diligence deck, the Series C timing, the CS headcount they already promised wouldn't be needed.

6. 6

   Minute 6 interrupt: "So what do you guys actually do?"

   Thirty seconds, tied to what they just told you, then hand the ball back. "Short version — we watch the usage signal inside existing accounts so your CSMs see the second and third team signing up before the renewal call, not after. But I'd honestly be guessing at whether that matters until I understand one thing: when a CSM does spot a drop, what can they actually do about it 60 days out?" If they push a second time, they genuinely need orientation. Give a clean 60 seconds, no logos, no funding, then: "Can I go back to the thing you said about the spreadsheet RevOps rebuilds every Monday? That's the part I'm not clear on." Almost everyone lets you.

7. 7

   16:00–20:00 — Qualify the path (weave it, don't recite it)

   "If you decided this was worth doing, what actually happens next in your world? Who gets pulled in — does RevOps have to bless the data flow before anything else moves?" "Have you tried to fix this before? What did you buy, and what happened to it?" (The graveyard tells you your real competitor and your real objection.) "What's forcing the timing — a renewal, the board cycle, a fiscal year, a diligence process?" If nothing is forcing it, you're having a nice conversation, not working a deal. "Is this a line item that already exists, or would it need to get created?" — far more useful than 'what's your budget.' "If finance is running the consolidation exercise, does anything new have to be paired with something coming out?" "And if you just keep doing it the current way for four more quarters — what happens?"

8. 8

   20:00–23:00 — Targeted relevance (90 seconds, only what they raised)

   "I'll take two minutes on the one thing you raised, then we'll figure out the next step. You said the CSM finds out a team went dormant when the renewal quote comes back short. The specific thing we do there is [mechanism], and it writes back to the renewal opportunity in Salesforce as a field your existing renewal report can filter on — so it lands in the report your team already opens on Mondays, not in a new dashboard. That's deliberately the narrow version. I'm not going to walk you through anything else today." No tour. No roadmap. No customer logo montage. If you find yourself on slide four, you've lost the room.

9. 9

   23:00 — Playback in their words

   "Let me make sure I've got it. NRR went from 118 to 103, and the reason isn't churn — it's accounts re-baselining seats at renewal because nobody sees the drop until the quote comes back. It's costing you roughly four points of NRR a quarter, and you know that from the warehouse but CS is disputing the attribution. The pressure's coming from the board because you said in February this was a coverage problem you'd fix without adding heads. Did I miss anything, or get anything wrong?" The 'or get anything wrong' is where the last hidden detail falls out. Wait for it.

10. 10

    23:00–25:00 — Close a dated, named next step

    "Based on that, the useful next thing isn't a demo — it's 45 minutes with you and whoever owns the Salesforce object model, and I'd want your VP of Customer Success in it too since it's her team's workflow. I'll show you specifically how the seat-drop signal lands in the renewal opportunity, and what implementation actually costs your RevOps person in hours — not the general tour. I've got Tuesday at 2 or Thursday morning. Which works?" Then: "What should they bring? If your team can pull the closed-lost-to-downgrade list from last two quarters, I'll run our signal against it live — if it doesn't surface accounts you actually lost seats in, we'll both know quickly." Send the invite before you hang up. Confirm out loud: who's on it, what you're showing, what they're bringing.

11. 11

    What goes in the CRM (their words, not yours)

    Bad: "Prospect has retention challenges and stack consolidation pressure." Good: "NRR 118 → 103 over two quarters. Not churn — downgrades. 'Nobody sees the seat drop until the quote comes back short.' CS and RevOps disagree on attribution; CRO told the board in February it was a coverage problem, no new heads. Finance running SaaS spend review, seat-level utilization requested on every line, new purchase requires a named line item coming out in writing. Renewal on their sequencer is in March — that's the pressure date. RevOps = one person, Salesforce + Snowflake, no appetite for custom objects." That paragraph is your follow-up email, your business case, and the exec deck. The first version is worth nothing.

1. Rep

   Thanks for the time. Quick frame — when we messaged, you said expansion had gone quiet and renewals were coming back re-baselined on seats. That's what I want to dig into. I'll ask a lot of questions for the first fifteen minutes and I'm not going to show you anything until I know it's relevant. Still good for 25?

2. Buyer

   Good for 25. Fair warning — finance has us in a consolidation exercise. I've got forty-one lines in the GTM stack and I've been told anything new has to be paired with something coming out, in writing. So I'm being honest with you: this is a learning conversation, not a buying one.

3. Rep

   Understood, and I'd rather know that now. Let's use it as a learning conversation then. Tell me about the re-baselining — walk me through the last account that came back down at renewal. What actually happened?

4. Buyer

   Manufacturing company, seven hundred seats, renewed at four hundred and twenty. They didn't churn, they just didn't need the seats. Two teams had gone quiet six months earlier and nobody flagged it. CS said they were 'green' on the QBR right up until legal sent the redline.

5. Buyer

   And before you say it — yes, we have a usage dashboard. Everyone has a usage dashboard.

6. Rep

   I wasn't going to. I want to know where the dashboard sits relative to the renewal. When the CSM opened it, was that data on the renewal opportunity in Salesforce, or somewhere separate?

7. Buyer

   Separate. It's a Looker view off the warehouse. The CSM's day runs in Salesforce and Gainsight, so realistically she looks at Looker when someone asks her to. Which is at the QBR, ninety days out — by which point the budget's already been cut on their side.

8. Rep

   So the signal exists, it's just not where the work happens. How many accounts came back down like that last quarter?

9. Buyer

   Eleven that I'd call material. NRR went from 118 to 103 across two quarters. GRR is actually fine — 91, basically flat — which is the part I keep having to explain in the boardroom. It's not churn. It's downgrades. Different problem, and nobody upstairs wants to hear the distinction.

10. Rep

    That distinction matters for what you'd even fix. How do you know it's eleven — is that coming out of the warehouse, or is CS reporting it up?

11. Buyer

    RevOps pulls it. My VP of Customer Success has a different number, because she counts a seat reduction with a price uplift as a win. So we spend twenty minutes of every forecast call arguing about the denominator instead of the accounts.

12. Rep

    That's the second time you've mentioned the two of you not agreeing on the number. Whose number does this land in when the board asks?

13. Buyer

    Mine. It's my number. And in February I told them this was a coverage problem, not a product problem, and that I'd fix it without adding CS headcount. That was two board meetings ago.

14. Rep

    …

15. Buyer

    There's also a raise conversation happening in the background. So the diligence version of this needs efficient growth — CAC payback's already drifted past twenty months and the magic number is under 0.7. I can't walk in with 103 NRR and a headcount ask.

16. Rep

    That's the real deadline, then, not the fiscal year. Have you tried to fix the visibility piece before? What did you buy and what happened to it?

17. Buyer

    Bought an intent vendor eighteen months ago. Everybody was in-market, every week, same four hundred accounts. Reps stopped opening the list inside a month. That's the vendor I'm currently trying to kill, actually.

18. Rep

    Then let me name the failure mode before you have to: topic-level intent at the domain level surfaces the same list forever because it isn't tied to anything happening inside your product. What signal would you actually have acted on with that manufacturing account?

19. Buyer

    Two named teams — not the domain, the workspaces — going from daily active to nothing over a six-week window, landing in the renewal opportunity where the CSM already works. If it's another tab, it doesn't exist.

20. Rep

    So let me play it back. NRR 118 to 103 over two quarters, GRR flat at 91 — this is downgrades, not churn. It happens because the usage signal lives in Looker and the work lives in Salesforce and Gainsight, so nobody sees a team go dark until the quote comes back short. Eleven material accounts last quarter, and you and your VP of CS don't agree on the count. It's your number, you told the board in February you'd fix it without heads, and there's a raise where twenty-month payback and 103 NRR is not a story you want to tell. Anything I got wrong?

21. Buyer

    No, that's it. The raise part isn't for general circulation.

22. Rep

    Understood, stays here. Then the next thing isn't a demo. Give me 45 minutes with you, your VP of Customer Success, and whoever owns the Salesforce object model — I'll show you how the team-level drop writes into the renewal opportunity, and exactly how many RevOps hours implementation costs, because I heard you say that team is one person. And bring me the eleven accounts. I'll run the signal against them live — if it doesn't flag those two teams six weeks before the redline, we've both saved a pilot. Tuesday at 2, or Thursday morning?

23. Buyer

    Thursday. But bring the displacement math too — if I'm putting this in front of finance I need to name the line coming out.

What are the best discovery call questions for SaaS deals where the buyer is a CRO or VP of Sales?

Start with one open thread, not a list: "Walk me through the last account that re-baselined at renewal — what actually happened?" Then follow it three times before changing subject. The highest-yield sequence in SaaS is mechanism ("where does that data sit between Salesforce and the warehouse?"), cost ("how many accounts, and what did NRR do?"), the verification beat ("how do you know — is that RevOps pulling it, or CS reporting it up?"), and finally stake ("whose number does this land in, and what did you tell the board you'd fix?"). Questions with a number in the answer beat questions with an adjective in the answer, every time.

How do I ask about metrics like NRR or CAC payback without sounding like I'm reciting jargon?

Use the terms precisely or not at all. NRR includes expansion, GRR doesn't, and mixing them up in front of a CRO ends the call. Ask them as connected questions rather than trivia: "NRR went from 118 to where, roughly — and is GRR holding, or is that moving too?" That single question tells you whether you're looking at a downgrade problem or a churn problem, which are completely different sales. Same with efficiency: "Where's CAC payback now versus a year ago?" is a conversation; "what's your magic number?" sounds like you read a blog post on the way to the call.

The prospect asks 'so what do you actually do?' six minutes in. Do I pitch?

Give 30 seconds tied to something they've already told you, then hand the ball back with your next question. "Short version — we surface the team-level usage drop inside the renewal opportunity so your CSMs see it before the quote comes back short. But I'd be guessing at whether that matters until I understand one thing: when a CSM does spot a drop 60 days out, what can they actually do about it?" If they push a second time, they genuinely need orientation — give a clean 60 seconds, no logos, no funding round, then ask to go back to their layer-two detail. Almost everyone lets you.

How should I run discovery differently when the company is PLG?

Assume any outbound-flavoured framing gets you dismissed in the first thirty seconds. Ask about the seam instead: what counts as a PQL, who agreed to that definition, what physically happens when a workspace crosses it, and who owns the account afterwards — sales-assist or the CSM. Then ask how many free workspaces are sitting inside accounts that already have paying teams. Most PLG companies can't answer that, and it's the expansion they're leaving on the table. You're diagnosing the handoff between the self-serve motion and the sales motion, not pitching a top-of-funnel tool.

What do I do when the buyer opens with 'finance is consolidating our stack and I can't buy anything'?

Take it at face value and use it as discovery material. Ask which lines are on the cut list and what criteria finance is applying — usually seat-level utilization. Then either name the two line items you'd expect to displace, or admit you don't displace anything and pivot to a pilot scoped to one team's budget. What you must not do is keep selling as though the constraint isn't real. The consolidation exercise also gives you a timeline lever: renewals being deliberately let lapse means there are dates on the calendar, and dates are what turn a nice conversation into a deal.

How do I close a next step that actually gets taken, instead of 'send me something'?

Prescribe it from what you found, with names and a purpose. "45 minutes with you, your VP of Customer Success, and whoever owns your Salesforce object model — I'll show you specifically how the seat-drop signal writes into the renewal opportunity and how many RevOps hours implementation costs. Tuesday at 2 or Thursday morning?" Then give them homework that makes the next call concrete: the eleven downgraded accounts, last quarter's closed-won list, the current pipeline coverage report. Send the invite before you hang up and confirm out loud who's attending and what they're bringing. "I'll follow up with some times" is a no with a smile on it.

• All SaaS playbooksEvery call type for SaaS, in one place.

Other SaaS calls

• Cold CallThe SaaS Cold Call Script for Reps Dialling CROs, VPs of Sales and RevOps Leaders
• Demo CallThe SaaS Product Demo Script for Selling Into a Revenue Team That's Already Cutting Tools
• Manager Coaching CallSales Coaching Roleplay for SaaS Teams: The 1:1 After Two Missed Quarters
• Pricing Negotiation CallThe SaaS Pricing Negotiation Script: Holding Price After the Technical Win
• Renewal CallThe SaaS Renewal Call Script for a Save Call You're Six Weeks From Losing
• Upsell CallThe Upsell Script for SaaS Customers That Survives a Seat Utilization Report
• Warm CallWarm Call Script for SaaS: Cashing a Referral With a CRO in Four Minutes

The same call in a neighbouring market

• Discovery Call for Financial ServicesDiscovery Call Questions for Financial Services: A 25-Minute Playbook for Wealth Management Buyers
• Discovery Call for InsuranceDiscovery Call Questions for Insurance: A 25-Minute Playbook for Selling Into Claims
• Discovery Call for HealthcareDiscovery Call Questions for Healthcare: A 25-Minute Playbook for CMIO and Clinical Ops Calls

Related reading

• "I Need to Run It By the Team" — What That Actually Means and How to Get in the Room"Let me run it by the team" is usually a handoff, not an objection — here is how to tell which of the three flavours you are facing and how to get in the room.
• The Post-Call Recap Email That Actually Moves the Deal (Write It in Six Minutes)Most recap emails are a thank-you plus an attachment, which is why nobody forwards them. Here is the structure that survives being sent to the person who wasn't on the call.