13/13 Gate✓ IQ Certified10/10?

What's the most underrated discovery question in B2B SaaS?

📖 3,623 words🗓️ Published Jul 20, 2026

Direct Answer

The most underrated discovery question in B2B SaaS is: "Who else on your team would be logging into this every week, and what does their day actually look like?"

Most sellers are trained to map *authority* — find the economic buyer, the champion, the blocker, the person who signs. That instinct is correct but incomplete. It optimizes for getting the deal *signed* and quietly ignores the population that determines whether the deal gets *renewed and expanded*: the five, fifteen, or fifty end-users who will open your product on a Monday morning to get real work done. Authority closes the first contract. Adoption closes every contract after it. In a subscription business, where the economics only work if a customer stays for years, the second number is the one that pays your bills.

This question outperforms flashier discovery questions ("What's your budget?", "What's your timeline?", "What keeps you up at night?") for four concrete reasons. It corrects your pricing — if you scoped three seats and the real daily-user count is fifteen, you are about to be badly underpriced and badly under-resourced for onboarding. It finds your real champion — the executive signs, but the operations lead governs day-two reality, and that person only defends your renewal if they felt heard on call one. It makes your implementation promise honest — a thirty-day go-live pitched to a CFO is malpractice if the actual users are non-technical staff who need sixty to ninety days of enablement. And it predicts adoption — users who had a voice in the buying decision adopt dramatically faster than users who are surprised by a rollout, and early adoption is the single strongest leading indicator of whether a customer renews.

If a reader stops here, this is the whole answer: stop mapping only who has authority and start mapping who has the workflow. The buyer signs the contract; the daily user signs the renewal. Ask about the daily user on the first call, quantify how many there are and what tools they're replacing, and you protect the entire lifetime value of the account before you've even built the demo. Everything below is the mechanics — why it works, exactly how to phrase it, what to do with the answer, and the specific situations where it backfires.

Why stakeholder breadth beats stakeholder rank

The prevailing wisdom in enterprise sales is "sell higher." Get to the VP. Skip the gatekeepers. And there is real truth in it — deals with no executive sponsor stall in procurement forever. But "sell higher" has curdled into a lazy heuristic that treats everyone below the buyer as noise. That's a mistake the subscription model punishes with unusual cruelty.

Gartner's research on the modern B2B buying journey has been consistent for years: a typical purchase now involves a buying group of roughly six to ten people, and that number climbs with deal size and organizational complexity. Those people don't move in lockstep. They gather information independently, form private opinions, and reconcile them in rooms you are never invited to. Harvard Business Review's work on "buyer enablement" and the consensus problem describes the same dynamic from the other side — the harder part of a complex B2B sale is often not convincing one person but helping a fractured group agree with itself. A seller who has only spoken to the economic buyer is, functionally, blind to most of the room.

Here is the asymmetry that makes the daily-user question so valuable and so overlooked. The economic buyer's risk is the purchase decision — did they choose the right vendor, did they get a defensible price. Once the contract is signed, that person's attention moves on to the next fire. The daily user's risk is the workflow — every single day for the life of the contract, your product either makes their job easier or harder. When renewal season arrives eleven months later, nobody asks the CFO whether the tool is good. They ask the operations manager, "Are we still using this?" If forty of fifty licenses are dormant, the answer is no, and no amount of executive relationship saves you.

So the discovery conversation has two jobs that most reps collapse into one. Job one is getting to yes — that's the authority map. Job two is making yes durable — that's the adoption map. The daily-user question is the cheapest, fastest way to start job two on the very first call, at the exact moment when the prospect is most motivated to talk openly about how their team actually works.

What's the most underrated discovery question in B2B SaaS — figure 1

The four things this one question surfaces

The reason the question is worth a dedicated slot on your discovery framework is that a single, well-phrased ask about daily users returns four separate pieces of deal intelligence at once.

1. Pricing accuracy — and the trap of under-scoping. SaaS sellers systematically under-scope early-stage deals because the buyer describes the *pilot* population, not the *full* population. A prospect says "we'd start with a few people on the ops team," and the rep quotes three seats. Six months later the real deployment is fifteen users across two departments, and now you're renegotiating mid-contract — which strains the relationship and signals to the customer that you didn't understand their business. Getting the true recurring-user count on call one lets you price correctly from the start and forecast the deal at a realistic size instead of an optimistic one. It also lets you re-score your own pipeline honestly: real deal size is *recurring seats × price per seat × the probability those seats actually get adopted*, and most reps skip that last multiplier entirely.

