How to Write an Agency Proposal That Closes (Without the "We'll Review Internally" Stall)

Why Most Agency Proposals Stall

The proposal is the document the prospect takes into a room you're not in. That's the whole problem. The agency spends a week writing it, sends it over, and then waits while someone else reads it to people who weren't on the call. Most proposals lose the deal at that moment, because the document can't do what the salesperson was doing - diagnose the problem, frame the choice, handle the objection in real time.

So the proposal has to do that work on its own. And almost none of them do. The default agency proposal is a scope document - here's what you'll get, here's what it costs, sign here. That reads fine to the buyer who's already decided. It does nothing for the buyer who is about to forward it to their business partner, their CFO, or their board.

The proposals that close are written for that second reader. They're shaped like a short business case. They tell the reader what the problem is, what the recommendation is, what the outcome looks like, and what it costs - in that order. Not scope first. Not price first. Problem first.

Treat the Proposal as a Memo, Not a Menu

The mental shift that changes everything is this: stop thinking of the proposal as a specification, and start thinking of it as a recommendation. A spec is a list of features the buyer compares against other specs. A recommendation is one person's best professional judgment about what the buyer should do next. Those two documents get read completely differently.

A menu invites deliberation. The buyer looks at the options, compares them against the other three agencies they're talking to, and slides into a multi-week internal debate. A memo invites a decision. The buyer reads it, sees the logic, and either agrees or pushes back on the specific thing they disagree with. The cycle time is shorter because the document is shaped to move, not to cover.

Practically, that means one recommendation, not three tiers. It means a narrative, not a bullet-list of deliverables. It means an author - a real name, a real voice, written as if you were explaining the call to them over coffee. It reads less like a corporate document and more like a sharp advisor's note. That's the voice that closes.

What Goes on the First Page (and Only the First Page)

The first page is the whole proposal, functionally. If the reader isn't bought in by the end of page one, the rest of the document is decoration. I'd treat the first page as the only page that matters and write the rest to support it.

Three things belong on the first page, in this order.

A short restatement of the problem, in the prospect's own language. Not your diagnosis in consultant-speak. Their words, from the call, played back with a bit of shape added. If they said "our pipeline feels random," I'd write "Right now, your pipeline feels random." Verbatim is fine. The point is to show them you listened. A prospect who feels heard has already moved half the distance to yes.

The restatement also does a second job - it anchors the deal around their problem, not your services. Every agency proposal that opens with "About BellPilot" or "Our Approach" has already lost. The prospect doesn't care about the agency yet. They care about whether the agency understands what's broken.

A one-sentence recommendation. A direct statement of what you think they should do. Not "we propose a three-phase engagement consisting of strategy, build, and optimisation." Something more like: "My recommendation is we run a ninety-day outbound build focused on mid-market agencies in your vertical, starting with the list and the message." One sentence, one call, obviously the agency's best professional judgment. Specific enough that the reader knows what they're being asked to agree to.

The headline number, in context of the outcome. Not a price tag in a vacuum. The fee is one number, and next to it is the number it's meant to unlock - the revenue, the pipeline, the hours reclaimed, whatever the real outcome is. "Fee: $18k over ninety days. Target: twenty qualified discovery calls, from which a single closed retainer would pay the fee back five times over." The comparison is what makes the number feel rational. Without it, the fee is just a fee.

Everything else in the document - scope, process, timeline, company background - supports those three things. Not replaces them.

Present One Decision, Not Three Tiers

The three-tier proposal is one of the most common closing killers. Good, better, best. Bronze, silver, gold. It feels helpful to the agency because it gives the client "options." In practice it does two bad things at once. It pushes the client toward the cheapest tier by default, and it tells them the agency doesn't actually know what they should do.

If you present three options, you've just admitted you don't have a recommendation. The client now has to make a strategic call they're not qualified to make, which is exactly the kind of call that triggers a two-week internal discussion about which tier is "the right fit." That discussion almost always ends in either the cheapest one or none at all.

I'd present one engagement. The one the agency actually thinks is right for this client, based on the discovery. If it's useful, I'd mention the alternatives briefly - "we could run this lighter if budget is the constraint, but I don't think it hits the target" - but only as a parenthetical. The proposal itself is one recommendation, confidently offered. That's the shape of a document the buyer can say yes to in one reading.

How to Frame the Price So It Doesn't Land as a Price

The price is the last thing the buyer reads carefully. Everything before it is landing into a mental accounting of "is this worth the number at the bottom." Which means the framing around the number matters almost more than the number itself.

Three moves I'd always make.

