Turn the attached discovery notes into a proposal DRAFT for [CLIENT / PROJECT]. Use only the supplied notes and my approved commercial terms [ATTACH OR SAY NOT SET].

1. Build a requirement table: source ID, requested outcome, proposed deliverable, acceptance criterion and unresolved dependency. Keep client requests separate from your suggestions.
2. Flag contradictions and missing decisions before assigning a price or delivery date. A stated budget is a spending ceiling, not my quoted fee; a preferred launch date is not a confirmed schedule.
3. Draft a concise project summary, scope, exclusions, client inputs, acceptance process and next steps. State which integrations or ongoing services require separate confirmation.
4. Use approved fees and dates only. Otherwise write “to be confirmed.” Do not infer maintenance, instant booking, payments, guarantees or support commitments from an ambiguous request.
5. Finish with up to five questions that could change scope, timing or price, each tied to the relevant note. Do not send the proposal, create an invoice or request a signature.