2. Champion identification — the person who governs day-two. The signer and the governor are frequently different humans. The VP of Finance approves the purchase; the finance operations manager decides, every day, whether the team uses the tool or quietly reverts to the old spreadsheet. That operations manager is your true champion — but only if they were part of the conversation. When you ask "who's logging in every week," and the buyer names that person and describes their day, you've located the individual whose advocacy you need to earn between now and renewal. Multi-threading into that relationship early is what separates a one-year deal from a five-year account.

What's the most underrated discovery question in B2B SaaS — figure 2

3. Implementation realism — matching the promise to the user. Time-to-value is where SaaS deals go to die. The classic failure mode is promising a fast go-live to an executive who wants speed, then discovering the actual users are non-technical staff for whom "fast" is a fantasy. If the daily users are power analysts comfortable with data tools, aggressive timelines are fine. If they're field staff who need hand-holding, you need to set a longer, honest onboarding expectation — and you need to know that *before* you commit to a date in the proposal. The daily-user question is how you calibrate the promise to the people, not to the buyer's optimism.

4. Adoption prediction — the renewal, twelve months early. This is the quiet payoff. Users who feel ownership over the buying decision — who were consulted, whose workflow was solved for, who got to voice a concern — adopt faster and more durably than users who wake up one morning to a mandated new tool. Early adoption, in turn, is the most reliable leading indicator of renewal and expansion. So a question that gets end-users into the process on call one isn't just discovery; it's the first move in a retention strategy that pays off a year later. The frameworks most sellers already claim to use — MEDDIC and its cousin MEDDPICC — put "Identify Pain" and "Champion" at their core precisely because pain and advocacy live with the people doing the work, not with the signer.

How to ask it on call one — and what to do with the answer

The phrasing matters enormously, because a lazy version of this question returns a name and nothing else, while a good version returns a workflow, a tool stack, and a technical-comfort read in a single answer.

What's the most underrated discovery question in B2B SaaS — figure 3

The weak version: "Who else uses this?" This yields a list of names. Names are almost useless — they tell you nothing about workflow, volume, or friction.

The strong version: "When you picture this rolled out next quarter, who on your team is opening it Monday morning to do the actual work? Walk me through their day — what tool are they replacing, and how technical are they?" This forces the prospect to narrate a real workflow. You learn the recurring-user count, the incumbent tool you're displacing, and the enablement burden you're signing up for.

The best version — an ask, not just a question: "I'd love fifteen minutes with whoever does that today. Not a pitch — I just want to solve for their actual workflow so we don't build the wrong onboarding plan. Could we add them to the next call?" This does something the other versions can't: it *tests internal alignment.* A prospect who happily connects you to the end-users is telling you the project is real and sponsored. A prospect who deflects — "let's not involve them yet" — is telling you either that the project isn't internally aligned or that you're being walled off, and both are things you need to know now rather than in the forecast review.

Once you have the answer, it should immediately change your behavior in four ways:

What's the most underrated discovery question in B2B SaaS — figure 4

Build a stakeholder map that includes daily-user count, technical comfort level, and current tool stack for each user role. This isn't a CRM formality; it's the input to your demo plan. You demo differently to fifteen non-technical field users than to three power analysts.
Re-score the deal size honestly. Recompute seats, apply an adoption-probability haircut, and update the forecast. Reps who skip this consistently over-forecast and then miss.
Rewrite the implementation promise to match user reality, not buyer optimism. If the users need ninety days, say ninety days, and explain why. An honest longer timeline beats a dishonest short one that produces a failed go-live.
Multi-thread deliberately. Use the daily-user answer as your reason to get a second and third contact into the deal — the governor, a power user, a skeptic. Single-threaded deals are fragile; a champion who leaves takes the whole opportunity with them.

The follow-up questions that compound the effect

The daily-user question is the anchor, but three follow-ups turn a good discovery call into a great one. Each one attacks a different blind spot that generic discovery misses.

"What would make them stop logging in after week three?" This sounds pessimistic; it's actually the sharpest adoption question you can ask. It forces the prospect to articulate their current friction in operational terms rather than feature-comparison terms. When an operations manager says "they'll stop when the data sync breaks and they have to re-enter everything by hand," you've just discovered a critical integration requirement that may appear in no RFP anywhere. Adoption research across the SaaS industry consistently attributes early abandonment less to product quality and more to unanticipated workflow friction — the small daily annoyances that accumulate until people quietly revert to the old way. Surfacing even one of those "week-three killers" during discovery lets you address it in the demo and the implementation plan, and it doubles as a test of your champion: a champion who can't name a single reason a user might drop off probably lacks real visibility into how their team works.

