How to write a freelance proposal that gets answered

Most freelance proposals go unanswered for a dull reason. The client opened the document, could not quickly tell what they would get or what it would cost, put it aside to read properly later, and later never came. A week passed, replying started to feel awkward, and the enquiry died there. Very little of that is about the quality of your work. It is about how much effort the document asked of a busy person who had about two minutes for it.

A proposal is a decision document. Whoever reads it has to do one of three things: approve it, decline it, or ask you one question. Everything on the page should make one of those easier. Long sections about your studio's philosophy, a cover image, and a fourteen-page PDF all pull in the opposite direction, because they add reading time without adding anything that helps the client decide.

Ask five questions before you write anything

The fastest way to write a proposal that lands is to have a short conversation first. Fifteen minutes on a call, or four or five questions in an email, will tell you more than an hour of guessing at what the client wants.

• What does this need to achieve? Push past "a new website" to something you could check later, like more enquiries from the contact form or a faster path from landing page to signup.
• What have you already tried? This tells you what not to propose, and it tells you whether the last person on this job left behind a mess you will have to price for.
• Who approves the spend, and by when? If your contact has to take the proposal to a director or a finance team, you are writing for two audiences and you need a version that survives being forwarded.
• What range were you expecting to spend? Some clients answer honestly, some deflect, and both responses are useful. A client with no number in mind is often a client with no approved budget.
• What happens if you do nothing? If the honest answer is "not much", the project is a nice-to-have and will lose to anything urgent. Price and sequence it accordingly.

A proposal written without these answers describes your services. One written with them describes the client's situation and what you plan to do about it. The second kind gets replies, and it is also much faster to write, because the client has already told you what belongs in it.

The seven parts of a proposal that works

Order matters here. The client should reach the price already knowing what it buys, and should never have to scroll back to work out what you are proposing.

1. Their situation, in their words

Open with two or three sentences on the problem as the client described it, using their vocabulary rather than yours. If they said their booking form loses people halfway through, write that, not "conversion funnel optimisation". This section does more work than any other part of the document. It proves you listened, and it gives the person who has to forward your proposal to a decision maker a paragraph they can point at.

2. What you propose to do

Describe your approach as an ordered sequence of steps, not a list of services. Three to five steps is usually right. Each one should be a sentence a non-specialist can follow, such as "review the current form and the drop-off data" or "rebuild the form as three short steps and test it on mobile". A client who can follow the sequence can picture the project happening, and that is most of what confidence in a freelancer comes from.

3. What they get, and what is not included

List the actual deliverables: the files, formats, pages, or sessions, with quantities. Then add a short exclusions line. Naming two or three things you are not doing feels blunt the first time you write it, and it prevents the most common kind of scope argument later, where the client believed something was part of the job and you believed it never was. If the deliverables need more detail than a proposal can hold, our scope of work generator produces a scope document you can attach.

4. Timeline tied to their dates

Give a start date, a delivery date, and the client dependencies in between. Write the dependencies plainly, for example "assumes copy is supplied by 12 September and feedback within three business days of each draft". This is where you protect your deadline before it exists. A schedule that never mentions the client's obligations turns their delay into your late delivery.

5. Price, with two options

State the total, the currency, and the payment split. A deposit of 30 to 50 percent before work starts, with the balance on delivery or across milestones, is a normal structure and worth making explicit here rather than saving for the contract. If you are unsure the number covers the real hours, the project quote builder works the scope back into a total, and the rate calculator checks that your baseline rate covers unbilled time and time off.

6. One piece of proof

Name a similar project you have done and what came out of it. One example with a specific outcome does more than a list of logos. If you are early in your career and have nothing directly comparable, use the closest adjacent work and be straightforward about how it maps to this job. Clients discount claims they cannot check, so a modest verifiable example beats an impressive vague one.

7. One clear next step

End with a single instruction, such as "reply with option A or option B and I will send the agreement and the deposit invoice the same day". Two calls to action produce hesitation. A named date works even better: saying you can hold a start date until Friday gives the client a reason to answer this week rather than whenever the inbox calms down.

Why two prices beat one

A single price gives the client a yes or no decision, and no is always the easier answer for someone who is unsure. Two options change the question to which version of yes makes sense. Build the smaller option as the core job done properly, and the larger one as the same job plus the extras that most clients ask for a month later anyway, such as extra revision rounds, a longer support window, or a second round of testing.

Keep the gap between the options meaningful, roughly 40 to 70 percent, so the choice is real rather than cosmetic. Do not build a deliberately bad cheap option to push people upward. Clients notice, and the cheap option is the one they will pick if money is tight, so you have to be willing to deliver it well. Three options can work for productised services where the tiers cover different amounts of work. Beyond three, the client stops choosing and starts comparing, which is where proposals stall.

Keep it to one page

One page covers most freelance projects. Two is reasonable when the work has several phases. Anything longer is usually padding that arrived because the proposal felt too thin, and thin is rarely the problem. If a document is running long, the fix is normally to move detail into an attached scope document and leave the proposal as the summary that gets read.

Send it in the body of an email where you can. A PDF attachment adds a download step, often opens badly on a phone, and cannot be skimmed in a preview pane. If your client's organisation expects a formal document, send the summary in the email body and attach the PDF as the record. Our freelance proposal generator lays out all seven sections above and gives you plain text you can paste straight into an email or print, with the second pricing option appearing only if you fill it in.

What to leave out

Several things that appear in proposal templates make replies less likely.

• Your company story. Two lines of relevant background is plenty. Nobody buys on a founding narrative.
• Full terms and conditions. Payment terms, revision limits, ownership and cancellation belong in the agreement that follows, covered in our guide to contract basics. Putting them in the proposal makes a decision document look like paperwork.
• Hourly breakdowns for fixed-price work. Showing the hours invites the client to argue about the hours instead of the outcome.
• Hedged language. "We could potentially look at" reads as uncertainty about your own plan. Say what you will do.
• Free strategy inside the proposal. A short paragraph of insight builds credibility. A full audit given away before anyone has committed is unpaid work, and it hands over the part of the job the client most needed you for.

Following up without chasing

Silence after a proposal usually means budget approval, a colleague on holiday, or a competing priority. It rarely means a decisive no, and clients who intend to decline often stop writing rather than say so.

Follow up twice. The first note goes out three or four business days after you sent the proposal, offering to walk through it or answer a question. The second goes about a week after that and gives a practical reason to reply, such as holding the start date until a named day. Keep both short, and leave out the apology for following up, since you are answering a question the client asked you to answer. After the second message, move on and put a reminder in your calendar for six weeks out. Dormant proposals do convert later, and a short "still happy to pick this up if the timing works now" note has restarted plenty of projects.

If a client accepts, send the agreement the same day while the decision is fresh. Match the deliverables and price in the contract to the proposal word for word, since a mismatch between the two is the first thing that gets argued about when a project goes wrong. The contract clause library has wording you can adapt, and the guide to getting paid on time covers the invoicing and reminder process that follows. If enquiries themselves are the bottleneck rather than the proposals, start with the guide to getting freelance clients.

Frequently asked questions