How to Write a Freelance Proposal That Closes
A proposal is a decision document, not a brochure. Here is the structure that gets signed, and the three clauses that decide whether the project stays profitable.
A proposal that closes does three things: it restates the client’s problem in their words, it defines exactly what is and is not included, and it gives a price with a payment schedule attached. Everything else — your bio, your logo, your process diagram — is optional and usually padding.
Most proposals fail for the same reason. They describe the freelancer instead of the project. The client already decided you were plausible or they wouldn’t be reading; what they need now is a decision they can defend to whoever signs off.
What goes in a proposal, in order
- The problem, in their words. One paragraph, using the language from your call. This is the single highest-leverage part of the document.
- What you’ll deliver. Concrete nouns. “Five-page marketing site, responsive, built in Webflow” — not “a digital presence”.
- What’s not included. The section everyone skips and everyone later needs.
- Timeline, with dependencies. “Three weeks from receipt of copy and brand assets.” The dependency clause is what stops you being blamed for their delay.
- Price and payment schedule. One number, split into stages.
- What happens next. One sentence, one action.
What should be in the exclusions section?
Anything a reasonable client might assume is included. Copywriting, if you’re not writing it. Stock imagery licensing. Post-launch changes. Hosting and domain costs. Third-party plugin licences. Training.
This reads defensive when you write it and saves the project when scope moves. You’re not predicting a difficult client — you’re removing the ambiguity that turns a reasonable client into a difficult one.
This structure assumes project work with a defined output. If you’re pitching a retainer or ongoing consulting, the scope section becomes a description of capacity — hours or days per month — and the exclusions matter more, not less.
How many revision rounds should you offer?
Name a number. Two is common for design work. The number matters less than its existence: “unlimited revisions until you’re happy” is how a three-week project becomes a three-month one, and the client rarely intends that outcome either.
Then state what happens after. Not as a threat — as information: “Further rounds are billed at the hourly rate below.” A client who knows the meter starts consolidates their feedback, which is better work for both of you.
The three clauses that decide profitability
| Clause | What it prevents | Typical form |
|---|---|---|
| Deposit | Funding the client’s cash flow | 30–50% up front |
| Revision cap | Unbounded rework | 2 rounds |
| Dependency clause | Their delay becoming your problem | Timeline starts on receipt of assets |
The ranges above are what appears commonly in freelance contract templates, not a surveyed average — check what’s normal in your market and for your kind of work before quoting them as standard.
Should you send a price range or a single number?
A single number for defined scope. Ranges invite negotiation toward the bottom of the range, and they signal that you’re unsure what the work involves.
If scope genuinely isn’t defined enough to price, that’s the actual problem — sell a short paid discovery session instead, and price the real project afterwards. This is also the honest answer when someone asks for a quote off a two-line brief.
- Lead with their problem in their words, not your background.
- Exclusions are the most valuable section in the document.
- Cap revisions and say what happens after the cap.
- Take a deposit. It is the clearest signal a project is real.
- Undefined scope means sell discovery, not a guess.
What to do this week
Take your last proposal and cut everything above the problem statement. Then write the exclusions section you didn’t include — the one that would have saved you on that project. That’s your template.