Summarise a Discovery Call Into a Project Scoping Document

You finished the discovery call with a page of messy notes and a proposal due. This turns them into a structured scope: the stated objectives in the client's own words, the requirements they implied but did not say, the constraints, and the open questions. You produce a document solid enough to build a proposal or statement of work on.

<context>
You have just completed a discovery call with {CLIENT_OR_PROSPECT} and need to turn your notes into a structured scoping document that captures requirements clearly enough to produce a proposal or statement of work.
</context>

<task>
**Step 1: Extract the stated objectives**
What did the client say they want to achieve? Use their language where possible.

**Step 2: Identify the implied requirements**
What did they reveal that they did not explicitly state? What constraints, preferences, or concerns emerged indirectly?

**Step 3: Note the open questions**
What do you still need to know before you can scope the work accurately?

**Step 4: Write the scoping summary**
A structured one-page summary: objectives, scope, known constraints, open questions, and suggested next step.
</task>

<output_format>
- A structured scoping summary: objectives, scope, constraints, open questions
- A suggested next step and a proposed timeline for the proposal
</output_format>