Client Proposal Builder

<discovery_notes>
[PASTE YOUR NOTES OR THE CALL TRANSCRIPT]
</discovery_notes>

Act as a consultant who writes proposals clients sign. Write a client proposal from the discovery notes above.

Client [NAME, COMPANY, ROLE] · what they asked for, in their words [QUOTE] · what I will deliver [LIST] · what is not included [LIST] · price [AMOUNT AND HOW IT IS BILLED] · timeline [START, MILESTONES, END]
What I need from them [ACCESS, PEOPLE, DECISIONS] · proof I can cite [REAL RESULTS OR CLIENTS, or NONE] · how they accept [SIGN / REPLY / PAY A DEPOSIT] · proposal valid until [DATE] · tone [DESCRIBE]

Write:
1. Summary: their situation and goal in their words, then what I will do about it, in under 120 words
2. Scope: deliverables as a numbered list, each with what "done" means; where neither my list nor the notes say, suggest a definition and mark it "CONFIRM"
3. Not included: stated as plainly as the scope
4. Timeline with milestones, and what I need from them at each one
5. Price: the amount, what it covers and how it is billed, exactly as I gave them
6. What this rests on: the assumptions behind the price and the timeline, one sentence each
7. Why us: only the proof I listed (with none listed, the proposal has no section 7 and the note to me says so)
8. Next step: how they accept, by when, and what happens first once they do

Use only the price, dates and proof I gave, because a proposal is the document a client holds me to. Before the proposal, add a short note to me listing anywhere the notes and my inputs disagree (follow my inputs) and every item marked "CONFIRM".

Success means the summary uses the client's own words for the problem, every deliverable has a definition of done, and the price section can be read on its own without raising a question.

Match the tone I specified above exactly; where I gave none, write plainly and warmly, the way a good operator talks to a customer: no corporate filler, no hedging phrases.

Apply every rule, limit, and format above to every item in the deliverable, not just the first one. Deliver the complete result in one response, every section filled in, nothing deferred to a follow-up.

If a required input is missing, ask for it once before starting; otherwise proceed and label any assumption you made.

Notes: R54 build; tuned to vendor prompting guidance