How I Write Upwork Proposals That Get Replies

My first fifty proposals got two replies. My last fifty got thirty-one. I keep a simple spreadsheet of every proposal I send on Upwork, and looking back at those early rows is a little painful. I wrote long, polite letters about myself, my skills, my tools, my design philosophy and my availability. Clients ignored nearly all of them, and for months I assumed the problem was my portfolio or my rate.

The difference wasn’t talent. It was who the proposal was about. When I finally rewrote my approach, I used the same portfolio, charged a higher rate and got fifteen times the response. Here is exactly what changed, with the outline I still use today.

Start with their problem

Repeat their goal in your own words. It proves you read the post — most freelancers don’t. A client posting a job for a new restaurant website might receive forty proposals within an hour. Most of them start with “Hi, I am a web designer with eight years of experience.” The client has read that sentence thirty times by lunch.

Now imagine one proposal that starts: “It sounds like your current site makes it hard for people to find the menu on a phone, and you are losing reservations to the place across the street.” That client keeps reading. They feel understood, which is the first thing anyone wants from a person they might hire.

To do this well, I read every job post twice. The first time, I read it normally. The second time, I underline the sentences that reveal feelings: frustration, worry, excitement. “Our last developer disappeared” tells me more than the list of required skills. A client who was burned before needs to hear about reliability and communication far more than about animation libraries.

Three sentences about them, one about me

That ratio has become my rule. My opening paragraph restates their goal, names the problem underneath it and shows I understand why it matters to their business. Only after that do I write a single sentence about who I am. If a proposal spends more words on me than on them, I rewrite it.

A quick before and after

Here is how one of my old openings read: “Hello, I am an experienced web designer skilled in responsive layouts, animation and online stores, and I would love to work on your project.” Every word is true, and every word is forgettable. It could have been sent to any client on the platform.

Here is how I would open the same proposal today: “You want your bike shop’s website to book tune-ups online so your mechanics stop losing time on the phone, especially in spring when the schedule fills up.” Same designer, same skills. The second version simply proves I read the post and thought about the shop owner’s real week.

A proposal is the first sample of how you communicate.

Ava

One relevant example

One project that looks like theirs beats a link to my whole portfolio. Clients rarely have time to browse twenty case studies. They want to know one thing: has this person solved something like my problem before? So I pick the single closest project and explain it in two sentences.

For a dental clinic, I might mention a booking site I built for a physical therapy office and the fact that online appointments rose after launch. For a bakery, I point to Bloom & Barley and their pickup ordering. If I do not have a close match, I choose the project that best shows the quality they care about most, such as speed, clarity or a smooth checkout, and say why I chose it.

Specific is always better than impressive. A modest project in the same industry builds more trust than a flashy one in an unrelated field. The client should be able to picture their own site in the example.

Ask one good question

Every proposal I send includes exactly one question about their business. Not about the budget or the deadline, which are usually in the post, but about the work itself. Who visits the site most often? What do customers call to ask about? What does success look like six months after launch?

A thoughtful question does two jobs. It shows I am already thinking about their project like a partner, and it gives them an easy reason to reply. Many of my best contracts started with a client answering that question in a long, detailed message. By the time we got on a call, we were already working together in spirit.

My proposal outline

Here is the structure I use for nearly every proposal. It fits comfortably on a phone screen, which matters because many clients review applicants on the go.

• Their goal in one line
• One similar project
• One question about their business
• A clear next step

The next step is simple and specific: “If this sounds like a fit, I can share a short plan for the first two weeks,” or “I am free for a fifteen-minute call on Tuesday or Wednesday afternoon.” A vague “Let me know” leaves the client to do the work of deciding what happens next. A clear next step makes saying yes easy.

What I removed

1. Long lists of tools and software I know
2. Generic praise like “I am hardworking and detail-oriented”
3. Apologies for being new or for my rate
4. Copied paragraphs from previous proposals
5. Attachments the client did not ask for

Each of those felt important when I was starting out. None of them helped. Cutting them made my proposals shorter, warmer and far easier to read.

Follow up once, kindly

If a client views my proposal but does not reply within a few days, I send one short follow-up message, never more. I usually add a small, useful idea, such as a note about their current site’s mobile menu or a suggestion for their contact page. It reminds them I exist without sounding needy, and it gives them something of value whether or not they hire me. A surprising number of contracts started with that second message.

Choosing where to apply

Better proposals helped, but so did sending fewer of them. I stopped applying to every job that matched my skills and started applying only to posts where I could genuinely picture the finished project. A clear description, a reasonable budget and a client history of fair reviews became my filters.

Fewer proposals meant I had time to make each one excellent. I would rather send five careful proposals in a week than twenty-five rushed ones. The math works out better, and so does my energy.

Key takeaway: a winning proposal is not a résumé. It is a short, thoughtful reply to one specific person about one specific problem.

Write the proposal you would want to read

Put yourself in the client’s chair. They have a business to run, a problem that has been bothering them for months and a stack of nearly identical messages from strangers. The proposal that stands out is the one that feels like it was written only for them, by someone who listened.

That is all I changed. Same skills, same portfolio, same freelancer. I simply stopped talking about myself first. If your replies have dried up, try my outline on your next five proposals and track the results. I suspect your spreadsheet will start to look a lot more like mine.