How to Write a Sales Proposal That Gets Signed
A proposal is not where you persuade someone. By the time it lands, the persuading should be mostly done, in the discovery call, in the questions you asked and in the way you restated the problem back to them. The proposal is the document that lets a decision that is already forming become a decision that is made. When a proposal has to do the selling from scratch, it usually fails, because nobody signs a document that surprises them.
This guide covers how to write a proposal that confirms rather than introduces: what to put in it, in what order, how to present price, how fast to send it, how to follow up without nagging, and how to handle the practical details such as deposits and revisions. It is written for small teams who send a handful of proposals a week and cannot afford to lose good ones to silence.
Key takeaways
- Nothing in the proposal should be new. Every item should already have been discussed. If the price or scope would surprise the buyer, you have a conversation to have first, not a document to send.
- Open with their problem in their words. Quote what they told you on the call. It proves you listened and it frames everything after it.
- Show price in context. Put it after the outcomes and scope, next to what it replaces or costs to ignore, and never as a lone number in a corner.
- Send it fast and give it a date. Speed after the call keeps momentum, and a valid-until date turns an open-ended document into a decision.
- End with exactly one next step. One button, one action, no menu of ways to respond.
- Send a link, not an attachment. A web link can be opened, signed and tracked. A PDF in an inbox gets forwarded, lost and printed.
What a proposal is actually for
It helps to be precise about the job. A proposal has four, and none of them is “convince a stranger.”
- Confirm understanding. It shows the buyer that you heard the problem correctly, which is the cheapest trust you can build.
- Make the decision easy to explain. Your contact usually has to justify the purchase to someone who was not on the call. The proposal is what they forward. Write it so a person who has never met you can follow it.
- Remove ambiguity. What is included, what is not, when it happens and what it costs. Disputes later almost always trace back to something that was left vague here.
- Make saying yes simple. The distance between “I agree” and “it is signed” should be as short as you can make it.
The structure that works
There is no single correct layout, but the proposals that get signed tend to follow the same order, because that order mirrors how a buyer thinks: do they understand me, what will I get, what will it cost, what happens next.
| Section | What it does | Common mistake |
|---|---|---|
| Their problem, in their words | Restates the situation and the cost of leaving it alone, using phrases from the call. | Opening with your company history instead. |
| Scope | States what is included and, just as importantly, what is not. | Listing activities rather than deliverables. |
| Outcomes | Describes what changes for them and how you will both recognise it. | Promising results you do not control. |
| Price, with options | Presents the cost in context, with a clear base and optional extras. | A single unexplained number. |
| Timeline | Gives start, key milestones and finish, with what you need from them and when. | Dates with no dependencies stated. |
| Terms | Covers payment, change handling and anything that protects both sides, in plain language. | Pages of legal text before the buyer has seen the value. |
| Next step | One action, with a date. | Ending with “let me know your thoughts.” |
Their problem, in their words
Start with a short description of the situation as the buyer gave it to you, using their phrases. If they said “we keep losing track of who has been quoted,” write that. Include the cost of the status quo only if they supplied a figure; an invented number destroys credibility.
Scope
Describe what you will deliver in terms they can verify. “Weekly reporting” is an activity; “a one-page report every Monday covering these four measures” is a deliverable. Then add a short “not included” list. It feels risky to write down what you will not do, but it is the single most effective way to prevent the disagreement that begins with “I assumed that was part of it.”
Presenting price so it makes sense
Price is the part of the proposal that gets read most carefully and judged least fairly. A number on its own is a number to haggle with. A number placed after the outcomes, beside the scope it buys and the cost of not acting, is a number to evaluate.
Show it in context
Put the price after the buyer has re-read what they are getting. Break it into the pieces they care about rather than hours or internal costs. If the buyer mentioned what they currently spend, or what the problem costs them, put that figure close by, clearly sourced to them. You are not arguing that your price is small. You are helping them compare it with the right thing.
Fixed price or optional add-ons
If the scope is clear and the buyer wants certainty, one fixed price is simple to approve and to explain upward. If there are natural extras, or the buyer is unsure how much to take on, a base price with a handful of optional items lets them shape the total without asking you to renegotiate. A buyer slightly over budget can drop an extra and sign, instead of going quiet. Keep the core offer complete on its own, and keep options few and real.
Set a validity date
Every proposal should say how long the price and availability hold. A date is not a pressure tactic when it is honest, and it should be. It reflects real things: your capacity, the start date you have pencilled in, costs that may change. Pick a window that suits the decision. For a small engagement, one to two weeks is typical; for a larger one that needs several approvals, allow longer. Whatever you choose, state it twice, near the price and near the call to action.
Without a date, a proposal has no reason to be read today. It sits in the “I will get to it” pile, and the longer it sits the more the original conversation fades.
Want to see what your own numbers look like? Start a workspace and price it against the table above.
Start free14-day free trial · No credit card required
Speed: send it while the call is still warm
The time between the discovery call and the proposal matters more than most people allow. The buyer’s interest is at its highest at the end of the conversation and decays from there. Other priorities arrive, a competitor replies sooner, and the urgency that made them take the call quietly fades.
As a working rule, aim to send within a day, and the same day where the scope is simple. That is only possible if you have prepared. Keep a template for each type of work you sell, with the structure and standard terms already in place, so that writing the proposal is mostly a matter of filling in the problem, adjusting the scope and setting the price. If the scope genuinely needs more time, tell the buyer when to expect it and keep that promise.
Following up without nagging
Most lost proposals are not rejected. They are never answered. A follow-up routine is what separates those two outcomes, and it works best when it is planned before you send rather than improvised afterwards.
A simple cadence
- Day of sending: the covering note, with the link and the valid-until date.
- Two to three days later: a short message asking if anything is unclear and offering a brief call.
- Around the midpoint of the validity window: something useful rather than a nudge, such as an answer to a question they raised, a relevant example or a clarified detail.
- Shortly before it expires: a plain note that the proposal is closing on the date stated, and an offer to extend if the timing is the only obstacle.
- After expiry: one final, gracious message that leaves the door open. Then stop.
Reading view signals
If you can see whether and when a proposal has been opened, you can tailor the follow-up instead of sending the same message to everyone. The signals are suggestive, not conclusive, so treat them as prompts to ask, never as proof of intent.
| What you see | What it might mean | A sensible response |
|---|---|---|
| Not opened after a day or two | It may be in a busy inbox, or the email went astray. It may not be a priority yet. | Resend the link by a different route, such as a short text or a different subject line. Do not assume disinterest. |
| Opened once, briefly, then silence | Someone skimmed it, or it was forwarded for a first look. | Ask whether anyone else needs to see it, and offer to walk through it. |
| Opened several times | It is being reread or shared. Interest is real, and something may be unresolved. | Ask directly what is still open. A question is more useful than a reminder. |
| Opened, but nothing for days | They may be waiting on an approval or be uncomfortable with something. | Offer to answer questions about price, scope or timing, in writing or on a call. |
A view count tells you someone opened the page, not who, and email scanners can register opens too. Let the signal change what you ask, not what you assume, and never open with “I saw you looked at it three times.” Ask what they would like to talk through.
Handling questions
A question about a proposal is usually a good sign. People do not interrogate documents they have already dismissed. Treat each question as a buying signal that also tells you what is blocking a decision.
- Answer quickly. A slow answer lets doubt settle. If you need time, acknowledge the question and say when you will reply.
- Answer the real concern. “Is this price fixed?” often means “I need to justify this to someone.” Ask what would help.
- Keep the answer where the decision is. If the answer changes anything, such as scope or timing, update the proposal itself so the signed version matches what was agreed.
Asking for a deposit on acceptance
Taking payment at the moment of signing has two benefits. It confirms the commitment is real, and it removes a second hurdle between agreement and start. Many sales stall in the gap between “yes” and the first invoice, simply because that gap exists.
There are four reasonable models, and the right one depends on the size and risk of the work:
- No payment up front. Reasonable for small, low-risk work where you invoice afterwards.
- A percentage deposit. Common for projects. It scales with the size of the job.
- A fixed deposit. Useful when you have a known start-up cost to cover, whatever the final total.
- The full amount. Suited to smaller fixed-price work, or to a subscription’s first period.
Whichever you choose, state it in the terms and show the exact amount due at acceptance in the proposal, so it is no surprise on the signing page. A deposit amount the buyer first sees at the moment of payment is the kind of surprise this whole guide is trying to avoid.
Common mistakes
Most proposals that go unsigned fail in the same few ways.
The generic template
Template the structure and the terms; write the problem and the scope fresh each time, or the buyer will see the template.
Burying the price or the deadline
Hiding the cost on page six makes the buyer suspicious. Leaving out a valid-until date makes the offer feel optional. Place the price where the logic leads, and state the date.
No single next step
“Let me know if you have any questions, or if you would like to proceed, or if you would like to schedule a call” offers three actions and invites none. Give one: accept here. Questions can be offered as secondary, but the main route should be unmistakable.
The PDF lost in email
An attachment cannot be updated once sent, cannot be signed without printing or a separate tool, and tells you nothing about whether it was opened. A live link solves all three.
How Scalry handles this
Scalry has proposals built into the same workspace as your contacts and deals, so the document is connected to the sale rather than living in a separate tool. A proposal is assembled from blocks and can start from a template, which makes it practical to send quickly after a call. There is also AI assistance for writing proposals, which is useful for a first draft that you then make specific to the buyer.
Each proposal can be linked to a contact and a deal, and carries a currency, a valid-until date and a note that is included in the email sending the link. The client receives a public link. Optional items and quantities can be chosen by the client, so they can shape the final total themselves. When they accept, Scalry captures the signer’s name, email and a drawn or typed signature. Payment on acceptance can be none, a percentage deposit, a fixed deposit or the full amount, and recurring items can create a subscription. If you want it, the linked deal can be marked won automatically on acceptance.
For follow-up, Scalry records what happens: sent, viewed (with a view count and the first and last time it was viewed), accepted, declined (with a reason), paid and voided, along with questions from the client and any reminders that were sent. Revisions are tracked, so you can see how a proposal changed. That gives you the view signals described above in the same place as the rest of the deal.
The honest limit is that Scalry makes the process consistent and visible. It does not write the insight into the buyer’s problem, choose your price or make an unsure buyer decide. That part is still the discovery call.
Questions to ask before you commit
Whichever way you are leaning, these are the questions that change the answer. Work through them against your own numbers rather than anyone's feature matrix — including this one.
- How long does it take from the end of a discovery call to a sent proposal? If it is more than a day or two, find out where the time goes.
- Does every proposal open with the buyer’s problem in their own words?
- Is there a valid-until date on every proposal?
- Do you know whether a sent proposal has been opened? If not, your follow-up is guesswork.
- How many versions of a proposal can exist at once? More than one signable version is a risk.
- How many steps lie between “yes” and a signed, paid proposal? Each one is a place to lose the sale.
If you cannot answer the first three, you are not ready to choose between Scalry and your current way of sending proposals yet — you are still deciding what you need, which is a cheaper problem to solve first.
A two-week plan to get started
In the first week, extract what your last two signed proposals had in common and build a template with the seven sections in order, short standard terms and a place for optional items. Leave the problem section empty so nobody reuses text. Decide your validity window, deposit model and follow-up cadence, and write the covering note once.
In the second week, send the next three proposals through the new process, within a day of each call, with a date and a single next step. Follow the cadence, note which questions come back, and fold repeated ones into the template. Proposal writing improves through small corrections, not one great rewrite.
Frequently asked questions
What should a sales proposal include?
A good proposal covers the buyer's problem in their own words, the scope of work including what is not included, the outcomes you expect, the price with any optional items, a timeline, short and readable terms, and a single clear next step. Everything in it should already have been discussed, so nothing comes as a surprise.
How long should a sales proposal be?
As short as it can be while still answering the buyer's questions. For most small-business sales that means a few focused pages. Move long legal terms or background material behind a link so the main document stays easy to read and easy to approve.
How soon after a discovery call should I send a proposal?
Ideally within a day, and the same day for simple work. The buyer's interest is highest at the end of the call and fades afterwards. Keeping a template for each type of work makes this realistic. If the scope truly needs more time, tell the buyer when to expect the proposal and meet that date.
How do I follow up on a proposal without being pushy?
Plan a short cadence before you send: a covering note, a check after two or three days, something useful around the midpoint, a note before the proposal expires, and one final message. Each touch should give the reader something, such as an answer or a clearer next step, rather than just asking if they have seen it.
Should I put a price in every proposal or offer options?
Always show price, in context, after the outcomes and scope. A single fixed price suits clearly defined work. A base price with a few optional items suits work where the buyer may want to adjust the amount, because they can drop an extra and still sign. Keep the options few and real.
Should I ask for a deposit when the client accepts?
Often yes. Taking a deposit, or the full amount for small fixed work, at the moment of acceptance confirms the commitment and removes a gap in which sales stall. State the exact amount in the proposal so it is no surprise on the signing page.
Why do sales proposals go unanswered?
The usual causes are a generic template that does not reflect the buyer's problem, a price that surprises them, no deadline, several possible next steps instead of one, and attachments that get lost in an inbox. A proposal sent before the buyer is genuinely interested will also go quiet, however well it is written.
Send your next proposal as a link with one deadline and one next step, and see what happens to your reply rate. You can rebuild one real campaign inside Scalry before moving anything else.
Start your free trialSee pricing14-day free trial · No credit card required
Build a workspace, import a real list, and run one campaign end to end before you decide anything.
14-day free trial · No credit card required