I used to write proposals like everyone else. "Hi, I'm Mateusz, I have X years of experience, I'm proficient in Y and Z, please consider me for your project." You know what happened? Nothing. Crickets. My response rate was around 10%.
Then I changed everything. I stopped writing about myself and started writing about their problem. My response rate jumped to 50%. And after they respond, my hire rate is about 85%.
Here's exactly what changed — and the three proposal templates I use today.
The #1 mistake most freelancers make
Go to any job posting on Upwork and read the proposals. They all start the same way:
Hi, I'm [name]. I have [X] years of experience in [tech]. I've worked on [irrelevant project]. I can do this. Please hire me.
Clients skip these. They get 30-50 proposals per job. They're not reading your resume — they're looking for someone who understands their problem.
The rule: talk about their problem, not your experience. Show them you read the brief. Prove you can think, not just code.
Proposal 1: The Diagnosis
Best for: medium to large projects where the client has described a specific problem.
The idea is simple: diagnose their problem better than they described it. Show them you understand what they actually need, not just what they posted.
Template:
I read through your posting and here's what I see:
[Specific problem they described, rephrased in technical terms]
The real challenge here isn't [obvious thing] — it's [deeper issue they probably haven't considered]. Most developers would [common wrong approach], but that creates [specific problem].
Here's how I'd approach it:
- [Step 1 that shows you know what you're talking about]
- [Step 2]
- [Step 3]
I can start this week. Want to hop on a quick call to discuss?
Why this works: you're not selling — you're diagnosing. Clients want someone who understands the problem, not someone who just says "I can do it."
Proposal 2: The Quick Win
Best for: small jobs, bug fixes, quick tasks under $500.
Short, direct, no fluff. For small jobs, the client wants to know you can start now and finish fast.
Template:
I can fix this. Here's what's causing [their specific issue]: [brief technical explanation].
I've dealt with this before — it usually takes about [realistic timeframe]. I can start today.
[One relevant project or proof, one line max]
That's it. Three sentences. For a $200 job, no client wants to read a page about your passion for development. They want it fixed. Show them you know the fix and you can start now.
Proposal 3: The Honest Take
Best for: complex projects where the client's scope is vague or overambitious.
This one is counterintuitive: you tell them what they don't need. It builds massive trust.
Template:
I read your posting carefully. A few thoughts:
You mentioned [feature X] — based on what you described, you probably don't need that. What you actually need is [simpler/better alternative], which costs less and works better.
The scope you described could be done in two ways:
- Option A: [What they asked for] — [price range], [timeline]
- Option B: [What I'd actually recommend] — [lower price range], [faster timeline]
Option B gets you to market faster. You can always add Option A features later once users start giving feedback.
Happy to break down the specifics on a call.
Why this works: you're saving them money. That's the fastest way to build trust. A client who sees you're willing to talk them out of spending more will hire you for the simpler version — and then come back for the bigger version later.
The subject line trick
Upwork lets you write a custom first line in your proposal. Most people waste it on "Hi" or "Dear client."
Instead, reference something specific from their posting that proves you actually read it:
- "Saw your Figma link — the checkout flow has a few issues I'd fix differently..."
- "Your current site is on WordPress, which explains the load time issue..."
- "The API integration with Stripe is the tricky part here, not the frontend..."
One specific detail. That's all it takes to stand out from 40 copy-paste proposals.
Pricing psychology
Don't be the cheapest. Don't be the most expensive. Be the one who understands the problem best.
When you write a proposal that shows you get it, price becomes secondary. The client has already decided you're the right person — now they're just checking if they can afford you.
Price fairly, explain what's included, and don't apologize for your rates. If you're confident in your proposal, be confident in your price.
My actual stats
- 200+ proposals sent over the past two years
- 40% average response rate (up from 10% when I started)
- 85% hire rate after a client responds
- Average project value: $2,000-$5,000
The proposals above aren't theory. They're what I send every day. The only "secret" is that most freelancers are too lazy to read the job posting carefully and respond to the actual problem. Do that, and you're already in the top 20%.
Want to work with someone who communicates clearly?
I build websites, mobile apps, and full platforms — and I apply the same clarity to every client conversation that I do to every proposal. Let's talk.