Writing Proposals That Win Freelance Projects
Show you understand the brief, outline milestones clearly, and state what you need from the client before starting work.
Start With the Brief, Not Your Rates
Most freelance proposals are rejected in the first ten seconds — not because the price is wrong, but because the client can tell the writer skimmed the brief. A winning proposal opens by proving you read it properly. That means echoing the client's own language back at them.
If their advert says "we need someone to turn our messy onboarding emails into something that doesn't scare new customers", don't reply with "I offer professional copywriting services". Reply with "Your onboarding sequence is losing people at step three — here's how I'd fix that."
Three things to capture in your opening paragraph:
- The actual problem, in the client's words, not yours.
- What success looks like to them — more sign-ups, fewer support tickets, a website that finally loads on mobile.
- One specific observation that shows you looked at their site, their shop, or their socials before writing a word.
That last point alone puts you ahead of most applicants. A single sentence like "I noticed your checkout asks for an account before payment, which is likely costing you sales" does more work than three paragraphs of credentials.
Structure Your Proposal Around Milestones
UK clients — particularly small businesses and sole traders — are often buying a freelancer for the first time. They are nervous about paying money up front and hearing nothing for three weeks. Milestones calm that fear because they turn an opaque project into a series of small, visible wins.
A simple milestone structure for most projects:
- Discovery and planning — a kick-off call, a written summary of what we agreed, any research needed.
- First draft or build — delivered by a named date, with a clear note on what you need reviewed.
- Revisions — state the number of rounds included, and what counts as a round.
- Final delivery and handover — files, logins, documentation, or training as appropriate.
Attach a date to each one. "Week one: kick-off call and content plan. Week two: first draft of five pages. Week three: revisions and final files." Vague timelines read as evasive; dated milestones read as professional.
You should also state your revision policy plainly. Two rounds included, with additional rounds charged at your hourly rate, is a perfectly reasonable position. It protects you from the client who wants endless small tweaks, and it signals that you have done this before.
Be Specific About What You Need From the Client
This is the section almost every freelancer skips, and it is the one that wins work. A proposal that lists your requirements tells the client you have thought past the pitch and into the actual working relationship.
Typical things you might need before starting:
- Access — website logins, shared drive, hosting panel, brand assets folder, or existing analytics.
- Materials — logos, product photos, tone of voice notes, previous copy, or a list of competitors they admire.
- A named decision-maker — the person who can sign off work, and how quickly they typically respond.
- Feedback windows — for example, comments returned within three working days of each milestone.
- Anything that could block progress — a designer still working on the logo, a developer mid-migration, an accountant who needs to approve the wording of a pricing page.
Framing these as "what helps me get you the best result" rather than "what you must provide" keeps the tone collaborative. It also gently filters out clients who cannot or will not engage, which saves you both time.
Talk About Money Without Apologising
Put your price in the proposal, not in a separate email three days later. UK clients respect clarity, and hiding your rate until the "let's chat" stage wastes everyone's time.
Give a fixed figure for the defined scope, and note what sits outside it. If the project grows, say how you handle that — an hourly rate, a day rate, or a new fixed quote. Mention payment terms in plain terms: a deposit to secure the dates, invoices due within fourteen or thirty days, and what happens if the project pauses.
If you are VAT registered, say so and show whether the figure includes VAT. If you are not, no need to mention it — a client will assume.
Avoid the Common Proposal Traps
Even good freelancers fall into habits that quietly cost them work.
- Talking about yourself first. Lead with their problem, not your biography.
- Templates with the wrong name left in. Check it twice, then check it again.
- Long portfolios with no context. Two relevant examples with a line explaining the outcome beat ten unexplained screenshots.
- Jargon. "Deliverables", "ideation" and "synergy" mean nothing to a plumber who needs a better website. Say "the pages I'll write" and "the ideas we'll test".
- No next step. Finish with a single clear action: a fifteen-minute call on Tuesday or Thursday, or a reply confirming the start date.
Follow Up Once, Politely
Send your proposal, then wait. If you have heard nothing after five to seven working days, one short follow-up is entirely appropriate. Keep it to three lines: a friendly nudge, a reminder that you have dates free, and an offer to answer any questions.
Then leave it. Chasing harder rarely converts a hesitant client and it damages your standing. Instead, keep a simple log of what you sent, when, and what happened. After a dozen proposals you will start to see which openings, milestone structures and price points actually land — and you can sharpen the next one in ten minutes flat.

Post a comment