How to write and follow up a sales proposal

A practical guide to writing a sales proposal that is clear enough to approve and detailed enough to deliver, plus the follow-up steps that help you keep the deal moving without sounding pushy.

By Sophie Bennett · Published 8 October 2026 · Updated 8 October 2026 · 13 min read

A sales proposal should do two jobs at once. It should help the buyer decide, and it should protect you from vague expectations later. If it is too brief, the buyer has to guess what is included. If it is too long or too promotional, it becomes harder to read and easier to ignore.

The best proposals are clear about the problem, the scope, the price and the next step. They show you understand what the buyer wants, but they also set boundaries. That matters because a good proposal is not just a sales document. It is often the first working draft of the commercial relationship that follows.

This guide walks through what to decide before you write, how to structure the proposal, how to price it clearly and how to follow up if the buyer does not respond straight away.

What a sales proposal needs to do before you write it

Before you open a document, make sure you know what the proposal is meant to achieve. You are not writing for a generic audience. You are writing for a specific buyer, usually with a specific decision process and a specific concern: “Will this solve my problem, at the right level of risk, for the right price?”

Clarify the buyer’s problem, the decision-maker and the outcome they want

Start with the basic commercial question: what problem are they trying to solve, and what outcome would make this proposal worth approving?

That sounds obvious, but proposals often fail because they describe the service from the seller’s point of view rather than the buyer’s. A buyer does not need a list of everything you can do. They need to see that you understand the issue they want fixed, the person who will approve it, and the result they are actually buying.

As you prepare the proposal, answer these questions:

• What is the problem from the buyer’s point of view?
• Who will read the proposal, and who will make the decision?
• What does success look like to them?
• What is driving the timing: urgency, budget, a contract renewal or a business change?

Illustrative example: if a company asks you to redesign a website, the real problem may not be “new design”. It may be poor conversion, an awkward customer journey or a site that is difficult for the team to update. Your proposal should reflect the real business issue, not just the visible symptom.

Set the scope, timing and commercial limits you are willing to offer

You should also decide, before you write, what you are and are not willing to include. That means being clear on the scope of work, the timing you can commit to, and any commercial limits that matter to your business.

For example, you may be happy to include two revisions but not unlimited changes. You may be prepared to start next month, but not next week. You may offer a fixed fee only if the brief stays within agreed boundaries.

This is where many proposals go wrong: the seller tries to make the document sound attractive by being flexible on everything. In practice, that creates risk. A good proposal gives the buyer enough choice to move forward, while keeping your own terms realistic.

Gather the information that makes the proposal credible

A credible proposal is based on what the buyer has already told you, not on guesswork. The more clearly you can reflect the brief, the more the buyer feels heard.

Pull together needs from the brief, discovery call or email trail

Use the material you already have. That might be a written brief, notes from a discovery call, a meeting recap or an email thread. Pull out the specific points that matter: goals, pain points, deadlines, stakeholders, constraints and anything that was explicitly ruled in or out.

If the conversation was informal, it is worth sending a short recap before you send the proposal. That reduces the risk of building the proposal on assumptions the buyer never agreed to.

Do not treat every comment as equal. A passing remark about “nice to have” features should not carry the same weight as a clear business requirement.

Separate must-haves from nice-to-haves so you do not overpromise

This is one of the most useful disciplines in proposal writing. Separate the essentials from the extras.

Must-haves are the points that the proposal has to solve for the buyer to say yes. Nice-to-haves are additional features or services that could be useful, but are not essential to the decision.

Keeping that distinction clear helps you avoid three common mistakes:

• quoting for work the buyer did not actually ask for;
• underpricing because you assumed a small request was the whole job;
• creating confusion later when the buyer expects extra work to be included.

Structure a sales proposal that is easy to buy

The easiest proposal to approve is usually the one that reads in the same order the buyer is thinking: problem, solution, scope, cost and next step. Keep the structure simple and make the commercial decision easy to find.

Start with a short summary of the problem and your recommended solution

Open with a brief summary that shows you understand the buyer’s situation and recommends a clear approach. This does not need to be dramatic. It needs to be readable.

A strong opening usually covers three things:

• the problem or objective;
• your recommended approach;
• the outcome the buyer should expect if they approve it.

Example: “You need a supplier who can produce monthly email campaigns that are consistent, on-brand and quick to approve. Our recommendation is a fixed monthly content and design package with a two-stage sign-off process, so your team can keep control without having to manage each campaign from scratch.”

That kind of summary gives the reader a reason to keep going. It also shows that your proposal is built around their priorities, not your preferred way of selling.

