How to Write a Sales Proposal That Closes Deals: Structure, Template, and Mistakes

A rep emailed the client a five-page PDF, and the deal stalled for two weeks. Sound familiar? In the CRM it shows up as a "Proposal Sent" stage where leads sit longer than they do on every other stage combined.

At Brutal Marketing we build sales departments end to end, and we keep seeing the same picture: a company invests in traffic, in scripts, in training — and then, at the finish line, sends a sales proposal the client opens once and closes for good. Not because it's expensive. Because they didn't understand what was being offered or why they should pay you specifically.

Below is a breakdown of how to build a proposal that moves the deal forward instead of freezing it. The block-by-block structure, a ready-made frame you can copy, the mistakes that cost money, and the techniques that lift your share of closed deals. No filler about "an individual approach" — only what we use ourselves.

Let's deal with the cause first, otherwise any structure is just a pretty wrapper around nothing. A proposal fails not because of the design and not because of the price. It fails because of three things we see in almost every sales department we audit.

Cause one: the proposal is about you, not the client
The first page is a logo, a founding year, "on the market since 2012," "a team of professionals." The client reads this and doesn't find themselves anywhere. They came in with a specific pain, and you hand them a contractor's résumé. Attention is gone in the first ten seconds.

Cause two: the proposal was sent at the wrong time
A proposal isn't a tool for discovering the need — it's a tool for locking in an agreement. If a rep sends the document before understanding the client's task, their budget, and their decision criteria, they're simply guessing. And guessing reads instantly: a set of services with no link to the actual situation.

Cause three: silence after sending
The rep drops the file and waits. The client doesn't reply — not because they said no, but because something else is on fire. Without a next step written into the proposal itself and backed by a call, the deal just cools down. In our experience, up to 40% of "lost" deals at the proposal stage are lost right here — not on an objection, but on silence.

The fix at the level of causes sounds simple but takes discipline: write the proposal after qualification, tailor it to that specific client's goals, and always bake in a next step. Everything else in this article is about how to do that by hand.

Before rewriting the document, let's agree on the metric we'll measure results by. Close rate is the share of deals taken to payment out of the proposals sent or qualified leads. If 5 out of 20 proposals get paid, that's 25%.

Here's the source of a common confusion: many people calculate close rate against all inbound leads, get a "terrible" 5–8%, panic, and start pushing discounts. But if your pipeline isn't filtered for unqualified inquiries, a low number isn't a proposal problem — it's a qualification problem. Clean the intake first, then measure the output.

What counts as a working close rate? For B2B deals with a meaningful average check, the benchmark is 25–40% from qualified leads at the "proposal sent" stage. The numbers vary heavily by niche and sales-cycle length, so the absolute value matters less than the trend. We don't ask "is this a lot or a little" — we ask whether the number moves after a change.

A real example from our practice: at a company selling industrial equipment, the close rate at the proposal stage sat at around 12%. We didn't touch the price. We rewrote the proposal's structure, added three packages instead of one, and baked in a mandatory follow-up call on day three. Two months later the figure rose to 19%. Same team, same product, same price — a different document and a different routine.

One thing matters here: a proposal isn't written once and for all. It's a tool you test. Change one element at a time — the headline, the package structure, the wording of the next step — and look at the number a month later. If you change everything at once, you won't know what worked. The discipline of "one change, one measurement" turns an average template into a strong one over six months, because you keep only what genuinely moves sales.

To measure this honestly, you need a system that records every send and every stage. Without one, you're judging sales on gut feel. How to build a funnel where you can see exactly where deals get stuck, we covered in our breakdown of the digital sales funnel and how to set it up.

This is the core of the article. What follows is the proposal broken down block by block, in the order the client reads it. The logic is the same throughout: the problem the block solves, the reason most people get it wrong, and how to do it right.

A quick note on length up front. A working proposal for most deals is one to two pages of dense text or a single screen of a presentation — not a ten-page document. The reason is simple: the decision-maker doesn't read, they scan. A long document doesn't impress, it scares off. Anything that doesn't help them decide works against you.

