Your First Discovery Call as a Builder - What to Ask, What to Listen For
- A discovery call is not a pitch. It is a diagnostic. Your job is to understand the problem, the budget, and whether you are the right person to solve it - not to convince the prospect you are great.
- The four questions that matter: what is the problem, what does success look like, what have they tried, and what is the budget. Get clean answers to those four and you have everything you need to decide whether and how to proceed.
- The most useful thing you can do on a discovery call is listen more than you talk. Prospects who describe their problem reveal the diagnosis, the priority, and the appetite for spending.
What a discovery call is actually for
Most builders treat the discovery call as a pitch. They prepare a talk track, explain what they do, show examples, and try to convince the prospect to hire them. This is backwards. The discovery call is a diagnostic, not a presentation. Your job is to understand the problem well enough to know whether you can solve it, whether the project is worth taking, and what the right approach would be. Pitching before you have that information is guessing.
The shift that makes discovery calls more productive: go in with the explicit goal of understanding the problem, not of winning the project. When you are genuinely trying to understand rather than trying to sell, you ask better questions, you listen more carefully, and the prospect trusts you faster. A builder who asks sharp questions and listens looks more competent than a builder who talks about their portfolio for twenty minutes.
The four questions that tell you everything
You can run a useful discovery call with four questions. Everything else is follow-up and clarification. These four give you the diagnosis, the success criteria, the context, and the budget - which is everything you need to decide whether to propose and what to propose.
- What is the problem you are trying to solve? Not 'what do you want me to build' - what is the underlying problem a build would solve. The answer tells you whether the project as described is actually the right solution, or whether the real problem is something different.
- What does success look like in six months? This reveals whether the client has a clear outcome in mind or is buying on hope. Specific answers - 'we cut the time to close a proposal from three days to one day' - are good. Vague answers - 'things run smoother' - signal that the scope will drift.
- What have you tried so far? This tells you the history: what they already know does not work, what the constraints are, and whether they are genuinely stuck or just casually exploring. If they have tried several things seriously, they are a motivated buyer.
- What is the budget you are working with? Ask this directly. If they say they do not know, offer a range and ask if that is the right area. Getting budget clarity on the call prevents the proposal stage from being a waste of time for both of you.
What to listen for beyond the answers
The four questions produce answers, but the most useful information often comes from the way the prospect answers them, not the answers themselves.
- Urgency: do they talk about this problem as if it is costing them something right now, or as a nice-to-have for eventually? Real urgency - lost revenue, a broken process, a deadline - is the strongest signal that there is a real project here.
- Decision-making clarity: can they tell you who signs off on this? If they are not the final decision-maker, you need to know who is and whether that person is aligned.
- Problem ownership: do they own this problem or are they describing someone else's frustration? A prospect who owns the problem predicts follow-through.
- How they talk about past vendors: clients who describe previous builders with real frustration have specific unmet expectations - and those expectations will apply to you. Ask what was missing.
How to close the call and decide what to do next
The discovery call ends with two decisions: yours and theirs. Your decision is whether to propose. Their decision is whether they want to see one. Before you end the call, make both decisions explicit.
Your closing statement should do three things: summarize what you heard (which proves you listened), name the next step if you want to proceed, and give a time frame. Something like: 'Based on what you described, I think I have a clear enough picture to put together a proposal. It would cover [the specific problem]. If that sounds right, I can have something to you by [specific date]. Does that make sense to move forward with?' This gives the prospect an easy yes or a clear moment to raise concerns before you spend time on a proposal.
What a good discovery call produces
A well-run discovery call produces four things: a clear description of the problem in the client's words, a specific success criterion, a budget number or range, and a decision on whether to send a proposal. If you leave a call without those four things, ask the missing question over email before starting on the proposal.
Short, practical drops on offers, outreach, pricing, and closing clients with Claude Code. No spam, unsubscribe anytime.
Frequently asked
How long should a discovery call be?
Thirty minutes is the right default. Long enough to get through the four questions and any necessary follow-up; short enough that a prospect with a real project will agree to it without friction. Sixty-minute discovery calls are usually a sign that the builder is pitching rather than diagnosing - the diagnosis part takes fifteen to twenty minutes when you have the right questions.
What if the prospect will not give me a budget?
Offer a range. 'Projects like this typically run between X and Y. Does that fit where you are thinking?' Most prospects will confirm, correct, or tell you you are way off. All three answers are useful. The ones who refuse to engage with any number after you have offered a range are the ones most likely to have sticker shock at the proposal stage.
Should I show work or case studies on the discovery call?
Only if they ask. Your job on the call is to understand the problem, not to audition. If you spend the first fifteen minutes showing portfolio work, you have used up the time you need to understand whether this project is right for you. The relevant credential is that you can solve the specific problem they described - and you demonstrate that by asking sharp questions and summarizing the problem back accurately.
What if I freeze up and forget the questions?
Have the four questions written somewhere visible during the call. There is nothing wrong with glancing at a short list. What matters is that you get through the questions and listen to the answers. Over time the structure becomes natural and you stop needing the list. In the meantime, having it in front of you is a practical solution.
Last reviewed August 1, 2026.
Co-founder of the Claude Code Profit Room. Built and sold AI services to real clients; writes about offers, pricing, outreach, and closing with receipts.
More from Duncan Rogoff →
