A client posts a job and gets twenty proposals in an hour. They're skimming on their phone, and they decide in a few seconds whether each one is worth a real read. Most lose them at the first line.
You don't need to write more. You need to write in an order that answers the client's questions in the sequence they ask them: do you get my problem, can you actually do this, and what happens next. That's the whole structure.
The 5-part structure that gets replies
1. Hook (the first line or two)
This is almost all the client sees before deciding to open your proposal, so it has to be specific to them. Skip "Dear Hiring Manager." Lead with their problem or a detail from the post.
Example: "Your checkout is probably losing sales on mobile, and it's usually one small fix."
2. Show you understand the job
Say back what they need in one or two sentences, in your own words. It proves you read the post and aren't mass-applying.
Example: "You need the dashboard loading faster and the new API integrated by mid-August."
3. Proof you can do it
One relevant result, ideally with a number. Not your whole history, one concrete thing that matches their job.
Example: "I cut load time on a similar React dashboard from 4 seconds to under 1."
4. One smart question or a first step
Ask something specific about their project, or lay out the first move. It shows you're already thinking about the work, not just the win.
Example: "Are you using server-side rendering on this yet? That changes where I'd start."
5. A clear call to action
End with one easy thing to say yes to. Not "let me know if you have any questions."
Example: "If it's useful, I can send a short plan and a quick Loom. What time zone are you in?"
A template you can adapt
Fill in the brackets with details from the actual job post. Keep it to two or three short paragraphs.
You need [restate their goal and main constraints in your own words].
I recently [one relevant project] where [specific result or number]. For your project, I'd start by [one concrete first step or a smart question].
If that's useful, I can send [a sample / a short plan / a quick Loom]. What time zone are you in?
Before and after
Same freelancer, same job. The only thing that changed is the structure.
The second one is shorter, and it never once mentions how motivated or reliable the freelancer is. It doesn't need to. It shows it.
Check your proposal before you send it
Our free Proposal Checker scores your draft against the six things clients notice first, including your opening line and preview. No signup, no card.
Check my proposal free →Keep it short
Most winning proposals are under 150 words. The client is skimming, and every extra sentence is another chance to lose them. If a line doesn't earn its place, cut it. Say less, and say it about them.
Common questions
What should the first line of an Upwork proposal say? Something specific to their job, not "Dear Hiring Manager." Lead with their problem or a detail from the post, because the first line or two is often all the client sees in the preview before deciding whether to keep reading.
Should I put my rates or full portfolio in the proposal? No. The client can already see your profile and rates. Use the space to show you understand their job and can solve it. Offer one relevant example, not your whole history.
How should I end an Upwork proposal? With one easy next step, not "let me know if you have any questions." Ask a specific question about their project, or offer to send a short plan or sample. Give them something simple to say yes to.
Related reading: Why your Upwork proposals aren't getting replies and How to make your proposals sound like you.
Try AuthorBid AI free for 7 days
Get a first draft built from the real job post, already following this structure, then make it sound like you and send. Fast, and still yours.
Start Free Trial →