Client Proposal Structure Prompt
Prompt
Help me structure a proposal for [WHAT YOU'RE PROPOSING]. Client: [company name and brief description] What they asked for: [describe their request or problem] What you're proposing: [describe your solution] Key outcomes you're promising: [list 2–3 measurable outcomes] Budget range: [approximate, if known] Timeline: [when they need it] Please create: 1. A recommended proposal structure (section titles + 1-sentence description of each) 2. An executive summary paragraph (100 words) 3. The 3 strongest points to make in your favour 4. 2 likely objections and how to address them in the proposal 5. A recommended call to action for the final page
Why it works
Structuring the proposal around measurable outcomes the client cares about rather than your service description converts a capabilities pitch into a results promise. The why us section positioned after the solution — not at the beginning — reflects how clients actually evaluate proposals: they decide whether the solution is right before they care about the provider's credentials. Keeping the scope clear and bounded protects both sides from scope creep disputes.
Watch out for
Proposal structure matters less than the precision of the outcomes promised — vague outcomes like 'improve efficiency' will lose to a competitor who says 'reduce invoice processing time from 5 days to 1 day.' Before accepting AI-generated outcome language, confirm each outcome is specific enough to be measurable and defensible if the client holds you to it.
Used by