How to Write a Freelance Proposal That Actually Wins

You lost the project before you started writing

A client replied to your pitch. They're interested. They asked for a freelance proposal. And now you're staring at a blank document wondering what to put in it.

So you write three paragraphs about your experience, attach a price, and hit send. Two days later: silence. A week later: "We've decided to go with someone else."

The proposal didn't lose you the project because your price was wrong. It lost because it read like a resume instead of a solution. The client wanted to see that you understood their problem. Instead, you talked about yourself.

Here's how to write a freelance proposal that actually wins.

What a freelance proposal is really for

A proposal is not a quote. It's not a scope document. It's not a cover letter.

A freelance proposal is a sales document that does three things:

1. Proves you understand the problem. The client needs to feel heard before they trust your solution.
2. Presents a clear plan. Not every detail — just enough to show you've thought it through.
3. Makes saying "yes" easy. Clear pricing, clear timeline, clear next step.

If your proposal does all three, you'll close more projects than freelancers who are technically better than you. Most proposals fail at step one — they jump straight to "here's what I'll do" without first establishing "here's what I heard."

The winning proposal structure

Every strong freelance proposal follows this structure. Customise the details, but keep the skeleton.

1. Opening: restate the problem (100–150 words)

Start with the client's words, not yours. Reference what they told you in the brief, the call, or the email thread.

Example:

"You mentioned that your current website isn't converting visitors into demo requests — your team is generating traffic through content marketing, but the site experience isn't translating that into pipeline. You need a redesign that prioritises conversion without losing the brand identity your team spent the last year building."

This does two things: it proves you were listening, and it forces the client to nod along before they've even read your solution.

Never start with: "Thank you for the opportunity to submit this proposal." That's filler. They know you're submitting a proposal — they asked for one.

2. Your approach (200–400 words)

Describe what you'll do and why. Not a task list — a strategy. The client should understand your thinking, not just your deliverables.

Example:

"I'll approach this in three phases. First, a conversion audit of the current site to identify where visitors are dropping off — this typically reveals 3–4 quick wins we can implement immediately. Second, a redesign of the core pages (homepage, pricing, product) focused on a single conversion path: visitor → demo request. Third, implementation in Webflow with A/B testing on the key pages so we can validate the changes with real data."

Notice what this doesn't include: jargon, vague promises, or a list of technologies. The client doesn't care that you use Figma. They care that you have a plan.

3. Scope and deliverables (a clear list)

Now be specific. A numbered list of exactly what they're getting.

Example:

1. Conversion audit report (PDF, 5–10 pages)
2. Wireframes for 5 core pages
3. High-fidelity designs in Figma (desktop + mobile)
4. Webflow implementation with CMS
5. A/B test setup for homepage and pricing page
6. 2 rounds of revisions per page
7. 30-day post-launch support

Why the detail matters: It protects you from scope creep. If the client later asks for a sixth page, you can point to the proposal: "We agreed on five core pages. I'm happy to add a sixth — here's what that looks like as an add-on."

If you're not sure how to handle those conversations when they come up, the Scope Creep Responder generates professional pushback emails that protect your boundaries without damaging the relationship.

4. Timeline

Give a realistic timeline with milestones. Clients don't want "6–8 weeks." They want:

| Milestone | Date | |---|---| | Conversion audit delivered | Week 1 | | Wireframes review call | Week 2 | | Designs delivered (round 1) | Week 4 | | Revisions complete | Week 5 | | Webflow build complete | Week 7 | | Launch + A/B test live | Week 8 |

Two rules:

• Always pad by 20%. If you think it takes 6 weeks, say 7–8.
• Always state what's required from the client. "This timeline assumes feedback within 2 business days of each delivery."

5. Investment (not "cost")

Frame pricing as an investment, not a cost. And always present options.

Option A — Full project: $12,500 Everything listed above. Conversion audit through launch and 30-day support.

Option B — Design only: $7,500 Conversion audit, wireframes, and high-fidelity designs. No Webflow build or A/B testing.

Why two options? It shifts the conversation from "yes or no" to "which one." The client feels in control. And most pick Option A — it's why you lead with the full package.

If you're not sure what to charge for either option, run your numbers through a freelance rate calculator first. Pricing should come from your costs and target income, not from what feels right.

Always break down what's included in each option. Never present a number without context.

6. Why you (keep it short)

