The client opens your proposal. They read the first sentence. If it sounds like every other proposal they've received today, they're done.
This happens faster than you think. Most clients make a keep/skip decision in under five seconds. Not because they're lazy — because they have forty other proposals and they're looking for any signal that this person actually read the job post.
That's the whole game in the first two sentences: show that you read their job post and that you understood it.
What a client sees when they open proposals
When 40 people apply to a job, the first lines of most proposals look like this:
"I am a highly skilled developer with 7 years of experience..."
"Hello, I am interested in your project and I believe I can help..."
"I am a passionate professional with expertise in..."
"Dear Client, I came across your job posting and would like to apply..."
All of these could have been submitted to any job. None of them reference the specific project. A proposal that opens differently — that shows the client their actual situation was read and understood — immediately stands out.
The proposal structure that gets replies
Opening: their situation, not your credentials
References the job specifically. Establishes relevance immediately. The client knows within one sentence that you read their post.
Middle: why you specifically
One specific past project beats a list of generic skills. A 2-sentence plan shows you've thought about their problem.
Close: a clear next step
Keeps it open without being pushy. Removes friction from the client's next move.
What to leave out
- ✕Your full work history — one relevant example is more convincing than a résumé
- ✕Adjectives about yourself: 'hardworking,' 'dedicated,' 'passionate' — these mean nothing
- ✕'I am available immediately' — signals desperation, not capability
- ✕Long paragraphs — clients skim; white space and short sentences help
- ✕A list of your skills without connecting them to their specific project
Writing this for every job takes time — here's a shortcut
Proposal Engine generates job-specific proposals from a job post URL or pasted description. It includes Generate mode (draft a proposal), Review mode (find weaknesses in one you wrote), and Refine mode (rewrite with specific guidance). Your Claude API key, ~$0.01 per run.
One-time purchase · No subscription · ~$0.01 per proposal
Try Proposal Engine
Generate, Review, or Refine Upwork proposals in under a minute. Job-specific every time.
See how it works →Frequently asked questions
What should I write in an Upwork cover letter?
Open by showing you understood their specific situation — reference something from the job post, not just the job title. Then describe your relevant experience briefly. End with a clear next step or question. Keep it under 200 words. The goal of a cover letter is to get them to reply — not to prove everything you're capable of.
How long should an Upwork cover letter be?
150–250 words is the range that works best for most jobs. Short enough to read in 30 seconds. Long enough to show you understand the project and have relevant experience. Proposals over 400 words are rarely read in full, especially when the client has 50 other applicants.
Should I mention my hourly rate in my Upwork cover letter?
Usually not in the cover letter itself — the rate shows on your profile. If the job post asks for your rate or you're proposing a specific project fee, include it briefly with context. Leading with price before establishing value tends to anchor the client on cost before they've evaluated quality.
How do I start an Upwork cover letter?
Don't start with 'I.' Start by referencing their project specifically — something from the job description that shows you read it. 'You mentioned you need the project done by [date]' or 'I noticed you're building [specific thing]' signals immediately that this isn't a generic proposal. Most proposals start with 'I am a [job title] with X years of experience.' Don't.
What makes an Upwork proposal get rejected?
The most common reasons: generic opening that could apply to any job, no clear connection between your skills and their specific need, too long or too vague, mentions of irrelevant experience, and no clear next step. Clients read dozens of proposals — anything that feels like a template gets skipped.