Most proposals don’t lose work because the price is too high. They lose work because they feel like the wrong kind of document at the wrong moment. You’ve done the meeting, asked the right questions, felt the energy in the room — and then you send over something that reads like a contractor’s quote rather than a considered response. The client reads it, feels vaguely underwhelmed, and quietly moves on.
That’s a frustrating place to be, especially when you know the work itself would have been excellent. The proposal is supposed to be the bridge between a good conversation and a signed agreement. Too often, it’s where momentum goes to die.
Here’s what a typical proposal looks like. It opens with a brief “thank you for the opportunity” line. Then there’s a summary of what the client told you they need. Then a list of deliverables, a timeline, a price, and some terms. Maybe a short paragraph about your background at the end, almost as an afterthought.
The problem isn’t that this format is offensive. The problem is that it’s forgettable. It confirms you listened, but it doesn’t demonstrate that you understood. There’s a meaningful difference between those two things, and clients feel it even when they can’t articulate why.
A proposal structured around deliverables and logistics puts the focus in the wrong place. The client isn’t buying a list of tasks. They’re buying a result, and more specifically, they’re buying their confidence that you’re the right person to produce it.
One of the more useful shifts you can make is understanding what the opening section of a proposal is actually for. Most people use it to repeat back what the client said. “You mentioned you’re looking to increase brand awareness and drive more qualified leads.” Fine. But the client already knows what they want. They were there.
What they want to see is whether you’ve thought about it properly. That means showing the underlying problem, not just the surface request. If someone asks for a new website, the real issue might be that their current one creates friction for prospects who aren’t yet ready to buy. That’s a different conversation, and the proposal that starts there is far more compelling than one that leads with “six pages of responsive design.”
Reframing isn’t about being contrarian or showing off. It’s about demonstrating that you’ve considered the situation from the client’s perspective, not just from the angle of what you can deliver. That shift in framing is, quietly, one of the most persuasive things a proposal can do.
Pricing is where proposals often fall apart, but not for the reason most people assume. It’s rarely about the number itself. It’s about context. A price that appears too early, without sufficient grounding in the value being created, feels like a demand. The same price, presented after a clear articulation of what’s at stake for the client, feels reasonable, sometimes even modest.
There’s also the question of how the price is presented. Itemising every component might feel transparent, but it invites the client to mentally subtract things they think they don’t need. A single well-explained investment figure, anchored to an outcome, is usually cleaner and more persuasive than a detailed breakdown that reads like a bill.
Offering multiple tiers can work, but only if each option is genuinely distinct. If your three packages feel like the same thing at different prices, the client doesn’t feel empowered. They feel confused. Confusion leads to delay, and delay is often where projects quietly expire.
Most proposals bury the evidence of past work at the bottom, or worse, link off to a portfolio and leave it there. That’s an odd choice when you consider what the client is trying to decide. They’re not evaluating your creativity or your technical capability in isolation. They’re trying to assess whether you can handle their specific situation.
A brief, well-chosen example, placed in direct relation to the problem you’ve just described, does considerably more work than a generic list of past clients. “We helped a professional services firm in a similar situation reduce their sales cycle by restructuring how their website handled first-time visitors” is far more useful than a logo wall. It’s concrete. It’s relevant. It reduces risk in the client’s mind.
The goal isn’t to impress. It’s to reassure. Those are different objectives and they require different material.
There’s a temptation to make proposals longer as a way of signalling effort. A twelve-page document feels like more value than a four-page one. In practice, the opposite is often true. A long proposal asks a lot of a client’s time and attention, and most of what fills those extra pages is padding, repetition or detail that only becomes relevant once the project is underway.
Brevity, done well, is a form of respect. It says: I understand your situation, I’ve thought carefully about the right approach, and I’ve been disciplined enough to give you only what you need to make a decision. That’s a quality most clients will notice, even if they don’t name it.
Aim for enough to be credible and clear, not enough to be exhaustive. If a client needs to read forty pages before deciding to work with you, something has gone wrong well before the proposal stage.
Sending a proposal and waiting is, in most cases, a passive and slightly anxious strategy. A short, direct follow-up message two or three days later isn’t pushy. It’s professional. It gives the client a natural moment to raise questions, flag concerns, or simply confirm they’ve had a chance to look at it properly.
The message doesn’t need to be elaborate. Something like: “Just wanted to check whether you had any questions after reading through the proposal, and whether there’s anything that would be useful to talk over.” That’s enough. It reopens the conversation without pressure, and it often surfaces objections that would otherwise have quietly killed the project.
Proposals don’t close deals. Conversations do. The proposal is a prompt for the conversation, not a substitute for it.
Strip everything back and a good proposal does three things. It shows you’ve understood the real problem, not just the stated brief. It gives the client confidence that your approach is sound. And it makes the decision to proceed feel low-risk and straightforward.
Everything else, the formatting, the testimonials, the process diagrams, is in service of those three things. When elements of a proposal don’t contribute to at least one of them, they’re probably adding friction rather than reducing it.
The uncomfortable truth is that most proposals are written for the person sending them, not the person receiving them. They demonstrate effort, list credentials and cover every technical detail, because that feels safe. But clients aren’t marking you on thoroughness. They’re asking a single, underlying question: do I trust this person to solve my problem? The proposal that answers that question well, concisely and with quiet confidence, is the one that tends to win.
So perhaps the more useful question to ask before you hit send isn’t “have I included everything?” but “does this give them a genuine reason to say yes?”
If you would like any guidence on how to move your business forward, G&G has the necessary skillset to help you manage your business more efficiently and more profitably. if you would like some assistance, please dont hesitate to contact us.
From business planning or Business Administration to assisting with your organisations growth, we are happy to advise and help where we can. Get in touch to start your no-obligation consultation!
Share this article:
Essential cookies required for the site to function. Cannot be disabled.
Cookies that help us understand how visitors use the site.
Cookies used to deliver relevant advertisements.
Privacy Policy Terms of Service