Set out scope, deliverables, timings, price and assumptions in plain English

Once the summary is in place, move into the working detail. Use clear headings and short sections for:

• scope of work;
• deliverables;
• timing or project stages;
• price and payment terms;
• assumptions.

Keep the language plain. Replace vague phrases such as “full support” or “end-to-end service” with a specific list of what you will actually do. If the buyer is paying for strategy sessions, drafts, implementation or reporting, say so.

Useful rule: if a line could be read two ways, rewrite it.

Assumptions matter because they explain what your price depends on. For example, the proposal may assume the buyer will provide brand assets, approve copy within a set time, or supply access to existing systems. If those things do not happen, the timeline or cost may change.

Explain what is excluded so you avoid scope creep later

Exclusions are just as important as inclusions. Scope creep happens when the buyer assumes extra work is part of the original deal and you assume it is not. That is avoidable if you state exclusions clearly.

Common exclusions include:

• additional revisions beyond the agreed number;
• new deliverables not listed in the proposal;
• ongoing support after handover;
• third-party costs such as software, printing or media spend;
• work delayed by missing approvals or materials from the client.

This is not about sounding defensive. It is about making the commercial boundaries visible before work starts.

Write persuasively without sounding pushy

A proposal needs to persuade, but it should do so with evidence and clarity rather than pressure. The aim is to make the buyer confident, not cornered.

Use specific outcomes, not vague claims

General claims are easy to ignore. Specific outcomes are easier to judge.

Instead of saying you will “improve efficiency”, explain what that means in practice. For example, you might reduce manual handovers, shorten approval chains or make the reporting process simpler. If you cannot yet measure the result exactly, describe the operational change you expect to create.

This approach also helps the buyer defend the proposal internally. A manager is more likely to support something they can explain clearly to finance, procurement or a director.

Show trade-offs, options and the cost of delay where relevant

Sometimes the buyer is not choosing between yes and no. They are choosing between different levels of commitment. In that case, give them sensible options.

You might offer:

• a basic option that covers the essentials;
• a fuller option with extra support or faster turnaround;
• a phased approach that reduces immediate spend.

Where relevant, explain the trade-off. A lower price may mean slower delivery, fewer revisions or less strategic input. A faster start may need earlier sign-off from the client. Making those trade-offs explicit helps the buyer choose on purpose rather than defaulting to confusion.

If delay creates a known business risk, state it carefully and factually. For example, waiting may push the launch date back or increase the time your team spends on temporary workarounds. Keep it concrete and proportionate.

Keep sentences short and remove jargon that slows the reader down

Busy buyers do not want to decode your language. Avoid jargon, internal shorthand and overlong sentences. If a sentence needs two reads, simplify it.

Useful editing questions:

• Would a non-specialist understand this line?
• Have I used the same term consistently throughout?
• Have I replaced buzzwords with actions or outcomes?
• Can I split this paragraph into two shorter ones?

The best test is practical: can the buyer skim the proposal and quickly find the decision points?

Price and present the commercial terms clearly

Many proposals lose momentum because the pricing section is hard to interpret. Do not bury the price in a long paragraph or mix it with too much explanation.

Choose between fixed fee, day rate or staged pricing

The right pricing model depends on the nature of the work and how much uncertainty there is.

• Fixed fee works best when the scope is clear and you can define what is included.
• Day rate can suit advisory or open-ended work, but it may make the buyer harder to budget.
• Staged pricing helps when the work has distinct phases, such as discovery, delivery and review.

Be honest about the trade-off each model creates. A fixed fee gives certainty to the buyer, but it only works if the scope is controlled. A day rate gives flexibility, but it can feel less predictable. Staged pricing can reduce commitment risk for both sides, especially on larger jobs.

Make payment terms, deposits and expiry dates easy to find

Put the key commercial terms where the buyer can see them quickly. That usually means including:

• the total price or pricing structure;
• when payment is due;
• whether a deposit is required;
• how long the proposal remains open for acceptance.

If the proposal has an expiry date, make it obvious. That protects you from holding prices open indefinitely when your availability or costs may change.

Practical point: if payment terms are important to your cash flow, do not rely on a verbal conversation. Put them in writing in the proposal itself.

Flag any dependencies, approvals or client responsibilities

Some proposals fail because the seller has not made the buyer’s responsibilities visible. If the project depends on approvals, materials, access, feedback or internal sign-off, say so.

For example, the proposal might require the client to provide:

• brand assets or existing documentation;
• access to relevant systems or platforms;
• a single decision-maker or named approver;
• feedback within a stated timeframe.