"How do you measure success for those users — and who sees that data?" Most discovery stops at "what metrics matter?" and misses the more important question of *visibility*. The distinction between an executive KPI and the daily operational signal that predicts renewal is enormous. If your product's impact is invisible to the person who controls the budget, your renewal is at risk no matter how well the tool works. When a prospect says "our VP sees a monthly dashboard," you now know exactly which numbers your value story has to connect to twelve months from now. And if the answer is "honestly, we don't track individual usage — we just look at total license count," you've found a gap your onboarding and success team can fill, and you've prevented the classic disaster where five power users carry the product while forty-five licenses sit dormant and drag down both retention and expansion.

What's the most underrated discovery question in B2B SaaS — figure 5

"When does this team's busiest season start — and what happens to their tool usage during it?" Seasonality is the most overlooked variable in SaaS discovery because reps assume usage is linear. It rarely is. A financial planning tool used by ten analysts in a normal month might need to support forty during budget close. A retail analytics platform is trivial in February and mission-critical in November. Two things fall out of this question. First, capacity: if you scope licenses and performance to average usage, you set up both a technical failure and a relationship crisis during the exact weeks that matter most to the customer. Second, quantified pain: peak season is a natural place to attach a number to the problem — "during quarter-end close, each analyst loses roughly a dozen hours to manual reconciliation" — and MEDDIC-style frameworks are explicit that pain has to be quantified in business terms to survive a procurement review. Seasonality gives you that quantification for free.

When the daily-user question backfires

Any honest sales coach will tell you no question is universally correct, and this one has three real failure modes. Treating it as a rigid rule instead of a situational tactic is how good reps embarrass themselves.

What's the most underrated discovery question in B2B SaaS — figure 6

First, in top-down or heavily regulated buying motions, end-users are deliberately walled off. In banking, defense, healthcare, and parts of the public sector, procurement policy often forbids vendors from talking directly to staff mid-evaluation. Pushing too hard to get end-users on a call can burn credibility with the very economic buyer whose procurement office is telling them *not* to expose staff to vendors. In those motions you still need the adoption map — but you build it *through* the champion, second-hand, rather than by demanding direct access. The question becomes "help me understand the daily users' workflow so we scope this correctly," asked of your sponsor, not of the users themselves.

Second, the eye-popping close-rate gaps you'll see quoted in sales-coaching content are correlation, not causation. You'll find articles claiming multi-threaded deals close at some multiple of single-threaded ones. Directionally that's true and well-supported, but the raw numbers are not controlled experiments. Deals where end-users are willing to join calls are *also* deals with stronger internal sponsorship to begin with — the willingness and the win are both symptoms of a healthy deal. Dragging a junior end-user into a call where the executive hasn't actually bought in doesn't magically lift your odds; it can dilute executive attention and slow the cycle. Multi-threading amplifies a deal that already has a pulse; it does not resuscitate a dead one.

Third, end-users can anchor on features the buyer will never fund. Give a power user the floor and they may fixate on a capability that's genuinely useful to them but irrelevant to the economic buyer's business case — and now you've created an internal misalignment that takes weeks to unwind. This risk is highest in product-led-growth (PLG) motions, where end-user enthusiasm is already flowing organically through free or self-serve usage. If you have a strong PLG motion, you often don't need this question on the *first* sales call — the end-user pull is already there. You need it on the *expansion* call, when you're converting organic adoption into a larger contract.

The honest synthesis: this is the most underrated discovery question in classic, top-down, sales-led B2B SaaS — roughly the mid-market and lower-enterprise range where a human seller is driving a considered purchase across a fragmented buying group. At the very top of the market, in regulated verticals with strict procurement walls, it becomes a tactic you execute through a champion rather than a question you ask directly. And in bottom-up PLG motions, its timing shifts from acquisition to expansion. Knowing *which* motion you're in is itself a discovery skill — and it's why "always ask about daily users" is good advice, while "always ask them directly, on call one, of everyone" is not.

FAQ

What if the prospect says they don't know who else would log in?

That's diagnostic, not a dead end. Not knowing usually means one of two things: the project is very early, or your contact is too junior to have visibility into the broader team. Ask them to check with their manager, or to run a quick internal poll before your next call. If they genuinely can't name a single other recurring user, treat it as a yellow flag on deal velocity — projects with exactly one committed person tend to stall — and factor that into your forecast rather than ignoring it.

How do I ask this without sounding like I'm prying into their org chart or just counting seats?

Frame it as *planning*, not *inventory*. "To make sure onboarding actually goes smoothly, could you walk me through a typical week for the people who'd use this day-to-day?" positions you as a partner trying to prevent disruption, not a rep trying to inflate the quote. The workflow framing ("walk me through their week") almost always feels helpful, whereas the seat framing ("how many licenses") almost always feels transactional. Same information, very different reception.

