How to create a proposal that actually gets signed

A proposal is not a writing task. It is the written record of a conversation the client already had with you. The proposals that get signed are the ones drafted straight from accurate discovery notes, so the scope, the language, and the pricing all mirror what the buyer actually said, then sent fast, kept short, and made trivially easy to accept. Almost everyone treats the proposal as a document-design problem (cover pages, fonts, swapping the logo on a template). The real advantage sits upstream and downstream: listen well on the call, then turn what you heard into a tailored proposal within hours, not days. The generic, slow, vague-scope proposal is the default failure mode this guide exists to kill.

What a proposal actually is (and how it differs from a quote, estimate, or RFP)

A proposal sells your approach and the value of working with you. It is persuasion, not arithmetic. People conflate it with a quote, an estimate, or an RFP response, then wonder why the document feels off. Here is the difference that matters.

Most B2B proposals are solicited: they follow a discovery or sales call where the buyer described a problem and you said you could help. Unsolicited proposals exist (you pitch someone cold), but they convert far worse because you are guessing at the problem instead of repeating it back. That distinction is the whole thesis of this guide. A great proposal is not invented at the keyboard. It is transcribed from a conversation you already had.

Step 1: win the proposal on the call, before you write a word

The proposal is downstream of the call. If the call went well, the document mostly writes itself. If the call went badly, no template saves you. So the first step in creating a proposal happens before you open a document.

On a discovery call, the best sellers talk a fraction of the time and listen the rest. Your job is to leave with the raw material for every section of the proposal:

• The problem, in the client's own words (you will quote this verbatim in the executive summary).
• Their definition of success and how they will measure it.
• Who is involved in the decision and who signs.
• Budget reality and timeline.
• The objections and worries they surfaced, so you can pre-answer them.

The trap is relying on memory and a few scribbled notes. You will lose the exact phrasing, mishear the budget, and forget which stakeholder cared about which thing. Then you write a generic proposal because generic is all you can remember.

This is where a meeting notetaker earns its keep. Scribbl records, transcribes, and summarizes your Google Meet calls (Zoom and Microsoft Teams are covered on the Team plan) with no bot sitting in the meeting, so you walk away with a clean transcript and a summary instead of fragments. You pull the scope, the pain points, and the exact quotes straight from the summary and drop them into the proposal. The summary is the raw material for the scope and executive-summary sections; you are mirroring the client, not inventing. If you want to run better discovery in the first place, start with a client meeting agenda and the top objectives for a first client meeting.

End every discovery call by confirming the next step out loud: what you will send and by when. "I'll have a proposal to you by Friday morning" sets a deadline you can actually hit, because the transcript means you are not starting from a blank page.

Step 2: use the structure that actually wins (keep it to about 7 sections and 11 pages)

Here the data is blunt: shorter wins. Proposify's State of Proposals 2024 analyzed more than 1.28 million proposals and found that winning proposals averaged 11 pages and 7 sections, while losing proposals averaged 13 pages and 8 sections. Length is not thoroughness. Padding signals that you do not know what matters.

Use these seven sections, in order:

1. Cover page with the client's name and yours. One line, not a brochure.
2. Executive summary, the only section many buyers fully read. Their problem and your answer, in their words.
3. Problem and goals, restated exactly as they said them on the call.
4. Proposed solution and approach, how you will get them the outcome.
5. Scope and deliverables, including what is explicitly out of scope.
6. Timeline and milestones, with real dates.
7. Your investment (pricing), plus proof (a case study or testimonial) and a clear next step and signature.

Open with the client's problem, not your company history. Nobody signs a proposal because your agency was founded in 2014. They sign because the first paragraph proves you understood them better than the last three vendors did.

Step 3: write the executive summary and scope so it mirrors the client

The executive summary is the highest-impact paragraph in the whole document. Proposify's data found that customizing roughly 30% of the executive summary to the specific client correlated with a 50% higher close rate, with bigger effects on bigger deals. That is not "change the company name." It is using their language, their numbers, and the goal they told you about.

Here is a copy-pasteable skeleton. Keep the placeholders specific and pull them from your call notes.

Executive summary

[Client] is [one-line description of their situation], and right now
[the specific problem they described on our call, in their words]. That
is costing you [the consequence they named: lost revenue, wasted hours,
churn].

We propose [the outcome, not the activity]. Over [timeframe], we will
[the 2-3 things you'll actually do] so that [the success metric they
told you matters]. We've done this for [comparable client], who saw
[result].

This proposal covers scope, timeline, and investment. If it matches
what we discussed on [day of call], you can accept it below and we'll
start on [start date].

Scope is where money leaks. Vague scope ("Marketing strategy") invites scope creep, payment disputes, and stalled signatures. Name exactly what you deliver, in what format, how many rounds of revisions, and what is not included.

Scope of work

In scope:
- [Deliverable 1], delivered as [format], by [date]
- [Deliverable 2], including [up to N rounds of revisions]
- [Deliverable 3]

Out of scope (available as add-ons):
- [The thing they'll ask for later: extra revisions, new channels,
  ongoing retainer]
