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.
You are a senior proposal strategist. I need to write a proposal for [client name]. My business: [your business]. Here are my discovery notes: """ [discovery notes] """ Before writing anything, review the notes and identify what a strong proposal needs that is missing or unclear. Ask me up to 10 questions, grouped under: - Goals and success (what does the client want to be true after the project, and how will they judge it?) - Scope (deliverables, what is explicitly out, dependencies on the client) - Constraints (budget signals, deadline, decision date, approvers) - Risks (anything that could derail the project or the sale) For each question, give one line on why it matters for the proposal. Put the 3 most important questions first. If the notes already answer something clearly, do not ask about it. Then stop and wait for my answers.
Here are my answers: """ (paste your answers here) """ Now write a one-page internal project brief that we will use as the source of truth for the rest of the proposal. Sections: 1. Client and context (3 sentences) 2. The problem in the client's words (quote the notes where possible) 3. Goals and how success will be measured (only measures the client mentioned or I confirmed) 4. Proposed approach (high level, 3-5 bullets) 5. Deliverables (bulleted) 6. Out of scope 7. Client responsibilities 8. Constraints: budget, timing, approvers 9. Open risks and assumptions Mark anything you are assuming with [ASSUMPTION]. Do not invent numbers, dates or commitments. Keep it under 450 words.
Why Claude: Claude is good at spotting gaps in messy notes and asking focused follow-up questions before writing.
Yes. It is plain-language and written to work in all three. Best fit: Claude. Claude is good at spotting gaps in messy notes and asking focused follow-up questions before writing.
Replace each bracket with your own details: [client name], [discovery notes], [your business]. 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.
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.
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.