• Put the outcome next to the price, every time. Not as a promise, but as a target. "Investment: $18k. Outcome we're aiming at: twenty qualified discovery calls in ninety days." The reader's brain now has two numbers to compare, not one number to accept.
• Use round, confident numbers. $18,000 not $17,850. Rounded numbers signal that the fee is tied to the value of the work, not to an hourly calculation. Hourly-anchored numbers always invite the buyer to negotiate the hours. Round ones invite them to evaluate the outcome.
• Name what's not included, once, clearly. Ad spend, licences, third-party tools, anything the client should expect to pay on top. Naming it in the proposal builds trust because it shows the agency isn't hiding downstream costs. Hiding those costs is the single fastest way to trigger a "we'll review internally."

What I wouldn't do is itemise the fee line by line. Strategy: $4k, build: $8k, optimisation: $6k. The moment the fee is broken into line items, the buyer starts negotiating the line items. The fee should be presented as one number for one outcome. If the buyer wants to understand how the hours shake out, I'd tell them on a call - not in the document.

The Close: Make Saying Yes the Easiest Move in the Room

A proposal that closes leaves one obvious next step, and that next step is small. Not "sign the SOW," not "wire the deposit and we'll get started." Something closer to "I'll send a kickoff invite for Monday - reply yes and we'll get the paperwork moving." The yes should feel like the continuation of a conversation, not a commitment ceremony.

That framing matters because the alternative is a yes that needs approval. The moment the reader has to get permission from someone else to sign the SOW, the deal enters an internal process the agency has no visibility into. Shortening the distance between "I want to do this" and "it's moving" is worth more than any other single optimisation to the proposal.

I'd also add a gentle deadline, framed around capacity, not urgency. Not "this offer expires in seven days." Something more like: "I'm holding capacity on this for the next week before I commit it elsewhere. If the timing's right, reply by Friday and we'll get started." The difference is small but the effect isn't. One reads as pressure. The other reads as a real business managing its own bandwidth.

What Triggers the "We'll Review Internally" Stall

When a prospect says "let us review this internally and come back to you," it almost always means the proposal didn't do its job. It wasn't that they needed more time - it's that the document didn't resolve the decision on its own, so now a second meeting has to happen without the agency present. A few specific things tend to trigger it.

Too many options. Three tiers, or worse, four. The buyer can't pick one on the spot, so the choice gets deferred to a committee.

Vague scope. "Strategy support," "creative direction," "outbound assistance" - language that could mean anything. If the buyer can't answer "what exactly am I buying," they won't sign. They'll ask their partner, who also can't answer it, and the deal dies in the ambiguity.

Pricing without context. A number with no anchor, no outcome, no frame. The buyer has nothing to evaluate it against, so the default evaluation is "it sounds expensive," which is a conversation that can only happen internally.

No clear recommendation. A proposal that reads as a specification of possibilities instead of a recommendation of a path. The buyer can't say yes to a possibility. They can only say yes to a path.

Fix those four and the "review internally" line mostly goes away. Not because the buyer doesn't consult their partner - they will - but because the document does enough work that the partner reads it and says "yeah, that makes sense, let's go." That's the version of the internal review that closes.

What I'd Never Put in an Agency Proposal

A few things that almost every agency proposal includes that I'd strip out entirely.

• A company overview section. Nobody reads it. If the prospect wanted to know about the agency, they'd have asked by now. The space is better spent on the problem.
• A portfolio wall of logos. Logos don't close. One short, specific case study close to their situation closes. If you don't have one, the best move is to name that directly and offer a conversation with a reference client.
• A methodology diagram. The four-phase process with the arrows. It makes the agency feel rigorous and makes the buyer's eyes glaze over. If the process matters, describe it in a paragraph.
• Legalese in the body. Terms and conditions can live at the back or in a separate MSA. They don't belong in the section where the buyer is deciding whether to say yes.
• Hedging language. "We anticipate," "we aim to," "we typically." A confident recommendation uses clean verbs. "We'll build the list. We'll send the sequence. We'll hit the target or we'll tell you honestly why we didn't." Hedging signals doubt, and doubt is the single thing that kills the deal in the internal read.

The Real Test of a Good Proposal

The honest test of whether a proposal is good is whether it can close the deal in a room you're not in. Read it back once the draft is done and ask a specific question: if the prospect forwarded this to their business partner right now, with no call, no context, no sales conversation attached - would the partner know what the agency is proposing, why, and what it costs relative to the outcome? If the answer is yes, the document is doing its job.

If the answer is no - and for most agency proposals it's no - the fix is almost always to cut, not add. Cut the company section. Cut the tier options. Cut the itemised fee. Cut the hedging. What's left is shorter, sharper, and reads like a professional recommendation from someone who actually knows the answer.

The shortest proposal I've seen close a six-figure retainer was two pages. Problem, recommendation, outcome, fee, next step. That's it. The length isn't the point, the shape is. A proposal that closes is shaped like a decision being offered - not a catalogue being presented. Once the shape is right, signing it becomes the obvious next move, and "we'll review internally" stops being the answer you keep getting.