Start With Their Problem, Not Your Life Story

Most freelance proposals are rejected within the first ten seconds, and it is rarely because the freelancer lacks skill. It is because the proposal opens with a paragraph about the freelancer. "I am a passionate designer with eight years of experience..." is a lovely thing to write, but the client is not hiring a personality. They are hiring a solution to a problem that is currently keeping them awake at night.

Before you write a single word, answer three questions in your own notes: what is the client trying to achieve, what is standing in their way, and what happens if nothing changes? A shop owner who needs a new website is not really buying a website. They are buying more weekend bookings, fewer abandoned baskets, or the ability to stop apologising for a site that looks tired on a phone. Name that outcome in your first two sentences and you have already separated yourself from the pile.

Mirror their language too. If the brief says "we need a landing page that converts paid traffic", do not translate that into "a bespoke digital experience". Use their words back to them. It signals that you read the brief properly, which an alarming number of applicants do not.

Show That You Understand the Job

A winning proposal proves comprehension before it proves competence. A short paragraph demonstrating that you have engaged with the specifics of their situation does more work than a list of your qualifications.

Try something like: "You mentioned that enquiries drop off after the first email. That usually means the follow-up sequence is either too slow or too generic, so the fix is probably process rather than copy." That single sentence tells the client you have seen this problem before and know roughly where to look. It also invites a reply, and replies are how proposals turn into conversations.

If you spot something the client has missed, say so politely. A gentle observation — that their timeline assumes content will be ready on day one, for example — demonstrates expertise and protects you both from a painful project later.

Outline Your Approach in Plain English

This is where many proposals collapse into jargon. Phrase like "holistic omnichannel strategy" and "synergistic deliverables" do not sound professional; they sound evasive. Clients are quietly asking one question: what will you actually do, and when?

Break your approach into three to five numbered stages. For each one, say what happens, what you need from them, and what they get at the end. For example:

• Discovery: a 45-minute call and a review of your existing analytics. You receive a short summary of priorities.
• Draft: I write the first version of all five pages and send them for comment.
• Revision: one round of amendments based on your consolidated feedback.
• Handover: final files plus a walkthrough recording so your team can make small edits.

Notice how each line is concrete. There is no mystery about what "discovery" means, and the client can picture the project unfolding. Specificity builds trust far faster than adjectives.

Give Real Dates and Real Numbers

Vague timelines are the fastest way to lose a good client. "Approximately four to six weeks" tells them nothing except that you are not sure. Instead, anchor everything to a start date: "Assuming we begin on Monday 3 March, you will have the first draft by Friday 14 March, and we will go live in the week commencing 31 March."

Then state your dependencies honestly. If you need their logo files and product photography before you can begin, say so and give a deadline for receiving them. This is not you being difficult; it is you being organised, and clients respect it.

Costs should be just as clear. Give a single figure or a simple breakdown, state what is included, and list anything that sits outside the scope — extra pages, additional revision rounds, rush turnaround. If you are VAT registered, confirm whether the quoted price includes VAT, because a surprise 20% on the invoice sours an otherwise happy relationship.

Payment terms matter too. A deposit of 25–50% upfront is normal and entirely reasonable for freelance work. Say when the balance is due, and mention late payment terms briefly and without apology.

Avoid the Traps That Lose Good Work

Even a well-structured proposal can be sunk by small errors. Watch for these:

• Length. One page for small jobs, two for larger ones. Nobody reads a nine-page tender for a logo refresh.
• Generic templates. If your proposal could be sent to any client in any sector, it will read like it. Ten minutes of tailoring beats an hour of polish on a template.
• No clear next step. End by telling them exactly what to do: "Reply to confirm and I will send the deposit invoice and a kick-off questionnaire today."
• Typos. Read it aloud, or ask someone else to check it. A proposal riddled with errors suggests the work will be too.
• Radio silence afterwards. If you have heard nothing in five working days, a short, friendly follow-up is perfectly acceptable and often welcome.

Treat Every Proposal as a Small Piece of Work

The freelancers who win consistently are not necessarily the most talented. They are the ones who make the client's decision easy. They show they understand the problem, describe a sensible route forward, and put a clear price and date against it — all without a whisper of unnecessary jargon.

Before you send your next proposal, read it back and ask yourself whether a busy person with no technical background could understand it in ninety seconds. If the answer is yes, you have done the hard part. The rest is simply pressing send.