Proposals that get replies
A client reads two lines before deciding whether to open yours. Almost every proposal spends both of them on the wrong thing.
The symptoms
If any of these sound like your last month, this page is about the cause.
Nobody replies, and nobody says why
Proposals go out and nothing comes back. Not a rejection, not a question. Silence.
Every silent proposal cost connects and told you nothing about what to change.
The good jobs never answer, the bad ones do
The clients who do reply are the ones haggling over an already low rate.
You end up with the work you least wanted, at the price you least wanted.
You write more and it gets worse
Sending twice as many proposals produced roughly the same number of conversations.
Volume is now the cost and none of it is buying attention.
A client posts a job and comes back to thirty proposals. They are not reading thirty proposals. They are reading the first line or two of each one in a list, opening four, and hiring from those four. Everything you write after the second line is being read by somebody who has already decided you are worth opening. Everything before it is doing the actual work.
This is the whole problem, and it is why writing more proposals does not fix a reply rate. A weak opening sent forty times is a weak opening forty times.
What the client is scanning for
They are not scanning for qualifications. They can see your job history, your score and your rate already, in the same row as your proposal. They are scanning for one thing: evidence that this was written for them.
That evidence is almost never a claim. It is a detail. Something in the posting that you could only have mentioned by reading it properly, said back to them in a way that shows you understood what it implies.
Before
Hi there! I'm a full-stack developer with 7+ years of experience building scalable web applications. I've worked with React, Node.js, Python, and AWS. I'm passionate about clean code and delivering high-quality results on time. I would love to discuss your project further.
After
You mentioned the export takes four minutes and users assume it has frozen. That usually means it is running synchronously and holding the request open. The fix is to move it to a background job and show progress, and it is normally a day or two rather than a rewrite.
The second one does not claim to be experienced. It demonstrates it, in a sentence, about their problem. And it could not have been sent to anyone else, which is the only quality a client can actually verify from a list view.
The shape that works
- Their problem, said back. One or two sentences. Specific. Something from the posting, not from your template.
- What you would do about it. The first step, not the full plan. Concrete enough that they can picture it starting.
- Why you, in one line. The closest thing you have actually done. One, not five.
- One question worth answering. Something the posting genuinely leaves open, that affects how you would approach it.
That is usually under a hundred and fifty words. If yours is four hundred, the extra two hundred and fifty are not being read, and they are pushing the question out of view on a phone.
Keep the template, change the opening
There is nothing wrong with a structure you reuse. Structure is not what a client recognises. What they recognise is an opening they have read forty times this week. Write those two lines from scratch every single time and reuse everything under them.
The question at the end
Most proposals end by asking for the job. That asks the client to do the deciding. A proposal that ends with a real question about the work asks them to do something much easier: answer it. And once they have answered, you are in a conversation rather than in a list.
The question has to be real. If the posting answers it, you have proved you did not read it. If it is generic, it reads as a closing technique, because it is one. The right question is usually the one you would genuinely need answered before quoting properly.
When not to send one at all
The fastest way to improve a reply rate is to stop sending proposals that were never going to get one. A posting with no budget, no detail and forty applicants inside an hour is not a job you lost. It is a job nobody won.
Bidding on fewer, better-matched jobs costs less and converts higher, and it is the same arithmetic covered in connects and bidding math.
A reply rate is fixed by writing differently, never by writing more
If twenty proposals produced no replies, the twenty-first will not either. Something upstream is filtering you out. Usually it is the opening. Sometimes it is the profile, which is a different problem with a different fix.
The moves, in order
Start at the top. The early ones cost minutes and the later ones compound.
- 01today
Delete your first paragraph
Send the proposal without it. Almost every proposal reads better with its opening removed, because the opening is almost always about you.
- 02today
Open with something only you noticed
One specific thing in their posting that most applicants will have skimmed past. It proves you read it, and nothing else does.
- 03this week
Say what you would do first
Not the whole plan. The first step, named concretely enough that they can picture Monday.
- 04this week
Cut it to what fits on a phone
Most clients triage on a phone. If your proposal needs scrolling before it makes a point, it does not make one.
Mistakes that feel like progress
Opening with your name and your years
It is the one thing already visible beside your proposal. You have spent the only two lines that matter repeating what is on the screen next to them.
Listing every skill you have
A client hiring for one thing reads a list of twelve as evidence that you do none of them for a living.
Asking a question you could have answered
A question that the posting already answers proves you did not read it, which is the exact opposite of what an opening is for.
Promising the moon on price
The clients this attracts are the ones who will hold you to it. The clients you want read it as a reason to keep looking.
What people ask about this
Short enough that the first two lines and the closing question both fit on a phone screen without scrolling. In practice that is usually 120 to 180 words. Length is not what loses proposals, but a long one hides the two things that win them.
One, and only if it is the closest thing you have done to their job. A list of five links reads as a portfolio dump and none of them get opened. One link with a sentence explaining why that particular piece is relevant gets opened often.
Yes, and badly answered screening questions sink otherwise good proposals. They are the one part the client is guaranteed to read, because they chose to ask them.
If the job has enough detail to quote honestly, quote. If it does not, say what it depends on and give a range. A refusal to say anything about money reads as a negotiation tactic, and it costs you the clients who are comparing on more than price.
Read these after
Find out what your profile is costing you
Seven questions, no account. You get a score, the three gaps costing you the most, and what to do about each one.