A proposal that has been out for three weeks is usually being forgotten, not negotiated.
The data on this is blunt. Proposify's State of Proposals research, built on an audit of close to two million proposals sent through their platform, found that winning proposals run about ten pages across roughly seven sections, and that 43% of the proposals that win are won within 24 hours of being opened. PandaDoc reports a similar shape from their side: roughly one in three documents sent through them gets completed, typically within six hours of sending.
Read those numbers together: a proposal usually gets its yes or no in a single sitting, on the day it's opened. Everything below follows from designing for that sitting. None of it requires our product, or any particular product.
Write the summary as a letter
Most proposals open with an "executive summary" that no executive would recognize: a page of third-person throat-clearing about "the partnership" and "the engagement."
Write a letter instead. One page, addressed to the person who decides, in first person: here's what you told us the problem is, here's what we'll do, here's what it costs, here's when we can start. A decision-maker who reads only that page should be able to say yes.
This is also where the ten-page finding earns its keep. Ten pages is evidence that winning proposals are short enough to finish, not a target to pad toward. If your boilerplate "About us" section is three pages, that's three pages standing between the reader and the signature.
Put the price where a skimmer will find it
The most-read parts of any proposal are the summary and the pricing table. Fighting this is pointless; design for it. One pricing table, one total, and if you offer options, three at most, labeled by outcome ("Launch site" / "Launch site + blog") rather than metal tier.
An opinion you're free to disagree with: hiding the price until a call is a tax on both sides. It filters out the clients who would have said yes without a call, and it signals the number can't survive being read alone.
Placeholders are where trust dies
Everyone who sends documents has shipped a [CLIENT NAME] at least once. It reads as a small thing, but it tells the reader how much of the document was written for someone else, at the exact moment they were deciding how much of it to believe.
Three habits fix most of it:
- Never type square brackets by hand. Use your tool's fields, tokens, whatever it has: anything a machine can find and flag. Handwritten brackets are invisible to every check except the client's eyes.
- Give every number one source of truth. The total should exist in one place, referenced everywhere else. The classic silent killer is a summary that says ₹4,80,000 and a pricing table that, after one late edit, says ₹5,20,000.
- Proofread the names last, separately from the prose: client name, your name, dates, addresses. The prose gets read; the names get checked.
Make the signature a click, not a project
Consider what "print, sign, scan, and email back" asks of a person in 2026: access to a printer, a working scanner or a scanning app, and ten minutes of attention. That's a next-day round trip in practice, often the difference between closing inside that first-day window and drifting past it.
Signature mechanics that consistently help:
- Name the signers before you send: "Signed by Priya Sharma, Director." Asking a company to "sign where appropriate" invites a two-day internal search for the appropriate.
- Send each signer a personal link. One shared PDF to a group means everyone assumes someone else owns it.
- Put the ask in the email body too. "The proposal is attached. If the scope works, you can sign at the link in two minutes." Don't make them discover the signature page on their own.
- Say what signing triggers. "Once signed, we book your kickoff for the following Monday." A signature that starts something concrete gets treated with more urgency than one that files something away.
For most B2B service agreements, a typed-name e-signature with a decent audit trail is legally solid in most jurisdictions, India, the US, and the EU included. (The exceptions and the fine print deserve their own post; we've written one.)
Answer fast, follow up precisely
Proposify's research has one more number worth internalizing: when prospects get answers to their questions within four hours, close rates run 35% higher than when answers take more than a day. The question a client asks after reading your proposal is the deal speaking. Treat it like an interrupt, not a ticket.
And when a proposal does go quiet, follow up once, about 48 hours in. Skip "just checking in"; that message transfers the work of remembering back to them. Re-send the link with something resolved: "Re-reading our conversation, I realized the timeline didn't account for your board meeting on the 12th. Updated version attached, same link to sign."
The honest summary
Short enough to finish in a sitting. A summary that's a letter. A price a skimmer can find. No hand-typed placeholders. A signature that's one click with a named owner. Answers in hours, one precise follow-up.
None of this needs special software: a word processor and any e-signature tool can do all of it. We built Triplewave because doing it every week, on brand, without shipping a single bracket, is where small teams wear down.