The first thing the client sees has to be about them. Not about you, not about the market, not about "today's realities." About their task, their numbers, their pain.

The problem this block solves: in the first few seconds the client decides whether to keep reading. If they don't recognize their own situation, the document closes. The reason most people botch the first screen is that reps start with a self-introduction, because talking about yourself feels easier and safer.

How to do it: open with the client's task in their own words — the ones you heard on the call. "You're losing up to 30% of your inquiries because your reps can't call back within the hour" — that's a first screen. Then a short confirmation that you understood the goal: not "implement a CRM," but "cut the response time to an inquiry and raise the lead-to-deal conversion." How to run a conversation where the client surfaces their own bottlenecks, we describe in our guide to leads, lead generation, and lead management as the backbone of a sales system.

Let's show it by contrast. A weak first screen: "Company N is a market leader in automation, 12 years in business, 300+ projects. We offer you a CRM implementation." The client found themselves in exactly zero of those lines. A strong first screen for the same client: "Three of your reps handle about 200 inquiries a month by hand, and some of them get lost because there's no one to call back in time. Below is how to close that gap in three weeks and stop losing paid inquiries." In the second case, the client understands from the first line that the document is about their money, not someone else's accolades.

If the client's task is complex and has several knots in it, don't try to list them all at once. Name the single pain that hurts most and build the proposal around it. You'll add the rest at the next step. One precise hit beats ten blurry ones.

Once the client has seen their own task, they're waiting for the answer: how exactly will you close it. And this is where the catalog usually begins.

The problem: the rep dumps the company's entire service list, hoping something fits. The client sees twenty items and can't tell which ones are about them. The reason is fear of missing a sale — "what if they need this too." The result: the main thing gets diluted.

How to do it: describe the solution as a path from the client's current point to their goal, not as a list of what you can do. One or two paragraphs on what you do, and always on what result it produces in their situation. Not "funnel setup, telephony integration, training," but "your reps see every inquiry in one window and lose none of them, because the system itself creates the task to call back."

Speak the language of results, not features. The feature is "end-to-end analytics." The result is "you see which ads bring in money and which ones burn budget" — and how to wire that up is exactly what end-to-end sales analytics is for. The difference is that a feature is bought by a techie, while the result is what the owner pays for.

If several people with different interests are involved in the deal — which is the norm in B2B — the solution should be framed so each of them finds their piece. How to define who you're really selling to and tailor the message to multiple decision-makers, we covered in our guide to building an effective B2B messaging strategy.

One of the most underrated techniques. Most proposals contain exactly one offer at one price. And that's a mistake.

The problem: when the client has one option, they have two decisions — "yes" or "no." And they pick "no" more often, because there's no point of comparison, nothing to anchor the price against. The reason reps give a single option is that it's simpler to calculate and simpler to explain. But what's simple for you turns into a loss for the deal.

How to do it: give three packages. This changes the question in the client's head from "buy or not" to "which of the three to take." The classic layout:

1. Basic — covers the minimum task, looks affordable, serves as the reference point.
2. Recommended — what you actually advise. Highlight it visually and mark it as "recommended." Most clients land here.
3. Extended — pricier and fuller. It doesn't have to sell often; its job is to make the recommended package look reasonable by contrast.

This works thanks to the anchoring effect: the extended package sets the upper bound, and against it the recommended one looks like the sensible choice. A bonus: three options keep the client from shopping around — they have no reason to look for an alternative, it's already on the table.

Just don't turn it into manipulation. Each package has to be honest and meaningful. A client who bought "recommended" and a month later realized they were sold air in the "basic" tier won't come back, and they'll tell others.

The client isn't paying for a service. They're paying for the gap between "how it is" and "how it will be," expressed in money or time.

The problem: the proposal states a price but doesn't explain why it's justified. The client is left alone with the number and compares it only to zero — that is, to the option of doing nothing. The reason: reps are afraid to "push with numbers," or they simply never ran the math for this specific client.

