How to Write a Freelance Proposal Clients Can Say Yes To (8-Part Template)
A freelance proposal has one job: to make it easy for the client to say yes to a specific piece of work, at a specific price, on a specific timeline. Most proposals that stall aren't badly written. They're vague in the places that matter: what's included, what isn't, what it costs and what happens next.
This guide gives you a plain 8-part structure that works for design, development, writing, marketing and consulting projects, plus a copy-paste skeleton and a checklist to run before you hit send.
Before you write: get these from the discovery call
You can't write a clear proposal from a fuzzy conversation. Before drafting, make sure your notes answer:
- The problem in the client's words. What prompted them to reach out now?
- What a good result looks like to them, ideally something they can see or check.
- Constraints: deadline, budget range, who approves the work, and anything already decided.
- What they'll provide: content, access, brand files, feedback turnaround.
- What's out of bounds: anything they've said they don't need, or that you won't do.
If an answer is missing, ask in a short follow-up email before you write. Guessing in the proposal is how scope problems start.
The 8-part freelance proposal structure
1. Understanding
Two or three sentences that restate the situation and the goal in the client's language. This is where the client checks that you were listening. Keep it about them, not about you.
Example: "River & Oak Coffee is opening a second location in March and needs a website that shows both locations, the menu and catering options, and that the team can update without a developer."
2. Recommended approach
How you'll get from here to the result, in plain steps or phases. If there are phases, a small table (phase, what happens, output) helps the client see the shape of the project.
3. Deliverables, plus what's not included
List each deliverable concretely ("5-page responsive website: Home, Menu, Locations, Catering, Contact") rather than describing an activity ("website design"). Then add a short Not included list with the things clients most often assume are part of the deal: copywriting, photography, extra pages, ongoing maintenance.
This list is what both of you can point to later. When a "quick favor" shows up mid-project, it's the list you point to. Our guide to handling scope creep with a simple change order covers what to do next.
4. Timeline
Milestones with target dates, plus what each one depends on ("Design review: Oct 3, assuming content arrives by Sep 26"). Dependencies keep the timeline honest when the client is late with their part.
5. Investment and payment schedule
The price, what it covers, and when each payment is due. For example: a deposit on acceptance, a milestone payment, and the balance on delivery. Say which payment terms apply (for example, "invoices due within 15 days"). If extra work is billed differently, state the rate here.
Call it "Investment" or "Fee", whichever fits your voice. What matters is that the number, the schedule and the terms are all visible in one place.
6. Working together
The practical rules of the project: main contacts on both sides, tools you'll use, your usual response time, how feedback should arrive (one consolidated round per review), and a one-line note on how extra requests are handled ("Requests outside this scope are quoted as a short change order before work starts").
7. Next steps
Numbered, short and concrete. For example:
- Reply "approved" (or sign below).
- I'll send the scope of work and the deposit invoice.
- Once the deposit is in, we schedule kickoff.
8. Acceptance
One line the client can reply with to say yes, plus an expiry date for the quote ("This proposal is valid until [date]"). An expiry date protects your calendar and your pricing without any pressure tactics.
A copy-paste proposal skeleton
Subject: Proposal: [Project name] for [Client]
1. Understanding
[2–3 sentences: their situation, goal and deadline, in their words]
2. Recommended approach
[Phase 1: what happens → output]
[Phase 2: what happens → output]
3. Deliverables
- [Deliverable 1, specific]
- [Deliverable 2, specific]
Not included: [item], [item], [item]
4. Timeline
| Milestone | Target date | Depends on |
| [Milestone] | [date] | [client input] |
5. Investment
[Total fee]. Payment: [deposit %] on acceptance, [milestone %] at [milestone], balance on delivery.
Invoices due within [N] days. Extra work: quoted separately before it starts.
6. Working together
Contacts: [you] / [them]. Tools: [tools]. Response time: [e.g. 1 business day].
Feedback: one consolidated round per review.
7. Next steps
1. Reply "approved" 2. Scope + deposit invoice 3. Kickoff
8. Acceptance
Valid until [date]. To accept, reply "Approved, please send the scope."
Common mistakes that stall a yes
- Leading with your background. One short credibility line is enough. The client is reading to find their project, not your history.
- A price with no structure. A single number with no schedule or terms raises questions you could have answered upfront.
- Too many options. One recommended approach, plus at most one smaller alternative, is easier to approve than a menu.
- No "not included" list. Silence reads as "everything's included".
- Ending without a next step. If the client doesn't know how to say yes, they'll say "let me think about it".
Pre-send checklist
- Client name and company spelled correctly everywhere
- No leftover placeholders like [Client] or TODO
- Deposit, milestones and balance add up to the total
- "Not included" list present
- Every date has its dependency noted
- Expiry date set
- You'd be comfortable if it were forwarded to their boss
FAQ
How long should a freelance proposal be? Long enough to cover the eight parts clearly. For a small project, that can fit on one or two pages. Length doesn't win work. Clarity about scope, price and next steps does.
Should I send a proposal or a contract first? Many freelancers send the proposal first to agree on the shape of the work, then a scope of work or contract with the detailed terms. Some combine them. Either way, the terms that matter (scope, price, payment schedule, how changes are handled) should be in writing before work starts.
Can I use AI to draft proposals? Yes, as a first draft from your own discovery notes, as long as you review and edit every line. Check names, numbers and promises especially carefully.
Is this template legal advice? No. It's a business draft to adapt and review. Have a qualified professional review anything you intend to rely on as a binding agreement.
Where this fits in the rest of the workflow
A proposal is the first document in a client project. Once it's approved, the next step is a calm, organized start; our client onboarding checklist covers what to collect on day one. The proposal is also where payment terms first appear; our guide to freelance payment terms and a late fee clause has example wording to adapt.
The Client Ops Starter Kit includes a proposal template with these sections, a longer proposal guide, an optional AI prompt that drafts this structure from your call notes, and a worked example for a fictional web-design project. Want to see the style first? Open the free sample. It includes the proposal prompt, with no sign-up needed.