Most freelance proposals lose the job before the price is even read. The client opens a document that leads with a number, skims for a reason to say no, and finds one. A proposal that wins work reads in a different order: it proves you understood the problem, defines exactly what will be delivered, and only then attaches a price to that understanding. Here is the structure, section by section.
Key takeaways
- A proposal is a sales document, not a quote. A quote prices a defined job; a proposal defines the job and then prices it.
- Lead with the client’s problem in their own words, not with your bio.
- Scope means listing what is excluded, not only what is included.
- Give two or three price options anchored to outcomes, not one take-it-or-leave-it number.
- Every proposal needs an expiry date and a visible next step.
Proposal, quote or contract?
These three documents do different jobs, and sending the wrong one costs you work. A quote answers “how much?” when the client already knows exactly what they want. A contract locks in terms after the client has said yes. A proposal sits between the first call and the yes: it defines the work, frames the price and asks for a decision. If you are sending prices before the client has agreed on scope, you are quoting when you should be proposing.
The structure, section by section
1. Restate the problem. One short paragraph describing the client’s situation and goal in the words they used on the call. This is the most persuasive paragraph in the document, because it proves the proposal was written for them. If you cannot restate the problem, you are not ready to price it.
2. Scope: in and out. List what the project includes, then explicitly list what it does not include. The exclusions do more work than the inclusions: they prevent the “I assumed that was covered” conversation six weeks in. When scope moves anyway, the mechanism is a written change order, which we walk through in Before You Say Yes to “One Small Thing,” Send the Change Order.
3. Deliverables with acceptance criteria. For each deliverable, write what “done” means in a way both sides can check. “Website redesign” is an argument waiting to happen. “Five page templates delivered as Figma files, revised through two feedback rounds” is a deliverable.
4. Timeline with milestones. Break the work into dated checkpoints. Milestones are not just project management: they are the skeleton your payment schedule hangs on. Our deposit and milestone payments checklist covers how to tie invoices to those checkpoints.
5. Price as options. Offer two or three tiers anchored to outcomes: a lean version that solves the core problem, a standard version, and a premium version with speed or extras. A single number invites a yes-or-no; options invite “which one.” If the client needs it faster than your standard timeline, that is a rush job with a rush price, and The Rush Fee Playbook shows how to charge for speed without losing the client.
6. Terms. Keep this short and plain: payment schedule (deposit first, per the checklist above), number of included revision rounds, who supplies what and when, and the proposal’s expiry date. Fourteen to thirty days is a common validity window; the point is that your price and availability should not be open-ended.
7. The next step. End with one instruction: how to accept. “Reply with ‘approved’ and I will send the deposit invoice” beats a vague “looking forward to hearing from you.” A proposal without a next step is a brochure.
How long should it be?
Long enough to define the work, short enough to be read. For most freelance projects that is one to three pages. The test is whether a client who only skims the headings still understands the project. If a section does not help the client say yes or understand what they are buying, cut it.
Mistakes that kill proposals
- Leading with your bio. The client’s problem comes first. Your experience belongs in one short section after scope, framed as proof you can deliver this specific job.
- A price with no expiry. An open-ended quote gets shopped against your future competitors. Expiry creates a reason to decide.
- Scope with no exclusions. Everything you do not list becomes an assumption the client fills in for you.
- No defined next step. If accepting your proposal takes effort, it will be postponed.
After the yes
A signed proposal is the start of onboarding, not the end of sales. The deposit invoice goes out the same day, and the client gets walked into a repeatable workflow, per our client onboarding checklist. If the work recurs monthly, the follow-up document is a retainer: Before You Sell a Retainer, Write Down What the Month Can Hold shows how to size it.
FAQ
Should a freelancer send a proposal or a quote?
Send a quote only when the client has fully defined the job and asked for a number. When the scope is still being shaped, which is most freelance work, send a proposal: it defines the work and then prices it. The proposal is where you win the job.
How many price options should a proposal have?
Two or three. One price gets a yes-or-no answer. More than three creates decision fatigue. Anchor the middle option as the one most clients choose, if that is true for your work.
Does a proposal need an expiry date?
Yes. An expiry date (commonly 14 to 30 days) protects your pricing and availability and gives the client a reason to decide. Without one, your proposal can be accepted months later at terms that no longer fit your schedule.
