Most freelance proposals are ignored, and the reason is usually not price. It is that the proposal was about the freelancer rather than about the client’s problem, and the client could not work out from reading it what would actually happen if they said yes.
A good proposal is shorter than you think, answers the questions the client is actually asking, and makes agreeing easy. None of that requires design skills or clever writing.
What the Client Is Really Asking
Whatever the brief says, the person reading your proposal has four questions in mind:
- Does this person understand what I need?
- Can they do it?
- What will it cost and how long will it take?
- What is it like to work with them?
Every paragraph should be answering one of those. Anything that answers none of them is padding, and padding is what makes proposals long and unread.
The Structure That Works
Open by restating their problem
Begin with their situation in your own words, not with your introduction. Two or three sentences showing you understood the brief, including the thing underneath the brief that they may not have stated outright.
This does more work than anything else in the document. It is also where most proposals fail, because they open with a paragraph about the freelancer’s years of experience, which the client has no reason to care about yet.
If you can name the real problem rather than the surface request — that the website redesign is really about the enquiry form nobody fills in — you have already distinguished yourself from everyone else quoting.
Say what you propose to do
Specific and concrete. Not “improve your web presence” but the actual work: what you will produce, how many of them, in what form.
List deliverables as items. A client can picture receiving items. They cannot picture receiving a strategy.
Say what is not included
Counter-intuitive and extremely valuable. A short “not included” list prevents the misunderstandings that sour projects and turn profitable work into unpaid work.
It also reads as confidence. Someone who defines boundaries clearly sounds like someone who has done this before.
Give a timeline with dependencies
Phases with rough durations, and, crucially, what you need from them and when. Most projects that run late run late because the client did not supply something on time, and a timeline that makes their obligations visible protects you.
Say plainly that dates shift if their inputs are late.
State the price clearly
One number, easy to find. Do not bury it, do not surround it with qualifications, do not present four options unless you have a good reason.
If you offer options, offer two or three at most, and make them genuinely different in scope rather than the same work at three prices. A smaller first phase is often the most useful second option, because it lets a hesitant client start.
Include payment terms here: how much upfront, when the rest is due, and what “due” means in days.
Prove you can do it, briefly
Now, near the end, a short section with two or three relevant examples. Relevant is the key word. One example of similar work beats a list of everything you have ever done.
For each, say what the problem was and what changed. If you can include a result, do. If not, describing the problem and the solution is still far better than a link with no context.
Close with one clear next step
Tell them exactly what to do: reply to confirm, book a call using a link, or sign and return. One action. Proposals that end with “let me know if you have any questions” end in silence, because you have given the reader nothing to do.
How Long Should It Be?
For most freelance work, one to two pages. Long enough to cover scope, price, and timeline properly; short enough to be read in full on a phone.
Long proposals are usually a sign of uncertainty. If you are not sure what the client wants, the answer is another conversation, not more pages.
Mistakes That Cost You Work
Sending it without asking questions first. If the brief is thin, ask two or three specific questions before proposing. This alone puts you ahead of most applicants, and it produces a proposal that fits.
Writing about yourself first. Your credentials matter, but they matter after the client believes you understood them.
Vague deliverables. Anything the client could interpret differently from you will eventually be interpreted differently from you.
Obvious templates. Reusing a structure is sensible. Sending something that reads as though the client’s name was pasted in is not.
No price. “Happy to discuss pricing once we talk” reads as evasive. Give a number or a clearly labelled range.
Too many options. Five tiers do not look thorough. They look like you are hoping one of them fits.
What to Do When You Hear Nothing
Silence usually means busy, not rejected. Follow up once after about a week, briefly and without reproach: checking whether they had questions, still available, happy to adjust the scope if the budget is not right.
That last offer is worth including, because budget is the most common unspoken reason for silence and many clients will not say so unprompted.
If there is still nothing after a second follow-up a couple of weeks later, let it go. Some proposals lose to internal decisions you will never hear about.
The Habit Worth Building
Keep a record of every proposal: what you quoted, what you scoped, whether you won it, and why if you know. After twenty or thirty you will be able to see which kinds of work you win, which you consistently under-scope, and which clients were never going to say yes.
That record improves your proposals faster than any amount of advice, including this article, because it is about your work and your market rather than someone else’s.