Guide
How to Write a Business Proposal (With Examples)
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.
From proposal to signed deal
Once the document looks right, the fastest path from "looks good" to "signed" is sending it for e-signature directly rather than a "reply to confirm" email — the latter is where good proposals quietly die in someone's inbox. A proposal that's already built with e-signature fields in mind gets signed faster than one that requires a separate follow-up step.