Why most freelance proposals fail

Clients don't read proposals the way you hope. They skim the first two lines, and if those lines are about you — your years of experience, your passion, your portfolio — they move on to the next freelancer. The proposals that win lead with the client's project, not the freelancer's biography.

The 5-part structure that gets replies

• 1. Open with their project. Name the exact thing they asked for, in their words. It proves you actually read the brief — most applicants clearly didn't.
• 2. Prove it with one result. One concrete, relevant outcome ("cut report time from 6 hours to 40 minutes") beats five vague claims. Specific numbers are believable; adjectives are not.
• 3. Show a short plan. Three numbered steps showing how you'd approach the work. A plan turns you from a gamble into a process.
• 4. State price and start date plainly. "Fixed price, no surprises, I can start Monday" removes the two fears every client has: runaway cost and an unreliable freelancer.
• 5. End with one smart question. A question about their project gives them an easy reason to reply — and a reply is what turns a proposal into a conversation, and a conversation into a job.

Keep it short, then follow up

For marketplace proposals, stay under about 150 words — the client reads dozens. And send one polite follow-up three or four days later if you hear nothing: inboxes bury good proposals, and a short follow-up that adds one new detail gets a surprising number of second looks.

Do ten minutes of homework before you write

Read the brief twice and underline the exact deliverable, the deadline, and any tool or skill the client names. Then look at their business for two minutes: what do they sell, who buys it, and what would success look like for this one job? A proposal that names their product and their customer reads completely differently from one that could have been sent to anyone. If the brief is vague, say so in your question at the end — clients respect a freelancer who spots a gap instead of pretending it is not there.

What to write when you have no direct example

New freelancers worry most about the proof step, but a transferable result works fine if it is honest. A shop assistant who cut stocktaking time with a spreadsheet can say so when applying for a data-entry job. A student who ran a small society page can quote its follower growth when applying for social media work. What you must not do is invent a client, a number, or a job you never did — one follow-up question from the client will expose it, and the damage lasts longer than one lost proposal.

Pricing lines that do not scare clients away

State the price, what it covers, and what it does not cover, in one short paragraph. A fixed price with a clear scope ("two revisions included, extra revisions charged separately") calms clients far more than a low hourly rate with no ceiling. If you ask for a deposit, say the percentage and when the balance is due — for example, half to start and half on delivery. Clients who argue about a deposit are often the same clients who pay late later, so a plain deposit line also filters bad jobs early.

Three sentences to never write

• "Dear Sir/Madam, I am writing to apply." It tells the client nothing about their project and marks the proposal as a copy-paste job.
• "I am passionate about excellence and hard work." Every applicant claims this. Replace it with one concrete result or one specific observation about their brief.
• "I can do everything you need, just tell me." It sounds eager but reads as unfocused. Name the one deliverable you will produce first, and the date you will deliver it.

A before-and-after opener

Weak: "Hi, I am a professional freelancer with 5 years of experience in many fields. I would love to work on your project." Stronger: "Your brief asks for a landing page that turns visitors into trial sign-ups. On a similar page last month I rewrote the headline and form and sign-ups rose from 2% to 5% in two weeks. Here is how I would approach yours in three steps." The second version names their goal, gives one believable result, and promises a plan — all in four sentences.

Send it, then stop rewriting. Most proposals lose more jobs to delay than to wording. If your draft names their project, gives one real result, shows a short plan, states price and start date, and ends with one question, send it. You can improve the next proposal from the reply you get; you cannot improve a proposal that is still sitting in your drafts.