The Truth About Winning Upwork Proposals (Fix It Now)

Michael Elliott, a top 1% Upwork freelancer who's sent over 5,000 proposals and earned $500k+, breaks down why volume matters less than win rate. Calculate yours by dividing hires by proposals sent: below 10% means fix your proposals first, above 20% means send more. The real edge is filtering for clients with $10k+ spend and 70%+ hire rates, then opening each proposal with one sentence about something specific in their post.
Chapters
There are 2 camps on Upwork, and both of them are wrong. One says it's a numbers game— send more, win more, keep grinding— but the other says send fewer, better proposals, and quality wins. Neither is the answer, because volume has never been the variable. Volume is a multiplier. It multiplies whatever your win rate already is. And if your win rate is bad, sending more just gets you broke faster. So the real question isn't how many to send, it's what's broken in the ones that you're already sending. And I'm not going to tell you to use their first name, or ask a question at the end, or it under 150 words. You've heard all of that. It's also exactly what every AI-written proposal in that inbox is already doing. There are only 2 things it can be: you're pitching clients who are never going to hire anybody, or you're sending something a machine wrote, which means that 30 other people sent exactly the same thing that morning. If you fix those 2 and volume stops being your enemy, the person sending 25 good proposals a week beats both camps. Quick context, and the second half matters more. 5,000 proposals sent, over half a million earned, top 1% on Upwork. But I also hire through Upwork. I open the job post that I wrote and read the 40 proposals that came in. So I sit in the inbox too. And from that seat, I watch the proposals get better written and completely interchangeable at the same time. Everybody's arguing about how many. The thing that actually broke is sameness. Stay to the end because the thing that used to make you competitive here has been deleted and I'll show you what replaced it. 1, the arithmetic that nobody finishes. You've seen the maths used to sell you on cutting volume. 40 proposals a week at a 5% win rate is 2 hires. 16 at 25% is 4 hires. Fewer applications, double the outcome. Everybody nods and it's true, but it stops one line too early and that missing line, that's the whole video. Because 40 proposals at a 25% rate Is 10 hires. Nobody finishes the sum because it ruins a good story. Volume isn't the opposite of quality. It's a lever that sits on top of it. At 5%, every extra proposal is you paying Connex to lose. At 25%, halving your volume throws away the money that you'd already earned. Sending fewer proposals doesn't fix anything. It just makes you fail more slowly and feel more disciplined about it. So go and open your history right now. Count last month's proposals. Count the hires. Work out the percentage. Most people have never once put those 2 numbers next to each other, and until you do, you're guessing about which lever you're even pulling. Under 10%, do not send another proposal until you've fixed what's in them. Above 20%, your problem isn't quality, it's that you're not sending enough. So let's fix the rate. 2 things break it, and the first has nothing to do with your writing. 2, you're pitching people who don't hire. Open any job post and look at the block under the client's name. Payment verified, total spend, and their hire rate. Those numbers are on every single post, and most freelancers, they scroll straight past them to get to the description. A client who's posted 20 jobs and hired twice doesn't have a problem a better proposal can fix. That's someone who collects quotes, and your win rate against them is near zero, no matter what you write. And this one catches good people because it isn't a discipline failure. Those posts are often the most appealing things in the feed. Big scope, interesting brief, barely any proposals on it. There's a reason that it's uncontested. Everybody experienced already checked the numbers and moved on. What I want is real money spent, ideally $10,000 or more, and a hire rate that's above 70%. That's my threshold, not a rule, but it's the one that I hold. And you read how the post is written— 3 vague sentences means they're thinking out loud and they're not ready. 3 detailed paragraphs where they've explained the problem, described what success actually looks like, and told you what they don't want. That's somebody that's already done the thinking. The quality of the post is the quality of the working relationship, and you get to see it for free before you commit anything. So that's who you're sending to. Now the bigger one, and this is what changed most in 2 years. 3, the machine can only read what everybody else read. My inbox this week, 40 proposals. 35 were well written. Correct grammar, tidy structure, 3 neat bullets, a confident closing line. 2 years ago, half of them would have had typos, and I cannot tell them apart. They open by restating my job post back to me. They say they came across the post and were immediately excited. They say they'd love to help me achieve my goals. They tell me that they're detail-oriented, and you already know what I think. That sentence is worth. Same rhythm, same length, same 3 bullets over and over. And the mechanical reason is simple. If you paste the job post into a model and ask for a proposal, the only information it has is that job post, which is the exact information that every other applicant has pasted in. So the output, it converges. Everybody gets a competent, plausible average proposal because that's the same input produces every time. You're not saving time. You're mass-producing the thing. 30 other people also mass-produced. And this is where it gets really expensive. Writing well used to be the differentiator. Now it's free and everybody's proposals are competent, which means competent is worth nothing. The only thing left with value is the part a model physically cannot access— what you noticed that isn't written down, what you've actually done before, the question that you'd ask that somebody else who's not done this work would think to ask. I'm not anti-AI. I use it every day and I make content about it, but there's a line and it matters. Use it where the input is yours. Give it your rough opening and ask it to cut the waffle. Give it your case study and ask it to tighten the numbers. Give it your draft and ask what a client would still be unsure about. All of that, it works because you brought something that it didn't have. What doesn't work is handing it the job post and asking for a proposal, because then the only ingredient is the one that everybody else used too. Do not let it write your opening line. That sentence, that's your entire asset. 4 is how to be specific and fast at the same time. The reason people mass-produce is that being specific feels slow. 40 minutes for a proposal and nobody's doing 20 a week. So here's how you get it to 8 minutes without going generic. Split the proposal in 2. The part that changes and the part that never does. The part that never changes is your proof. Your results, your numbers, your 2 or 3 case examples. You're close. Write those once properly this week. Get them good. Feel free to test them as you go, but you'll get them ready and use them for the next 2 years. The part that changes is one thing: the opening. One sentence that could be only sent to this client about the thing that you noticed in their post that they didn't even spell out. That's the whole bespoke element of this. Everything under it is assembly. And I got this wrong in the other direction. Which is why I'm that confident about it. I templated the whole thing, opening line included, because it felt efficient and my volume skyrocketed. But my response rate halved. So I was doing double the work for the same number of projects and calling it a system. Every proposal I sent was technically fine. The order matters too. Shortlist first, then write. 15 minutes at the start of the session picking your best few, then open a blank proposal. Do it the other way around and you'll talk yourself into whatever you've already spent 20 minutes on. Because nobody deletes their own draft. 15-minute shortlisting, 8 minutes each, that's 25 real proposals a week, not 12. And that's the version where volume is finally working for you instead of against you. Track 4 numbers while you do it: sent, responses, interviews, and hires. If you're not tracking, you can't tell which of these 2 problems you've actually got. 5. What's actually scarce? Now, this is the shift underneath everything we've discussed. The bottleneck used to be the writing. Write clearly, confidently, and you were ahead of most of the platform. That's how I got started. That bottleneck is now gone. It got deleted. Anybody can produce a clean, professional, well-structured proposal in 6 seconds, which means the floor came up and the ceiling came down at the same time. Everybody is now competent and nobody's distinctive. So the scarce thing— the goalposts moved. It isn't writing anymore. It's Having read the post properly and having actually done the work before. Neither of those 2 things can be generated. That is the entire opportunity, and it's bigger than it ever has been because most of your competition has stopped doing both. Volume was never the problem. Sameness was, and sameness is now the default setting for anybody who isn't paying attention. Now the test, and it's uncomfortable. Take the last 10 proposals that you sent How many of them could have been sent to a completely different client unchanged and they'd have still made sense? Drop that number in the comments, 0 to 10, and be honest because mine would have probably been a 5, maybe a 6 for my first year on this platform, which is exactly why my win rate looked the way it did. Guys, you simply cannot out-send sameness, and every week you try costs you connects and the jobs that you'd have won if you'd been paying attention. Attention. Everyone else in that inbox sent a proposal this morning. Almost none of them sent one that only they could have written. The framework, the client filters, the proof blocks, the tracker is all in one doc and it's linked below. And the deep version of the opening line, the one thing that you can't automate, is on screen now. Go and count your last 10, comment it below. That's the homework.










