Why Most Upwork Proposals Get Ignored
Upwork clients reviewing a busy job post are skimming. They open a proposal, read the first two sentences, and decide whether to keep reading or move on. The freelancers who get replies are the ones whose first two sentences made the client think 'this person gets what I need.' The freelancers who get ignored opened with 'Hi, my name is [name] and I have X years of experience in...'
This is not a writing problem. It is a prioritization problem. Clients do not care about you yet. They care about their problem. The proposal that leads with their problem wins the first read. Everything else follows from that.
Section 1 - The Hook (Lines 1 and 2)
The hook is a one or two sentence statement that names the client's specific problem or goal back to them in a way that proves you actually read the post. It is not a greeting. It is not your name. It is a mirror of their situation.
Example: if the post says 'we need someone to fix our blog traffic - we have 40 posts but almost no organic visitors,' your hook could be: 'Your 40 posts are not ranking because most of them are targeting keywords with too much competition and too little search intent match - that is fixable without rewriting everything.' That hook is specific, diagnostic, and immediately useful. It signals that you have context they do not have to explain.
Section 2 - Proof of Understanding (2 to 3 Sentences)
After the hook, briefly show that you understand why the problem exists or what it is costing them. This is not about you - it is about demonstrating that you have dealt with this type of problem before and know what causes it.
Example: 'Most content teams hit this problem at the 30-50 post mark. Posts got published before anyone had a keyword strategy, so you end up with a lot of content competing for terms that established sites already own. The fix is usually a combination of consolidation, redirect strategy, and targeting secondary keywords with less competition.'
Notice that this paragraph does not say 'I have done this for five clients.' It says what the problem actually is. The expertise is implied by the accuracy of the diagnosis.
Section 3 - Relevant Evidence (1 to 2 Sentences or a Short List)
This is where you briefly point to something real - a sample, a link, a relevant past project, a quick audit you ran on their site. Keep it tight. One strong piece of evidence beats three weak ones.
- If you have a portfolio sample that matches their deliverable, link it directly: 'Here is a content audit I ran for a similar SaaS blog - [link to portfolio item].'
- If you ran a quick check on their actual situation before writing the proposal, mention what you found: 'I looked at your top 10 posts in Ahrefs - five of them are cannibalizing each other on the same keyword cluster.'
- If you have no directly relevant work yet, cite a transferable skill: 'I do not have a past Upwork project in this niche yet, but here is a spec audit I built to show you exactly what my process looks like.'
Section 4 - Your Offer (2 to 3 Sentences)
State clearly what you would do for them, approximately how long it would take, and - for fixed-price jobs - what they will have at the end. Be specific enough to show you have thought about the scope, but not so detailed that you are writing a full project plan unpaid.
Example: 'For this project I would start with a full keyword audit of your existing content, identify the 10 posts worth consolidating, and write updated versions for the five highest-priority ones. Turnaround is 10 business days from kickoff. Deliverable is a live doc with the audit plus the five revised posts formatted for your CMS.'
Section 5 - The Next Step (1 Sentence)
End with a single, low-friction ask. Not 'please hire me.' A question, an offer to run a quick analysis, or an invitation to a 15-minute call. Make it easy to say yes to.
Example: 'If you want, share your top five URLs and I will tell you in 24 hours which ones are worth consolidating before we talk scope.' That is a concrete, valuable offer that costs you 30 minutes and costs them nothing.
Length, Tone, and Formatting
Under 200 words for fixed-price jobs under $1,000. Under 300 for complex hourly engagements where scope needs more explanation. No bullet lists in the main body - clients read proposals on mobile and bullets that look clean on desktop turn into fragmented text on a phone screen. Write in prose.
Tone should match the job post. A startup founder writing in casual shorthand does not want a formal proposal. A large company post that reads like an internal HR brief probably expects a more structured response. Match their register.
Proposal length by job type
| Job type | Target word count |
|---|---|
| Small fixed-price (under $500) | 100 to 150 words |
| Mid fixed-price ($500 to $2,000) | 150 to 200 words |
| Hourly or ongoing engagement | 200 to 300 words |
| Complex project (enterprise, $5k+) | 250 to 350 words |
Short, practical drops on proposals, niches, client scripts, and rates. No spam, unsubscribe anytime.
Frequently asked questions
Should I answer the screening questions Upwork clients add to job posts?
Yes, always. Clients who add screening questions use them as a filter. A proposal that skips them signals either that you did not read the post or that you do not care about the details. Answer them directly and concisely - usually one or two sentences each.
How personal should the proposal be? Should I mention the client by name?
Using the client's name or their company name in the opener signals that you actually looked at who posted the job. It is a small thing that costs nothing and reads well. Avoid generic openers like 'Dear Hiring Manager' - they undermine the impression that you treated this as a specific job, not a mass-apply.
Is it worth sending a video proposal on Upwork?
Video proposals are underused and can stand out in competitive categories. Keep them under 90 seconds, record in decent lighting, and use the first 15 seconds to name their problem - same logic as the written hook. Not every client watches them, but the ones who do tend to be the ones already interested.
What if I genuinely do not know enough about their problem to write a specific hook?
Do more research before writing the proposal. Read the full job post twice. Look at the client's past job history to understand what they hire for. If they have a company name or website visible, spend five minutes there. A vague hook is worse than no hook - it signals that you skimmed.
Should I mention my rate in the proposal body?
You already set a bid amount when submitting the proposal, so the client can see your rate. Repeating it in the body text usually adds nothing. The exception is if your rate is significantly different from other bids and you want to contextualize it - in that case a single sentence explaining the scope it covers is fine.
How many proposals should I track before deciding my template is not working?
Give any new proposal structure at least 20 sends before drawing conclusions. Upwork shows you whether clients opened your proposals at all - if fewer than 30% are opening, your title or first line is the problem. If they are opening but not replying, the body is the problem. Fix one variable at a time.
Last reviewed by David Iya on July 27, 2026
