The difference between a discovery call that converts and one that does not is rarely about your skills or your price.
It is about whether the client left the call feeling understood.
The questions you ask in a discovery call do more to win the project than anything you say about yourself.
Why questions win more than answers
Clients have heard developer pitches before. Portfolio links, technology stacks, years of experience. All of it blurs together.
What clients rarely experience is a developer who asks exactly the right questions about their problem, listens carefully to the answers, and demonstrates through the conversation that they understand the situation.
That experience stands out. It is also not difficult to create. It requires preparation and genuine curiosity, not a sales script.
The five categories of questions that matter
Understanding the problem as it actually exists, not as they described it.
"Walk me through exactly how this works today, step by step." Not the summary. The actual workflow. Where the friction is. What happens when it breaks. What they have tried already.
This question takes longer to answer than expected and reveals more than any brief could.
Understanding what success looks like specifically.
"If this project goes perfectly, what is different in six months?" Not what features exist. What is different about their day, their team's work, their business outcomes.
This question aligns your definition of done with theirs before you start.
Understanding the decision-making structure.
"Who needs to be happy with this for the project to be considered successful?" Who has final approval. Who is the daily contact. Who could change the direction mid-project.
You need to know this before you start, not after the first revision cycle.
Understanding what has been tried.
"Have you tried to solve this before? What happened?" The failure mode of the previous attempt is the most useful risk information you can get. Most clients will tell you if you ask directly.
Understanding the constraints that are real versus preferred.
"What is the hardest constraint here - the budget, the timeline, or the technical requirements?" Understanding which constraint is actually fixed tells you how to structure your proposal and where flexibility exists.
The question that closes more projects than any pitch
After you have listened carefully to everything: "Based on what you have told me, the thing that seems most important to get right is [your observation]. Does that match how you see it?"
If you are right, the client hears that you understood them. That feeling is what makes them choose you.
If you are wrong, they correct you. Which gives you more information and shows you were listening.
The Solopreneur AI Toolkit includes prompts for preparing discovery calls, structuring briefs, and writing proposals from discovery notes. EUR 12.
Top comments (0)