Most freelancers lose proposals at the writing stage — not because their pricing is wrong or their work isn’t good enough, but because they start from a blank page, run out of steam, and send something that undersells them. The proposal that took four hours to write doesn’t communicate four hours of value. It communicates fatigue.
The fix isn’t to become a better writer. It’s to stop writing proposals from scratch.
Why Proposals Written From Scratch Fail
A blank page turns a 45-minute discovery call into a 3-hour writing exercise. By the time you’re done, you’ve spent more time writing the proposal than you’ll spend doing some of the deliverables inside it.
The structural problem: you know what you want to say — you just said it on the call — but translating spoken conversation into a well-organized, professional document requires a different kind of energy. Claude handles that translation reliably.
The System: Discovery Notes → Claude → Polished Draft
Step 1: Take Notes During the Discovery Call
You don’t need to be exhaustive. You need to capture:
- The specific problem the client is trying to solve
- What “success” looks like to them (in their words, not yours)
- Timeline and any hard deadlines
- Budget range if they mentioned it
- Any constraints, stakeholders, or complications they raised
5–10 bullet points is sufficient. Don’t try to write a brief during the call — just capture the raw material.
Step 2: Run the Core Prompt
Paste your notes into Claude with this prompt:
“Based on these discovery call notes, write a consulting proposal for [client name / company]. Include these sections: Executive Summary (under 150 words), Problem Statement (what they told me they’re facing), Proposed Approach (methodology and process), Deliverables (specific outputs they’ll receive), Timeline (broken into phases), Investment (placeholder for price — I’ll fill this in), and Next Steps (what happens after they sign).
Tone: professional and direct. Avoid vague phrases. Be specific about process and outputs. Discovery notes: [paste notes]”
The output won’t be finished — it will be a strong first draft. You’ll spend 20 minutes editing, not 3 hours writing.
Step 3: Edit for Three Things
Specificity: Replace any generic statements with specific details from the engagement. “We will improve your marketing” should become “We will audit your current email sequence, rewrite the three-email welcome flow, and set up A/B testing on subject lines.”
Voice: Remove phrases that sound like an AI wrote them. Common culprits: “leveraging,” “synergies,” “robust solution,” “value-add.” Read it aloud — if a sentence makes you cringe, rewrite it.
Investment section: Add your actual pricing here. Claude will leave a placeholder.
The Proposal Structure That Works
Executive Summary
What you heard, what you’re proposing, and what the outcome will be — in under 150 words. Decision-makers read this first. If it’s vague, they’ll skim the rest.
Problem Statement
Reflect back what the client told you. This section proves you listened. If you can articulate their problem better than they did on the call, you’ve already differentiated yourself.
Proposed Approach
Your methodology. Don’t be mysterious about process — clients who understand what you’re doing feel in control. Clients who don’t understand what they’re buying push back on price.
Deliverables
Specific, enumerated outputs. Not “strategic recommendations” — “a 10-page strategic brief covering X, Y, and Z, delivered as a PDF and a 45-minute presentation.”
Timeline
Phase it. Even a 2-week project benefits from being broken into phases — it makes the work feel manageable and shows you’ve thought it through.
Investment
Put the price on one line. Don’t apologize for it or bury it. If you’ve done everything above correctly, the price should feel proportionate to the problem you’ve described.
Next Steps
Remove friction from the yes. “Reply to this email to proceed” or “sign the attached agreement” — something specific and easy.
Common Mistakes to Fix Before Sending
Passive voice everywhere. “Deliverables will be produced” should be “I will produce.” Take ownership of the work.
Scope that’s too vague. If you can’t enumerate what you’re delivering, you’ll have scope creep. Claude sometimes writes broad scope — tighten it.
Timeline that’s too optimistic. Add 20% buffer to whatever timeline feels right. You’ll thank yourself.
No clear next step. The proposal should end with a specific action the client takes to move forward.
Advanced: Building a Proposal Library
After 5–10 proposals, you’ll have reusable Claude prompts for your most common project types. Build a prompt for each:
- Brand strategy engagement
- Content creation retainer
- Website redesign
- SEO audit
- Marketing campaign
Each prompt embeds your methodology, your typical deliverables, and your process. You’re no longer generating a proposal — you’re customizing a proven template.
Bottom Line
A proposal is a sales document. Its job is to make the client feel confident that you understand their problem and have a credible plan to solve it. Claude doesn’t make the work better — it makes the document representing your work better.
Stop losing deals because your proposal doesn’t reflect how good you actually are at your job.