Client discovery questions: ask these ten before you quote
The client discovery questions below are the ones I ask before any number exists, because a quote built on assumptions is a quote built on sand. Discovery is not the friendly warm-up before the real sales pitch. Discovery is the work. It is where you decide whether the project is worth doing, what it will actually take, and whether this is a client you want.
I have spent fifteen years shipping inside teams at Apple, PlayStation and Schwab, and the pattern held everywhere: the projects that went sideways were the ones where nobody asked the uncomfortable questions early. A good discovery call is mostly listening. Your job is to ask the ten things that let you price with your eyes open.
The Discovery Ten: the questions that decide the quote
The Discovery Ten is our CCC checklist for a discovery call. Ten questions, asked in roughly this order, that surface the outcome, the constraints, and the risk. You do not need clever wording. You need to actually ask them and to write down the answers.
- What does success look like? Get them to describe the result in their own words, the outcome they are buying, not the feature they named.
- Who owns the data? Find out whose data the Claude Code build will touch, where it lives, and whether the person on the call can actually grant access to it.
- What systems must it connect to? Every integration is a dependency you do not fully control. List them now, not during the build.
- Who signs off? Identify the single person whose yes ends the project. If there are three, you have a problem to solve before you quote.
- What is the deadline, and why? A date with a real reason behind it is a constraint. A date with no reason is often movable, and knowing which is which changes your price.
- What is the budget range? Ask plainly. If they will not give a range, you are guessing, and guessing is how you underquote.
- What have they already tried? Their past attempts tell you what is genuinely hard here and where the real friction sits.
- Who maintains it after you leave? A build nobody can maintain is a build that fails in a month. This shapes your handover and your scope.
- What could go wrong? Ask them directly. Their fears reveal the edge cases and the reliability work you will need to price.
- What happens if you do nothing? This tells you what the project is really worth to them, which tells you whether your number will land.
Why each question earns its place
Every question in the Discovery Ten either sizes the work or sizes the risk. The success and do-nothing questions tell you what the outcome is worth. The data, systems, and sign-off questions tell you where the project can stall. The maintenance and what-could-go-wrong questions tell you how much of the invisible last mile you have to build and charge for.
Notice that only one of the ten is about money. That is deliberate. If you understand the outcome and the constraints, the budget conversation gets easier, because you are talking about value and not just cost.
Reading the answers you do not get
The most useful moments in discovery are often the non-answers. A client who cannot say who owns the data usually does not control it. A client who dodges the budget range is often shopping on price alone. A client who cannot name a single sign-off is describing a committee, and committees turn small builds into long ones.
None of these are automatic reasons to walk. They are reasons to price differently, to add a discovery phase, or to slow down. A missing answer is data. Write it down and let it shape the number.
Run the Ten every time, then trade notes
The Discovery Ten only works if it becomes a habit. Keep it open on the call. Tick the questions off. The moment you start freestyling to seem relaxed is the moment you skip the one question that would have saved the project.
Different niches surface different landmines, so the way you weight these questions will evolve. If you are refining your own discovery process for AI work, bring your version to the CCC community and compare notes. The eleventh question you are missing is probably one someone else learned the hard way.
Frequently asked questions
What are the most important client discovery questions?
The two that carry the most weight are what success looks like and what happens if they do nothing. Together they tell you the outcome the client is buying and what it is genuinely worth to them. From there the constraint and risk questions size the work.
Should I quote a price on the discovery call?
No. Say you will send a proposal after the call. Quoting live puts you under pressure and leads to numbers you regret. The pause also lets you actually think through the answers you just heard.
What if a client will not share their budget range?
Ask once, plainly. If they still refuse, treat it as a finding rather than a dead end. A hidden budget often signals price shopping, so you may price more conservatively or add a small discovery phase before committing to a full number.
Why ask who maintains the build after I leave?
Because a Claude Code build that nobody on the client side can maintain will fail soon after handover, and that reflects on you. The answer shapes how much documentation, training, and handover work you scope and charge for.
How long should a discovery call be?
Long enough to get honest answers to the Discovery Ten, usually a focused session rather than a rushed fifteen minutes. Keep the checklist open and let the client talk. Most of the value is in listening, not pitching.
What does the do-nothing question actually reveal?
It reveals the cost of the status quo, which is the real value of your project. If nothing bad happens when they do nothing, the urgency is low and your number needs to reflect that. If the status quo is expensive, your work is worth more.
Last reviewed by Duncan Rogoff on June 28, 2026
