Most freelancers spend 3–5 hours writing a single client proposal — and still lose the deal. I know because I was one of them. After testing Claude extensively for my own consulting work, I found that the right prompts cut that time to under 45 minutes and noticeably increased my close rate. The difference wasn’t Claude itself — it was knowing exactly what to ask it.
According to McKinsey’s 2023 report, generative AI could add $2.6–$4.4 trillion annually to global productivity.
This is a working swipe file. Every prompt below is copy-paste ready. I’ve organized them into six categories that cover the full proposal lifecycle: from discovery and positioning through pricing, objection handling, and follow-up. I’ll also explain when and why each prompt works, so you can adapt them to your specific situation instead of just blindly copying.
If you’ve been using Claude like a fancy spell-checker, this article will change how you work.
Why Claude Outperforms Other AI Tools for Proposals
Before we get into the prompts, a quick word on tool choice. I’ve used ChatGPT, Gemini, and Claude side-by-side for proposal work. Claude (specifically Claude 3.5 Sonnet and Claude 3 Opus, available via Claude.ai at $20/month for Pro) consistently produces more nuanced, client-focused writing. It’s less likely to produce that generic “I am excited to submit this proposal” tone that kills deals before they start.
Claude also handles long context windows well — you can paste in an entire email thread, a job description, and your existing service menu, and it will synthesize all of it without losing the thread. That’s critical for proposal work where context is everything.
Now, the prompts.
Section 1: Discovery — Extracting the Right Information Before You Write
The biggest reason proposals fail is that they’re written before the freelancer truly understands what the client needs. These prompts help you either prepare for a discovery call or extract key information from what you already know.
Prompt 1 — Discovery Call Question Generator
When to use it: Before your first client call. Paste this in and you’ll walk into the meeting with targeted questions instead of generic ones.
You are an experienced freelance consultant preparing for a discovery call with a potential client. The client is a [type of business, e.g., "B2B SaaS startup with 15 employees"] and they reached out about [brief project description, e.g., "redesigning their onboarding email sequence"].
Generate 12 specific discovery questions that will help me understand: (1) their actual business goal behind this project, (2) what success looks like to them in concrete terms, (3) what they've already tried, (4) who the decision-maker is, (5) timeline and budget expectations, and (6) any internal constraints or politics I should know about.
Make the questions conversational, not interrogative. Avoid yes/no questions.Prompt 2 — Turning a Vague Brief Into a Clear Scope
When to use it: When a client sends you a rambling email or a poorly written brief. Paste their message in and let Claude identify what’s actually being asked.
Below is an email/brief I received from a potential client. Please analyze it and extract: (1) the core deliverable they're actually asking for, (2) any secondary requests that might be out of scope, (3) what's unclear or missing that I'll need to clarify before writing a proposal, and (4) any red flags I should be aware of (unrealistic timelines, scope creep risk, etc.).
After the analysis, write 3 clarifying questions I should ask before I commit to a scope.
Client message:
[PASTE CLIENT EMAIL OR BRIEF HERE]Prompt 3 — Competitive Landscape Research Brief
When to use it: When you’re pitching to a client in an industry you’re not deeply familiar with. This helps you sound informed without spending hours researching.
I'm preparing a proposal for a client in the [industry] space. They are a [company size/type] and their main challenge is [problem].
Give me a concise competitive and market context summary that would help me: (1) understand the pressures this client is likely facing right now in 2026, (2) reference industry-relevant context in my proposal to show I understand their world, and (3) position my solution as addressing a real, current pain point rather than a generic one.
Keep it under 300 words. Be specific, not generic.Section 2: Writing the Core Proposal — Structure, Tone, and Positioning
This is where most people use AI — and where most people get mediocre output because they prompt too broadly. These prompts are structured to produce proposals that actually sound like you wrote them.
Prompt 4 — Full Proposal First Draft
When to use it: After discovery. Fill in the brackets thoroughly — the quality of the output is directly proportional to the detail you provide.
Write a professional freelance proposal for the following project. Use a confident, direct tone — not corporate, not sycophantic. Do not start with "I am thrilled to submit this proposal."
About the client:
- Company: [name]
- Industry: [industry]
- Size: [team size/type]
- Main goal: [what they want to achieve]
- Current problem: [what's not working]
- Timeline: [their desired timeline]
- Budget range: [if known]
About me/my service:
- My name/business: [your name]
- What I do: [your service]
- Relevant experience: [2-3 specific past results]
- My approach: [how you work]
Proposal structure to follow:
1. Opening — restate their problem in my own words to show I understood
2. Proposed solution — specific, not vague
3. Scope of work — bullet list with clear deliverables
4. Timeline — week-by-week if possible
5. Investment — [I'll fill this in, leave a placeholder]
6. Why me — 2-3 sentences max, proof-focused
7. Next step — one clear action
Keep it under 600 words. Clients don't read long proposals.Prompt 5 — Executive Summary / Proposal Opening Paragraph
When to use it: When you have the full proposal but the opening feels flat. The first paragraph is what determines whether they read the rest.
Write 3 alternative opening paragraphs for a client proposal. The client is [description]. Their core problem is [problem]. My solution is [solution].
Each version should take a different angle:
- Version A: Lead with their problem (empathy-first)
- Version B: Lead with the outcome/result they'll get
- Version C: Lead with a surprising insight about their situation
Do not start any version with "I", "We", or "Thank you." Keep each under 60 words.Prompt 6 — Scope of Work Section Builder
When to use it: When you know what you’re delivering but struggle to articulate it clearly without sounding either vague or overwhelming.
Write a clear, professional "Scope of Work" section for a client proposal. The project is [project description].
Format it as two parts:
PART 1 — "What's Included": A bulleted list of specific deliverables (not tasks — deliverables). Be concrete. Example: "3 email sequences (welcome, nurture, re-engagement), each with 4 emails" not just "email copywriting."
PART 2 — "What's Not Included": A short list of common add-ons or adjacent work that is explicitly out of scope, to prevent scope creep.
Deliverables I plan to provide: [list your planned deliverables]Prompt 7 — Rewrite My Draft in a Stronger Voice
When to use it: You’ve written a rough draft but it sounds weak, passive, or too formal. This is one of my most-used prompts.
Rewrite the following proposal section to sound more confident and direct. Remove any passive voice. Cut any sentence that doesn't add value. Replace corporate jargon with plain language. Do not add anything that wasn't already implied in the original — just make it stronger and cleaner. Keep the same length or shorter.
Original text:
[PASTE YOUR DRAFT HERE]Section 3: Pricing and Value Framing That Reduces Sticker Shock
The pricing section is where proposals die. These prompts help you present your investment in a way that feels justified, not arbitrary.
Prompt 8 — Value-Based Pricing Justification
When to use it: Before you write the pricing section, use this to build your own internal justification — and then pull language from it for the proposal.
Help me build a value-based argument for my pricing.
My service: [what you do]
My price: [your fee]
Client's business goal: [what they want to achieve]
Estimated impact if successful: [revenue gain, cost saved, time saved — be specific if possible]
Write a 3-sentence value statement I can include in my proposal that connects my fee to their expected outcome. Do not say "invest in your success" or any similar cliché. Be concrete and logical.Prompt 9 — Three-Tier Pricing Options Table
When to use it: When you want to present tiered options instead of a single price. Research consistently shows that offering 3 options increases average deal value because clients anchor to the middle.
Create a three-tier service offering for my proposal. The client wants [core deliverable].
My core service is: [describe your standard offering]
Design three packages:
- ESSENTIAL: Stripped-down version at approximately [lower price]
- STANDARD: My core offering at [your target price]
- COMPLETE: Enhanced version with additional value at [higher price]
For each tier, list: what's included (specific deliverables), what's NOT included, and one sentence on who it's best for. Make it easy to skim. The goal is to make STANDARD look like the obvious choice.Prompt 10 — ROI Calculator Language
When to use it: For higher-ticket proposals ($3,000+) where you need to help the client see this as an investment, not a cost.
Write a short ROI framing paragraph for a proposal where my fee is [your fee]. The client's business generates approximately [their revenue or relevant metric]. The project aims to [specific outcome, e.g., "increase email conversion rate from 2% to 4%"].
Calculate or estimate what that outcome is worth in dollars over 12 months if the project succeeds (be conservative and transparent about the assumptions). Then write 2-3 sentences that frame my fee as a percentage of that projected return. Be honest, not hype-y.Section 4: Handling Objections Before and After Sending
The best time to handle an objection is before the client raises it. These prompts help you build pre-emptive responses into the proposal itself and craft strong replies when objections come in.
Prompt 11 — Anticipate and Address Common Objections
When to use it: After writing your draft, before sending. Add a short FAQ section or weave the answers into the copy.
I've written a proposal for [type of project] at [your price].
List the 5 most common objections a client in [industry/size] might have about hiring a freelancer for this. For each objection, write a 2-3 sentence response I could include in a FAQ section of my proposal or use in a follow-up email.
Tone: confident but not defensive. Acknowledge the concern, then redirect to value or risk reduction.Prompt 12 — “Your Price Is Too High” Response Email
When to use it: When a prospect pushes back on price. This prompt helps you respond without immediately discounting.
A client responded to my proposal saying my price is too high. My proposal was for [project] at [price]. Their response was: "[paste their message]"
Write a reply email that: (1) acknowledges their concern without being defensive, (2) reinforces the value of the full scope, (3) offers ONE alternative (either a reduced scope at a lower price, or a payment plan) — not both, and (4) ends with a clear question or call to action.
Do not apologize for my pricing. Keep it under 200 words.Prompt 13 — “We’re Comparing Other Vendors” Response
When to use it: When a client tells you they’re also talking to other freelancers or agencies. This is a critical moment most people fumble.
A potential client told me they're comparing my proposal with 2-3 other options. I offer [your service] at [your price]. My key differentiators are: [list 2-3 specific things that set you apart].
Write a short, confident email response that: (1) welcomes the comparison without sounding desperate, (2) highlights my top 1-2 differentiators in concrete terms (not "I'm passionate about your success"), and (3) offers something specific to help them decide — a reference call, a small paid pilot, or a specific question they should ask every vendor.
Do not beg for the business. Under 150 words.Prompt 14 — Risk Reversal / Guarantee Language
When to use it: When you want to reduce the client’s perceived risk without offering a money-back guarantee you can’t back up.
Write 3 versions of a risk-reversal statement I can include in a proposal. I offer [service]. I cannot offer a full money-back guarantee, but I am willing to [what you're actually willing to do, e.g., "revise deliverables up to 3 times" or "provide a free strategy session if results underperform"].
Each version should reduce the client's perception of risk without making promises I can't keep. Keep each under 40 words. Sound human, not legal.Section 5: Follow-Up Sequences That Close Without Feeling Pushy
80% of deals close after the first follow-up, not after the initial proposal. These prompts build out a follow-up sequence that feels natural.
Prompt 15 — 3-Touch Follow-Up Email Sequence
When to use it: Right after you send the proposal. Set up these three emails in advance so you’re not scrambling to write follow-ups under pressure.
Write a 3-email follow-up sequence for after I've sent a client proposal. The proposal is for [project] at [price]. I sent it on [day].
Email 1 (send 2 days after proposal): Check-in, add one new value point or relevant piece of information I didn't include in the proposal
Email 2 (send 5 days after): Address a likely concern proactively, create gentle urgency
Email 3 (send 9 days after): Final check-in, keep the door open without pressure
Each email should be under 100 words. Subject lines included. No "just following up" as a subject line. No fake urgency.Prompt 16 — The “Radio Silence” Follow-Up
When to use it: When a prospect has gone completely quiet after 2+ weeks. This is a high-stakes email — it’s your last shot.
Write a final follow-up email to a prospect who has gone silent for [number] days after receiving my proposal for [project].
The goal is to get a response — even a "no" — so I can move on. Write an email that: (1) is short (under 80 words), (2) assumes they're busy, not uninterested, (3) makes it extremely easy to respond, and (4) closes the loop without burning the relationship. Include two subject line options.Prompt 17 — Proposal Accepted: Kickoff and Onboarding Email
When to use it: Immediately after a client says yes. The first email after acceptance sets the professional tone for the whole engagement.
Write a professional kickoff email to send after a client has accepted my proposal for [project].
Include: (1) genuine but brief enthusiasm (not over-the-top), (2) a clear list of next steps with who does what, (3) what I need from them to get started, (4) the first milestone or deliverable date, and (5) how we'll communicate during the project (e.g., weekly check-in, Slack, email).
Tone: warm but businesslike. Under 250 words.Section 6: Advanced Prompts for Specific Proposal Scenarios
These are the prompts I reach for in trickier situations — retainer proposals, re-engaging old clients, or pitching without a formal RFP.
Prompt 18 — Retainer Proposal Builder
When to use it: When pitching ongoing monthly work. Retainers need a different structure than project proposals because you’re selling a relationship, not a one-time deliverable.
Write a retainer proposal for a client who currently uses me for [type of project work] on a per-project basis. I want to propose a monthly retainer instead.
My proposed retainer: $[amount]/month for [what's included]
Current per-project spend: approximately $[amount] per month
Structure the proposal to: (1) show them the financial and operational benefit of a retainer vs. project-by-project (predictability, priority access, savings), (2) clearly define what's included in the monthly retainer and what would be billed separately, (3) propose a 3-month trial period to reduce their perceived risk.
Keep it under 400 words. Practical, not salesy.Prompt 19 — Re-Engagement Proposal for a Past Client
When to use it: When reaching out to a past client you haven’t worked with in 6+ months. This requires a different tone than a cold proposal — warmer, but still professional.
Write a proposal email to a past client I worked with [timeframe] ago on [previous project]. I want to pitch them a new project: [new project description].
The email should: (1) briefly reference our previous work together and the result it achieved (I'll fill in the specific result), (2) explain why I'm reaching out now — a specific reason tied to their business or something I noticed, (3) present the new project idea clearly but without over-explaining, and (4) suggest a short call to discuss, not immediately ask for a yes.
Do not open with "I hope this email finds you well." Keep it under 200 words.Prompt 20 — Unsolicited Proposal / Warm Cold Pitch
When to use it: When you’ve identified a specific problem a company has and want to pitch them without them asking. This is one of the most powerful ways to win high-quality clients — if the pitch is specific enough.
Write an unsolicited proposal email to a company I researched independently. I've identified a specific problem they have: [describe the problem you noticed — be very specific]. My proposed solution is: [your solution].
The email should: (1) open by demonstrating I've done real homework on their business (specific detail, not generic flattery), (2) name the problem clearly — they may not have articulated it themselves, (3) propose a specific, small first step (not a full project) to reduce their risk in responding, and (4) include a concrete proof point from my past work.
Under 180 words. No attachments. One clear call to action.Prompt 21 — Case Study Snippet for Proposal
When to use it: To create a persuasive 100-word case study snippet that fits inside a proposal without derailing the flow.
Write a concise case study snippet (under 120 words) for inclusion in a client proposal.
Client I worked with previously: [type of client, no name needed]
Project: [what I did]
Result: [specific measurable outcome — numbers preferred]
Timeline: [how long it took]
Format it as a mini before/after story: the problem they faced, what I did, the result. End with one sentence tying it to the current prospect's situation. Make it feel real, not like marketing copy. First person is fine.Prompt 22 — Proposal Audit / Feedback Request
When to use it: Before sending a high-stakes proposal. Paste your full draft and ask Claude to critique it as if it were the client reading it for the first time.
Read the following proposal draft as if you are the client receiving it. The client is [brief client description]. They are [skeptical/price-sensitive/comparing multiple vendors — choose the relevant challenge].
Give me honest, critical feedback on:
1. Clarity — is the scope immediately clear?
2. Value — do I feel like the price is justified?
3. Trust — does this person seem credible and competent?
4. Friction — what questions or doubts does this leave me with?
5. Call to action — do I know exactly what to do next?
Be direct. Tell me what to cut, what to add, and what's weak.
Proposal draft:
[PASTE YOUR FULL PROPOSAL HERE]Quick Reference: Claude Prompts by Proposal Stage
| Stage | Prompt # | Use Case | Time Saved |
|---|---|---|---|
| Discovery | 1, 2, 3 | Prep for calls, decode briefs | 30–60 min |
| Writing | 4, 5, 6, 7 | Full draft, opening, scope, editing | 2–3 hours |
| Pricing | 8, 9, 10 | Value framing, tiers, ROI | 45 min |
| Objections | 11, 12, 13, 14 | Pre-empt and respond to pushback | 1 hour |
| Follow-Up | 15, 16, 17 | 3-touch sequence, silence, kickoff | 1–2 hours |
| Advanced | 18–22 | Retainers, re-engagement, audits | Variable |
3 Tips to Get Better Output From These Prompts
1. Give Claude more context than you think it needs
“`html
Last March, I had a seller in Funchal who wanted to list a three-bedroom villa and needed a full proposal — pricing rationale, marketing plan, commission structure, the works — before our second meeting the following morning. I had two other property visits that afternoon and zero time to sit down and write something from scratch. I pulled up Claude, fed it the property details, the comparable sales data I already had in a spreadsheet, and a rough outline of what I wanted to say. Forty minutes later I had a complete, professional proposal I was genuinely proud to hand over. That meeting closed. I’ve now used Claude specifically for client proposals across 18 different listings over a four-month stretch. What I track is simple: before, a solid proposal took me around two to three hours. With Claude handling the first draft and me editing for tone and local specifics, I’m consistently done in under 45 minutes. That’s not a small thing when you’re running everything yourself with no assistant. The prompts in this article do genuinely work, but here’s the limitation I kept hitting: Claude doesn’t know Madeira. It doesn’t know that Calheta and Ponta do Sol are completely different markets, or that a sea-view premium in Câmara de Lobos means something very specific to local buyers. Every proposal still needs a layer of localisation from me — swapping out generic neighbourhood language for things that actually resonate here. If you paste a prompt and expect a finished product ready to send, you’ll be disappointed. Think of it as a very fast first draft, not a done deal. On the rating side, if I’m being honest about real estate use specifically, I’d give Claude prompts for client proposals a 4.5 out of 5 — the templates cut proposal time in half even for a solo agent working a niche regional market, which is where most of the value lives. Bottom line: If you’re a solo real estate agent writing proposals alone, this is worth your time and costs you nothing to try. Just plan to spend ten minutes localising every draft before it goes to a client — that part Claude can’t do for you. Robson Penassi Real estate consultant in Madeira, Portugal. Solopreneur since 2012. Testing AI tools since 2023 to automate his one-person business. Writes about what actually works — and what does not.My Real-World Experience
