How to Write a Freelance Proposal (Step by Step)

A proposal isn't a CV or a price list. It's the document a client uses to decide, often after you've left the call. This guide walks through what to ask before you write, what goes in each section, and how to send it so it gets read.

Updated September 30, 2026

Before you write: ask better questions

Proposals that win are usually won on the discovery call. If you don't know why the client wants the project, what success looks like, or who signs off, the proposal has to guess, and guesses read as generic. Ask these, and write down the answers in the client's own words:

1. What's prompting this project now? What happens if you don't do it?
2. What does success look like six months after it's finished?
3. Who else is involved in the decision, and what do they care about?
4. Have you tried solving this before? What didn't work?
5. Is there a date this has to be done by, and what's driving it?
6. Do you have a budget range in mind, even a rough one?
7. What would make you choose one freelancer over another?

The budget question feels awkward, but skipping it means pricing blind. If they won't give a number, offer ranges: "Projects like this tend to land somewhere between A and B depending on scope. Where does that sit for you?"

The structure

Eight sections covers almost any freelance project. Use this outline as a starting point and drop sections that genuinely don't apply.

[Project name]: Proposal for [Client]

1. Summary
   Their problem, in their words. What changes when it's solved.

2. Approach
   How you'll solve it, in 3-5 plain steps. Why this way.

3. Scope
   Deliverables (countable). What's not included.

4. Timeline
   Milestones with dates. What you need from them, and when.

5. Investment
   Price, or 2-3 options. Payment schedule.

6. Why me
   1-2 relevant examples. Skip the full CV.

7. Terms
   Revisions, changes, ownership, cancellation.

8. Next step
   How to accept. When you can start. Valid-until date.

Step 1: Open with their problem

The first paragraph decides whether the rest gets read. Restate the problem the client described, with a detail only someone who listened would know, then say what changes when it's fixed.

Thank you for the opportunity to submit this proposal. I am a freelance designer with over 8 years of experience and a passion for creating great work for my clients.

You mentioned that leads from the website have dropped since the redesign last spring, and that your sales team now spends the first call explaining what you actually do. This proposal covers a rewrite of the five core pages so visitors understand your offer before they get in touch.

Step 2: Explain your approach briefly

Three to five steps, in plain language. The goal is to show you have a plan and to make the price feel earned, not to teach the client your craft. If a step exists to reduce a risk they mentioned, say so: "We'll test the new checkout with five real customers before launch, since you mentioned the last redesign confused repeat buyers."

Step 3: Make the scope checkable

Every deliverable should be something both of you could point at and agree is done. "Brand refresh" isn't checkable; "primary logo, secondary mark, colour palette and a 10-page brand guide as PDF" is. Then add a "Not included" list. It feels negative, but it's the section that prevents most disputes.

Step 4: Tie the timeline to what you need from them

Give milestones with dates, and next to each one, what the client has to provide. Add one sentence that protects you both: "If feedback or materials arrive later than planned, later dates move by the same amount."

Step 5: Price it so the decision is easy

• Put the price after the scope, so it reads as the cost of something specific.
• Consider two or three options with genuinely different scope. It turns "yes or no" into "which one".
• State the payment schedule: deposit, milestones, and when invoices are due.
• Say how long the price holds. A valid-until date also gives a natural reason to follow up.

For how to arrive at the number itself (hourly, day rate, fixed or value-based), work from your own costs and the value to the client rather than a rate you read online. Rates vary widely by skill, location and client.

Step 6: Keep proof short and relevant

One or two examples close to this project do more than a full portfolio. For each, a sentence on the problem and a sentence on what happened. If you're new, describe how you'd handle the project's biggest risk instead. Specific thinking is proof too.

Step 7: Cover the terms in plain English

• Revisions: how many rounds, and what one round means.
• Changes: anything outside scope gets quoted before you start it.
• Ownership: when rights transfer (usually on final payment).
• Cancellation: what's owed if either side stops.

Step 8: End with one clear next step

Tell them exactly how to say yes (reply, accept online, sign), what happens straight after (invoice, kickoff call), and when you could start if they confirm by a certain date. A proposal that ends on "let me know if you have any questions" leaves the next move undefined.

How long should it be?

As long as it takes to make the decision easy, and no longer. For a small project that can be one page. For a larger one, a few pages with a summary at the top that works on its own, because that's the part that gets forwarded to whoever holds the budget.

Sending it

• Send it within a day or two of the call, while the conversation is fresh for both of you.
• If you can, walk the client through it live instead of just emailing an attachment. Questions get answered before they become objections.
• Send it as a link where you can, so you know whether it's been opened before you follow up.
• Put a follow-up in your calendar before you hit send.