- [Anything dependent on a third party or the client's input]

Assumptions:
- [Client provides X by Y date; delays shift the timeline accordingly]

That "out of scope" block is the single cheapest insurance you can buy. If you want a deeper playbook, read how to prevent scope creep and how to manage client expectations. Write the whole thing in plain language. Cut the jargon. A confused buyer does not sign.

Step 4: price for a decision, not for confusion

Nearly every proposal includes pricing (Proposify reports about 98% do), so the question is not whether to show the price but how. Three rules.

First, rename the section. "Your investment" beats "Cost" because it frames the number against the outcome. Tie the price to the result you promised in the summary, not to your hours.

Second, give options. A single take-it-or-leave-it number forces a yes/no decision. Two or three tiers (or a base scope plus add-ons) changes the question from "do I buy?" to "how much do I buy?" Proposify found that interactive pricing tables nudged close rates up by roughly 6% versus static pricing.

Your investment

Option A - Core            $6,000 / month
  [The minimum scope that solves the problem]

Option B - Core + Growth   $8,500 / month   (recommended)
  Everything in Core, plus [the add-on they hinted they wanted]

Payment: [50% to start, 50% on delivery] or [monthly on the 1st].
This pricing assumes [the scope and timeline above] and is valid for
[30 days].

Third, avoid open-ended ranges like "$3,000 to $8,000." A range tells the buyer you have not thought it through, and they will anchor to the low end while you planned for the high end. State the schedule, state what the price assumes, and discount strategically rather than reflexively.

Step 5: make it trivially easy to accept (and legally sound)

The most common own-goal in proposals is making the buyer work to say yes. A PDF they have to print, sign, scan, and email back adds days of friction at exactly the moment momentum matters most.

Build acceptance right into the document. E-signed proposals were 3.3 times more likely to close and closed about 30% faster in Proposify's dataset. Pre-signing your own side of the agreement (your signature already in place when it arrives) lifted close rates by another 26%, because it signals you are ready and removes a blank field. One-click acceptance, or accept-and-pay in the same flow, beats every print-sign-scan workflow.

E-signatures are binding. Under the U.S. ESIGN Act (15 U.S.C. 7001), a signature or contract "may not be denied legal effect, validity, or enforceability solely because it is in electronic form." You need genuine intent to sign and consent to do business electronically. For required consumer disclosures specifically, 7001(c) adds affirmative-consent and paper-copy-notice steps. For a normal B2B services proposal, a clear "accept" action plus a name and date holds up.

A signature is what turns an offer into a binding agreement, so do not bury it. The last thing the buyer sees should be a button, not a paragraph of legalese.

Step 6: send fast, then follow up like the winners do

Speed beats polish. Proposify found the average proposal takes about 17 minutes to create and half are opened within roughly 74 minutes of sending, while the average time from first open to close is about 51 hours. Translation: buyers move within two days of opening, so a proposal that arrives a week after the call has already lost the room.

Two follow-up moves move the needle. First, get the proposal in front of every decision-maker: when multiple stakeholders viewed a proposal, Proposify found close rates nearly doubled. Second, actually follow up. Only about 7% of sellers used automated reminders, and the ones who did were roughly 10% more likely to close. Send the proposal within hours of the call (the transcript-to-draft workflow makes that realistic), then use a real cadence. For the follow-up itself, lift templates from our sales follow-up email templates and the guide to after-meeting emails to clients.

Tools and templates: where software helps, and where it doesn't

Two different jobs, two different tools, and people buy them backward.

Proposal software (PandaDoc, Proposify, and others) handles the delivery half: templating, interactive pricing, e-signature, and open-tracking. PandaDoc reports an 18% close-rate lift, and for its top 10% of users the median time from creating an agreement to sending it was three minutes (per its proposal-software page, February 2023). That speed is real and worth having. For a deeper tool comparison, see proposal software and the project-specific angle in how to create a proposal for a project.

But none of that fixes a proposal built on bad discovery. Templating a generic doc just gets you to "wrong" faster. The upstream half (accurate notes from the call, captured verbatim) is the part most teams skip, and it is the part that decides whether the scope and summary actually match the buyer. Pair a meeting notetaker for the discovery with proposal software for the delivery. If you sell for a living, Scribbl for sales keeps your discovery calls on record so every proposal mirrors the conversation; agencies running proposals across many clients can see how it fits at Scribbl for agencies. Either way, start by getting better at taking meeting notes and turning calls into action items.

Frequently asked questions

How long should a proposal be?

Shorter than you think. The winning proposals in Proposify's 1.28M-proposal dataset averaged 11 pages and 7 sections, versus 13 pages and 8 sections for the ones that lost. Aim for roughly seven focused sections and cut anything that does not help the buyer decide. Length reads as padding, not diligence.

What is the difference between a proposal and a quote?

A quote is a fixed price for an already-defined scope, usually with a validity window. An estimate is a ballpark, not a commitment. An RFP or RFQ is the buyer's request that you respond to. A proposal is the persuasive document that sells your approach and value and then asks for the yes. If scope is already settled and all the buyer needs is a number, send a quote. If you are still selling the approach, write a proposal.

Are electronic signatures legally binding on a proposal?

In the United States, yes. The ESIGN Act (15 U.S.C. 7001) says a signature or contract cannot be denied legal effect solely because it is electronic, as long as the parties intend to sign and consent to transact electronically. That is why e-sign acceptance is both faster and safe for standard B2B proposals. Required consumer disclosures have extra consent rules under 7001(c), but a normal services proposal does not trigger those.

How fast should I send a proposal after the call?

Same day if you can, within hours ideally. Half of proposals get opened within about 74 minutes of sending, and the average deal closes around 51 hours (just over two days) after the first open. Buyers act on the momentum from the call, and that momentum decays fast. Drafting from a transcript instead of a blank page is what makes same-day delivery realistic.

What is the single biggest proposal mistake?

Sending a generic, slow proposal with vague scope. It is the failure mode three different data points punish at once: customizing the executive summary lifted close rates 50%, speed-to-send tracks with closing, and ambiguous scope invites disputes and stalls. Swapping a logo onto a template you wrote for someone else is not personalization, and buyers spot a recycled document instantly. Mirror the actual conversation, send it fast, and make the scope unmistakable.