Two to three sentences about why you're the right person. Not your life story. Not every project you've ever done.

Example:

"I've redesigned conversion-focused SaaS sites for 12 companies in the last two years, including [Company X] where the redesign increased demo requests by 34%. I specialise in Webflow builds, which means you get design and development from one person — no handoff delays."

One relevant stat. One proof point. Done.

7. Next step (one clear action)

End with exactly one thing the client needs to do.

Example:

"If this looks good, reply to this email and I'll send over a contract and invoice for the 50% deposit. I can start the conversion audit the week of May 12th."

Never end with "let me know if you have questions." That's passive. Tell them the next step.

What separates a winning proposal from a losing one

After reviewing hundreds of freelance proposals (both winning and losing), the pattern is clear:

Winning proposals:

• Lead with the client's problem, not the freelancer's background
• Include a clear scope list that can be referenced later
• Present 2 pricing options
• Have a specific next step
• Are under 2 pages (excluding appendices)

Losing proposals:

• Open with "About me" or "Our company"
• Use vague scope like "website redesign as discussed"
• Present a single take-it-or-leave-it price
• End with "looking forward to hearing from you"
• Are either too short (half a page) or too long (10 pages)

How to set payment terms in your proposal

Always include payment terms in the proposal — not as a separate document. Seeing the terms alongside the scope makes it feel like a complete package, not an afterthought.

Standard freelance payment terms:

• Projects under $5,000: 50% upfront, 50% on delivery
• Projects $5,000–$15,000: 50% upfront, 25% at midpoint, 25% on delivery
• Projects over $15,000: 30% upfront, 30% at midpoint, 30% on delivery, 10% at 30-day review

If you haven't written your payment terms yet, the Payment Terms Writer creates professional, client-friendly terms in seconds — including a plain-English explanation you can paste directly into your proposal.

State the payment method (bank transfer, Stripe, PayPal) and the payment window (net 7 or net 14 — never net 30 for project work). And make sure you know what to do if they don't pay on time. Having an invoice follow-up process ready means you don't freeze when the first payment is late.

Red flags in the proposal stage

Sometimes the best proposal decision is not to send one. Watch for these signals during the briefing stage:

• The client won't share a budget range ("just tell us your price")
• They've already talked to 8+ freelancers (they're price shopping)
• They want a detailed proposal before a discovery call
• The brief is a single sentence ("we need a new website")
• They push back on your process before you've even started

If any of these come up, run the conversation through the Client Red Flag Detector before investing hours in a proposal. It scores the client across 12 risk dimensions so you know what you're walking into.

There's a faster way

Writing a freelance proposal from scratch takes 1–3 hours. Veloce_'s Proposal Generator turns a client brief into a complete project proposal in seconds — introduction, scope, timeline, investment, and next steps. Win the project before someone else does.

You paste in the brief, add your details, and get a proposal that follows the structure above. Edit it, add your personal touches, and send. The hard part — structuring the document and framing the narrative — is done for you.

FAQ

How long should a freelance proposal be?

One to two pages for projects under $15,000. Two to four pages for larger projects. The body of the proposal should be concise — save detailed appendices (portfolio samples, case studies, technical specifications) for attachments. Clients skim proposals. If the core message isn't clear on page one, they won't read page two.

Should I send a proposal before or after discussing price?

After. Always have a budget conversation on the call before writing the proposal. Ask: "Do you have a budget range in mind for this project?" If they won't share a number, give them a ballpark: "Projects like this typically run $8,000–$15,000 depending on scope. Does that align with what you're expecting?" If there's a mismatch, you find out before wasting hours on a proposal.

How long should I wait before following up on a sent proposal?

Three to four business days. Send a short follow-up: "Just checking in on the proposal I sent over on Tuesday. Happy to jump on a quick call if you'd like to discuss anything or if the scope needs adjusting." If you don't hear back after two follow-ups, move on.

Should I include a contract with my proposal?

No. Send the contract after the proposal is accepted. Including it upfront can feel premature and overwhelming. The proposal is a sales document — keep it focused on the value and the plan. The contract is a separate step that comes after they say yes.

How do I compete with freelancers who charge less?

Don't compete on price. Compete on clarity, professionalism, and proof. A freelancer who sends a well-structured proposal with a clear plan, relevant experience, and specific next steps will beat a cheaper freelancer who sends a paragraph and a number — every time. Clients pay more for confidence and reduced risk.