Picture a client who posts a job and gets 60 proposals within a few hours. Most begin with "Dear Sir, I am a hardworking professional" and end with a price. The client reads the first two lines of each, if that. Your proposal has to earn the rest of the reading in those two lines.
This guide shows you how to write proposals that get read and answered. It won't promise you'll win work. Competition is real, many applicants are experienced, and even good freelancers hear back from only a share of the jobs they apply to. What you can control is how clearly you show that you understood the job.
What a client is actually looking for
A client with a problem wants three things quickly: proof you read the post, proof you can do it, and a sense that working with you will be easy. Everything in your proposal should serve one of those.
They are also scanning for risk. Will this person disappear? Will they misunderstand the brief? Will we spend a week on back-and-forth? A short, specific, well-written message answers those fears better than a long list of your qualities.
The five-part structure
You can write a strong proposal in 120 to 200 words using this order.
- A first line about their project. Mention something specific from the post: the product, the audience, the problem. This is what shows in the preview, so don't waste it on a greeting.
- Your relevant proof. One or two sentences with the closest example of past work. A link to a sample beats an adjective.
- Your approach. Two or three lines on how you'd handle it, or what you'd do first.
- One good question. It shows you've thought about the job and gives them a reason to reply.
- A clear next step. For example, offering to start with a short call or a small paid first piece.
A before-and-after example
Here is a hypothetical job: a small online skincare shop wants five product descriptions and a welcome email.
Weak version: "Hello, I saw your job. I am an expert writer with many years of experience and I can deliver quality work on time. Please hire me. My rate is negotiable."
Stronger version: "Your post mentions customers with sensitive skin, so I'd keep the descriptions free of vague claims and focus on ingredients and how the product feels to use. I've written similar product copy for a candle brand (sample here: [link]). I'd draft one description first so you can check the tone before I do the other four. Quick question: do you want a warm, chatty voice or a clean, clinical one? Happy to send the first draft within two days of your reply."
The second one is about the client, shows a sample, and asks something they can answer in five seconds. That's the pattern to copy.
Handling "no experience" honestly
If you're new, don't pretend. Build two or three samples that match the job type, ideally self-made projects, and link to them. Our guide on building a freelance portfolio with no experience walks through how.
In the proposal, you can say: "I'm newer to freelancing, so I've prepared a sample on a similar topic for you." That is honest and often more persuasive than a vague claim of years of experience.
Talking about price without underselling
Check whether the platform asks for a price up front. If it does, give a specific number or range rather than "negotiable." Vague pricing looks unsure. If you haven't set your rates, read how to price your freelance services in dollars first.
Avoid being the cheapest on purpose. Very low bids attract clients who haggle and expect endless changes. Instead, define what the price covers: number of revisions, word count, delivery time. Clear scope protects you and reassures them.
Mistakes that get proposals ignored
- Copy-pasting one message everywhere. Clients can tell. Keep a template for structure, but rewrite the first line and the question every time.
- Starting with your life story. Power cuts, school history and "I really need this job" don't help them decide. Keep the focus on their problem.
- Ignoring instructions. Some posts ask for a keyword, a specific sample, or a certain format in the reply. Skipping this is often an automatic rejection.
- Typos and long blocks of text. For writing and admin jobs, errors are the proof you're not right for it. Read it aloud before sending.
- Applying to everything. Sending 50 weak proposals usually works worse than 10 careful ones.
- Moving off-platform too early. If a "client" quickly pushes you to WhatsApp, asks for money, or sends a suspicious file or link, stop. See our guide on spotting fake remote job offers if you're unsure.
Adjusting for different situations
Platform job boards
Speed matters because early proposals tend to get seen first, but not at the cost of quality. Keep a bank of samples, then spend five to ten minutes customising each message. Check the platform's own site for how its bidding or credits work, since these rules change.
Cold emails to businesses
Here nobody asked for help, so be shorter still and point out one concrete observation, such as a typo on their website or a missing page. Offer something small and specific. Many won't answer, so expect a low reply rate and keep going without taking it personally.
Time zones and connectivity
Tell the client your working hours in their time zone, and say how you'll handle outages, for example by checking messages at set times and using a backup data plan. Clients value reliability, and a short, calm line on this answers a worry they may not voice.
A quick pre-send checklist
- Does my first line mention something only this job has?
- Have I linked one relevant sample?
- Did I follow every instruction in the post?
- Is there one clear question?
- Is my price or range clear, with what it includes?
- Is it under about 200 words?
Track what works
Keep a simple sheet with the date, job type, what you wrote, and whether you got a reply. After 20 proposals, look for patterns: which samples got answers, which openings were ignored. That small habit improves your results more than any template.
Frequently asked questions
How long should a proposal be?
Usually 120 to 200 words. Longer only if the client asks for a detailed plan.
Should I send a free sample?
A short, relevant sample you already made is fine. Be careful with free work on the client's actual project; offer a small paid trial instead.
Why am I not getting replies?
Common reasons are generic openings, missing samples, and applying to jobs far from your skills. Fix those before changing your price.
Can I use AI to help write proposals?
You can use it to tidy grammar or structure, but edit heavily. A message that sounds generic loses the main advantage, which is showing you read the job.
Next step: pick one open job today, write a proposal using the five parts above, and have it ready to send within 20 minutes.
Results from any side hustle or online work vary widely, and nothing here is a promise of income. Be wary of anyone who asks you to pay upfront to start earning.