freelancing
How to Write Freelance Proposals That Win
A practical guide to writing freelance proposals that close more clients — structure, tone, scope, and pricing tips that work.
A great freelance proposal is not a long PDF. It is a clear summary that helps a busy client say yes. Most freelancers lose proposals because they over-explain or under-clarify scope.
1. Start with the client's real problem
Open with the client's situation, not your bio.
Example:
- "You mentioned the new pricing page is converting at 1.4 percent and the team wants to move it past 2 percent before Q3."
When you mirror the client's words back, they read the rest of the proposal.
2. Show one specific approach
Skip menu-style proposals with five options.
Pick one approach that fits the goal. Describe:
- the deliverables in plain language
- the steps in order
- a clear timeline
Specific is more confident than flexible. Confidence closes deals.
3. List inclusions and exclusions
Vague scope creates conflict later.
Include both:
- what is included (e.g., 3 page redesign, 2 rounds of revisions, copywriting for hero sections)
- what is not included (e.g., custom illustration, paid stock photos, ongoing maintenance)
Exclusions protect your margin and prevent misunderstandings.
4. Provide a clear timeline
A short timeline beats a long Gantt chart.
Example:
- week 1: discovery and outline
- week 2: first draft
- week 3: revisions
- week 4: final delivery
Timelines reassure clients that you have done this before.
5. Anchor the price with structure
Avoid hourly pricing in proposals when possible. Use packages.
Two structures that work:
- single project price with milestones
- two or three tiers (starter, growth, premium)
When you offer tiers, most clients choose the middle option.
6. Add a soft assumption section
Include a small block of assumptions.
Example:
- assumes content is delivered by the client by week 2
- assumes one stakeholder review per round
- assumes responses within 48 business hours
Assumptions create boundaries without sounding adversarial.
7. End with a small ask
Close the proposal with one clear next step.
Example:
- "If this looks right, reply to this email or sign here, and I will send the kickoff brief."
Avoid open-ended endings like "let me know what you think." Specific asks close faster.
8. Keep it short
Most winning proposals are between 400 and 900 words. Long proposals signal indecision and effort, not value.
If your proposal feels long, cut:
- biography sections
- generic process explanations
- big lists of past clients
- terms and conditions buried in the body
Short proposals close faster.
9. Send it through one clean format
Pick one format:
- a one-page Notion or Google Doc
- a short email proposal
- a tool like Bonsai, HelloSign, or Better Proposals
Avoid sending PDFs and decks for early-stage projects. They slow review.
10. Follow up once, politely
If you do not hear back, send one polite follow-up after three to five business days.
Example:
- "Just bumping this — happy to adjust scope or timeline if anything is off. Let me know either way."
Most proposals close after the second touch.
What to remember
Winning freelance proposals are short, specific, and structured for a yes. Show you understood the problem, propose one clear path, and ask for a clear next step.
Keep learning
Related guides
How to Run a Freelance Discovery Call That Closes
A practical discovery call script and framework to qualify clients, scope projects, and increase close rate.
How to Write Cold Emails That Get Replies
A practical playbook for cold emails that get freelance clients replying — subject lines, structure, and follow-ups.
How to Handle Scope Creep (Without Losing the Client)
A practical framework to handle scope creep on freelance projects — early signals, scripts, and pricing strategies.
How to Set Freelance Boundaries With Clients
Practical scripts and frameworks to set freelance boundaries — working hours, scope, communication, and protecting your energy.
Ready to find your next remote role?
Browse curated remote job boards, freelance marketplaces, and role-specific directories.