Durvy
Retour au blog
3 min de lecture

How to write a freelance proposal that closes

A proposal is a decision document, not a brochure. The six sections that matter, the ones to delete, and how long it should take you to write.

A freelance proposal has one job: make it easy for someone to say yes. Most proposals fail because they are written as a sales brochure aimed at nobody in particular, when the actual reader is one person who needs to justify a number to themselves or to a boss.

The six sections that matter

  • Restate the problem in their words. Open with the situation as they described it on the call. This is the highest leverage paragraph in the document, because it proves you listened, and clients buy from people who understood the problem.
  • What you will deliver. Concrete, countable, and boring on purpose. Five templates. Two rounds. A migration of existing content. Not "a beautiful modern experience."
  • What is not included. The section most proposals omit and every dispute later references. It also makes the included list look more valuable.
  • Timeline with dependencies. Dates, plus what you need from them and by when. "Content by 12 October, feedback within three business days."
  • Price and payment schedule. One number, prominent. Deposit, milestones, terms. If you offer options, offer three, and make the middle one the one you want them to pick.
  • How to accept. A single instruction. "Reply yes to this email and I will send the agreement and deposit invoice today." Never end a proposal without telling the reader exactly what to do next.

What to delete

  • Your company history, unless the client asked.
  • A generic list of services you offer that are not part of this project.
  • Stock language about passion, partnership, or being results driven.
  • A twelve page process diagram. Clients do not buy your process, they buy the outcome and enough confidence that you will get there.
  • Case studies unrelated to their problem. One relevant example beats six impressive ones.

Pricing options, done properly

Three tiers work well when the scope has natural levels:

  • Core. The minimum that solves the problem. Priced so it feels like the safe choice.
  • Recommended. Core plus the things you know they will want in month two. This should be where you actually want to land, and it should be visually marked as the recommendation.
  • Extended. Core plus everything, priced high enough that it makes the middle option look reasonable.

If the scope has no natural levels, do not manufacture tiers. One clear number beats three confusing ones.

Length and turnaround

Two to four pages. Every extra page reduces the chance it is read in full and increases the chance it is forwarded to someone who will find one line to object to.

Send it within 24 hours of the call. Proposal win rates fall sharply with delay, not because clients are impatient but because enthusiasm decays and competing priorities arrive.

After you send it

  • Say when you will follow up, in the sending email, then do it. "I will check in Thursday if I have not heard back."
  • Follow up twice, three to four business days apart, then stop. A third chase costs you more credibility than it gains replies.
  • When you follow up, add something rather than asking for status. A relevant example, a small clarification, a note about availability.
  • Track close rate by proposal type. If you are winning more than 70 percent, your prices are too low.

TL;DR

  • Restate their problem first, in their words. That paragraph does most of the work.
  • Include exclusions, dependencies, a payment schedule, and a single explicit next step.
  • Two to four pages, sent within 24 hours of the call.
  • Three tiers only when the scope has natural levels. Otherwise one clear number.