Proposal & Pitch Writing
Craft compelling business proposals and pitch decks with Claude — from problem statements to ROI projections.
What You’ll Learn
- How to structure a persuasive business proposal that moves prospects from interest to decision
- How to use Claude to build ROI projections and quantify your value proposition
- How to tailor pitch narratives to different audiences — investors, clients, and internal stakeholders
The Use Case
Writing a business proposal or pitch is one of the most time-consuming and high-stakes writing tasks in business. A strong proposal doesn’t just list what you offer — it tells a story: here is the problem you have, here is why the current solutions fail, here is how we solve it, here is the evidence we can deliver, here is what it costs, here is what you gain.
Most proposals fail not because the product or service is weak, but because the writing is unfocused, the value isn’t made concrete, or the document talks about the vendor instead of the client’s problem. Claude helps you avoid all three of these failure modes by forcing structure and client-centricity from the start.
This workflow applies whether you’re writing a client proposal for a consulting engagement, a pitch deck for a startup fundraise, a grant application, or an internal business case to get budget approved. The underlying structure — problem, solution, evidence, cost, outcome — is universal.
Step-by-Step Guide
Step 1: Define the audience and their primary concern
Before writing a single word, you need to understand who reads this document and what they care most about. A CFO cares about ROI and risk. A CTO cares about integration and technical feasibility. A startup investor cares about market size and defensibility. Each audience requires a different emphasis.
Prompt:
“I’m writing a business proposal for [describe the deal]. The primary reader is [job title] at a [company size/type] company. Their biggest concern is likely [cost/timeline/risk/compliance/ROI]. Help me outline a proposal structure that leads with what matters most to this reader and builds toward a clear call to action.”
Claude will return a tailored outline that front-loads the reader’s concern rather than starting with your company history (a common mistake).
Step 2: Write the problem statement
The problem statement is the most important section — if the prospect doesn’t feel seen and understood, they won’t trust your solution. Ask Claude to help you articulate the problem in the prospect’s language, with the pain points made vivid and concrete.
Prompt:
“Write a problem statement for this proposal. The client is a [describe company]. Their current situation is [describe]. The pain they experience includes [describe consequences — lost revenue, manual work hours, compliance risk, etc.]. Make it specific and emotionally resonant without being manipulative. Two paragraphs.”
Then share the draft with a colleague who knows the prospect and ask if it resonates. Iterate with Claude until the problem section sounds like something the prospect would have written themselves.
Step 3: Build the solution narrative
Now introduce your solution — but frame it as the answer to the specific problem you just described, not as a generic product brochure. Claude helps you connect your capabilities directly to the pain points.
Prompt:
“Based on the problem statement above, write a solution section for this proposal. Our offering is [describe]. The three most relevant capabilities for this client’s situation are [list them]. For each capability, explain how it specifically addresses one of the pain points from the problem section.”
This creates a point-by-point response to the problem rather than a features list, which is far more persuasive.
Step 4: Develop the ROI or value quantification section
Proposals without numbers are easy to deprioritize. Help the prospect see the concrete value of saying yes — and the concrete cost of saying no or waiting.
Prompt:
“Help me build an ROI section for this proposal. Current state: [describe their current cost/situation with numbers if available]. Our solution costs [X]. Expected outcomes include [list benefits]. If I don’t have exact numbers, help me build a reasonable estimate using industry benchmarks and label it as an estimate. Format it as a simple before/after comparison table.”
Claude will build a defensible projection and flag where your assumptions are weak, which lets you strengthen them before the client challenges them.
Step 5: Write the call to action and next steps
The ending of a proposal determines whether it moves forward or dies in someone’s inbox. Make the next step frictionless and specific — not “please let us know if you have questions” but “here is exactly what happens next and when.”
Prompt:
“Write a closing section and call to action for this proposal. The next step I want the client to take is [schedule a call / sign the agreement / respond with a decision by date X]. Make it confident, clear, and low-friction. Include a proposed timeline for the engagement start if they decide this week.”
Prompt Template
I'm writing a [client proposal / pitch deck / internal business case / grant application] for the following:
Context:
- What I'm proposing: [brief description of your offering or project]
- Audience: [job title, company type, their primary concern]
- Deal size / scope: [approximate budget or engagement size]
- Their current situation: [what they're doing now, what's broken]
- Key pain points: [list 2-3 specific problems with consequences]
- Our differentiators: [what makes our approach better than alternatives]
- Evidence / case studies: [any proof points, past results, or data]
- Timeline: [when they need to decide, when engagement starts]
Please help me:
1. Create a proposal outline ordered by what this specific audience cares about most
2. Write a client-centric problem statement (2 paragraphs)
3. Write a solution section that connects each capability to a specific pain point
4. Build an ROI estimate or value quantification section (with a before/after table)
5. Write a closing section with a clear, specific call to action
Tone: [professional / consultative / urgent / aspirational]
Length target: [executive summary style (2 pages) / detailed proposal (5-8 pages) / pitch deck outline (10-12 slides)]
Tips & Best Practices
-
Start with the client’s words, not yours — Before writing, prompt Claude: “Based on this job description / LinkedIn / website, what language does this company use to describe their own challenges?” Then use those exact words in your problem statement. Prospects feel understood when they read their own vocabulary back to them.
-
Use Claude to steelman the competition — Ask: “What objections would a prospect raise to this proposal? What would they say if they chose a competitor instead?” Then address those objections proactively in your proposal. This makes it much harder to dismiss.
-
Build the executive summary last — Write the full proposal first, then ask Claude to condense it into a half-page executive summary for decision-makers who won’t read the whole document. This ensures the summary is accurate and complete.
-
Ask Claude to audit your proposal for client-centricity — After drafting, prompt: “Read this proposal and count how many sentences start with ‘we’ or ‘our’ versus ‘you’ or ‘your.’ Rewrite any sections that are too vendor-focused.” Strong proposals talk about the client more than themselves.
-
Generate multiple subject lines and follow-up emails — The proposal is only part of the process. Ask Claude to write 3 subject line options for sending the proposal by email, plus a follow-up email for if you don’t hear back in 5 business days. These small pieces have outsized impact on response rates.
Try It Yourself
Think of a proposal you’ve sent in the past that didn’t close — or one you need to write now. Share the key context (what you offered, who the client was, what the outcome was) with Claude and ask: “What are the most likely reasons this proposal would fail to win the business?” Review Claude’s analysis. Then ask it to rewrite the opening problem statement and closing call to action. Compare the new versions to your original. The difference will show you exactly what to change in your next proposal.