A proposal is not a price sheet with a logo. It's the written version of the discovery call — their problem, your plan, the number, and the next step. This is the business proposal for services template we'd use, section by section.
1. What a Proposal Is For
By the time a proposal exists, the deal is usually decided by three questions: do they believe you understand their situation, do they believe you can run it better than the current setup, and can they defend the number internally. A winning proposal answers those in that order. The person you handed it to is rarely the only reader — write for the partner, the controller, or the spouse who wasn't on the call.
2. The Template, Section by Section
1. Cover + Executive Summary (1 page)
Their name larger than yours. Three sentences: where they are, what you propose, what changes in 90 days. The reader who only reads one page should be able to say yes from this one.
2. The Problem — in Their Words
Quote the discovery call directly: the outage that cost a day, the ex-employee whose accounts nobody disabled, the "IT guy" who takes three days to answer. Numbers where you have them. This section is why proposals can't be written before discovery — it's also the section that makes the rest credible.
3. Proposed Services
Map each service to a problem from section 2 — monitoring to the outage, security stack to the offboarding scare, help desk to the response-time complaints. Reference your SLA tiers here (response commitments, coverage hours) instead of listing generic features.
4. Pricing
The three-tier table, recommended tier marked, per-month per-user framing where it helps the comparison against a salary or the incumbent. Onboarding fee stated plainly. No asterisks — surprises here surface later as churn.
5. Onboarding Timeline
Weeks 1–2 discovery and documentation, weeks 3–4 stack deployment, month 2 stabilization, month 3 first business review. A concrete timeline makes switching feel survivable — fear of the transition kills more deals than price does.
6. Proof
Two or three named references in their vertical or size band, certifications and insurance, and one honest sentence about your actual response performance versus your committed SLA. One page maximum.
7. Terms + The Next Step
Term length, start date, what happens when they sign (the kickoff call, the onboarding checklist), validity window for the pricing (30 days), and one — exactly one — call to action: the signature link or the scheduled decision call.
3. Presenting the Price
Anchor high: present the premium tier first, then the recommended tier reads as reasonable. Translate to the comparison they're already making — against a $70k internal hire or the incumbent's invoice, per-user per-month math wins. And never negotiate the number without removing something; discounting the same scope teaches the client the first price was padding.
Send it, then walk it through
4. Why Proposals Lose Deals
- Generic problem sections that prove nobody listened — the fastest way to lose to the incumbent's inertia.
- Feature lists instead of problem mapping: 40 bullet points about your stack and none about their business.
- Ten-plus pages of boilerplate that bury the executive summary the actual decision-maker needed.
- No expiration date, so the proposal sits in a drawer while the environment (and your pricing math) drifts.
- Multiple competing CTAs — "sign here, or call, or reply, or book a call" — instead of one next step.
Key Takeaways
Problem in their words, services mapped to problems, three tiers anchored high, a timeline that makes switching feel safe, and one next step. When they sign, the managed services agreement and the SLA are the documents the proposal just sold.