Does this work for low-frequency tools, or only daily-use products?

It works for both — you just change the cadence in the phrasing. For a monthly reporting product, ask "who needs to review this report each month, and what do they do with it?" For a daily CRM or support tool, ask "who's opening this every morning?" The underlying principle is constant: the number of *recurring* users always predicts retention far better than the number of *licenses sold*. Match the timeframe in your question to the natural rhythm of the product.

What do I do when the prospect only names decision-makers and skips the end-users entirely?

Redirect gently and specifically. "That's really helpful — and for the folks who'd actually be clicking through this every day, the ones doing the hands-on work, who are they?" Buyers routinely forget the admins, coordinators, and junior analysts who drive the real usage, precisely because those people aren't in the buying meetings. Those forgotten roles are usually where under-scoping and later churn originate, so it's worth the small nudge to surface them.

How does this question change a pricing or negotiation conversation?

It moves the pricing conversation to the front, where it's cheap, instead of the back, where it's expensive. Discovering fifteen real users up front lets you scope and price accurately from day one. Discovering them *after* you've quoted three seats forces an awkward mid-contract renegotiation — you either eat the cost or ask for more money, and both erode trust. Accurate early scoping is quietly one of the biggest levers on both your deal size and your relationship health.

Can I use this in the demo, or is it strictly a discovery-call question?

Use it in the demo too. As you walk through a workflow, pause and ask "picture your team here — who's the person who'd live in this screen most, and what would their week look like?" This keeps the demo grounded in the prospect's real usage instead of a generic feature tour, and it frequently surfaces adoption blockers — integration gaps, permission concerns, training needs — while you still have time to address them before a contract is drafted.

Sources

Gartner — B2B Buying Journey research (buying-group size, buyer enablement, "buying jobs"): https://www.gartner.com/en/sales/insights/b2b-buying-journey
Harvard Business Review — "The New Sales Imperative" (buyer consensus and group decision-making in complex B2B purchases): https://hbr.org/2017/03/the-new-sales-imperative
Gong — Labs research on sales conversations and multi-threading: https://www.gong.io/resources/labs/
Bessemer Venture Partners — State of the Cloud / Atlas (SaaS efficiency and retention benchmarks): https://www.bvp.com/atlas
SaaS Capital — B2B SaaS metrics, retention, and growth benchmark research: https://www.saas-capital.com/
MEDDIC Academy — MEDDIC / MEDDPICC qualification framework (Metrics, Economic Buyer, Champion, Pain): https://meddic.academy/
Forrester — B2B buyer journey and technology purchasing research: https://www.forrester.com/

flowchart TD A[Discovery call one] --> B{Who did you map} B -->|Only the buyer| C[Authority map] B -->|Buyer plus daily users| D[Authority plus adoption map] C --> E[Deal signs] D --> F[Deal signs] E --> G[No user voice, surprise rollout] F --> H[User voice, calibrated rollout] G --> I[Low early adoption] H --> J[High early adoption] I --> K[Churn risk at renewal] J --> L[Renewal plus expansion]

flowchart LR A["Anchor question: who logs in weekly"] --> B["Follow-up: week three drop-off"] A --> C["Follow-up: how success is measured"] A --> D["Follow-up: peak season load"] B --> E[Integration and friction requirements] C --> F[Value story tied to buyer visible metric] D --> G[Capacity plan and quantified pain] E --> H[Stronger demo and implementation plan] F --> H G --> H H --> I[Durable adoption and renewal]

Related on PULSE

[What is the most effective question to ask after a discovery call to evaluate qualification quality?](/knowledge/q14363)
[What specific question helps a rep realize they are not asking enough discovery questions during the first call?](/knowledge/q14412)
[What's the best discovery question to ask when a buyer says they're "just exploring" with no clear timeline?](/knowledge/q1103)
[What is the most effective question to determine if a rep is relying too heavily on discounts to close deals?](/knowledge/q14406)
[What role does generative AI play in B2B sales discovery calls this year?](/knowledge/q16691)

Download:

## Direct Answer

The most underrated discovery question in B2B SaaS is: **"Who else on your team would be logging into this every week, and what does their day actually look like?"**

Most sellers are trained to map *authority* — find the economic buyer, the champion, the blocker, the person who signs. That instinct is correct but incomplete. It optimizes for getting the deal *signed* and quietly ignores the population that determines whether the deal gets *renewed and expanded*: the five, fifteen, or fifty end-users who will open your product on a Monday morning to get real work done. Authority closes the first contract. Adoption closes every contract after it. In a subscription business, where the economics only work if a customer stays for years, the second number is the one that pays your bills.

