Client Discovery Prompts: From Enquiry to a Clear Brief
A discovery call should reveal the problem before you promise a solution. These prompts help you prepare questions, organise answers and confirm what is still unknown. They are intended for freelancers and small teams defining a new brief, rather than writing a proposal or managing an agreed scope change.
A small workflow
- Write down what the client has said and what you are merely assuming.
- Ask about the desired outcome, current process and constraints.
- Send back a brief for confirmation before agreeing delivery details.
Worked example
A client asks for a dashboard, but the underlying goal is to identify late orders every morning. Before choosing a dashboard tool, ask where order data lives, how lateness is defined and who acts on the result. The requested interface is one possible solution, not a fully defined requirement.
Identify your starting assumptions
You get: Known facts and questions to ask.
Bring: enquiry, service
Review this client enquiry [enquiry]. My service is [service]. Separate the client’s explicit problem, requested solution, desired outcome if stated and assumptions I am bringing. Identify up to five questions that could change the proposed work. Do not invent a budget, decision-maker or timeline.
Follow-up
Which three questions belong in the first call rather than a later implementation discussion?
Plan a problem-first conversation
You get: A short sequence of discovery questions.
Bring: minutes, enquiry
Prepare a [minutes]-minute discovery call for this enquiry [enquiry]. Ask about the current process, who uses it, a recent example of the problem, desired improvement and constraints. Give six concise questions in a natural order, with a reason for each. Avoid leading questions that assume my service is the right solution.
Follow-up
Remove questions already answered in the enquiry and replace them with useful follow-ups.
Organise the answers
You get: A brief that distinguishes needs from suggestions.
Bring: notes
Organise these call notes [notes] into current situation, users, desired outcome, constraints, confirmed requirements and unresolved questions. Mark a requested feature separately from the need it is meant to address. Preserve disagreements or conflicting statements instead of choosing one. Do not infer approval from enthusiasm.
Follow-up
Identify the highest-risk assumption before I estimate the work.
Confirm the brief
You get: A short message requesting specific confirmation.
Bring: brief
Draft a confirmation message using this discovery brief [brief]. State the problem we understand, the proposed deliverable for discussion and the decisions still needed. Ask the client to correct the summary and answer the most important open questions. Do not present a quote, deadline or contractual commitment unless supplied as approved.
Follow-up
Shorten this message to one clear paragraph and three confirmation questions.
Check the result
- Do not treat a stated tool preference as proof that it solves the problem.
- Record budget and delivery dates only when confirmed.
- Get approval for the brief before turning it into a commitment.
