TL;DR
- Most first-line tricks move Upwork reply rate by about half a point or less, and a few backfire.
- Repeating the job title word for word gets 5.5% replies vs the 6.4% average.
- Attachments look like they hurt, but within the same agency the gap disappears (about +0.1 points).
- On dev jobs, mirroring the client's need is the best hook (+0.5); self-intros (−0.4) and insight openers (−0.5) lose.
- The top peers in my case study write letters of about 630 characters; the struggling agency writes 1,130.
Most first-line tricks people argue about move Upwork reply rate by about half a point or less, and a few backfire. I tested the usual Upwork proposal tips on 166,000 proposals that GigRadar agencies sent between June and August.
The questions came from our Skool members: title restating, native greetings, attachments, dev hooks, and one agency stuck at 3.8%.
The method in one table
| What | Value |
|---|---|
| Proposals (outbound bids only, invites excluded) | 166,075 |
| Window | 1 Jun to 20 Aug 2026 |
| Reply | Client opened a chat |
| Average reply rate | 6.4% |
Teams that use a trick are rarely a random sample, so a raw comparison mostly measures who uses the trick. Where it matters, I also compare each team against its own average ("within the same agency").
1. Does restating the job title in line one help?
Almost nobody does it: about 5% of proposals repeat the job title (or 70%+ of its words) in the first sentence. Less than 1% repeat it word for word.
| First sentence | Share | Reply rate |
|---|---|---|
| Repeats the title word for word | 0.6% | 5.5% |
| Paraphrases the title | 4.2% | 6.8% |
| Doesn't restate it | 95.2% | 6.4% |
Word for word does worse (5.5% vs 6.4%), and a paraphrase looks a bit better raw (6.8%). In Sales & Marketing any restating drops replies: 5.4% vs 7.3% without it.
Reply rate when line one restates the job title
GigRadar proposals data, 1 Jun to 20 Aug 2026. Dashed line: 6.4% average reply rate.
All categories
Sales & Marketing
The client wrote the title, so reading it back to them tells them nothing.
2. Does greeting the client in their language help?
We looked at clients in non-English-speaking countries (France, Germany, Spain and Latin America, Brazil, Italy, the Netherlands, the Nordics, Poland). About 8% of proposals to them open with a native greeting ("Bonjour", "Hallo", "Hola").
| Job post written in | Native greeting | Reply rate | Other openers | Reply rate |
|---|---|---|---|---|
| English | 1,037 bids | 6.4% | 11,459 bids | 6.3% |
| The client's language | 56 bids | 8.9% | 576 bids | 5.7% |
When the post is in English, the native greeting does nothing. In posts written in the client's own language it looks better, but 56 bids is far too few to call it.
Match the language of the post, not the flag on the profile. Our earlier study found "Bonjour" below average; on English posts this one shows no difference.
3. Do attachments lift reply rate?
Raw numbers say attachments hurt: 6.0% with one or more vs 6.4% without. Within the same agency, the gap disappears (about +0.1 points).
| Category | Bids with attachments | Raw: with / without | Within the same agency |
|---|---|---|---|
| All | 13,171 | 6.0% / 6.4% | +0.1 pts |
| Web, Mobile & Software Dev | 8,188 | 2.8% / 3.3% | −0.1 pts |
| Sales & Marketing | 2,379 | 5.3% / 7.3% | +0.3 pts |
| Design & Creative | 1,005 | 4.7% / 4.7% | +1.0 pts |
Raw reply rate with vs without attachments
GigRadar proposals data, 1 Jun to 20 Aug 2026. The within-agency effect is in brackets.
This corrects our February finding, when attachments looked like +14.7 points on 132 Sales & Marketing bids. On 2,379 bids from 43 agencies the effect is close to zero.
If you design, a portfolio attachment may add a point. Everyone else: put proof in the letter, where the client reads it.
4. Which hooks work for development jobs?
We sorted 91,500 Web, Mobile and Software Dev proposals by their first sentence (after the greeting).
| Opening move | Share | Reply rate | Within the same agency |
|---|---|---|---|
| Mirror the need ("You need…", "I see your…") | 10% | 3.5% | +0.5 pts |
| Availability ("Ready to start this week") | 2% | 3.9% | +0.3 pts |
| Offer to help ("Happy to help…") | 5% | 3.3% | +0.1 pts |
| Proof ("I recently shipped…") | 7% | 2.6% | 0.0 pts |
| Loom or video offer | 2% | 3.4% | 0.0 pts |
| Question | 7% | 3.8% | −0.2 pts |
| Self-intro ("I'm a senior developer…") | 8% | 2.8% | −0.4 pts |
| Insight ("The real risk here is…") | 3% | 3.9% | −0.5 pts |
| Everything else | 57% | 3.2% | 0.0 pts |
Dev clients reply to about 3 bids in 100. The best hook adds half a point; the worst costs half a point.
Dev hooks: effect on reply rate within the same agency
91,500 Web, Mobile and Software Dev proposals, 1 Jun to 20 Aug 2026. Points of reply rate vs the team's own average.
Mirror the client's need (+0.5, the best hook); self-intros (−0.4) and insight openers (−0.5) lose. The self-intro result matches our earlier study on stack name-drops.
Fix targeting, profile and proof before you polish line one.
5. Case: an email agency with 3.8% replies
An email-marketing agency runs Klaviyo and Omnisend work for e-commerce brands. 267 bids since mid-August, 10 replies, 1 hire, while the peer median gets 6.0% replies.
We compared them with 22 other agencies bidding on email-marketing jobs in the same weeks (50+ bids each).
| This agency | Peer median | Top 5 peers | |
|---|---|---|---|
| Reply rate | 3.8% | 6.0% | 11.6% |
| Cost per reply (Connects at $0.15) | $60 | $41 | |
| Minutes from post to bid | 9 | 8 | 8 |
| Cover letter length (characters) | 1,130 | 634 | 626 |
| Median client lifetime spend | $8,300 | $4,950 | $4,680 |
The case agency vs its peers
Email-marketing jobs, same weeks: the case agency and 22 peers with 50+ bids each.
Reply rate
Cover letter length (characters)
They rank 19th of 23. Speed is fine: 9 minutes from post to bid vs 8 for peers.
Half the letters are the same letter: nearly half carry the same case study line from the agency's own template, and a third have the same five bullets ("Review your existing Klaviyo flows… Conduct A/B tests…"). A client reading 30 bids sees the template.
Proof hides behind a short link and Behance: 30% of bids send the case study through a link shortener. Shortlinks and Behance links both reply below average in our earlier study.
They aim at whales: their clients have spent about 70% more than peers' clients, and big spenders reply less, as our earlier study found.
Their letters run nearly twice as long as the winners': 1,130 characters vs about 630 for the top peers.
The top peers write short letters that read as human: a named person ("Hey! I'm Rachael…"), brands the client may know, a look at the client's own store, and one ask (a 60-second Loom).
Upwork proposal tips that held up: a 5-minute check
Interactive checklist
Run it on your last three proposals. Tick each check once your letter passes it.
| OK | Check | Fix if it fails |
|---|---|---|
| Does line one repeat the job title? | Replace it with the client's problem in your words | |
| Would this letter fit another job unchanged? | Rewrite the first two lines for this client | |
| Is your proof behind a shortlink, Behance or Calendly? | Put the number in the letter; link Dropbox, Notion or Loom | |
| Are most of your targets big spenders? | Mix in clients like the top peers' (median lifetime spend about $4,700) |
0 of 4 checks passed
Want to see how GigRadar bids for your agency?
Book a demo and I'll walk you through how GigRadar runs Upwork bidding for agencies. Your agency invites our Upwork Business Manager account, and proposals go out from it under my team's supervision.
Book a demo with GigRadarMethod and data
Every number here comes from GigRadar proposals data: outbound proposals sent 1 June to 20 August 2026, with invites excluded. A reply means the client opened a chat, and replies still arriving can pull the most recent weeks slightly low.
Language detection and the hook groups are rule-based, which is why "everything else" is 57% of dev bids. The case agency is measured from 17 August to 20 October 2026, so its reply rate may still rise slightly, and its peers use the same window.
Where I mention our earlier study, I mean an older GigRadar dataset I checked these results against. Title restating and native greetings by post language had no earlier check, so those two results are new.
