How to Write a Freelance Proposal That Wins (With a Template)

A client posting a job gets somewhere between 20 and 80 proposals. They do not read 80 proposals. They skim until something stops them, then read that one properly.

Your job is to survive the skim.

Why most proposals fail

They open with the writer. *"I am a passionate full-stack developer with 8 years of experience..."*

The client does not care yet. They have a problem, and they are scanning for someone who understands it. Every sentence about you before you demonstrate understanding of them is a sentence spent on the wrong thing.

The structure that works

1. First line: prove you read the posting

Reference something specific — a constraint, a stack choice, an odd requirement. Not "I read your job description" but a detail that proves it.

"You mentioned the migration has to preserve existing URLs — that's usually where these projects go wrong, so I'd start there."

This single line separates you from the 60% who paste a template.

2. Second paragraph: show you have done this exact thing

One relevant example. Not your whole CV. The closest match you have, with a concrete outcome.

"I migrated a 400-post publication from WordPress to Next.js last year. We kept every URL, added redirects for the ones that had drifted, and organic traffic was flat within three weeks — no ranking dip."

Numbers make this real. "Improved performance" is noise. "LCP from 4.2s to 1.1s" is evidence.

3. Third: a short plan

Three to five steps showing how you would approach *their* project. This is the part almost nobody includes, and it is the most persuasive thing in the document, because it turns an abstract hire into a concrete sequence.

You are also, quietly, demonstrating that you have thought about it more than the other applicants.

4. Fourth: price and timeline, stated plainly

Do not hide the number or make them ask. Give a figure or a tight range, and what it covers.

"$4,200 fixed for the migration, redirects, and a post-launch check. About three weeks from kickoff."

5. Last: one question

End with a specific question about their project. It invites a reply, and it signals you are evaluating fit too — not just hoping to be chosen.

The template

Copy this and adapt:

Hi [name],

>

[Specific observation about their project that proves you read it. Mention the risky or interesting part.]

>

I've done this before: [one closely-matched example with a concrete outcome and a number].

>

How I'd approach yours: 1. [First step — usually the thing that de-risks the project] 2. [Second step] 3. [Third step] 4. [Handover / verification step]

>

[Price] for the above, roughly [timeline] from kickoff. That includes [what's covered]; [what's not] would be separate.

>

One question: [specific question about scope, constraints, or priorities]?

>

[Portfolio link]

>

[Your name]

Rules that make a measurable difference

Keep it under 250 words. Long proposals read as desperate. Confident people are brief.

Do not apologise for anything. No "I know I don't have much experience with X, but...". If you cannot do the job, do not apply. If you can, act like it.

Do not list every technology you know. It reads as unfocused. Name the ones relevant to their project.

Answer their screening questions properly. Many clients filter on these first; a lazy answer there means your beautiful proposal is never read.

Send it soon. Early proposals get read while the client is still enthusiastic. A great proposal sent on day four often loses to a decent one sent in the first hour.

What to do after sending

Nothing. Do not follow up in 24 hours; it reads as pressure. If you have not heard back in a week and the job is still open, one short message is fair:

"Still interested in this — happy to answer any questions. If you've gone another way, no problem at all."

Then move on. The single biggest predictor of getting hired is the number of good proposals sent, not the amount of polish on any one of them.

On Freelancezero applying is free — no Connects, no per-application currency — so the only cost of sending a proposal is the fifteen minutes it takes to write a good one.