How to Write a Freelance Proposal That Gets Accepted (With Checklist)
The proposal that lost a ₹40,000 project in 12 seconds
Arjun is a freelance video editor in Kochi. A startup founder asked him for a quote on a product launch video and Arjun sent what most freelancers send: a long email about his 6 years of experience, his software, his awards — and a price buried at the bottom. The founder later told him she'd hired someone else. "His first line told me he understood my launch date problem. Yours told me about you."
Arjun's work was better. His proposal wasn't. Most proposals fail for exactly one reason: they talk about the freelancer, not the client's problem. This guide gives you a 6-part structure that fixes that — short, clear, and built to make "yes" easy.
In this guide
- 1. Start with their problem, not your profile
- 2. State your solution in plain language
- 3. Define the scope — included and not included
- 4. Give a timeline with real dates
- 5. Quote one clear number with payment terms
- 6. End with a single next step
- A weak proposal vs a strong one — worked example
- Email or PDF? A quick decision table
- The full template — copy and fill
- Proposal checklist
- 4 mistakes that quietly kill proposals
1. Start with their problem, not your profile
Show you understood the brief in 2–3 lines, using the client's own words where you can. Example: "You need a landing page that explains your coaching offer and gets trial bookings. Your current page has no clear call-to-action, so visitors leave without booking."
Do not start with "I am a designer with 5 years of experience…" — the client knows they asked a freelancer; what they don't know yet is whether you understood them. The first three lines decide whether the rest gets read.
2. State your solution in plain language
Say what you will do, in 3–5 lines a non-expert can understand. "I will design a 1-page landing page with a headline, your offer, a testimonials section, and a booking form — mobile-friendly, ready to connect to your domain."
Avoid jargon ("synergistic UX paradigm") and avoid listing tools ("Figma, Webflow, Photoshop"). Clients buy outcomes, not your toolbox. Name the deliverable and the result it produces.
3. Define the scope — included and not included
This is where most freelancer pain is born. Write two short lists:
Included: 1 landing page, 2 revision rounds, final files, 1 week of post-launch support. Not included: logo design, copywriting, hosting setup — quoted separately if needed.
Clear scope prevents the slow bleed of "can you just add one more section?" Every undefined deliverable becomes free work. If the client later wants the excluded items, that's a second quote, not a favour.
4. Give a timeline with real dates
Bad: "2 weeks." Good: "Draft by 24 Oct, revisions by 28 Oct, final delivery 30 Oct — provided feedback comes within 24 hours."
Real dates do two things: they prove you've thought about the work, and they make the client feel the project is already planned. Always add one line: "The timeline depends on timely feedback from your side." That single sentence has saved more freelancers than any contract clause.
5. Quote one clear number with payment terms
Give one total — not your hourly math, not a range, not "let's discuss." Example: "Total: ₹12,000. 50% upfront (₹6,000) to start, 50% on delivery. Payment via UPI or bank transfer, due within 7 days of invoice."
If you offer packages, show a maximum of 2 options (Basic vs Standard) — more choices slow the decision. And get your number right before you write it: see How to Price Freelance Work in 2026 for the formula. One clear number plus clear terms beats a clever price every time.
6. End with a single next step
Tell the client exactly what "yes" looks like: "Reply 'Yes, let's start' and I'll send the invoice for the first 50%. I can begin on [date]." Then add a deadline: "This quote is valid for 7 days."
A proposal without a next step is a document. A proposal with one is a decision waiting to happen. Never end with "let me know what you think" — end with one action and one date.
A weak proposal vs a strong one — worked example
Same project, same freelancer, different proposal. This is an illustrative example (a ₹15,000 landing page project):
| Part | Weak version | Strong version |
|---|---|---|
| Opening | "I am a designer with 5 years of experience in Figma and Webflow…" | "You need a landing page that turns visitors into trial bookings before your 15 Nov launch." |
| Solution | "I will create a stunning, modern website." | "1-page landing page: headline, offer, testimonials, booking form — mobile-friendly." |
| Scope | (not mentioned) | "Included: 1 page, 2 revision rounds, final files. Not included: logo, copywriting." |
| Timeline | "Around 2 weeks." | "Draft 24 Oct, revisions 28 Oct, final 30 Oct — if feedback comes within 24 hours." |
| Price | "Let's discuss the budget on a call." | "Total ₹15,000. ₹7,500 upfront, ₹7,500 on delivery. Valid 7 days." |
| Next step | "Let me know what you think." | "Reply 'Yes' and I'll send the first invoice. I can start Monday." |
Notice: the strong version is actually shorter. Clarity is not length — it's decisions already made for the client.
Email or PDF? A quick decision table
| Situation | Best format | Why |
|---|---|---|
| Small job, enquiry came by email/WhatsApp | Fast, readable on phone, no download friction | |
| Larger project (₹25,000+), corporate client | PDF, 1–2 pages | Looks formal, easy to forward to a manager |
| Upwork / platform bid | Platform message + short PDF | Platform keeps the record; PDF shows professionalism |
| Client asked "send me your proposal" | Match what they asked | Never make the client convert formats |
Rule of thumb: email for speed, PDF for formality. Both must contain the same six parts.
The full template — copy and fill
Fill the brackets, personalise the first three lines, and send within 24 hours of the enquiry:
Hi [Name], You need [result the client wants]. The problem with [current situation] is [specific pain point]. I'll deliver [deliverable] — including [scope items]. Not included: [excluded items], which I can quote separately. Timeline: draft by [date], final delivery [date], provided feedback comes within 24 hours. Total: [₹ price]. 50% ([₹]) upfront to start, 50% on delivery via [UPI/bank transfer]. Revisions: 2 rounds included; extra rounds at [₹] each. This quote is valid for 7 days. Reply "Yes, let's start" and I'll send the first invoice — I can begin on [date]. Thanks, [Your Name] · [email] · [portfolio link]
Personalise the first three lines for every client. A copy-paste proposal with the wrong name — or the right name and nothing else changed — loses faster than no proposal at all.
Proposal checklist
Run this before you hit send:
- ☐ Client's problem stated in their words (first 3 lines)
- ☐ Solution in plain language, no jargon
- ☐ Scope: included AND not included
- ☐ Timeline with real dates + feedback condition
- ☐ One total price + payment terms + validity period
- ☐ Single next step with a start date
- ☐ Your name, email, and portfolio link
4 mistakes that quietly kill proposals
1. Sending a 5-page PDF for a small job. Match the proposal to the project — one page covers most freelance work. Length signals cost, and cost signals "expensive."
2. No price — "let's discuss." Busy clients read this as "this will be awkward" and move on. Name your number.
3. No revision limit. Unlimited revisions is a promise of endless changes. Two rounds is standard; say so.
4. Speed. Every day you delay, the client talks to someone else. Send within 24 hours of the enquiry — speed wins ties.
Frequently asked questions
Should I send my proposal as a PDF or an email? Email for small jobs and fast enquiries; a short PDF for larger or corporate projects. Both must contain the same six parts.
What if the client asks me to lower my price? Don't cut the price — cut the scope. "I can do X without Y for [lower price]" keeps your rate intact and gives the client a real choice.
How fast should I send a proposal? Within 24 hours of the enquiry. After that, your chances drop with every day — the client is already talking to your competitors.
Should I include my full portfolio in the proposal? No — link to it. Include at most 2–3 directly relevant samples. A proposal is a decision document, not a gallery.
What if the client ghosts after receiving the proposal? Follow up once after 3–4 days ("Checking in — happy to answer questions on the proposal"), then once more after a week. Then move on; chasing harder rarely converts.
Educational info only, not legal advice. For large projects, pair your proposal with a simple written contract.
Comments
Post a Comment