Set the frame and confirm scope at a glance.
Draft a one-page proposal cover for a [project type] for [client]. Include project title, prepared-for, prepared-by, date, and a one-sentence summary of the outcome we are committing to. Tone: confident, specific, no buzzwords.
Restate the client's problem in their own words to prove fit.
Using these discovery notes [paste notes], write a 120-word "Problem" section. Mirror the client's vocabulary. End with the cost of inaction in dollars or hours.
Show how you will solve it without giving away the playbook.
Write a 150-word "Approach" section describing our 3-phase methodology to solve [problem]. Reference one relevant case study. Avoid jargon; a non-technical buyer must understand it.
Bullet exactly what is in — and what is not — to prevent scope creep.
List "In Scope" and "Out of Scope" as two bullet groups for a [engagement type]. 5–8 bullets each. Be ruthlessly specific (deliverables, formats, review cycles).
Anchor expectations with phases and milestones, not vague months.
Build a phased timeline table: Phase | Weeks | Milestones | Client inputs needed. Total duration [X] weeks. Flag dependencies that could slip the date.
Frame price as investment, anchor with options, end with a single recommended path.
Write an "Investment" section presenting 3 packages (Essential / Recommended / Premium) for [engagement]. Include what each tier includes, the fee, and a one-line ROI rationale. Recommend the middle tier explicitly.
Make signing the easiest action on the page.
Write a 60-word "Next Steps" section with three numbered actions: (1) sign + return, (2) kickoff date, (3) what we send within 48 hours of signing. Add a clear single CTA line at the end.