If your pipeline feels slow, the problem probably is not pricing or proposals. It is weak discovery. Ask better questions, get clearer signals, write shorter proposals, and win faster. If you want a complete sales system to plug this into, read Sales & Client Acquisition: The Complete Founder’s Playbook and adapt the parts that fit your market.
In this article, we’re going to discuss how to:
- Use Question Sets That Uncover Real Buying Signals
- Turn Answers Into Offers, Next Steps, And Pricing
- Avoid Common Mistakes That Kill Momentum
What ‘Great Discovery’ Means In Practice
Great discovery is a structured conversation that produces evidence you can act on within days. It is not a chat about features or a therapy session about pain. It is a sequence that surfaces the problem worth solving, the measurable outcome, the decision path, and the risks that will slow you down.
Sense checks for effective discovery:
- You can write a one sentence summary of the problem and desired outcome using the buyer’s words.
- You can name the sponsor, the approver, and the blocker.
- You know the date by which the buyer wants to see results.
- You can explain why your project matters more than the three other things on their plate.
Sales Discovery Questions That Do The Heavy Lifting
The best sales discovery questions are short, precise, and point at numbers, dates, or behaviours. Ask open, then tighten. Start broad to earn context, then anchor to specifics you can price and schedule.
The core set, with intent explained:
- ‘What has made this a priority now rather than last quarter?’
Surfaces a trigger or deadline and tells you if urgency is real. - ‘How are you handling this today, and where does it break?’
Moves from opinions to current behaviour. You learn the messy workaround you must replace. - ‘If nothing changes for 90 days, what happens?’
Quantifies the cost of delay. If there is none, you will drift. - ‘What would a good result look like in numbers and in words?’
Locks a metric and a narrative. You need both for a proposal and a future case study. - ‘Who needs to be happy for this to proceed, and what do they care about?’
Maps stakeholders and their criteria so you can tailor the offer. - ‘What have you already tried, and what did you learn?’
Avoids repeating failed tactics and uncovers constraints. - ‘What would make this a no, even if we agree the plan?’
Surfaces hidden blockers early rather than after you price. - ‘How do you typically buy services like this, step by step?’
Replaces guesswork with their process. You can build a mutual plan from it. - ‘If we agreed the right plan this week, when would you want to start and when should results show?’
Pins dates you can plan resources against. - ‘What is the smallest sensible first step to prove value?’
Clears the path to a paid pilot or milestone one.
Sprinkle in proof checkers when answers feel vague. Ask, ‘How do you know?’ or ‘Can you give me an example?’ You are collecting artefacts you can price against, not winning a debate.
H3: Follow-On Probes That Create Clarity
- Volume and baseline: ‘How many per month right now?’
- Quality bar: ‘What would make you say this is working after four weeks?’
- Ownership: ‘Who will own this in your team once we hand over?’
- Risk: ‘What has bitten you before with suppliers like me?’
- Budget reality: ‘Is this planned spend or are we making a case to unlock funds?’
Use these probes to move from story to numbers so you can frame a proposal quickly.
Turn Answers Into A One-Sentence Offer
You should be able to craft a clean offer on the call or immediately after.
Offer template:
‘We help [buyer type] achieve [specific outcome metric] in [timeframe] by [mechanism], typically for [£X to £Y], proven by [proof point].’
Example filled from discovery notes:
‘We help UK e-commerce brands reduce paid media waste by 20 to 30 percent in 60 days by restructuring accounts and creative testing, typically for £6k to £9k, proven by the Finch & Co result in May.’
If you cannot write that sentence, your discovery is incomplete. Ask for a 10 minute follow up to fill gaps.
From Answers To Next Steps, Without Awkwardness
Close every meeting with a clear, dated next step. Do it while you are live together, not in a later email.
Use this close:
‘Here is what I heard: you are spending £45k a month, performance has been flat since June, and a 20 percent lift by quarter end is the target. The decision is you plus Finance, and you buy in two steps, a pilot and then a roll out. If I write a one page plan with two options, can we review it at 14:10 on Thursday and lock the first step?’
This turns talk into a calendar event and gives you permission to write a short, optioned proposal.
Build Your Personal Discovery Script
A script is a checklist, not a teleprompter. Design a flow that fits your service and buyer. Keep it short enough to learn in a day.
A practical 7-section flow:
- Set the frame: ‘Plan for today, a few questions so I understand your context, I will share how we approach similar projects, and if useful we agree next steps. Sound OK?’
- Context: ‘What is in place now? Tools, process, people.’
- Problem and impact: ‘What is not working, and what is the cost if this holds for 90 days?’
- Outcome: ‘What does good look like in numbers and in words?’
- Constraints: ‘What competes for this, time, budget, approvals?’
- Decision path: ‘Who decides and how do you buy services like this?’
- Close: Summarise in their words, propose a dated next step, and confirm ownership of actions.
Print the flow, keep it beside your screen, and tick sections off as you go. You will sound natural after three or four calls.
Data You Can Gather In A Few Hours
Improve your question set this week by reviewing your own data before you read anyone else’s.
Internal checks:
- Listen to three recent calls and list the questions that triggered useful numbers.
- Read your last five proposals and highlight where you had to guess. Turn those guesses into future questions.
- Map your last ten losses by reason. Write the question that would have surfaced each reason earlier.
Public clues:
- Scan job ads for your ICP. They reveal tools, targets, and gaps.
- Read customer reviews of your client’s product. You will learn language their team uses and what annoys buyers.
- Look at press releases and funding notes. These create deadlines and politics.
Feed the findings into your script. Review weekly for a month, then monthly.
Converting Discovery Into Pricing And Scope
Your question set should lead directly to scope and price. Keep your maths simple and transparent.
Unit economics example for a consultant:
- Day rate fully loaded: £600.
- A four week pilot with 2.5 days per week is 10 days, so £6k.
- Add 20 percent for risk and coordination, round to a neat number, £7.2k becomes £7k for a Starter pilot.
- Offer a Growth option at £10.5k with enablement, and a Scale option at £14k with training and reporting.
Use the buyer’s own numbers to justify the price. ‘At £45k a month in spend, a 12 percent lift returns £5.4k in 30 days. The Starter pilot at £7k pays back in under six weeks.’
Operational Guardrails For Clean Discovery
You can be likeable and still run a tight process. Protect your time and margin with these rules.
- Do not present or demo before you have a clear problem, outcome, and decision path.
- Do not write long proposals. One page is enough when discovery is good.
- Book the review while live on the call. If they will not, your timing is off.
- Put an expiry date on proposals to avoid drift.
- Use a short mutual action plan with dates to move from proposal to start.
- Track objections in a simple sheet. Write one crisp response for each and practise.
Mini Examples In Different Sectors
Creative studio, Leeds
The founder used three questions to cut long meetings. ‘What launch date are we working back from?’ ‘What are three brands you want to be compared with?’ ‘What decision will make your CFO say yes?’ Proposals dropped from 12 pages to one page. Win rate rose from 26 to 41 percent.
IT support, Birmingham
They added two probes on risk. ‘What has failed with previous providers?’ ‘How will we know in week two that we are on track?’ It surfaced a compliance review the team used to delay sign off. They put a compliance checklist in the plan and cut cycle time by nine days.
B2B SaaS, Glasgow
The founder asked, ‘What usage threshold would make expansion a no brainer after 30 days?’ The buyer said, ‘50 weekly active users with two features adopted.’ The pilot focused on a single department, hit 58 users by week three, and converted to an annual at £24k.
Risks And Hedges
Risks:
- Questions that feel like interrogation.
- Letting the buyer talk for 40 minutes without steering to outcomes.
- Missing the decision path and discovering procurement at signature time.
- Agreeing to write a proposal with no review booked.
Hedges:
- Signal intent at the start: questions, approach, next step.
- Time-box sections. ‘Ten minutes on context, ten on outcomes, five on decision path, then next steps.’
- Ask the buying process question early.
- Propose two time slots for the review before you close the call.
A 7-Day Validation Plan For Your Question Set
You can test and improve sales discovery questions in a week.
- Day 1: Draft a 12 question script with the core set and four probes for your sector.
- Day 2 to 4: Use it on five calls. Record where you stumbled or got weak answers.
- Day 5: Edit the script. Remove two questions that never produced useful data. Add a new probe for the most common gap.
- Day 6 to 7: Run three more calls with the revised script. Compare quality of answers and how fast you could price.
Completion check: You should now craft a one page proposal in under 45 minutes using answers you trust.
Cross-Reference Your Wider Sales System
Discovery does not live alone. Fold what you learn into proposals, outreach, and deal reviews. If you want ready-to-use stage definitions, objection scripts, and pipeline habits, refer to Sales & Client Acquisition: The Complete Founder’s Playbook and copy the templates you need.
Take The Next Step And Get The Discovery Toolkit
If you want a plug-and-play script, question bank, recap email template, and a mutual action plan you can drop into your process, download Discovery Call Frameworks: Say Less, Learn More, Close Better. It saves hours of tinkering and helps you run cleaner meetings this week.
Key Takeaways
- Strong discovery is a short, structured conversation that produces numbers, names, and dates you can price against.
- Turn answers into a one sentence offer, book a dated review, and keep proposals to one page with options.
- Protect margin with expiry dates, mutual action plans, and a simple objection log you review weekly.
FAQ For Discovery Questions That Actually Work
What is the right number of questions for a discovery call?
Ten to twelve is plenty. You need enough to hit problem, outcome, decision path, risk, and timing, not a full interview.
How long should a discovery meeting last?
Book 30 to 45 minutes. If you keep the frame tight and move to numbers early you will usually be done in 25 to 35.
Should I send questions in advance?
Send a short note with two or three prompts if stakeholders are senior. It raises the quality of answers and shows respect for their time.
How do I handle vague answers?
Ask for an example, a number, or a time reference. ‘Can you quantify that for last month?’ or ‘What would make you say this is working by week four?’
When do I ask about budget?
After the outcome is clear and the decision path is sketched. Use, ‘Is this planned spend, or are we making a case to unlock funds?’
Should I record discovery calls?
If policy allows, yes. Confirm permission, record, and take structured notes. You will write better proposals and onboard more cleanly.
What if the buyer will not book a review meeting?
It is a timing or priority issue. Offer a short recap with two time options. If they still avoid it, close the loop and revisit when a real trigger appears.
Can these questions work outside of software and marketing?
Yes. The structure is universal. Swap examples and metrics for your sector. The intent is the same, get to numbers, dates, and decision steps you can act on.
