A business proposal is the document that turns a B2B opportunity into a signed contract — but only if you write it for the right reader. The mistake almost every templated business proposal makes is treating solicited (RFP response, requested pitch) and unsolicited (cold proposal to a prospect you identified) as the same document. They aren't. The structure is similar but the emphasis flips. Below is the nine-section structure that works for both, with the specific shifts to make depending on which one you're writing.
This is the long-form B2B version. If you're writing a tighter freelance engagement proposal (response to a discovery call, defined scope, 2-4 pages), the structure is simpler — see the project proposal guide for the eight-section freelance version. This guide is for the longer business-pitch document: capabilities pitches, partnership proposals, multi-engagement consulting frames, RFP responses.
Solicited vs unsolicited: the choice that changes everything
Before drafting a single section, identify which type you're writing. The structure overlaps but the emphasis flips.
- Solicited business proposal (the client asked for it or issued an RFP) — they already know they have a problem. Spend less time selling the problem; spend more time selling the solution and your fit. Tighten the executive summary, expand the methodology/approach section, lead with credentials early.
- Unsolicited business proposal (you're pitching cold to a prospect) — they don't know they have a problem yet, or don't know they have the budget for it. Spend more time on the problem framing, lead with the diagnostic insight that earned you the right to write, hold the credentials to the end.
The nine-section business proposal structure
In the order most B2B clients read. Some clients will read top-to-bottom; many will read the executive summary and pricing first, then dip into specific sections. Structure each section so it stands alone — assume non-linear reading.
- Cover page (title, client name, date, your company)
- Executive summary (1 page — must stand alone)
- Problem statement / situation analysis
- Proposed solution / approach
- Scope of work and deliverables
- Timeline with phases
- Team and qualifications
- Investment and payment structure
- Terms, assumptions, and next steps
1. Cover page: title, names, date
The cover page exists for two reasons: it signals formality and it gives the document an obvious identity when it gets forwarded internally. Four elements: clear title ("Business Proposal: [WHAT] for [CLIENT]"), client company name, your company name, date. Skip taglines, mission statements, or design flourishes that don't help the reader recognize what they're looking at.
2. Executive summary: the one page that has to stand alone
The most important page in the document. Most stakeholders will only read this one. Has to communicate four things in 4-6 short paragraphs (3/4 page max):
- What problem you're solving (one paragraph)
- What approach you're proposing (one paragraph)
- What outcomes the client should expect (one paragraph, ideally with metrics)
- What the engagement looks like at a high level — timeline range, investment range, team size (one paragraph)
Executive Summary Acme Corp's customer support team is currently resolving 67% of tickets within SLA, down from 84% in 2024. The decline correlates with a 40% growth in monthly ticket volume against flat headcount. Anecdotally, the team reports that triage and routing consume the majority of their capacity, leaving less time for resolution. We propose a four-phase engagement to redesign the support workflow: diagnose current capacity allocation (Phase 1), redesign triage and routing (Phase 2), implement workflow changes with your existing tooling (Phase 3), and measure outcomes against agreed SLAs (Phase 4). We expect the engagement to recover 12-18% of agent capacity within 60 days of implementation, returning resolution-within-SLA to 78-82% by Q3 without adding headcount. Full methodology and case-study references are in Section 4 below. The engagement runs 14 weeks, with a 4-person team (lead consultant + 3 senior analysts) at an investment of $185,000. Payment is structured 30% on signing, 30% at Phase 2 sign-off, 40% at engagement completion. We can begin July 7 if the proposal is signed by June 21.
3. Problem statement: the data the client doesn't yet have
This section is where unsolicited proposals win or lose. For unsolicited proposals, the problem statement is your earn-the-right-to-pitch moment — you have to demonstrate that you understand their specific situation better than they do, or at least that you've done enough research to be credible. Pull in publicly available data, industry benchmarks, or insights from your discovery research.
For solicited proposals, this section is shorter — the client knows they have the problem; you're just confirming you understood the brief. Two to three paragraphs is enough.
The opportunity we see for Acme Corp Based on public review data (G2 scores down 0.3 points in the last 6 months, with 'response time' appearing in 41% of recent 1-2 star reviews) and our analysis of comparable mid-market SaaS support teams, we believe Acme is approaching the inflection where ticket volume growth outpaces team capacity faster than support tooling can compensate. The specific pattern: 47% of mid-market SaaS companies in the $20-100M ARR range hit this inflection between Series B and Series C. The companies that handle it well typically restructure triage workflows 9-12 months before the next funding round. The companies that don't show measurable churn impact within 18 months — typically a 2-4 point NRR decline that takes 2+ years to recover. We don't have access to Acme's internal data, but the patterns above and your public hiring posts (3 senior CX roles open since March) suggest you're seeing some version of this dynamic. The proposal below is our recommended approach if so — and a separate diagnostic engagement option if you'd want to validate the pattern before committing.
4. Proposed solution: the methodology, not just the deliverable
Where freelance project proposals can jump straight to deliverables, business proposals need a methodology layer — the framework or approach you'll use to do the work. This is the section that demonstrates expertise: a clear, named approach communicates that you've done this before and aren't inventing it for them.
Pattern that works: name your methodology (even if it's a name you just gave it), describe it in 3-5 phases, explain what each phase produces. Keep it concrete — "we'll do discovery" is meaningless; "we'll run 12 agent shadow sessions in week 1, then build a capacity allocation map by end of week 2" is specific.
5. Scope of work and deliverables: list them, count them
Same principle as the project proposal version: list deliverables explicitly, one per line, with the same noun-phrase structure for parseability. The difference in a business proposal is volume — you might have 15-30 deliverables across phases instead of 5-8. Group them by phase so the list stays scannable.
Always include a "not included" or "out of scope" subsection at the bottom of this section. For business proposals especially, the out-of-scope list often runs as long as the in-scope list — and that's a feature, not a bug. It prevents 6 months of scope-creep arguments.
6. Timeline: phases, milestones, dependencies
Business proposals run longer than freelance projects, so the timeline needs phase-level structure rather than week-by-week. Three to five named phases with concrete milestones at the end of each. Always name client dependencies explicitly — business engagements typically require more client input than freelance engagements, and unnamed dependencies cause schedule slip.
Engagement timeline (14 weeks) Phase 1 — Diagnose (Weeks 1-3) Deliverables: Current-state capacity allocation map, baseline SLA report, top-10 friction points by ticket type, agent interview summary (12 interviews) Client input required: 2 hours of executive interviews, access to ticketing system data, scheduling assistance for agent interviews Milestone: Diagnostic readout meeting at end of Week 3 Phase 2 — Design (Weeks 4-7) Deliverables: Proposed triage workflow, agent role/skill matrix, technology integration map, implementation roadmap with risk register Client input required: 3 review sessions (60 min each), CXO sign-off at end of phase Milestone: Design sign-off at end of Week 7 ...(Phases 3-4 follow same structure) Key dependencies: Phase 1 begins only after data access is granted (typically 1-2 weeks from engagement signing). Phase 2 design cannot begin until diagnostic readout sign-off. Phase 3 implementation timeline assumes existing helpdesk tool stays in place; tool migration would add 3-4 weeks.
7. Team and qualifications: case studies, not bios
The temptation in this section is to drop in standard team bios. Better: name the specific people on this engagement, their roles, and one or two case studies showing relevant work. Three or four case studies max — quality over quantity. Each case study should follow a tight structure: client (anonymized if needed), problem, approach, measurable outcome.
For solicited proposals, this section can be longer (3-5 pages) because the client is partly buying the team. For unsolicited proposals, keep it shorter (1-2 pages) — too much credentialing in a cold pitch reads as defensive.
8. Investment: the multi-option price structure
Same principle as the project proposal: always present 2-3 options, never a single number. The difference in business proposals is the size of the gap between options. For business proposals over $100K, the typical structure is a recommended option flanked by a lighter scope option (often 50-60% of the recommended price) and an expanded scope option (often 130-150% of the recommended price). The recommended option closes most often because it sits at the perceived center.
Investment options Option A — Diagnose Only (Phase 1) • 3-week diagnostic engagement • Deliverables: current-state assessment, prioritized roadmap, executive readout • Investment: $42,000 • Payment: 50% on signing, 50% at delivery • Best for: validating the pattern before committing to a full engagement Option B — Full Engagement (recommended) • 14-week engagement covering Phases 1-4 above • All deliverables listed in Section 5 • Investment: $185,000 • Payment: 30% on signing ($55,500), 30% at Phase 2 sign-off, 40% at engagement completion • Best for: most clients in your situation Option C — Full Engagement + Implementation Partner • Everything in Option B, plus 12 weeks of post-implementation support • Includes weekly office hours, training refresh, and dashboard monitoring • Investment: $245,000 • Payment: 30% on signing, 30% at Phase 2 sign-off, 30% at engagement completion, 10% at end of post-implementation period • Best for: clients with limited internal change-management capacity
9. Terms, assumptions, and next steps
The final section serves three functions: list the key terms governing the engagement (payment, IP, termination, confidentiality), state the explicit assumptions you've made in pricing the proposal, and give specific next steps for moving forward.
Assumptions are the section most templates skip and most engagements blow up over later. State 5-10 explicit assumptions — anything from "engagement begins July 7" to "client's existing helpdesk tool will not be migrated" to "agent interviews can be scheduled within first 2 weeks." If any of these assumptions changes, the price and timeline are subject to renegotiation.
Next steps 1. Review this proposal. We're happy to discuss any section by phone — I've blocked time June 17-19 specifically for this conversation. Calendar link: [LINK] 2. Once you've selected an option (A, B, or C), reply with your selection. We'll send a signed Master Services Agreement + first invoice within 24 hours. 3. Engagement begins approximately 2-3 weeks after countersignature, contingent on data access being granted. 4. If we haven't connected by June 28, I'll follow up directly to make sure the proposal hasn't been lost in your inbox. We're committed to this engagement starting July 7 — if you need a faster or slower start, please flag in your reply.
Format and length
- Length: Typical business proposal is 8-15 pages. RFP responses can run 30-50+ pages depending on the RFP requirements. If you're under 6 pages for a $100K+ engagement, the proposal probably feels thin to the client. If you're over 20 pages without an RFP requirement forcing it, the proposal is probably padded.
- Format: PDF is the default. Proposal-software output (PandaDoc, Proposify, Loopio for RFPs) is acceptable and often preferred for engagements over $50K because of e-signature and read-tracking. Word docs are accepted but signal less polish.
- Delivery: Email the PDF to the primary contact with the executive summary copy-pasted into the email body. The email body should be short — 4-6 sentences — and serve as the cover note. Always include yourself on the email so you have a sent record.
- Follow-up cadence: Follow up 5 business days after sending if you haven't heard back. Second follow-up 5 business days after that. After two follow-ups with no response, the deal is probably dead — move on rather than continuing to chase.
After the proposal is accepted
The signed proposal converts into a Master Services Agreement (or accepted Statement of Work) and the first invoice. The payment structure you defined in Section 8 becomes the milestone schedule. The hardest part of long business engagements isn't winning them — it's keeping the milestone billing tight enough that you don't end the engagement with $40K of unbilled work. For the templates and reminder cadence to keep milestone billing on track, read the related posts.
Three mistakes that lose business proposals
- Burying the price. Many business proposals put the investment section near the end without an indication earlier. Stakeholders skim — the executive summary should always reference the investment range. Hidden pricing reads as embarrassment about the price, which suggests the price might not be defensible.
- Generic case studies. If your case studies don't reference companies or industries close to the prospect's situation, leave them out. A generic case study is worse than no case study because it signals you don't have relevant experience.
- No assumptions section. Without explicit assumptions, every change in the engagement becomes a difficult renegotiation. With a clear assumptions list, changes follow a predictable change-order process. The 30 minutes spent writing assumptions is the highest-ROI section of the entire proposal.