Most proposals don't lose because the writing is bad. They lose because of what happens — or doesn't happen — after you hit send.
I once spent four hours on a proposal. Detailed scope, a clear timeline, a competitive price, even a short paragraph about why I was the right person for the job. Sent it on a Wednesday. Got a read receipt. Then nothing.
Early in my career managing web projects, I put together what I thought was an exceptional proposal. Forty pages. Detailed project plan, resource allocation, risk register, phased timeline. I spent three days on it. The client acknowledged receipt and went quiet.
I waited a week. Sent a polite chase. Nothing again. Two weeks later I found out through a mutual contact that they'd hired someone else — someone they'd met at a networking event who'd sent them a two-paragraph email and a day rate. No formal proposal. No detailed scope. Just a quick reply and a follow-up call the next day.
That stung. But it taught me something important: a proposal is not the thing that wins the work. It's one part of a process, and most freelancers spend 90% of their energy on the part that matters least.
After spending years on the other side of the table — commissioning freelancers as a Senior Digital Project Manager — I can tell you exactly how decisions get made. And it's rarely about who wrote the most thorough document.
When a client receives three or four proposals, they typically open them all in the first hour. They scan, they don't read. They're looking for three things: do you understand the problem, does the price feel right, and do I want to work with this person? That last one is almost entirely formed before they even open your document — based on your emails, your responsiveness, how you showed up in the initial conversation.
The proposal confirms or undermines that first impression. It rarely creates it.
So why do freelancers spend so long agonising over proposal copy? Partly because it feels like work. Partly because it's the thing you can control — you can endlessly polish a document in a way you can't engineer chemistry. But mostly, I think, because nobody tells them this is the wrong thing to optimise for.
Keep it short. I mean it. The proposals I've seen win, consistently, are never the longest ones. They're usually one to two pages. They make the client feel understood, they answer the obvious questions, and they make it easy to say yes.
Here's the structure I'd use every time:
1. Show you understood the brief. Open with a short paragraph that summarises the project back to them in your own words. Not copy-pasted from their brief — genuinely restated. This one paragraph does more work than anything else in the document. It proves you listened. It shows you've thought about it. And it gives the client an immediate feeling that you get it.
2. Your approach — briefly. Two or three sentences on how you'd tackle this. Not a methodology document. Not a 12-step process. Just: here's roughly how I'd approach this, and here's why. Clients don't want to understand your process. They want to feel confident it exists.
3. What's included and what isn't. This is the part most freelancers skip, and it's the part that causes the most arguments later. Be specific about what's in scope. And be equally specific — even in plain English — about what isn't. "Two rounds of revisions. Copy and photography not included. If the scope changes significantly we'll discuss separately." That's it. Not a legal document. Just clear expectations.
4. Timeline. Give them a start date and an end date. Even rough ones. Clients find vague proposals anxiety-inducing. "Approximately four weeks from project kick-off" is fine. It gives them something to hold onto.
5. Investment. Don't bury it. Don't call it "investment" either, actually — just call it cost or price and put it somewhere obvious. If you have options, give them two, not five. One price at your full rate and one at a reduced scope, if applicable. More than two options creates decision paralysis.
6. A clear next step. End with a specific call to action. "I'd love to jump on a call to walk you through this — are you free Thursday afternoon?" Not "please let me know if you have any questions." That's a passive close. Give them something to respond to.
Starting with yourself. "Hi, I'm [name], I've been a freelance designer for eight years and my clients include..." Nobody cares yet. Open with them, not you. The client wants to know you understand their problem before they care about your credentials.
Explaining your process instead of your outcome. "I start with a discovery phase where I conduct stakeholder interviews and create a comprehensive brief that feeds into a wireframing stage..." This reads like a job application, not a proposal. What will the client actually have at the end? What will be different? Lead with outcomes.
Vague pricing. "Price on application" or "dependent on final scope" is a red flag to most clients. Even if the project is genuinely variable, give them a ballpark with caveats. "Based on our conversation, I'd estimate £3,500–£4,500 depending on the number of pages. We'd confirm the exact scope before starting." That's honest and still gives them a number to react to.
Too many options. I've seen freelancers send proposals with four or five pricing tiers. They think it shows flexibility. What it actually does is make the client defer the decision because they can't choose. Two options is the maximum. Three if you genuinely can't avoid it. Any more and you're making their life harder.
Sending it and disappearing. This is the big one. Sending a proposal and then waiting passively for a response is the single biggest mistake freelancers make. You need a follow-up plan from the moment you send it. More on this in a minute.
I see two extremes constantly. Freelancers who underprice because they're afraid of losing the work, and freelancers who overprice with no justification and then wonder why they never hear back.
Here's the thing about price in a proposal: clients aren't just evaluating the number. They're evaluating whether your confidence in that number matches what they've seen from you. An underconfident freelancer who charges £500 for something they should charge £2,000 for doesn't look like a bargain. They look like someone who isn't sure their work is worth much.
Price honestly. If your rate is £400 a day and the project will take eight days, say £3,200. Don't go to £2,800 to seem "reasonable." Don't go to £3,800 to leave "negotiation room." Just say what you actually need to charge to do the job properly and feel good about it.
If a client haggles, the right response is to reduce scope, not price. "I could do it at £2,800 if we remove X" is a professional answer. "Okay, I'll do it for £2,800" teaches them that your prices are made up.
Here's what the data in my own pipeline tells me, after years of tracking this properly: the majority of my lost proposals didn't lose because the client chose someone else. They lost because I never heard back, assumed they'd gone elsewhere, and moved on. Then months later I'd bump into them and find out they just got busy, or the project got delayed, or they were waiting for budget approval and assumed my silence meant I wasn't available anymore.
Most proposals go cold because both sides stop communicating. Not because of price. Not because of capability. Just silence on both ends.
So here's the follow-up sequence I actually use:
Day 3 after sending: A short, warm check-in. "Just wanted to make sure this landed — happy to jump on a call if anything needs clarifying." Not chasing. Not needy. Just present.
Day 7: Something more specific. If you spotted anything relevant since sending — a portfolio piece that's relevant, a question you forgot to answer, something that shows you're still thinking about their project — include it. Even a one-line email that shows you're engaged does more than silence.
Day 14: A genuine last reach-out. "I wanted to check in one final time before I allocate my capacity for the coming weeks. Are you still looking to move forward, or has the timeline shifted?" This creates gentle urgency without being pushy. And it's honest — your time genuinely is a finite resource.
After that, mark it as cold in your pipeline and move on. Don't keep chasing indefinitely. But three well-timed follow-ups, sent with care, will double your close rate. I've seen this in my own numbers. It's not a theory.
For years I managed proposals in my inbox and a mental list. I'd send something, feel good about it for a day, and then let it drift. The ones that closed were the ones where the client chased me. Which meant I was only winning the most motivated clients — the ones who were going to hire someone regardless. The harder wins, the ones where a good follow-up would have swung it my way, I was just leaving on the table.
When I started tracking proposals properly — with a value, a sent date, a follow-up reminder, and a stage — the close rate went up noticeably. Not because my proposals got better. Because I stopped letting good leads go cold through forgetfulness.
A simple CRM pipeline does this automatically. You send a proposal, move the deal to "Proposal" stage, set a follow-up reminder for three days out. The tool handles the memory. You handle the relationship. That's the right division of labour.
The freelancers I've seen consistently win work aren't always the best writers. They're not always the most talented. They're the ones who show up reliably, communicate clearly, and never let a promising lead go quiet without at least one more conversation.
That's not talent. That's process. And process is something anyone can build.
Flowboard lets you build professional client quotes and proposals with PDF export — and track every one through your sales pipeline so nothing goes cold without a follow-up.
See What Flowboard Does → View Pricing