An agency director asks AI to draft a proposal for a new client engagement. He feeds in the project scope, his agency’s methodology, a description of the deliverables, and the proposed timeline. The proposal comes back professional and well-structured. The language is confident. The methodology section is clear. The deliverables are organized logically. He reads it and knows it will not win the work. The proposal sounds like it was written for a client — not for this client. It uses the agency’s language for their methodology rather than the language the client used in their original brief. It emphasizes the deliverables the agency is most proud of rather than addressing the specific concern the client expressed twice during the discovery call. The “why us” section describes the agency’s general capabilities rather than drawing a direct line between those capabilities and the client’s stated problem. The AI wrote a good proposal. He needed a proposal written for a specific person.
Why Proposals Written in Your Language Don’t Win
A proposal that wins work does one specific thing: it makes the client feel understood. Not impressed — understood. The difference between a proposal that gets a yes and one that gets “we’re going with someone else” is often not quality, scope, or price. It is whether the client finished reading the document and thought “they get what we’re actually trying to do.” AI cannot produce that feeling without being told what the client actually said — the exact language they used to describe their problem, the concern they expressed that seemed more important than the others, the outcome they described as success in their own words. Without that input, AI writes a proposal that uses the service provider’s vocabulary for the client’s situation. That vocabulary is often close but never quite right, and clients feel the distance even when they can’t articulate it.
The Brief That Turns AI Into a Proposal Writer
A brief for a client proposal has to transfer the intelligence gathered in discovery directly into the writing instructions. This means including: the client’s own language for their problem — quoted directly if possible, paraphrased closely if not. The specific concern that came up more than once or seemed to carry the most emotional weight. What success looks like in the client’s terms, not in the service provider’s terms. The objection or skepticism that needs to be addressed before they will say yes. The competing proposal they are likely evaluating and how it is probably positioned. This is not abstract strategy. It is the notes from the discovery call, given to AI as a brief instead of stored in a CRM where they influence nothing.
What a Properly Briefed Client Proposal Request Looks Like
Role: You are a senior proposal writer helping an agency develop a winning
proposal for [specific type of engagement].
Context: The client is [role] at [type of company]. Their stated problem: [quote
or close paraphrase of how they described it]. The concern they raised most
prominently: [specific worry — timeline, internal adoption, budget scrutiny].
What success looks like in their words: [how they described a successful outcome].
The objection we need to preempt: [specific skepticism expressed or implied].
What our proposal must not do: lead with our methodology or credentials before
demonstrating that we understand their situation. The client said they have
received "a lot of proposals that sound great but don't address what we're
actually dealing with."
Output: A proposal structure where the client's problem is stated in their
language before our solution is introduced. Every section should answer the
client's question, not demonstrate our expertise. The credentials and methodology
section should come after the solution, not before it.The proposal produced from this brief uses the client’s language. It addresses the concern they expressed. It is structured around their questions rather than the agency’s credentials. It reads like it was written for them.
The Discovery Call Is the Brief
Everything needed to write a winning proposal is collected during discovery. The client’s problem, in their language. The concern they keep returning to. The way they described a successful outcome. The skepticism they have about vendors in this space. This information is gathered during the engagement before the proposal is written — and then almost never transferred into the writing process. The brief is the transfer mechanism. When the discovery intelligence goes into the brief, it goes into the proposal. When it stays in notes, the proposal ends up sounding like every other proposal the client has read — because it was built from generic inputs rather than specific ones. For agencies and consultants who write proposals regularly, Briefing Fox helps structure the briefing step that sits between discovery and writing — ensuring client intelligence drives the proposal rather than sitting unused.
Before Your Next Proposal
Before asking AI to help write any client proposal, find the two or three things the client said that felt most specific and most important — and put them in the brief verbatim. Brief AI with the client’s language, not yours. The proposal that wins is the one that sounds like it was written after someone really listened. Try Briefing Fox free at www.briefingfox.com.