How to do it: show the cost of inaction and the return on the solution. If the client loses 30% of inquiries, the average check is $1,000, and 200 inquiries come in per month, the loss is 60 inquiries, some of which would have become deals. Even at a modest conversion rate, that's hundreds of thousands a month. Against that backdrop, your implementation price stops being an expense and becomes an investment with a clear payback.

Calculate in the client's terms: payback, time to recoup the investment, additional revenue. A single line — "at current figures the solution pays for itself in 2.5 months" — works harder than a paragraph of advantages. If you don't have exact data, use a conservative estimate and label it honestly — even a cautious calculation beats none.

A small move that strengthens the justification: present the price not as one number but in comparison with the loss. "The implementation costs X. Right now you're losing roughly X every month on unhandled inquiries" — the client sees that inaction is more expensive than action. That defuses half of the price objections before they're even raised. And if you've given three packages, the math is done for the recommended one — it becomes the reasonable middle between "too little" and "too expensive."

The most underrated block, and at the same time the cheapest to execute. Most proposals end with a price and silence.

The problem: the client has read it, understood everything, agrees — and does nothing, because they don't know what to do next. The reason: there isn't a single pointer to the next step in the document, and a person defaults to inaction.

How to do it: end the proposal with a concrete action and a deadline. Not "get in touch with us," but "confirm your chosen package by Friday — we'll reserve the project start for next week." Set a follow-up date right in the document: "On Wednesday I'll call to answer your questions." That's not pressure, it's removing uncertainty.

It works well to leave room for a signature or a confirmation button at the bottom of the proposal. The document turns from an "offer" into the first step of a contract — it's psychologically easier for the client to tick a box than to start negotiations from scratch.

And the main thing — the next step has to happen in reality, not just on paper. A rep who promised to call on Wednesday and did call closes noticeably more. So these promises don't get lost, they're logged in the system as tasks with deadlines; how to use a CRM for follow-ups and manager control without chaos, we walk through in our piece on 7 ways small businesses actually use a CRM to move revenue.

Let's pull it all into one frame you can copy and adapt to your niche. This isn't a rigid form, it's the logic of the blocks in reading order.

Note the social-proof row — we haven't covered it separately yet, but it matters. One short case from the same niche as the client, with a concrete result ("a similar company cut its inquiry response time from 4 hours to 15 minutes"), convinces more than a wall of testimonials. The reason is that a client projects someone else's result onto themselves only when they recognize their own situation in the case.

Keep the document itself to one or two pages. If you really want to attach details, move them into a separate appendix so the main proposal stays short and scannable.

Let's gather separately the things that most often kill a deal. For each mistake — why it happens and what to replace it with. These are the rakes we keep stepping on when we audit sales departments.

Mistake 1. Talking about yourself instead of the client
Comes from habit and from the fear of looking insufficiently solid. Cured by moving everything "about the company" to the end or into an appendix, and putting the client's tasks on the first screen.

Mistake 2. Jargon and a glut of terms
Technical terms create an illusion of expertise, but the decision isn't always made by a technical person. Write so the owner understands, not just the IT director.

Mistake 3. A discount instead of value
"I'll give a discount — it'll close faster" is the most expensive myth in sales. A discount devalues the product and trains the client to haggle. Push on price and the margin walks out while loyalty never shows up. Instead of a discount — justification and options.

Mistake 4. A single option to choose from
Turns the decision into a binary "yes/no." The fix is three packages, as covered above.

Mistake 5. No next step
The document ends and the deal hangs. The fix is a concrete action and a contact date inside the proposal.

Mistake 6. A proposal before qualification
The rep sends the offer without learning the budget and the criteria. It's a shot in the dark. The fix is qualification first, document second.

Mistake 7. Send and forget
Without follow-up, the lion's share of warm deals is lost. The fix is a cadence of touches baked into the CRM.

Behind many of these mistakes is not a lazy rep but the absence of a standard: everyone writes the proposal however they know how. When there's no single template and no oversight in the department, proposal quality swings from deal to deal. How to bring order to this without becoming an overseer, we covered in our material on sales department quality control.

