Should my proposal always be under 150 words?

For most jobs, yes. The exception is complex, high-value projects where the client has signaled they want a detailed response - look for clues in the job posting like 'please describe your process' or 'explain how you would approach this.' In that case, 200-250 words is acceptable. But the default is short.

Can I use the same proposal for multiple jobs?

The structure stays the same; the proof and offer should change for each job. A client can tell when a proposal was written for someone else. At minimum, change the first sentence to name their specific problem and pick the proof point most relevant to their situation.

Should I include my hourly rate or a fixed price?

Either works. Fixed price anchors the conversation and filters out budget mismatches early. Hourly is better when the scope is genuinely unclear. Whichever you choose, include a number - 'I'll need to see more details to quote' is weaker than a range or a specific price.

What if I do not have a proof point yet?

Describe your process and how you will measure success instead. 'I will start with a full audit of your checkout flow, document the top 3 drop-off points, and fix them in order of impact - you'll see the change in your analytics within a week' is a credible offer even without a past result.

Do I need to include a cover letter question answer?

If the client asked a screening question, answer it briefly at the start of your proposal before the hook. Keep it one sentence. Then lead into the 5-section structure. Ignoring the screening question is the fastest way to get filtered out.

How many proposals should I send per week?

The UIC curriculum recommends treating proposal sending as a consistent daily habit rather than a burst-and-wait cycle. A realistic target for someone building their Upwork business is 3-7 tailored proposals per day. Volume and quality together are what move the needle - neither alone is enough.

Upwork Income Club

Join the club

Back to the shop

Upwork Proposal Builder

Build a tailored, under-150-word proposal that gets replies.

$29 Free
20 sec
No signup

Enter the client's job title and the problem they want solved

Add your relevant proof and your offer or price anchor

Copy the finished proposal and paste it into Upwork

You get: A tailored, under-150-word Upwork proposal ready to paste and send.

About this job

Client's job title (what they're hiring for)Their problem (what they actually want solved)

Your angle