This helps the buyer see that the work is a shared process, not something your business can control alone.

Make it simple to approve

The best proposal is one the buyer can act on without having to work out what to do next. Approval should feel straightforward.

Use a clear call to action and a named next step

Tell the buyer exactly what you want them to do next. That might be to reply by email, sign the proposal, book a call or confirm the preferred option.

Do not assume they know the process. A proposal that ends with “let us know if you are interested” creates delay. A proposal that says “reply to confirm option B, and we will send the onboarding checklist” gives them a clear path forward.

Add signature, acceptance or reply instructions

Make acceptance easy by giving one obvious route. Depending on your setup, that may be:

• an e-signature section;
• a reply email template;
• a purchase order reference;
• a short acceptance statement with the buyer’s name and date.

Keep the instruction simple. The less friction there is at the approval stage, the less likely the proposal is to stall.

Include a follow-up date if the buyer does nothing

If you know the buyer needs time, set a polite expectation for when you will follow up. This does not need to sound forceful. It simply creates a process.

Example: “If we have not heard from you by Friday, we will check in to see whether you need any changes or have any questions before deciding.”

That kind of line is useful because it keeps the conversation active without making the buyer feel chased.

How to follow up after sending the proposal

Sending the proposal is not the end of the process. A sensible follow-up often matters as much as the document itself.

Time your first follow-up based on the buying cycle and urgency

There is no single right delay. The timing should reflect how quickly the buyer is likely to decide and how urgent the problem is.

If the buyer asked for the proposal quickly and the need is urgent, a short follow-up sooner may be appropriate. If the decision involves several stakeholders, give them enough space to review it first.

Your aim is not to create pressure. It is to stay useful while the proposal is still under consideration.

Ask whether they have questions, need revisions or are comparing options

Good follow-up messages do not just ask “have you decided yet?” They ask something more helpful.

You could ask whether they:

• have any questions about the proposal;
• would like a revised scope or alternative pricing structure;
• need anything clarified for internal approval;
• are comparing options and want to discuss the trade-offs.

This gives the buyer a reason to answer even if they are not ready to commit.

Keep follow-ups brief, useful and focused on decision-making

Follow-up messages should be short. Remind the buyer of the main issue, restate the value in one sentence and offer a useful next step. Avoid repeating the whole proposal.

A simple structure works well:

1. reference the proposal;
2. ask a clear question;
3. offer help with any remaining decision points.

For example: “I’m checking in on the proposal I sent last week. If it would help, I can revise the scope into a smaller first phase or talk through any questions before you decide.”

What to do if the proposal stalls

Even a strong proposal can go quiet. When that happens, do not keep sending the same message. Work out what is actually blocking the decision.

Reconfirm the problem, the decision process and the remaining objections

Often the issue is not the proposal itself. It is uncertainty about budget, timing, internal approval or whether the buyer still sees the problem as urgent.

Ask what has changed, whether the right people have seen it, and what would need to be true for the buyer to move forward. This helps you find the real objection instead of guessing.

Offer a shorter call, revised scope or alternative pricing structure

If the buyer is interested but hesitant, make it easier for them to choose. You could propose:

• a short call to answer questions;
• a trimmed scope for a smaller first step;
• a phased structure that spreads commitment;
• an alternative pricing model if the original one does not fit their budget process.

The point is to reduce friction without discounting automatically. A smaller or better-shaped offer is often more useful than a cheaper one.

Know when to close the file and move on

There is a point where continuing to chase becomes unproductive. If the buyer is not responding, has no clear timeline or keeps postponing without a reason, it may be better to close the file for now.

That does not mean the opportunity is dead. It means you stop spending time on a deal that is not moving and keep the relationship open for future contact.

A simple proposal-and-follow-up checklist

• Confirm the problem, the decision-maker and the outcome they want.
• Set your scope, timing and commercial limits before writing.
• Use the brief, call notes or email trail to build the proposal.
• Separate must-haves from nice-to-haves.
• Summarise the problem and your recommended solution in a few lines.
• List scope, deliverables, timings, price, assumptions and exclusions in plain English.
• Choose a pricing model that fits the work and explain the trade-off.
• Make payment terms, deposits, expiry dates and dependencies easy to find.
• Tell the buyer exactly how to accept.
• Follow up with a brief, useful message that helps them decide.

If a proposal is not moving, review the real objection, offer a practical alternative and then decide whether to leave the door open or close the file.

Useful sources

• GOV.UK — Marketing and advertising law
• ICO — Advice for small organisations