Writing proposals that win

0:00 Writing proposals that win

Most freelance proposals lose before the client reaches the price. They open with the freelancer's biography, list services the client didn't ask about, and bury the one thing the client cares about: do you understand my problem, and will this fix it? In this lecture, you'll learn to write proposals as decision documents: when to send them, the structure that wins, why the understanding section matters most, how to present options, how to attach a statement of work, and how to use AI to draft faster without losing the client's voice.

0:40 Why it matters

Why does this matter? Because a proposal is the moment a client decides. If it's clear, specific and about them, saying yes is easy. If it's generic, they compare you on price, or do nothing. And a good proposal also protects you, because it sets scope, timeline and terms before work starts. Here's the key idea. A proposal isn't a description of you. It's a mirror of the client's situation, followed by a clear recommendation and an easy next step.

1:15 The architect analogy

Here's an analogy. Think of an architect presenting plans to a family. They don't start with their awards. They start with: you told us you need space for your parents to move in, natural light in the kitchen, and a budget that doesn't mean remortgaging. Then they show three options: a sensible extension, the recommended design, and the dream version. Each with a cost and a timeline. The family feels heard, and choosing feels easy. Your proposal works the same way. Understanding first, then options, then the path to start.

1:54 When and how

First, when should you send a proposal? Only after a discovery conversation, when you understand the problem, the value, the decision makers and the budget range. A proposal sent to a cold enquiry is a price list in disguise. And a practical tip: tell the client on the call when they'll receive it, and send it on time. Now the structure. Title and date, with a validity period. Understanding. Approach. Options. Timeline and client responsibilities. Investment and terms. Proof. And next steps. Two to four pages is plenty for most freelance work, with a statement of work and terms of business attached.

2:38 The understanding section

The understanding section wins proposals. Write it in the client's own words from the call. Their situation. What's at stake. What success looks like in a specific timeframe. For example: you opened your second branch in March, and bookings are handled by phone at both. Missed calls at peak times are costing you appointments, and the team is stretched. Success in three months means online booking at both branches and fewer no-shows. When a client reads their own words back, they think, this person was listening. That feeling does more selling than any credentials.

3:19 Options and terms

Next, options. Offer three: essentials, recommended and complete. Each with a clear scope and price. This does two things. It shifts the question from, should I hire this person, to, which option suits me. And it anchors the recommended option against a larger one. Keep the differences meaningful and easy to see. Then the investment and terms section: currency, deposit, milestone payments, payment method, who pays transfer fees, late-payment terms and how long the proposal is valid. And finish with a next step that takes seconds: reply with the option you'd like and I'll send the agreement and deposit invoice today.

4:03 Worked example 1: Lucy in Edinburgh (illustrative)

A simple worked example, illustrative. Lucy, a marketing consultant in Edinburgh, used to reply to enquiries with a price list. Her win rate was low. She switched to discovery calls followed by short proposals. For a gin distillery, her understanding section quoted the founder: we sell out at summer events and then sales go quiet for months. Her three options were a six-week email and social plan, a three-month plan with a subscriber club launch, and a six-month plan including trade outreach. The founder chose the middle option, and told her the first page made it an easy decision.

4:46 The statement of work

Now the statement of work, the SOW. It's the precise description of what you'll deliver, and it's what prevents arguments later. Objective. Deliverables, with formats, quantities and languages. What's out of scope, explicitly. Assumptions, like the client supplying copy by a certain date. Client responsibilities, including approvals within, say, three working days. Timeline, noting that late inputs move dates. Acceptance: how deliverables are approved, and when they're deemed accepted. Revisions, with a definition. Fees and payment. Change control. AI use. And signatures. It's more detail than the proposal, and that's the point.

5:26 Worked example 2: Yusuf in Lahore (illustrative)

Now the realistic scenario, illustrative. Yusuf runs a small development studio in Lahore and sends a proposal to a UK e-commerce brand. He uses an AI assistant to turn his call notes into a first draft of the understanding section, then rewrites it with the client's exact phrases, like, our checkout feels slow on mobile. He sets the scope, price and timeline himself. His options are priced in pounds, with a forty percent deposit and milestones, and the terms state that the client pays their own transfer fees and that final code transfers on full payment. He attaches the SOW, sends it through an e-signature tool, and it's signed within two days.

6:15 Watch me: AI-assisted drafting

Watch me use AI to draft, safely. I paste my anonymised call notes into an assistant on a business plan that doesn't train on my data. I ask: draft an understanding section using the client's quoted phrases exactly as written, and list any gaps in what I know. It produces a clean draft and flags that I don't know who approves the budget. Good catch. Then I edit every line so it sounds like me and the client. I write the approach, options, scope and price myself, because those are my professional judgement. Finally, I check the proposal against my checklist before sending.

7:00 Common mistakes

Let's list the common mistakes. Sending proposals without discovery. Starting with your biography. Generic understanding sections that could apply to anyone. One take-it-or-leave-it price. Vague scope with no exclusions. Missing payment terms, currency or validity date. No clear next step. Letting AI write in a voice that isn't yours, or inventing details the client never said. And not following up. A polite follow-up after three or four working days, and another a week later, is professional, not pushy.

7:34 Recap and try this now

Let's recap. A proposal is a decision document. Send it after discovery. Lead with understanding in the client's words, explain your approach, offer three options, and set out timeline, responsibilities, investment and terms clearly. Attach a statement of work that makes scope precise. Use AI to draft faster, but keep the client's words and your judgement in charge. Your try this now: turn your last discovery call into a proposal using the template, write the matching SOW, and review both against the checklist. Next, we'll look at the contract that protects both sides.