How to Write a Proposal That Centres the Client

TL;DR: Most proposals fail because they lead with your credentials rather than the client’s problem. Centre the client’s situation first and articulate their challenge accurately, and you’ll write proposals that make clients feel understood, not sold to.

Most proposals fail before anyone reads the pricing page. They fail because they open with the wrong subject: the person writing them.

Flipping that instinct, genuinely centring the client’s problem rather than rushing to present your solution is one of the more quietly powerful things you can do as a consultant, agency or freelancer. It changes not just how your proposal reads but also how the client feels when they read it.

Why Most Proposals Get It the Wrong Way Round

There’s an understandable logic behind the typical proposal structure. You’re proud of what you do. You want to establish credibility quickly. So you lead with your methodology, your team, your case studies, and your process. It feels professional. It feels safe.

But from the client’s perspective, it can feel oddly impersonal. They came to you with a specific, probably urgent problem, and you’ve responded by talking largely about yourself. That’s not a connection ; that’s a brochure.

The client isn’t buying your process. They’re buying relief from their problem. The proposal that wins is usually the one that makes them feel most understood, not the one with the most impressive credentials.

How to Write a Proposal That Centres the Client’s Problem

This isn’t about flattery or hollow mirroring. It’s a structural discipline. Here’s how to build it properly.

1. Start with the situation, not the solution. Open by articulating the client’s context in specific, accurate terms. What’s the environment they’re operating in? What pressures are they facing? What led them to this moment? If you can describe their situation more clearly than they described it themselves, they’ll lean forward. That’s the effect you’re after.
2. Name the problem with precision. There’s a difference between “you need better marketing” and “your conversion rate suggests the real issue is further up the funnel, not at the point of decision.” One is vague. The other demonstrates diagnostic thinking. Be specific about what the problem actually is, including the parts the client might not have articulated yet.
3. Identify what’s at stake if it isn’t solved. This isn’t about manufacturing urgency. It’s about making the cost of inaction visible. Every significant problem has consequences that compound over time. Name them honestly. Doing so shows that you have thought beyond the immediate brief and are invested in their actual outcomes.
4. Only then introduce your approach. Once the problem is fully established, understood, defined, and given weight, your proposed solution lands in completely different territory. It reads as a direct response rather than a pre-packaged pitch. The client sees their problem reflected in your thinking, which makes your solution feel tailored rather than templated.
5. Connect every deliverable back to the problem. Don’t just list what you’ll do. Explain why each element matters in the context of the specific challenge you’ve identified. “We’ll conduct three stakeholder interviews” means less than “We’ll conduct three stakeholder interviews because the misalignment between your sales and product teams appears to be creating friction at the handover stage.”
6. Let success speak in their language. Define what a good outcome looks like using terms and metrics that matter to the client, not to you. You might measure success by deliverables. They measure it by whether their actual problem gets solved. That’s a meaningful distinction.

The Research That Makes It Possible

None of this works without proper discovery. You can’t write a client-centred proposal if you’ve only had a thirty-minute introductory call and skimmed their website. The quality of your proposal is largely determined before you open a document.

Good discovery goes beyond gathering requirements. It means understanding the organisational context: who has influence over the decision, what’s been tried before, where previous attempts fell short, what internal politics might affect implementation. That kind of knowledge doesn’t come from a standard briefing form.

Ask better questions in your initial conversations. Not just “what do you need?” but “what’s made this difficult to solve so far?” and “how will you know when this is actually fixed?” The answers reveal far more about what should go into a proposal than any brief ever will.

Tone and the Temptation to Over-Sell

There’s a particular kind of proposal language that sounds confident but actually erodes trust. Phrases like “our proven methodology” or “industry-leading expertise” don’t communicate competence; they signal that you’ve stopped thinking about the client and started thinking about your own reassurance.

The more specific and measured your language, the more authority it carries. “We’ve seen this pattern in three similar businesses” is more compelling than “We have extensive experience in this sector. ” One is concrete. The other is wallpaper.

Quiet confidence, the kind that doesn’t need to announce itself, comes from demonstrating understanding rather than declaring it. Show that you’ve thought carefully about this particular problem, and your credibility follows naturally.

A Note on Structure Versus Feeling

Getting the structure right matters, but structure alone won’t do it. The client needs to feel that you actually care about their problem, not that you’ve run their brief through a clever template. That distinction lives in the texture of the writing, the specificity of your observations, the honesty of your framing, the absence of anything that feels generic.

If you can write a section of your proposal and then ask yourself “could this appear, unchanged, in a proposal for a completely different client?” and the answer is yes, it needs reworking. Every meaningful section should be essentially unsalvageable for any other brief.

What This Approach Actually Signals

Beyond the tactical advantages, writing a proposal that genuinely centers on the client’s problem sends a signal about how you work. It tells the client that you listen carefully, that you think before you act, and that you’re more interested in their outcomes than in selling your existing offer. These are precisely the qualities they’re trying to assess when evaluating you.

The proposal isn’t just a document. It’s a rehearsal for the working relationship. If it reads as though you’ve already invested in understanding their situation, the client can imagine what it might be like to have you in the room when things get complicated.

That’s a hard thing to fake. Which, if you think about it, is probably the point.

The Bottom Line

• Open with the client’s situation, not your credentials or methodology.
• Name the problem with precision, including dimensions the client may not have articulated.
• Make the cost of inaction visible before introducing any proposed approach.
• Connect every deliverable explicitly to the specific problem you’ve identified.
• Good discovery is what makes client-centred writing possible; the proposal reflects the quality of the conversations that preceded it.
• Specific, measured language always carries more authority than generic confidence claims.
• If a section of your proposal could appear unchanged in a pitch for someone else, it needs rewriting.

How can G&G assist you ?

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!