Your one relevant proof point (a real result, not a claim)Your offer or price anchor (what you'll do + what it costs)Call to action (how you want them to respond)

Your proposal

116 words (good length)

I noticed you're looking for help with your checkout flow has a high drop-off rate and you need someone to diagnose and fix it fast.

I specialize in react developer and have helped clients solve exactly this.

Specifically: I rebuilt a checkout flow for an e-commerce client last quarter - conversion rate went up 18% after fixing two broken async steps.

Here's what I'd do for you: audit your current flow, identify the top 2-3 friction points, and deliver a fix with a summary of what I changed and why - fixed price $350.

I'm open to a quick 15-minute call this week if you'd like to talk through the details. Happy to answer any questions.

5-section structure used

1. Hook - open on their problem, not on yourself

2. Why you - your relevant specialization

3. One proof - a real result, not a generic claim

4. Clear offer - what you will do and what it costs

5. Next step - a low-friction ask + friendly close

Paste directly into Upwork's proposal field - edit the proof to match each job.

Why most Upwork proposals get ignored

The average Upwork client receives 20-50 proposals on a well-posted job. Most of those proposals open with 'Hi, my name is [name] and I am an experienced [title] with [X] years of experience.' The client has read that sentence 40 times before they reach yours. It does not give them a reason to keep reading. The proposals that get replies open differently: they name the client's specific problem in the first sentence, they show one concrete result that proves the freelancer can solve it, they state a clear offer, and they end with a simple next step. Under 150 words. Nothing wasted.

Short proposals win for a structural reason: clients skim. A client reviewing 30 proposals is not reading each one in full. They are pattern-matching for signals. A long proposal buries the signals. A short, direct proposal puts them in the first three sentences. The builder above is structured to keep you under 150 words by design, because that is the ceiling where the signal-to-noise ratio stays high.

What goes in each section

Hook - open on their problem, not on yourself. The client cares about their problem, not your background. 'I noticed you're struggling with X' is more powerful than 'Hi, I'm a developer with 5 years of experience.'
Why you - one sentence that connects your specialization to their specific situation. Not a resume, not a list of skills - one relevant connection.
Proof - one real result, not a vague claim. 'I rebuilt a checkout flow and conversion went up 18%' beats 'I have extensive experience with conversion optimization' every time. Specifics are credible; generics are not.
Offer - what you will do and what it costs. Anchoring a price in the proposal pre-qualifies the conversation. Clients who reply knowing your price are more likely to hire.
Next step - a low-friction ask followed by 'happy to answer any questions.' The ask should be easy to say yes to: a 15-minute call, a quick question, a small paid discovery. 'Happy to answer any questions' signals you are not pushy.

The proof section is where most proposals fail

Generic claims ('I am passionate about quality') are invisible to clients. Specific results ('the last three clients I worked with saw faster load times, a cleaner checkout, and fewer support tickets') are scannable and memorable. If you do not have a result to cite yet, describe exactly what you will do and how you will measure whether it worked. Process credibility is better than a vague passion claim.

How many proposals to send

The UIC curriculum is direct about this: getting your first Upwork job is a numbers-and-quality game. You will likely need to send 30-100 well-crafted proposals over several weeks before landing a first contract. Do not send 100 identical proposals - customize the proof and offer for each job. But do not send 3 proposals and conclude the platform does not work. Volume matters, and the builder above is designed to make each proposal faster to write so you can send more of them without sacrificing quality.

Editing the output before you send

The builder gives you a starting draft. Before you send it, scan the job posting again and check: does your proof point actually match what they need? Is your offer specific enough for this scope? Is the call to action appropriate for the project size - a $100 project does not need a 60-minute discovery call, but a $5,000 project might. The 30 seconds you spend customizing each proposal is the difference between a template the client recognizes and a proposal that reads like you actually read their job post.

What to do when you get a reply

A reply is not a hire - it is an opening. The goal of the proposal is to get them to respond with a question or to book a call. When they do, your job is to listen first, confirm you understand their situation, and then scope the work clearly before you discuss price further. The UIC curriculum covers the full call-to-contract flow in Stage 9: Win The Call, Bank The Money. The proposal is the front door.

Frequently asked questions

Should my proposal always be under 150 words?
For most jobs, yes. The exception is complex, high-value projects where the client has signaled they want a detailed response - look for clues in the job posting like 'please describe your process' or 'explain how you would approach this.' In that case, 200-250 words is acceptable. But the default is short.
Can I use the same proposal for multiple jobs?
The structure stays the same; the proof and offer should change for each job. A client can tell when a proposal was written for someone else. At minimum, change the first sentence to name their specific problem and pick the proof point most relevant to their situation.
Should I include my hourly rate or a fixed price?
Either works. Fixed price anchors the conversation and filters out budget mismatches early. Hourly is better when the scope is genuinely unclear. Whichever you choose, include a number - 'I'll need to see more details to quote' is weaker than a range or a specific price.
What if I do not have a proof point yet?
Describe your process and how you will measure success instead. 'I will start with a full audit of your checkout flow, document the top 3 drop-off points, and fix them in order of impact - you'll see the change in your analytics within a week' is a credible offer even without a past result.
Do I need to include a cover letter question answer?
If the client asked a screening question, answer it briefly at the start of your proposal before the hook. Keep it one sentence. Then lead into the 5-section structure. Ignoring the screening question is the fastest way to get filtered out.
How many proposals should I send per week?
The UIC curriculum recommends treating proposal sending as a consistent daily habit rather than a burst-and-wait cycle. A realistic target for someone building their Upwork business is 3-7 tailored proposals per day. Volume and quality together are what move the needle - neither alone is enough.

Liked this tool? The club is the next step.

Join Upwork Income Club for $9/month. 650+ lessons, weekly updates, and the workflows behind every tool on this site.

No experience needed
Cancel anytime
Updated weekly

Join the club All tools