How to write a freelance proposal that wins the work

Most freelance proposals look the same: a greeting, a list of skills, a link to a portfolio and "I am the perfect fit for this job". Clients read dozens of them and remember none.

A winning proposal is different. It shows that you understand the client's problem, explains how you would solve it, proves you have done it before and makes the next step easy. Here is how to write one.

Before you write: qualify the opportunity

Not every opportunity deserves a proposal. Ask:

• Is the scope clear enough to propose something concrete?
• Does the budget match your rate?
• Is this the kind of work you want more of?
• Is the client responsive and serious?

Spending an hour on a great proposal for the right client beats sending ten generic ones.

The structure

1. Open with their problem, not yourself

Start by showing you understand what they need, in your own words:

"You need your booking app live on iOS and Android by March, so clinics can stop taking bookings by phone. The web app and API exist, and designs for the core flow are ready."

This one paragraph proves you read the brief, which immediately sets you apart.

2. Add an insight

Show that you have thought about the problem:

"The trickiest part will be handling appointment changes when patients are offline. I would design for that from day one rather than adding it later."

One sharp observation is worth more than a page of generic skills.

3. Describe your approach

Outline how you would tackle the work, in three to five steps:

1. A short discovery call to confirm priorities and constraints
2. Set up the project, CI and app store accounts
3. Build the core booking flow, with a demo every week
4. Testing on real devices with a few clinics
5. Launch and two weeks of post-launch support

Clients want to see a plan, not just enthusiasm.

4. Prove it

Link to one or two projects that are directly relevant, with a sentence each on the result:

"I built a similar booking app for a physiotherapy chain: 10,000 bookings in the first three months, 4.8 stars on both stores."

Relevant proof beats a long portfolio.

5. Timeline and price

Be clear and confident:

"I estimate 10 to 12 weeks at 30 to 35 hours a week. My rate is $70 per hour, so the estimated total is $21,000 to $29,000. I can start on the 15th."

Ranges are fine and honest. Explain what could make it shorter or longer.

6. A clear next step

End with a simple call to action:

"Would a 20-minute call this week work to go through the scope? Here is my calendar link."

Keep it short

Most winning proposals are under 300 words. Use short paragraphs and lists. If the client wants more detail, they will ask on the call.

Personalize, every time

Templates are useful for structure, but the first paragraph and the insight must be written for each client. Mention their product, their users or something specific from their brief. Clients can spot copy-and-paste instantly.

Respond quickly

Speed matters. Clients often start conversations with the first few strong candidates. A good proposal sent within a day beats a perfect one sent next week.

Follow up once

If you do not hear back within a few days, send one short follow-up:

"Hi Sam, just checking whether you had a chance to look at my proposal for the booking app. Happy to answer any questions or adjust the approach."

After that, move on.

Common mistakes

• Talking only about yourself
• Listing every skill you have
• Generic portfolios with no explanation
• Avoiding the price question
• No clear next step
• Spelling mistakes in the client's name or company

Learn from every proposal

Keep a simple log of proposals: client, type of work, price, outcome. After 10 or 20, patterns appear: which kinds of clients say yes, which price points work and which openings get replies.

Skip the bidding

On HireCurated, you do not need to write proposals for every opportunity. We match you with clients based on your vetted profile. Apply here.