The AE ran a good first call with the VP of Operations. The pain was real and the opportunity moved to stage three. Then the CFO and the CTO joined. The CFO asked what the purchase would return in the first year, and nobody had a number the buyer had agreed to. The CTO asked who would own the CRM integration, and the AE promised to "loop in a solutions engineer." Six weeks later the deal was still "in review": two of the three people who decide had never been given a reason to say yes.
The discovery was not wrong. It was written for one person. This guide gives a question bank for three personas who may shape a purchase at a $3M to $30M ARR B2B SaaS company, organized by what each owns, the unit they measure pain in, and the proof they need.
Meeting a CFO, VP of Operations or CTO this week? Pitch Pacer takes who is on the call and what is broken, then returns a stage-by-stage script with minutes attached. A work email opens the tool for 30 minutes.
The buying group has grown wider and better prepared. Forrester's State of Business Buying 2024, published in December 2024, found that on average 13 people are involved in a buying decision and that 89 percent of purchases involve two or more departments. G2's 2026 Buyer Behavior Report, based on a June 2026 survey of 1,038 software decision-makers, found that finance involvement in software decisions rose from 31 percent to 46 percent in a single year, and that 49 percent of buyers said their CFO had vetoed an already-approved software purchase in the previous 12 months.
The executives in that group arrive with their homework done. Wynter's 2025 survey of 200 B2B SaaS leaders at companies above $50M in revenue (100 finance, 100 technology) found that 84 percent of technology leaders review vendors before any sales call, and 78 percent of finance leaders verify their team's vendor picks independently.
That makes this a sales operations problem, not a talent problem. Strong AEs adapt to the person in front of them by instinct; a persona question bank is how the rest of the team does it on purpose.
Diagnosis: why generic discovery call questions stall with executives
Four failures explain most stalls like the one above.
1. One question list for every title
Most discovery question lists are grouped by topic (process, tools, budget, timeline) rather than by who is answering. A CFO asked to "walk me through your current process," or a CTO asked about budget, hears a question for someone else. Executives give short answers outside their remit, and the rep reads them as low interest.
2. The pain is never translated into the persona's unit
The VP of Operations says the team loses "a lot of time" reconciling handoffs. That is real, but it is not yet a CFO problem. Until someone converts hours into dollars, the finance leader has nothing to weigh against the price, and with finance in nearly half of software decisions, that translation is no longer optional.
3. Asking executives what their website, their team or your intake form already said
A technology leader who read your documentation before the call does not want to explain their stack from the top. Questions that collect facts research could have answered spend the minutes executives give least willingly, and signal that the rep did not prepare.
4. The ROI story is the vendor's, not the buyer's
When 58 percent of finance leaders say they do not trust vendor ROI calculations (Wynter, 2025), a slide with your own numbers is weak evidence. A cost the buyer stated, in their own words, is strong evidence, and most discovery calls never ask for it.
Framework: the Three-Lens discovery question bank
The framework keeps the structure of a good discovery call and changes the questions by persona. Each question is tagged with its job: Confirm tests a pain hypothesis, Size puts a number on it in the persona's unit, and Decide maps how that person will judge the purchase. Treat the bank as a suggested starting point, not a benchmark, and replace questions that do not earn answers in your market.
| Persona | What they own | Unit of pain | Proof they need |
|---|---|---|---|
| CFO / VP Finance | Budget, return, contract terms, vendor risk | Dollars, payback period, risk to a forecast or audit | A cost of the problem they agreed to, total cost of ownership, exit terms |
| VP of Operations | Process, throughput, the team doing the work | Hours, cycle time, error and rework rates | A credible rollout plan, who does what, how adoption is measured |
| CTO / VP Technology | Architecture, security, integration, technical debt | Risk, maintenance load, engineering time | Integration detail, data access scope, a way to test before committing |
Discovery call questions for the CFO
The CFO set assumes the rep knows the problem from an earlier call and is testing whether it is worth funding. Wynter found that cost (76 percent) and ROI (48 percent) were finance leaders' top selection criteria, and 66 percent evaluate total cost of ownership, so every question points at a number.
| Job | Question |
|---|---|
| Confirm | "Your operations team described this problem to us. When it shows up in your numbers, where does it show up first: revenue, cost, or a forecast you had to revise?" |
| Size | "If nothing changes for the next twelve months, what does this cost you? I would rather use your estimate than ours." |
| Size | "What return would a purchase like this need to show, and over what period, for you to approve it?" |
| Decide | "How do you build the business case internally? Is there a template or a threshold above which you review every purchase yourself?" |
| Decide | "Which contract terms matter most to you: term length, exit rights, price protection, payment schedule?" |
| Decide | "What would make you stop a purchase your team had already approved?" |
The second question carries the call: write the CFO's answer down in their words and reuse it in every later document. The last question is uncomfortable but valuable; with 49 percent of G2's 2026 respondents reporting a CFO veto of an approved purchase, knowing the veto criteria early is cheaper than discovering them at signature.
Discovery call questions for the VP of Operations
The VP of Operations usually feels the problem first and becomes the champion. Their questions are about the work: how much time it takes, where it breaks, and what a change would ask of the team. G2's 2026 report lists implementation planning as a post-selection delay for 25 percent of buyers, and the operations leader is the person who will be asked whether the plan is realistic.
| Job | Question |
|---|---|
| Confirm | "Walk me through the last time this went wrong. Who noticed, how, and how long after it happened?" |
| Size | "How many hours a week does your team spend on the manual workaround, and whose hours are they?" |
| Size | "How often does an error get through, and what does one cost to fix once a customer or a rep has seen it?" |
| Decide | "What did the last rollout of a new tool cost your team, and what would you do differently?" |
| Decide | "Who on your team would own this day to day, and how much of their time can you give it in the first month?" |
| Decide | "How will you know in ninety days that it worked? What number would you show your CEO?" |
The hours answer is the bridge to the CFO: multiply it by a loaded cost the buyer agrees to, and the operations problem becomes a finance problem with a number both recognize.
Discovery call questions for the CTO
The CTO wants to know whether the product can work in their environment without adding risk or maintenance load. Wynter reports that 83 percent of technology leaders want to explore before any sales conversation, so the best CTO questions acknowledge that research and go past it. G2 found IT security review is the biggest source of delay after vendor selection, cited by 39 percent of buyers in 2026, so the security path is a discovery topic, not a procurement afterthought.
| Job | Question |
|---|---|
| Confirm | "If you have reviewed the technical material already, which part of your stack worries you most about this connection?" |
| Confirm | "Where does the data for this process live today, and which system is the source of truth when two of them disagree?" |
| Size | "How much engineering time goes into keeping the current workaround running: scripts, syncs, fixes after field changes?" |
| Decide | "What does your security review need from us, who runs it, and how long does it usually take?" |
| Decide | "What access would you be comfortable granting at the start, read-only or write, and who approves widening it?" |
| Decide | "How would you want to test this before committing: a sandbox, a pilot on historical data, or a limited live rollout?" |
Implementation: putting persona questions into your sales process
As a planning exercise, allow three to four weeks from first draft to routine use, then adjust for your team. This is a suggested rollout, not a measured benchmark.
Map who actually decided your last twenty deals. Pull ten won and ten lost opportunities and record which titles joined, when, and who raised the objection that stalled each one.
Write the bank by segment, one page per persona. Start from the tables above and replace the problem language with the two or three pains your won deals actually solved. Six questions per page, used in preparation, not read aloud.
Add persona fields to the opportunity. For each persona, a contact lookup, a "cost of the problem in their words" field, and a status (not engaged, engaged, evidence captured). Require the CFO cost field before proposal, so no business case rests on the vendor's own estimate.
Prepare every executive call against the persona page. Ten minutes before, choose two Confirm, one Size and two Decide questions, and set a time budget. Pitch Pacer or a shared template makes that a habit.
Review executive calls weekly. Managers check one per rep: did the rep get a number in the persona's unit, stored in the buyer's words? Coach on the missing number, not on style.
Recalibrate after one quarter. Compare deals with all three persona fields filled against deals without. If a persona's fields do not change outcomes in a segment, stop requiring them there.
Workflow: who owns each part of persona discovery
Attach the likely finance, operations and technology contacts to the opportunity.
Discovery with the champion first, then a short call with each other persona, capturing the cost in each one's words.
Review deals by persona coverage, not just stage. A stage-three deal with no finance contact engaged is flagged before the business case is written.
Owns the question bank, the persona fields and the stage gate, and reports persona coverage next to win rate each quarter.
Board narrative: explaining multi-persona discovery in three sentences
When the board asks why deals slip late, these statements tie the answer to discovery.
"Reps now prepare separate discovery questions for the finance, operations and technology leaders in each deal, and record the cost of the problem in each one's words before any proposal."
"G2's 2026 survey found finance involved in close to half of software decisions, and 49 percent of buyers reported a CFO veto of an approved purchase. We engage finance before proposal so its approval criteria are not discovered at signature."
"Each quarter we compare win rate and cycle length for deals with and without full persona coverage, and drop the requirement where it does not move outcomes."
Cross-domain: where persona discovery connects to the rest of the revenue engine
Persona evidence is only useful if it reaches the next person who needs it: the CFO's stated cost belongs in the proposal, and the operations leader's ninety-day measure belongs with the customer success manager at kickoff. Moving that context without asking the buyer again is the job of a Handoff Orchestrator, and our piece on why deals die between marketing, SDR and AE shows where that context usually drops.
Persona coverage is also a pipeline quality signal: a Pipeline Hygiene Sentinel can flag opportunities that reached proposal with no finance contact or an empty cost field. Stage definitions that require evidence rather than activity follow the principle in our guide to evidence-gated lifecycle stage logic. And to turn operational gaps into dollar figures a CFO will accept, our leak ledger framework is a useful model.
Frequently asked questions
What questions should you ask a CFO on a discovery call?
Ask a CFO questions that lead to a number they agree with: what the problem costs if nothing changes for a year, what return a purchase needs to show and over what period, how the business case is built internally, which contract terms matter most, and what would make them stop an approved purchase. Avoid process walkthroughs, which belong with the operations team.
How do you talk to a CTO in a sales discovery call?
Assume the CTO has already read your documentation, and start from their concerns rather than your overview. Ask which part of their stack worries them most, where the relevant data lives and which system wins when two disagree, what their security review requires, what access they would grant at the start, and how they would want to test the product before committing.
What are good discovery questions for operations leaders?
Good discovery questions for operations leaders focus on the work: the last time the problem occurred and who noticed, the weekly hours spent on workarounds, how often errors get through and what each costs, who would own the new process day to day, and what number would prove success in ninety days. Their hours become the basis for the CFO's dollar figure.
Should discovery questions be different for each stakeholder?
Yes. Each stakeholder judges the same problem in a different unit: finance in dollars and risk, operations in hours and errors, technology in integration risk and engineering time. Keep one shared structure of confirm, size and decide, but write the questions in each person's terms so every member of the buying group has evidence of their own to defend the purchase.
How many stakeholders are involved in a B2B software purchase?
Forrester's State of Business Buying 2024 found that an average of 13 people are involved in a B2B buying decision, and that 89 percent of purchases involve two or more departments. The number for a particular $3M to $30M ARR company depends on its actual buying process; map the finance, operations and technology stakeholders rather than assuming they all join every deal.
Sources: G2, 2026 Buyer Behavior Report press release (1,038 B2B software decision-makers, surveyed June 2026), July 2026. Forrester, "The State of Business Buying, 2024", December 2024. Wynter, "How CFOs and CTOs buy B2B software in 2025" (200 finance and technology leaders surveyed at companies with $50M+ revenue), 2025. VANDFORT, Pitch Pacer page, accessed November 2026.
