Proposal intake: clarifying questions and project brief (two-step)
Start every proposal here. The model reviews your notes, asks the questions a good proposal needs answered, then writes a one-page project brief that the rest of the pack builds on.
Use this to write the most-read page of your proposal: a short executive summary that shows you understand the client's problem, states the outcome and gives the investment, so a busy decision-maker can say yes from one page.
You are an expert proposal writer. Write the executive summary for my proposal, based on the project brief below. The reader: [decision maker] Investment: [investment summary] Project brief: """ [project brief] """ Structure (about 250-300 words total): 1. Opening (2-3 sentences): their situation and problem, in their language. Show we listened. Do not start with "We are pleased to submit" or anything about us. 2. What success looks like: the 2-3 outcomes they care about, framed as what will be true for them after the project. 3. Our recommended approach: 3-4 short bullets, in plain language. 4. Timeline and investment: one or two sentences with the key date(s) and the investment exactly as I gave it. 5. Next step: one sentence telling them exactly how to proceed (e.g., reply to approve, sign by a date to hold the schedule). Rules: - Do not invent statistics, guarantees or results. If a benefit depends on the client, phrase it honestly ("designed to reduce..."). - Write for a busy reader who may only read this page. - Active voice, short sentences, no jargon. Then give me 3 alternative proposal titles that lead with the client's outcome, not our service.
Why Any: All major models write strong summaries when given a good brief. Claude and ChatGPT tend to be the most concise.
Yes. It is plain-language and written to work in all three. Best fit: Any. All major models write strong summaries when given a good brief. Claude and ChatGPT tend to be the most concise.
Replace each bracket with your own details: [project brief], [investment summary], [decision maker]. The more specific your input, the more useful the result.
Yes. Copy it above and use it as often as you like. It is one of the free samples from the Proposal writer pack.
No. The example was made for a fictional business to show the shape and quality of the output. Your result depends on your input and the model, so review and edit before you use it.
Usually not. Free plans handle most prompts. Paid plans help when you paste in long documents or run a long multi-step sequence in one chat.
Start every proposal here. The model reviews your notes, asks the questions a good proposal needs answered, then writes a one-page project brief that the rest of the pack builds on.
Use this to write the section that prevents scope creep: deliverables, what is explicitly excluded, client responsibilities, assumptions and how changes are handled, in plain language the client will actually read.
Use this to present your price as three clear options (good, better, best) so the client chooses how to work with you rather than whether to. You set the prices. The model structures and explains them.
Use this to turn your scope into a realistic week-by-week timeline with milestones, client checkpoints and dependencies, so the client sees exactly when they need to show up and what happens if things slip.