Writing a proposal that gets read
What a client is actually looking for in the first ten seconds, how to open, what to include and what to leave out, how to price without underselling, and the mistakes that get a proposal archived unread.
A client with fifteen proposals gives each one about ten seconds before deciding whether to keep reading. Everything below is about surviving those ten seconds and then being worth the next two minutes.
What the client is actually doing
They are not comparing you against an ideal. They are sorting a pile into "worth a conversation" and "not", using two questions:
Did this person read my post?
Do they understand my problem?
Almost nothing else matters at this stage. Not your years of experience, not your list of technologies, not how much you want the work.
The opening
Your first two sentences decide whether the rest is read.
Do not open with yourself. "I am a full-stack developer with eight years of experience" is how most proposals start and it is the reason most are not read. It says nothing about their problem.
Open with their problem, showing you understood it. "You have a Figma design for twelve pages and an existing Next.js codebase, and you need the two joined without rebuilding what works." A client reading that knows instantly you read the post.
Or open with the question that matters. "Before quoting I would need to know whether the existing components are staying — that changes this from a two-week job to a five-week one." This is extremely effective, because it demonstrates you are thinking about the actual work rather than a generic version of it.
The middle
Once you have their attention, earn the conversation.
Your approach, briefly. Not a full plan — you do not have enough information for one, and pretending you do is a warning sign. Enough to show there is a method.
Relevant evidence, narrowly chosen. One project resembling theirs beats a list of ten that do not. Link it. If you cannot link it, describe the problem and what you did.
What you need from them. Access, assets, decisions, a point of contact. Clients rarely think about this and are impressed by someone who has.
Risks or unknowns you can see. Naming the thing that might go wrong makes you look experienced, not negative. Every experienced client has been burned by someone who said everything was straightforward.
Length
Long enough to be substantive, short enough to be read. Three or four tight paragraphs is usually right.
Very short proposals read as low effort. Very long ones do not get read at all. If you are over about four hundred words, you are probably explaining rather than demonstrating.
Pricing
Explain the number. A price with reasoning is worth far more than a lower price without. "Roughly three weeks at this rate, assuming the components are reusable; if they are not it is closer to five, and I would want to check before committing" is a professional answer.
Do not underbid to win. It attracts clients who chose on price, who are the same clients who dispute, demand extras and leave poor reviews. And you will resent the work by week two, which shows.
Do not pad either. Clients compare.
If the budget is unrealistic, say so respectfully with a reason. Sometimes the budget was a guess and you have just educated them. Sometimes they move on, which saves you a bad engagement.
Propose milestones on fixed-price work. It shows you think in stages and gives the client a way to commit gradually, which makes hiring you less risky and therefore more likely.
Mistakes that get you archived
The obvious template. Clients see dozens. A proposal that mentions nothing specific to their post is instantly recognisable.
Getting their name or business wrong. Fatal, and more common than you would think.
Promising everything. Agreeing to an impossible deadline with no questions does not read as confidence, it reads as not having understood.
Pasting your CV. Your profile carries your background. The proposal is about their problem.
Asking to move off-platform. An instant no from any experienced client, and a terms breach that risks your account.
Typos in the first line. Unfair perhaps, but it is what people do.
Before you send
You can save a proposal as a draft and come back to it, and edit or delete a draft before submitting. Use that. A proposal written in ninety seconds reads like one.
Check: does the first sentence mention their problem? Have you asked one good question? Is the price explained? Would you reply to this?
Afterwards
The client may shortlist you, message you, or archive it. Shortlisting means you are in contention — respond promptly, because responsiveness at that stage is being assessed whether or not anyone says so.
If you get no response, that is normal and not personal. Clients go quiet, budgets vanish, someone internal takes the work.
If you are consistently getting no responses, the problem is upstream of your proposals. Usually the profile: an incomplete one undermines even a good proposal, because clients look at it before deciding. Sometimes targeting: applying to jobs you are not really suited to produces silence no writing can fix. See Your freelancer profile.
Three openings that work
Concrete examples, because the advice above is easier to agree with than to apply.
The specific read. "You have a working Rails app and a designer's Figma file, and you need them joined without touching the API. I have done exactly this twice, most recently for a logistics company with a similar setup."
The good question. "Before quoting properly I would want to know whether the existing checkout stays. If it does this is about two weeks; if it is being replaced it is closer to five, and the approach is different."
The honest reservation. "I can do this, but the two-week deadline is not realistic for the scope described unless the content is already written. If it is, I am available and can start Monday."
All three do the same thing: demonstrate you engaged with their actual situation, in the first two sentences.
Proposals for different job types
Fixed price. Propose milestones. It shows you think in stages and reduces the client's risk, which makes hiring you easier.
Hourly. Address the weekly hour cap directly and say what you would realistically use. A client's main worry about hourly is an open-ended bill; addressing it unprompted is reassuring.
Dedicated Hire. These cost more bids to apply to and deserve more effort. Talk about availability, how you would work, and what a month would look like. The client is hiring a relationship rather than a deliverable.
Drop-In, if the client seems to want something packaged, mention that you have one that fits. Sometimes the fastest route to work is pointing them at a package rather than proposing a project.
After sending
Do not send a follow-up chasing a response. Clients see it as pressure, and the proposal is already visible to them.
Do respond quickly if they shortlist or message you. Responsiveness at that stage is being assessed whether or not anybody says so, and being slow at the shortlist stage undoes a good proposal.
Length, structure and formatting
A proposal is read on a screen alongside a dozen others, so structure matters as much as content.
Short paragraphs. A blank line between them. No wall of text.
Bold sparingly, for the two or three phrases that matter most.
A short list where you are genuinely listing things, and prose everywhere else. A proposal made entirely of bullet points reads as a form rather than a considered response.
Three or four paragraphs is usually the right size. If you are past about four hundred words, you are explaining rather than demonstrating, and the client has stopped reading.
Adapting rather than starting fresh
Nobody writes every proposal from nothing, and you do not need to. What matters is what you adapt.
Keep a structure you trust and a couple of paragraphs about how you work that are genuinely reusable. Then write the opening and the specifics fresh every time, because that is the part being assessed.
The failure is not reuse, it is reuse of the part that should be specific. A proposal whose first two sentences could have been sent to any job is the one that gets archived.
Learning from what does not work
If you are applying steadily and not converting, the useful thing is to look for the pattern rather than to try harder.
Are you applying to jobs where you are a genuine fit, or ones you could plausibly do? Are you getting shortlisted and losing, or not getting shortlisted at all? The first is a pricing or interview problem; the second is a profile or targeting problem, and no amount of proposal writing fixes it.
Track it roughly for a month. Most freelancers discover the problem is upstream of the proposals entirely.
Common questions
Should I include a price if the client did not give a budget? Yes, with reasoning. A proposal with no number is hard to act on.
Can I edit a proposal after sending? No. Save a draft and check it before submitting.
Should I attach samples? Link to relevant work rather than attaching large files.
How long should I wait before assuming no? Do not chase. If a job closes, you are notified.
Related
Did this answer your question?
Did this not answer it?
Open a ticket and a person will read it. You do not need an account.