The difference between a proposal that converts and one that doesn’t usually comes down to what happened before it was written. Discovery questions are how you collect the raw material for a proposal that speaks to a client’s actual situation. Ask them well and you spend half the time writing a proposal twice as likely to close.
Why most proposals miss
Freelancers often skip the discovery phase and move directly from inquiry to proposal. The result: a generic document that describes your services but doesn’t speak to their specific problem.
Clients feel the difference. A proposal that starts by accurately describing their situation — the problem they’re dealing with, the constraints they’re working within, the outcome they want — signals that you actually listened. That signal is worth more than any design element or copywriting technique.
Discovery questions make that possible.
The 10 questions that matter
1. “What’s the core problem you’re trying to solve?”
This seems obvious, but most clients answer it differently than you expect. Let them describe it in their own words. Don’t reframe it yet. The language they use here is the language that should appear in your proposal.
2. “What have you already tried?”
This tells you what not to propose and why previous solutions didn’t work. If they tried a template website and it underperformed, proposing a template solution will land poorly. If they hired a writer and got content that sounded nothing like them, they have a specific concern you’ll need to address.
3. “What does success look like six months from now?”
This question shifts the conversation from deliverables to outcomes. You learn whether they’re measuring success by metrics, feelings, or milestones — and which ones matter most. It also surfaces unstated expectations before they become problems.
4. “What’s driving the timeline?”
Timeline questions reveal urgency and constraints. A client who says “we need this by September because that’s when we launch the product” has a hard deadline tied to a real event. A client who says “as soon as possible” often doesn’t have a true deadline — meaning their urgency may not be real.
5. “Who else is involved in deciding on this?”
If a manager, partner, or committee needs to approve the project, you need to know. It changes the proposal format, the follow-up approach, and your realistic close timeline. Proposals that get passed up a decision chain need to be written for an audience who wasn’t in your discovery call.
6. “What’s your budget range?”
Ask this directly. Most clients have a range in mind even if they won’t give you an exact number. You can also frame it as: “For projects like this, I typically work in the $X–$X range. Does that fit with what you have available?” Either approach gives you the data you need to scope the proposal correctly.
7. “What happens if this doesn’t get solved?”
This question reveals stakes. If the answer is “we lose the account” or “we miss the product launch window,” you understand the urgency and can price accordingly. If the answer is vague, the project may not be a real priority.
8. “Are there any constraints I should know about — technical, brand, process?”
Constraints you discover after writing the proposal require a revision. Constraints you discover in discovery get incorporated the first time. Ask about tech stack, existing assets, stakeholder preferences, and process requirements.
9. “Have you worked with a [designer/developer/consultant] on something like this before?”
This tells you their frame of reference. A client who’s worked with freelancers before has expectations. A client who hasn’t may need more education about the process. Both are fine, but they’re different conversations.
10. “What’s your ideal working process?”
Some clients want frequent check-ins. Others want to be left alone until delivery. Some are highly involved in feedback. Others want you to make the decisions. You won’t always accommodate their preference, but knowing it upfront prevents friction later.
How to ask these without sounding like a form
Good discovery conversations feel like conversations, not interviews.
You don’t have to ask all 10 questions in sequence. Start with the core problem question and let the answers lead you to the next one. Many of the answers will surface multiple questions’ worth of information.
Take notes. If a client uses a specific phrase — “we’ve been spinning our wheels on this for six months” — write it down. That phrase belongs in your proposal.
What to do with the answers
Use the discovery call output to write a proposal that opens with their situation. Not your bio. Not your credentials. Their problem, their constraints, their success criteria — and then your specific approach to addressing them.
With a tool like Waco3, you can build that proposal into a professional document that tracks when and how often it gets viewed, so your follow-up after sending can reference what they seem to be paying attention to.
One question you should never skip
If you’re pressed for time and can only ask one discovery question, ask: “What does success look like for this project?” That answer tells you the outcome they’re buying — and your whole proposal can be built around delivering that outcome.
Ready to send stronger proposals?
Build, send, and track proposals in one place so follow-up is easier.
Start your free trial →
