Clients do not hire freelancers. They hire solutions to problems they already have. That is the single most important thing to understand about freelance proposals, and it is why most of them fail. A typical proposal opens with a paragraph about the freelancer: their experience, their skills, their passion. The client, who has fifty other proposals to read, stops there. A winning proposal does the opposite. It opens with the client's problem, shows that you understand it, offers a specific plan to solve it, and proves you have done it before. Everything else is decoration.

This applies whether you are writing a proposal on Upwork, replying to a job post, or sending a cold pitch to a business. The structure below works for all three, and it can be adapted to almost any service, from writing and design to development and virtual assistance. The whole proposal should fit on one page or one screen: if it is longer than that, the client will not read it.

The structure: problem, plan, proof, price, next step

Start with a one- or two-sentence hook that names the client's problem in their own words. If the job post says the client's blog has not been updated in six months and traffic is falling, open with that: I can see your blog has gone quiet and your traffic is dropping. That tells the client you actually read the post, which puts you ahead of most applicants immediately. Follow with a short plan: what you will do, in what order, and what the client will receive. Be specific. I will publish two articles a week, optimised for your target keywords, with images and internal links is a plan. I will help with content is not.

Then add proof. One relevant example beats five irrelevant ones. Link to a single piece of work that is as close as possible to what the client needs, and add one line about the result it produced, such as traffic growth, sales, or a testimonial quote. If you have no client work yet, use a sample project you made for exactly this purpose, and label it honestly as a sample. End with the price and the next step: a clear call to action, such as a fifteen-minute call on Tuesday, or a question that invites a reply.

The mistakes that kill proposals

The most common mistake is the generic template. Clients can tell when a proposal was copied and pasted, because it does not mention anything specific about their business, their post, or their problem. A second mistake is leading with price, or with a long list of qualifications. Price matters, but it matters after the client believes you can solve the problem. A third mistake is making the proposal about you: your journey, your tools, your certifications. The client cares about their outcome, and every sentence should serve that.

Two more mistakes are worth naming. The first is promising too much: a proposal that claims you can do everything, in any style, by any deadline, reads as desperate rather than capable, and it sets you up for a project you cannot deliver. The second is forgetting to ask a question. A short, intelligent question about the project, such as who is your ideal reader, or what does success look like in three months, shows engagement and gives the client a reason to reply, which is the real goal of the proposal: not to win the job in one message, but to start a conversation.

A reusable template

Here is a template you can adapt. Keep it short, and customise the bracketed parts for every client. Opening: Hi [name], I noticed [specific problem from their post or website]. Plan: Here is how I would fix it: [step one], [step two], [step three]. You would receive [deliverable] by [date]. Proof: I did similar work for [client or sample project], where [result]. You can see it here: [link]. Price: My rate for this is [price], which includes [what is included]. Next step: Would a short call on [day] work to discuss it? Or, if you prefer, I can start with [small first task] and you can judge the work before committing to the full project.

That last line is a powerful closer for beginners: offering a small paid first task lowers the client's risk and gives you a chance to prove yourself without a long commitment. Once you have delivered it well, the larger project usually follows. Track which proposals get replies and which do not, and adjust the template based on what works. A proposal is a sales document, and like any sales document, it improves with testing.

Frequently Asked Questions

Q: How long should a freelance proposal be?

A: Short. Aim for one screen or one page, roughly 150 to 250 words. Clients skim, so lead with their problem and your plan, and cut everything else.

Q: Should I include my price in the first proposal?

A: Yes, unless the client explicitly asks for a quote later. A clear price with what it includes builds trust and filters out clients who cannot afford you.

Q: What if I have no past work to show in a proposal?

A: Create one sample project that matches the job, label it honestly as a sample, and link to it. One relevant sample is better than no proof at all.