How to write an agency proposal that closes
Lead with the client's problem stated in their own words, then move to scope and price. A proposal that opens with the agency's own credentials answers a question the client did not ask first.
The short answer
- A proposal that opens with the client's problem, in language close to how the client described it during discovery, reads as understanding before it reads as selling. Opening with agency credentials answers a question the client did not ask yet.
- Shorter proposals that clearly cover the problem, the scope, and the price outperform longer ones padded with generic agency background that buries the parts a client needs to decide.
- Pricing should be unambiguous. One number for a fixed offer, or clear line items for a more custom engagement. A vague range with no anchor makes the decision harder, not easier.
- Case studies or examples only help if relevant to this prospect's situation. A single relevant example does more work than several loosely related ones included as filler.
Why leading with credentials is the wrong opener
A common proposal structure opens with the agency. Who we are, what we have done, why we are qualified. This answers a question the client has not necessarily asked yet, especially if discovery has already established some trust. What the client is looking for when they open a proposal is confirmation that the agency understood the problem correctly, before anything about how that problem will be solved.
Opening instead with the client's problem, in language close to how the client framed it during discovery, does two things at once. It shows the conversation was heard and understood, which builds more trust than a credentials section ever will. And it sets up everything that follows, the scope, the approach, the price, as a direct response to that specific problem, rather than a generic offering pitched at whoever happens to be reading.
A proposal structure that leads with the problem
| Section | Content |
|---|---|
| The problem | The client's situation, in language close to how they described it |
| The approach | How this specific problem will be addressed, not a generic service description |
| The scope | What is included, specifically, avoiding vague or open-ended language |
| The price | A clear, unambiguous number or line-item breakdown |
| Next step | One specific action to move forward, not several options that create friction |
What to actually do before sending a proposal
Reread the discovery notes before writing the proposal's opening section. Pull language the client used, rather than paraphrasing from memory. Cut any section that exists only to describe the agency in general terms rather than respond to this client's situation. If a section could be sent unchanged to a different prospect with a different problem, it is not doing enough work in this proposal.
Have someone outside the deal read the proposal before it goes out, ideally someone who was not on the discovery call. If that reader cannot summarize the client's problem after reading the opening section, the proposal has not made it clear enough. The client reading it cold will feel the same gap. This outside check catches assumed context that made sense to whoever wrote the proposal but is not on the page.
Disclosure: SalesCrew is our product. Discovery notes and call summaries logged against a deal give a team the language a prospect used to reference when drafting a proposal, rather than relying on memory of a conversation days earlier. It does not write the proposal itself. The structure and the framing remain a judgment call based on the relationship.
A generic proposal signals a generic engagement
Questions
- How long should an agency proposal be?
- As short as it can be while still covering the problem, the scope, and the price clearly. A long proposal padded with generic agency background buries the parts the client needs to make a decision.
- Should pricing be a single number or broken into line items?
- It depends on the offer's structure. A fixed productised offer often reads cleaner as one number. A more custom or phased engagement can benefit from line items that show what each part of the price covers. Either way, the price should be unambiguous, not a range with no clear anchor.
- Should a proposal include case studies or client examples?
- Only if they are genuine and relevant to this prospect's situation. A generic case study bolted onto every proposal reads as filler. A relevant one, even a single specific example, does more work than several loosely related ones.