This question outperforms flashier discovery questions ("What's your budget?", "What's your timeline?", "What keeps you up at night?") for four concrete reasons. It **corrects your pricing** — if you scoped three seats and the real daily-user count is fifteen, you are about to be badly underpriced and badly under-resourced for onboarding. It **finds your real champion** — the executive signs, but the operations lead governs day-two reality, and that person only defends your renewal if they felt heard on call one. It **makes your implementation promise honest** — a thirty-day go-live pitched to a CFO is malpractice if the actual users are non-technical staff who need sixty to ninety days of enablement. And it **predicts adoption** — users who had a voice in the buying decision adopt dramatically faster than users who are surprised by a rollout, and early adoption is the single strongest leading indicator of whether a customer renews.

If a reader stops here, this is the whole answer: **stop mapping only who has authority and start mapping who has the workflow.** The buyer signs the contract; the daily user signs the renewal. Ask about the daily user on the first call, quantify how many there are and what tools they're replacing, and you protect the entire lifetime value of the account before you've even built the demo. Everything below is the mechanics — why it works, exactly how to phrase it, what to do with the answer, and the specific situations where it backfires.

## Why stakeholder breadth beats stakeholder rank

The prevailing wisdom in enterprise sales is "sell higher." Get to the VP. Skip the gatekeepers. And there is real truth in it — deals with no executive sponsor stall in procurement forever. But "sell higher" has curdled into a lazy heuristic that treats everyone below the buyer as noise. That's a mistake the subscription model punishes with unusual cruelty.

Gartner's research on the modern B2B buying journey has been consistent for years: a typical purchase now involves a **buying group of roughly six to ten people**, and that number climbs with deal size and organizational complexity. Those people don't move in lockstep. They gather information independently, form private opinions, and reconcile them in rooms you are never invited to. Harvard Business Review's work on "buyer enablement" and the consensus problem describes the same dynamic from the other side — the harder part of a complex B2B sale is often not convincing one person but helping a fractured group agree with itself. A seller who has only spoken to the economic buyer is, functionally, blind to most of the room.

Here is the asymmetry that makes the daily-user question so valuable and so overlooked. The **economic buyer's risk is the purchase decision** — did they choose the right vendor, did they get a defensible price. Once the contract is signed, that person's attention moves on to the next fire. The **daily user's risk is the workflow** — every single day for the life of the contract, your product either makes their job easier or harder. When renewal season arrives eleven months later, nobody asks the CFO whether the tool is good. They ask the operations manager, "Are we still using this?" If forty of fifty licenses are dormant, the answer is no, and no amount of executive relationship saves you.

So the discovery conversation has two jobs that most reps collapse into one. Job one is **getting to yes** — that's the authority map. Job two is **making yes durable** — that's the adoption map. The daily-user question is the cheapest, fastest way to start job two on the very first call, at the exact moment when the prospect is most motivated to talk openly about how their team actually works.

