Start with the client's goal
Ask what the client is trying to achieve and why it matters. A stated business outcome is usually more useful than jumping straight into a list of requested features.
Understand the current situation
Ask what exists today, what is not working, and what constraints you already know about. This can reveal requirements that were not obvious from the initial inquiry.
Clarify scope
Discuss the work the client expects, important deliverables, exclusions, dependencies and stakeholders. Avoid treating a vague request as a fully defined scope.
Discuss timing
Ask about the desired launch date and any fixed deadlines. Check whether approvals, content, access or other dependencies could affect the schedule.
Discuss budget professionally
If appropriate for your business, ask whether the client has an investment range. Budget information can help determine whether the requested scope and timeline are realistic.
Identify decision makers
Find out who approves the work, who supplies information, and whether other stakeholders need to review the proposal. This reduces avoidable delays later.
End with explicit next steps
Summarize what you heard and agree on the next action. That might be a proposal, a follow-up call, additional information, or a decision by a particular date.
Turn the call into project records
Write down important decisions and requirements after the call. If the project moves forward, use those notes to create a proposal and a more precise project scope.