Guide

How to Write a Business Proposal That Gets Signed

A good business proposal has five parts: what the client's problem is, what you'll do about it, when, what it costs, and what happens if either side wants out. Everything else — branding, extra sections, boilerplate — is decoration around those five things.

1. Overview — frame the problem, not just yourself

Open with what the client actually needs, in their language, before you talk about your company. A weak opener leads with "We are a full-service agency founded in..."; a strong one leads with the problem: "[Client] needs a rebuilt checkout flow that stops losing mobile customers at the payment step." The overview earns the reader's attention for the rest of the document.

2. Scope of work — specific enough that "done" is obvious

Scope disputes are the single most common source of friction in any engagement, and they almost always trace back to a vague scope section. Instead of "redesign the website," write "redesign and rebuild the 8-page marketing site (home, product, pricing, about, blog index, contact, 2 landing pages), responsive across mobile/tablet/desktop, CMS-editable via [platform]." List what's explicitly excluded, too — it prevents "well, I assumed that was included" later.

3. Timeline — milestones, not just a start and end date

A single end date gives the client nothing to check progress against. Break it into milestones with target dates: "Discovery & wireframes — 2 weeks. Design — 3 weeks. Development — 4 weeks. QA & launch — 1 week." This also gives you natural checkpoints to flag scope creep before it compounds.

4. Investment — the number, and how it's paid

State the total fee plainly, then the payment schedule: "Total: $12,000. 50% deposit to begin, 50% due at launch." or "$150/hour, invoiced biweekly." Vague pricing ("starting at...") is fine for a website's marketing page; it's the wrong move in an actual proposal someone is about to sign.

5. Terms — what happens if it doesn't go as planned

Cover how long the proposal is valid (30 days is standard — it should expire, not sit open-ended), what triggers work starting (signature, deposit, or both), and how either side can end the engagement early — with a clause on what's owed for work already completed. This is the section people skip writing and then wish they hadn't.

Common mistakes

• Burying the ask. Get to scope and pricing by page one or two — don't make the reader hunt for what this actually costs.
• No expiration date. A proposal that's valid forever gives you no leverage and complicates pricing changes later.
• Treating it as a formality. See our note on proposals vs. contracts — once a proposal is signed with real terms in it, it typically functions as the actual contract, whether or not you called it one.

What gets a proposal signed instead of stalled

A well-written proposal can still sit unsigned for weeks. These are the things that usually make the difference between the two:

• Make it easy to say yes. Two or three clearly different options, such as a core package and an expanded one, let the client choose how to proceed rather than whether to. Price each option fully so any of them can be accepted as written; an option marked "to be scoped" is a reason to wait.
• Address it to the person who can sign. If the person you've been talking to has to forward the proposal to an owner or a finance contact, find out who that is before you send it, and make them a signer. A proposal with no clear decision-maker stalls in forwarding.
• Answer the objections before they're raised. An assumptions section ("client provides product photos by week two") and a clear list of what's excluded remove the most common reasons a client goes quiet: uncertainty about what they're actually getting and what it will really cost.
• Give one next step, and make it the signature. Ending with "let me know if you have questions" invites a conversation; ending with a signature block and a validity date invites a decision. The proposal itself should be the document they sign, not a prelude to another one.
• Remove friction from signing. Most clients will read and act on your proposal from a phone. If accepting means printing, signing, scanning, or creating an account, some won't do it that day, and "not today" often becomes "not at all."

Following up without guessing

Agree a decision date when you send the proposal, so the follow-up is expected rather than pushy. Before you follow up, check whether the proposal has actually been opened: an unopened proposal needs a "did this reach the right inbox?" note, while one that's been read twice but not signed needs a conversation about what's holding it up. See how to tell if a client read your proposal for what that tracking can and can't tell you. DocuAgree records when each signer views the document and which pages they spend time on, and can send automatic reminders on a schedule you choose, from daily to weekly, until it's signed or the proposal expires.

A quick pre-send checklist

1. The overview names the client's problem in their words.
2. The scope says what's included and what isn't.
3. The timeline has milestones, not just an end date.
4. Every price is a real number, with a payment schedule.
5. There's a validity date and a clear start trigger (signature, deposit, or both).
6. The person with signing authority is a signer.
7. It ends with a signature block, not "let me know."

Frequently asked questions