![What's the most underrated discovery question in B2B SaaS — figure 1](/assets/qa/q55-b1.jpg)


## The four things this one question surfaces

The reason the question is worth a dedicated slot on your discovery framework is that a single, well-phrased ask about daily users returns four separate pieces of deal intelligence at once.

**1. Pricing accuracy — and the trap of under-scoping.** SaaS sellers systematically under-scope early-stage deals because the buyer describes the *pilot* population, not the *full* population. A prospect says "we'd start with a few people on the ops team," and the rep quotes three seats. Six months later the real deployment is fifteen users across two departments, and now you're renegotiating mid-contract — which strains the relationship and signals to the customer that you didn't understand their business. Getting the true recurring-user count on call one lets you price correctly from the start and forecast the deal at a realistic size instead of an optimistic one. It also lets you re-score your own pipeline honestly: real deal size is *recurring seats × price per seat × the probability those seats actually get adopted*, and most reps skip that last multiplier entirely.

**2. Champion identification — the person who governs day-two.** The signer and the governor are frequently different humans. The VP of Finance approves the purchase; the finance operations manager decides, every day, whether the team uses the tool or quietly reverts to the old spreadsheet. That operations manager is your true champion — but only if they were part of the conversation. When you ask "who's logging in every week," and the buyer names that person and describes their day, you've located the individual whose advocacy you need to earn between now and renewal. Multi-threading into that relationship early is what separates a one-year deal from a five-year account.

![What's the most underrated discovery question in B2B SaaS — figure 2](/assets/qa/q55-b2.jpg)


**3. Implementation realism — matching the promise to the user.** Time-to-value is where SaaS deals go to die. The classic failure mode is promising a fast go-live to an executive who wants speed, then discovering the actual users are non-technical staff for whom "fast" is a fantasy. If the daily users are power analysts comfortable with data tools, aggressive timelines are fine. If they're field staff who need hand-holding, you need to set a longer, honest onboarding expectation — and you need to know that *before* you commit to a date in the proposal. The daily-user question is how you calibrate the promise to the people, not to the buyer's optimism.

**4. Adoption prediction — the renewal, twelve months early.** This is the quiet payoff. Users who feel ownership over the buying decision — who were consulted, whose workflow was solved for, who got to voice a concern — adopt faster and more durably than users who wake up one morning to a mandated new tool. Early adoption, in turn, is the most reliable leading indicator of renewal and expansion. So a question that gets end-users into the process on call one isn't just discovery; it's the first move in a retention strategy that pays off a year later. The frameworks most sellers already claim to use — MEDDIC and its cousin MEDDPICC — put "Identify Pain" and "Champion" at their core precisely because pain and advocacy live with the people doing the work, not with the signer.

```mermaid
flowchart TD
    A[Discovery call one] --> B{Who did you map}
    B -->|Only the buyer| C[Authority map]
    B -->|Buyer plus daily users| D[Authority plus adoption map]
    C --> E[Deal signs]
    D --> F[Deal signs]
    E --> G[No user voice, surprise rollout]
    F --> H[User voice, calibrated rollout]
    G --> I[Low early adoption]
    H --> J[High early adoption]
    I --> K[Churn risk at renewal]
    J --> L[Renewal plus expansion]
```

## How to ask it on call one — and what to do with the answer

The phrasing matters enormously, because a lazy version of this question returns a name and nothing else, while a good version returns a workflow, a tool stack, and a technical-comfort read in a single answer.

![What's the most underrated discovery question in B2B SaaS — figure 3](/assets/qa/q55-b3.jpg)


**The weak version:** "Who else uses this?" This yields a list of names. Names are almost useless — they tell you nothing about workflow, volume, or friction.

**The strong version:** "When you picture this rolled out next quarter, who on your team is opening it Monday morning to do the actual work? Walk me through their day — what tool are they replacing, and how technical are they?" This forces the prospect to narrate a real workflow. You learn the recurring-user count, the incumbent tool you're displacing, and the enablement burden you're signing up for.

**The best version — an ask, not just a question:** "I'd love fifteen minutes with whoever does that today. Not a pitch — I just want to solve for their actual workflow so we don't build the wrong onboarding plan. Could we add them to the next call?" This does something the other versions can't: it *tests internal alignment.* A prospect who happily connects you to the end-users is telling you the project is real and sponsored. A prospect who deflects — "let's not involve them yet" — is telling you either that the project isn't internally aligned or that you're being walled off, and both are things you need to know now rather than in the forecast review.

Once you have the answer, it should immediately change your behavior in four ways:

![What's the most underrated discovery question in B2B SaaS — figure 4](/assets/qa/q55-b4.jpg)


- **Build a stakeholder map that includes daily-user count, technical comfort level, and current tool stack** for each user role. This isn't a CRM formality; it's the input to your demo plan. You demo differently to fifteen non-technical field users than to three power analysts.
- **Re-score the deal size honestly.** Recompute seats, apply an adoption-probability haircut, and update the forecast. Reps who skip this consistently over-forecast and then miss.
- **Rewrite the implementation promise to match user reality, not buyer optimism.** If the users need ninety days, say ninety days, and explain why. An honest longer timeline beats a dishonest short one that produces a failed go-live.
- **Multi-thread deliberately.** Use the daily-user answer as your reason to get a second and third contact into the deal — the governor, a power user, a skeptic. Single-threaded deals are fragile; a champion who leaves takes the whole opportunity with them.

## The follow-up questions that compound the effect

The daily-user question is the anchor, but three follow-ups turn a good discovery call into a great one. Each one attacks a different blind spot that generic discovery misses.

**"What would make them stop logging in after week three?"** This sounds pessimistic; it's actually the sharpest adoption question you can ask. It forces the prospect to articulate their current friction in operational terms rather than feature-comparison terms. When an operations manager says "they'll stop when the data sync breaks and they have to re-enter everything by hand," you've just discovered a critical integration requirement that may appear in no RFP anywhere. Adoption research across the SaaS industry consistently attributes early abandonment less to product quality and more to unanticipated workflow friction — the small daily annoyances that accumulate until people quietly revert to the old way. Surfacing even one of those "week-three killers" during discovery lets you address it in the demo and the implementation plan, and it doubles as a test of your champion: a champion who can't name a single reason a user might drop off probably lacks real visibility into how their team works.

**"How do you measure success for those users — and who sees that data?"** Most discovery stops at "what metrics matter?" and misses the more important question of *visibility*. The distinction between an executive KPI and the daily operational signal that predicts renewal is enormous. If your product's impact is invisible to the person who controls the budget, your renewal is at risk no matter how well the tool works. When a prospect says "our VP sees a monthly dashboard," you now know exactly which numbers your value story has to connect to twelve months from now. And if the answer is "honestly, we don't track individual usage — we just look at total license count," you've found a gap your onboarding and success team can fill, and you've prevented the classic disaster where five power users carry the product while forty-five licenses sit dormant and drag down both retention and expansion.

![What's the most underrated discovery question in B2B SaaS — figure 5](/assets/qa/q55-b5.jpg)


**"When does this team's busiest season start — and what happens to their tool usage during it?"** Seasonality is the most overlooked variable in SaaS discovery because reps assume usage is linear. It rarely is. A financial planning tool used by ten analysts in a normal month might need to support forty during budget close. A retail analytics platform is trivial in February and mission-critical in November. Two things fall out of this question. First, capacity: if you scope licenses and performance to average usage, you set up both a technical failure and a relationship crisis during the exact weeks that matter most to the customer. Second, quantified pain: peak season is a natural place to attach a number to the problem — "during quarter-end close, each analyst loses roughly a dozen hours to manual reconciliation" — and MEDDIC-style frameworks are explicit that pain has to be quantified in business terms to survive a procurement review. Seasonality gives you that quantification for free.

```mermaid
flowchart LR
    A[Anchor question: who logs in weekly] --> B[Follow-up: week three drop-off]
    A --> C[Follow-up: how success is measured]
    A --> D[Follow-up: peak season load]
    B --> E[Integration and friction requirements]
    C --> F[Value story tied to buyer visible metric]
    D --> G[Capacity plan and quantified pain]
    E --> H[Stronger demo and implementation plan]
    F --> H
    G --> H
    H --> I[Durable adoption and renewal]
```

## When the daily-user question backfires

Any honest sales coach will tell you no question is universally correct, and this one has three real failure modes. Treating it as a rigid rule instead of a situational tactic is how good reps embarrass themselves.

![What's the most underrated discovery question in B2B SaaS — figure 6](/assets/qa/q55-b6.jpg)


**First, in top-down or heavily regulated buying motions, end-users are deliberately walled off.** In banking, defense, healthcare, and parts of the public sector, procurement policy often forbids vendors from talking directly to staff mid-evaluation. Pushing too hard to get end-users on a call can burn credibility with the very economic buyer whose procurement office is telling them *not* to expose staff to vendors. In those motions you still need the adoption map — but you build it *through* the champion, second-hand, rather than by demanding direct access. The question becomes "help me understand the daily users' workflow so we scope this correctly," asked of your sponsor, not of the users themselves.

**Second, the eye-popping close-rate gaps you'll see quoted in sales-coaching content are correlation, not causation.** You'll find articles claiming multi-threaded deals close at some multiple of single-threaded ones. Directionally that's true and well-supported, but the raw numbers are not controlled experiments. Deals where end-users are willing to join calls are *also* deals with stronger internal sponsorship to begin with — the willingness and the win are both symptoms of a healthy deal. Dragging a junior end-user into a call where the executive hasn't actually bought in doesn't magically lift your odds; it can dilute executive attention and slow the cycle. Multi-threading amplifies a deal that already has a pulse; it does not resuscitate a dead one.

**Third, end-users can anchor on features the buyer will never fund.** Give a power user the floor and they may fixate on a capability that's genuinely useful to them but irrelevant to the economic buyer's business case — and now you've created an internal misalignment that takes weeks to unwind. This risk is highest in product-led-growth (PLG) motions, where end-user enthusiasm is already flowing organically through free or self-serve usage. If you have a strong PLG motion, you often don't need this question on the *first* sales call — the end-user pull is already there. You need it on the *expansion* call, when you're converting organic adoption into a larger contract.

The honest synthesis: this is the most underrated discovery question in **classic, top-down, sales-led B2B SaaS** — roughly the mid-market and lower-enterprise range where a human seller is driving a considered purchase across a fragmented buying group. At the very top of the market, in regulated verticals with strict procurement walls, it becomes a tactic you execute through a champion rather than a question you ask directly. And in bottom-up PLG motions, its timing shifts from acquisition to expansion. Knowing *which* motion you're in is itself a discovery skill — and it's why "always ask about daily users" is good advice, while "always ask them directly, on call one, of everyone" is not.

## FAQ

### What if the prospect says they don't know who else would log in?

That's diagnostic, not a dead end. Not knowing usually means one of two things: the project is very early, or your contact is too junior to have visibility into the broader team. Ask them to check with their manager, or to run a quick internal poll before your next call. If they genuinely can't name a single other recurring user, treat it as a yellow flag on deal velocity — projects with exactly one committed person tend to stall — and factor that into your forecast rather than ignoring it.

### How do I ask this without sounding like I'm prying into their org chart or just counting seats?

Frame it as *planning*, not *inventory*. "To make sure onboarding actually goes smoothly, could you walk me through a typical week for the people who'd use this day-to-day?" positions you as a partner trying to prevent disruption, not a rep trying to inflate the quote. The workflow framing ("walk me through their week") almost always feels helpful, whereas the seat framing ("how many licenses") almost always feels transactional. Same information, very different reception.

### Does this work for low-frequency tools, or only daily-use products?

It works for both — you just change the cadence in the phrasing. For a monthly reporting product, ask "who needs to review this report each month, and what do they do with it?" For a daily CRM or support tool, ask "who's opening this every morning?" The underlying principle is constant: the number of *recurring* users always predicts retention far better than the number of *licenses sold*. Match the timeframe in your question to the natural rhythm of the product.

### What do I do when the prospect only names decision-makers and skips the end-users entirely?

Redirect gently and specifically. "That's really helpful — and for the folks who'd actually be clicking through this every day, the ones doing the hands-on work, who are they?" Buyers routinely forget the admins, coordinators, and junior analysts who drive the real usage, precisely because those people aren't in the buying meetings. Those forgotten roles are usually where under-scoping and later churn originate, so it's worth the small nudge to surface them.

### How does this question change a pricing or negotiation conversation?

It moves the pricing conversation to the front, where it's cheap, instead of the back, where it's expensive. Discovering fifteen real users up front lets you scope and price accurately from day one. Discovering them *after* you've quoted three seats forces an awkward mid-contract renegotiation — you either eat the cost or ask for more money, and both erode trust. Accurate early scoping is quietly one of the biggest levers on both your deal size and your relationship health.

### Can I use this in the demo, or is it strictly a discovery-call question?

Use it in the demo too. As you walk through a workflow, pause and ask "picture your team here — who's the person who'd live in this screen most, and what would their week look like?" This keeps the demo grounded in the prospect's real usage instead of a generic feature tour, and it frequently surfaces adoption blockers — integration gaps, permission concerns, training needs — while you still have time to address them before a contract is drafted.

## Sources

- Gartner — B2B Buying Journey research (buying-group size, buyer enablement, "buying jobs"): https://www.gartner.com/en/sales/insights/b2b-buying-journey
- Harvard Business Review — "The New Sales Imperative" (buyer consensus and group decision-making in complex B2B purchases): https://hbr.org/2017/03/the-new-sales-imperative
- Gong — Labs research on sales conversations and multi-threading: https://www.gong.io/resources/labs/
- Bessemer Venture Partners — State of the Cloud / Atlas (SaaS efficiency and retention benchmarks): https://www.bvp.com/atlas
- SaaS Capital — B2B SaaS metrics, retention, and growth benchmark research: https://www.saas-capital.com/
- MEDDIC Academy — MEDDIC / MEDDPICC qualification framework (Metrics, Economic Buyer, Champion, Pain): https://meddic.academy/
- Forrester — B2B buyer journey and technology purchasing research: https://www.forrester.com/

## Related on PULSE

- [What is the most effective question to ask after a discovery call to evaluate qualification quality?](/knowledge/q14363)
- [What specific question helps a rep realize they are not asking enough discovery questions during the first call?](/knowledge/q14412)
- [What's the best discovery question to ask when a buyer says they're "just exploring" with no clear timeline?](/knowledge/q1103)
- [What is the most effective question to determine if a rep is relying too heavily on discounts to close deals?](/knowledge/q14406)
- [What role does generative AI play in B2B sales discovery calls this year?](/knowledge/q16691)

Was this helpful?

Sources cited

gong.iohttps://www.gong.io/forcemanagement.comhttps://forcemanagement.com/sandler.comhttps://www.sandler.com/bvp.comhttps://www.bvp.com/atlas/state-of-the-cloud-2026 iconiqcapital.comhttps://www.iconiqcapital.com/insights/state-of-saas keybanccm.comhttps://www.keybanccm.com/insights/saas-survey

⌬ Apply this in PULSE

Gross Profit CalculatorModel margin per deal, per rep, per territory How-To · SaaS ChurnSilent revenue killer playbook

Kory White