Another common storyline: the client objects right after receiving the proposal — "too expensive," "I need to think," "send me more info." That's not a refusal, it's a signal that some block didn't land. How to handle these reactions calmly and on point sits inside our breakdown of the B2B negotiation mistakes that quietly cost six-figure contracts.

A separate layer that owners often miss: the same offer can't be sent to everyone. A proposal for a client you spent an hour on the phone with and a proposal for a cold contact from a campaign are different documents, even though both are called a sales proposal.

The problem: the company makes one universal template and sends it into both situations. To the warm client it feels dry and impersonal, to the cold one it's too long and unclear. The reason is saving time — one template is easier to maintain. But a universal proposal loses with both recipients.

A warm proposal is written after a conversation in which you've already pulled out the pain, the budget, and the criteria. Here you can go straight into the client's task in their own words, give three concrete packages, and set a next-touch date. The document is short and precise, because you've already prepared the ground by voice.

A cold proposal works on different logic. You have no data on the client, so the first screen is built around the typical pain of their segment, not a personal task. The goal of that document isn't to close the deal — it's to get a reply and move the conversation into a live dialogue. So a cold proposal carries fewer price details and more about the result, and its main call isn't "pay" but "let's discuss on a short call."

How to do it in practice: keep two frames. The warm one — detailed, with packages and a payback estimate. The cold one — short, with one segment-level pain and a soft invitation to talk. Don't try to sell the full check with a cold email: its job is to open the door, the conversation does the rest. Moving a cold contact into a live dialogue is its own skill — we break down the channels and approach in our piece on what conversational marketing is and how it helps your business.

On segmentation specifically: the more precisely you split clients into groups by niche, size, and task, the fewer "universal" proposals you have and the higher your response rate. One template across three segments almost always loses to three templates across three segments — even if all that changes is the first screen and the set of cases.

A separate point owners often overlook: a proposal emailed without a word and a proposal presented out loud are two different tools with different conversion rates.

The problem: the rep drops a PDF into a messenger with the caption "here's our offer, take a look." The client opens it without you, without context, alone with the price — and interprets everything for the worse. The reason: it's faster and there's no need to schedule a meeting.

How to do it: present the proposal by voice whenever you can — on a call or in a meeting, walking the client through the document. You see the reaction, handle objections on the spot, and control what they're looking at. The file then stays as a reminder after the conversation, not as a replacement for it. The document and the spoken delivery have to work together, and the proposal is only ever as strong as what you learned before writing it.

A good proposal template solves half the task. The other half is making sure no sent proposal ever drops off the radar. This is where the system comes in.

The problem: even a perfect proposal is useless if the rep forgot to call back, lost the thread, or doesn't remember which option they offered the client. You can't hold this in your head or in spreadsheets, especially when there are dozens of deals. The cause of the losses is the human factor, and willpower doesn't cure it.

How a CRM solves it: every sent proposal becomes a deal at a specific stage with a follow-up task and a deadline. The system itself reminds the rep to call on Wednesday, stores which package was offered, and shows how many deals have been stuck at "proposal sent" longer than they should. The manager sees the bottleneck not by feel but by the numbers — and that visibility into where money leaks is exactly what we lay out in how small and medium businesses profit from a CRM, in numbers.

For the owner this means control without micromanaging: no need to stand over a rep, it's enough to watch the funnel. For the head of sales it's a tool that turns "I should call back" into a task with a reminder. Which system to choose for your size and niche we help you figure out as part of a CRM implementation.

The connection is simple: a working proposal template plus a system that carries the deal after sending. The first raises proposal quality, the second keeps proposals from getting lost. Together they're what moves the close rate.

We'll review your current process, build a sales proposal structure for your niche, and configure the CRM so no deal gets lost after the proposal goes out.

Book a sales-department review and CRM implementation with Brutal Marketing at form below — we'll show you on your own numbers where you're losing deals and how to raise your close rate.