Checklist: Question-based Selling

"With Weflow, we’re now capturing all relevant activities and have full transparency into the performance of each sales rep. It’s a game changer."

"Weflow gives us better visibility and predictability of our business."

"Weflow eliminated the need for our VP to ask, ‘Did you follow up with that deal?’. It tracks customer interactions automatically, creating a framework that drives accountability across the team."


"None of the other tools gave us a solution like Weflow. From the beginning, we had a really smooth process."
.webp)
"I had a first introductory call with Weflow. I think I was sold after 15 minutes. There’s no question that the people at Weflow understood the problems that we were trying to solve."

"I’ve worked with Gong before, but Weflow’s simplicity and real-time sync are game-changing."
.webp)


"We use Weflow to auto-capture activity data, run deal reviews, and analyze our pipeline to inform our forecast. Being able to spot deal risks early has improved win rates and pipeline health."

What's Inside
Goal discovery prompts
- Direct questions to surface the prospect's top need and why it ranks above competing team priorities
- Prompts that connect team-level goals to broader business outcomes the executive layer actually cares about
- Questions to test internal alignment and flag whether other stakeholders see the goal as equally critical
Outcome definition questions
- Prompts that push past the stated goal to define what the buyer actually considers a successful outcome
- Questions that separate individual buyer wins from team-level wins so you can map value to each stakeholder
- Comparative framing that forces the buyer to articulate how success changes their position versus the status quo
Obstacle and risk mapping
- Questions that surface prior failed attempts and the specific reasons those initiatives did not stick
- Prompts to map competitive history, including which solutions were tried and where they broke down
- Discovery angles that expose internal dissenters, late-stage challenges, and new hurdles success itself could create

Daniel Schemmert
Daniel Schemmert is the Head of Growth at Weflow, where he's built the GTM engine from scratch. He spends valuable time talking to RevOps leaders about how they run pipeline, forecasting, and Salesforce. He's also the co-founder of RevOps Chat, the Slack community where 1,000+ RevOps practitioners share what's actually working inside their revenue orgs.
Go Deeper
Question-Based Selling: Discovery Checklist with Example Questions
#54 Creating a highly effective sales & forecasting process
Sales Methodology Guide & Checklists
Frequently asked questions
What is question-based selling and how is it different from a standard discovery call script?
Question-based selling is a structured approach where you guide the conversation entirely through questions — surfacing goals, desired outcomes, and blockers — rather than pitching features or following a rigid script. The difference is that a discovery script often has you talking at the prospect, while this method keeps the prospect talking and self-diagnosing. The questions in this checklist are sequenced deliberately: goals first, then value, then obstacles — so you're building context before you ever position a solution.
Do I need a specific CRM or sales tool to use this checklist effectively?
No specific tool is required — these questions work in any sales conversation, whether you're taking notes in Salesforce, HubSpot, or a plain Google Doc. That said, the checklist maps cleanly to opportunity fields like goals, business outcomes, and blockers, so if your CRM has those fields, you can use this as a data-capture guide in parallel. The value is in the conversation structure, not the tooling.
Which of these three question categories — goals, outcomes, or roadblocks — should I prioritize if a call is running short on time?
Start with goals every time. If you don't know what the prospect is actually trying to achieve, the outcome and blocker questions have no anchor. In a compressed call, one solid goal question like "What is your biggest need today and why is it important to your team?" will give you more usable context than rushing through all three sections at surface level.
What do I need to know about the prospect before these questions will actually land well?
You need enough account context to ask about goals at the right altitude — whether that's team-level, department-level, or company-level. If you walk in cold, the broader business goal questions ("What are the larger business goals your team is hoping to achieve?") can feel presumptuous without at least basic research on their role, company size, and current priorities. Five minutes of prep on the prospect's title and their company's recent activity is enough to make these questions feel relevant rather than generic.
How do I know if I'm getting real answers versus polished, surface-level responses from a prospect?
The checklist includes a built-in signal for this: questions like "Is there anyone on your team who disagrees with this goal?" and "Have you tried to achieve this goal before — why weren't you successful?" are specifically designed to surface friction and dissent. If a prospect gives you a clean, frictionless answer to those questions, push one level deeper with a follow-up like "What made that solution fall short?" Vague answers to obstacle questions usually mean you haven't built enough trust yet, or you're talking to someone who doesn't own the problem.
How often should I revisit and use this checklist across a multi-stage deal?
Run through the goals and outcomes sections in your first substantive discovery call, then revisit the roadblocks section in your second call once you've established some rapport. As the deal progresses, the question "If you achieve this goal, what new hurdles might appear?" becomes especially useful in later-stage conversations to pressure-test whether the prospect is thinking past the purchase decision. Treat this as a living reference across the deal, not a one-time intake form.
-p-1600.avif)

-p-1600.avif)