Sample sales proposal: four worked formats

At 11pm, a proposal template looks deceptively helpful. The logo is in place, the colors are approved, and the cursor is blinking inside a half-written scope section while Friday's deadline gets closer. You don't need another article telling you to add value. You need a sample sales proposal you can open, adapt, and send.

The test I hold every proposal to now is this: could my contact forward this to someone else and still make the case? That standard changes the writing more than any template does. The executive summary becomes a decision aid, the scope becomes protection against confusion, and the signature block becomes a route to approval rather than a decorative footer.

Four formats below, with what belongs in each and what to cut. The numbers in all four are invented to make the structure concrete. They are not benchmarks and you should not price against them.

What a sample sales proposal actually looks like

A sales proposal isn't a company brochure with a price attached. It connects a buyer's stated problem to a defined solution, commercial terms, proof, and a next action. A quote confirms products, quantities, and prices. A proposal gives those figures a reason to exist.

The four working formats:

Mid-market SaaS, where the buyer needs confidence in fit, implementation, and recurring cost.
Consulting project, where scope, milestones, and client commitments matter more than feature lists.
One-page SMB close, where extra detail creates hesitation instead of trust.
Enterprise approval document, where several stakeholders need different evidence before procurement can move.

The anatomy every proposal shares

Every strong proposal has a recognizable spine, even when the page count changes. Guidance from Responsive's RFP best-practices guide emphasizes direct answers to requirements, transparent pricing, concise formatting, and headings, bullets, and tables that make review easier.

The sections that earn their space

The cover and title block identify the buyer, sender, date, and proposal name. Use the customer's company and contact instead of opening with a generic logo wall.

The executive summary should survive a skim. State the problem, recommended approach, expected outcome, and commercial shape in plain language. It's often the first section a busy decision-maker reads, so don't spend it introducing your company.

The problem statement mirrors the buyer's language back to them. If discovery revealed slow reporting, inconsistent handoffs, or unclear ownership, use those terms. Don't invent pain that wasn't discussed.

The solution and scope map what you'll do to the named use cases. Separate included work from exclusions. A feature list without context makes the buyer translate your product into their own situation.

Pricing and assumptions need visible line items, payment terms, and dependencies. Buried assumptions are where otherwise healthy deals develop friction.

Proof, timeline, terms, and signature complete the approval path. Use relevant case studies or references, show milestones, state responsibilities, and make acceptance unambiguous. Put compliance and legal detail in an appendix when specialized reviewers need it.

The order and weight change with deal size. A small buyer may need one page. An enterprise committee may need a concise main document plus appendices.

SaaS, for mid-market buyers

A mid-market SaaS proposal answers three questions quickly: does this fit our use case, can we implement it safely, and can finance understand the commitment? The illustrative scenario here is roughly 250 seats, a three-year term, and about $180,000 in total contract value.

Start with a cover page that names the buyer and the specific contact. "Sales Proposal for Northstar Manufacturing, Prepared for Jordan Lee" creates ownership. "Platform Proposal" with four vendor logos does not.

Executive summary

Lead with the buyer's language:

> Your revenue operations team needs one reliable workflow for user provisioning, single sign-on, and reporting. This proposal outlines a three-year rollout designed to reduce manual administration, give managers consistent visibility, and establish a controlled implementation path.

Then name the outcomes the buyer agreed to evaluate. Keep them measurable only when the baseline and measurement method are real. Avoid promising a result your team can't support.

The solution section should connect each module to a use case:

Module	Buyer use case
User provisioning	Create and remove access through an agreed administrative workflow
SSO	Give users a controlled sign-in path managed through the buyer's identity provider
Reporting	Provide recurring visibility into adoption and operational activity

Pricing and implementation

Present tiers, seat counts, implementation fees, and separate Year 1, Year 2, and Year 3 figures. Finance shouldn't need a spreadsheet reconstruction to understand the commitment. Add a short ROI table beside relevant, verified case studies. If you can't substantiate a case-study metric, use a reference or describe the result qualitatively.

The implementation timeline runs six weeks in named phases: configuration, access setup, validation, launch. Add a mutual action plan with dates owned by both sides. For another practical model of proposal structure, see these example proposal letters.

Mid-market buyers scan headings, pricing, implementation risk, and proof before deciding which details deserve attention. Write for that order.

Consulting, for project-based work

A consulting proposal sells a defined change, not access to a product. The buyer's fear is usually scope drift, unclear ownership, or a final deliverable that doesn't match what they thought they bought.

The illustrative scenario: a twelve-week brand strategy engagement at $48,000. Open with a discovery recap that records the working sessions already completed. That recap proves the proposal came from conversation rather than a recycled services menu.

Make the work visible

Organize the approach into four plain-language stages:

Discover: review existing positioning, customer evidence, and internal priorities.
Define: agree on the strategic direction and decision criteria.
Design: develop the core brand recommendations and supporting materials.
Deploy: prepare the final handoff and explain how the team should use it.

List deliverables under each stage. "Stakeholder alignment workshop" may be accurate, but "one workshop to agree on the target audience, positioning direction, and open decisions" is easier to approve.

Place risks and assumptions before pricing. Name the client-side commitments: access to stakeholders, timely feedback, content approvals. This isn't defensive language. It tells both parties what the schedule depends on.

Price against milestones

A sensible rhythm is 30% at kickoff, 40% at the midpoint deliverable, and 30% at final handoff, anchored to accepted milestones rather than calendar months. If the midpoint deliverable moves, everyone can see what happens to the invoice.

Include a short change-order clause and a one-page terms summary. The buyer doesn't need a legal essay in the main narrative, but they do need to know how new requests affect timing and cost.

SMB, the one-page close

Small-business buyers don't need a miniature enterprise document. They need to understand the offer between meetings and know exactly how to accept it.

The illustrative scenario: a $450-per-month bookkeeping package for a twelve-person dental practice. The opening sentence names the problem: "Your practice needs current books and tax-ready reporting without asking the office manager to chase reconciliations."

Then keep the scope tight:

Monthly reconciled books
Quarterly tax-ready financials
One strategy call per quarter

Place the price in the upper-right corner, with three tier options stacked vertically. Make the recommended middle tier visually obvious, but don't hide what the other options include. A short proof line can reference a comparable client by industry and outcome without naming them if confidentiality prevents attribution.

Remove decision friction

Put one signature block at the bottom, along with the contact details of the person who will answer questions. Add a 30-day cancellation clause so the buyer doesn't have to search through legal language to understand the commitment.

Every line needs a job. A second page would dilute urgency. A long company history would distract from the practice's immediate need. A contact form would add distance when the office manager is probably coordinating the decision.

Enterprise, for long approval cycles

An enterprise proposal must help several people approve the same purchase for different reasons. The illustrative scenario: a $740,000, eighteen-month implementation for a global logistics carrier. The CFO needs commercial clarity. IT security needs controls and data handling. Procurement needs negotiable line items. The executive sponsor needs confidence that the program won't stall.

Open with an executive summary written for the CFO, then create a separate security section for the technical reviewer who may never read the summary.

Write for the committee

Include a stakeholder map with the economic buyer, technical evaluator, end-user champion, and executive sponsor. Record each person's role and the question they need answered. That turns a vague committee into a review plan.

The pricing section should include a three-year TCO table:

Cost Category	Year 1	Year 2	Year 3	Three-Year Total
License	[amount]	[amount]	[amount]	[amount]
Implementation	[amount]	[amount]	[amount]	[amount]
Training	[amount]	[amount]	[amount]	[amount]
Support	[amount]	[amount]	[amount]	[amount]
Total	[amount]	[amount]	[amount]	[amount]

Use real figures only after finance has approved the model. Separate license, implementation, training, and year-over-year support so procurement can adjust a line without breaking the math.

Compliance attachments should cover the documentation the buyer requested, such as SOC 2 Type II, data residency, and a redlined MSA. A risk register with known risks and mitigations signals that your team has thought beyond the sale.

Assume several readers. Create persona-specific covers or navigation, use pricing tiers that absorb negotiation without crossing your approved floor, and keep legal detail available without making the executive summary unreadable.

The four side by side

Proposal Type	Typical Deal Size	Page Count	Pricing Rhythm	Decision-Maker	Approval Timeline	Main Weakness
SaaS mid-market	Substantial recurring contract	Several focused pages	Per seat and annual term	Business owner plus finance and operations	Multi-stakeholder review	Can become feature-heavy
Consulting project	Defined project fee	Several pages plus terms	Milestone payments	Project sponsor	Tied to scope and approvals	Scope can drift
SMB one-page	Lower-complexity monthly offer	One page	Monthly package or tier	Owner or office manager	Short review	May omit needed detail
Enterprise	Large strategic program	Main document plus appendices	Annual contract and TCO	Committee, procurement, legal, security	Extended approval cycle	Can overwhelm executives

Two mistakes appear constantly. Teams use the enterprise template for a small deal because it feels credible, then bury the decision in unnecessary detail. I have watched that happen to a deal that could have closed on one page, and the extra thirty pages bought nothing except three more weeks. Or they send a one-pager to a procurement-led buyer who needs security, legal, and implementation evidence before approval.

Blocks you can drop into any proposal

Treat proposal content as a parts catalog, not a blank page. Build each block once in a shared document, then use the deal profile to decide what belongs in the final version. A structured MakeAutomation software overview can also help teams think through reusable document components and automation workflows.

Blocks worth keeping ready

Executive summary: one paragraph that mirrors the buyer's stated problem and names the recommended outcome. It belongs in all four formats, but it should be shortest in the SMB version.
Case study block: put a relevant, measurable result in the first sentence when verified evidence exists. Use it for SaaS, consulting, and enterprise proposals. Leave it out when the example is too distant from the buyer's situation.
ROI table: use the customer's numbers, assumptions, and measurement method. Vendor-supplied assumptions weaken trust unless the buyer has agreed to them.
Pilot clause: useful for risk-averse SaaS or enterprise buyers when the test has a defined scope, success criteria, owner, and commercial next step.
Timeline block: express work in weeks and milestones when the buyer cares about delivery. A consulting proposal benefits more from this than a seat-based SaaS document.
Mutual action plan: name the buyer's tasks alongside yours. It fits every complex deal and prevents "waiting on the client" from becoming invisible.
Security appendix: reserve this for enterprise or regulated purchases. Don't force a small buyer through controls they didn't ask about.
Plain-English terms: surface renewal, cancellation, price-lock, payment, and acceptance language before the formal terms section.

Keep the source versions accurate, then customize the assumptions, proof, scope, dates, and commercial terms each time.

Pairing a proposal with a short video walkthrough

A short video can orient the buyer before they start reading. It shouldn't turn the proposal into homework.

Record a two- to four-minute walkthrough with a direct opening: "You said the main issue was inconsistent reporting across regional teams. I've reflected that in the first section, then mapped the rollout and pricing to the review points we discussed."

Use this sequence:

Restate the buyer's problem in their words.
Point out two sections that matter most.
Name one honest caveat or dependency.
Close with the next decision and how to make it.

Any screen recorder will do for the recording itself. What matters more is where the video ends up, because a walkthrough sitting in a separate link in a separate email is a second thing for the buyer to open, and the second thing is the one that doesn't get opened. That is the gap LiveDocument's video walkthrough closes, by putting the narration beside the relevant pages on one link. It will not write the proposal for you and it is not e-signature, so acceptance still happens wherever it happens today.

The mistake that ruins these videos is narrating every page. Busy executives don't need an audiobook. They need help with the two or three decisions that could block approval.

Following up after it goes out

Follow-up should respond to behavior, not run on autopilot. Check the view history first. A full read followed by silence may point at price or authority concerns. Repeated visits to security language may point at procurement friction, and it is worth asking about directly rather than guessing.

If the proposal is unread after two business days, send a short note offering a two-minute clarification call. If it has been opened, mention the section they spent time on instead of writing "just checking in". After a meaningful call, send a decision recap with owners, unresolved questions, and the next deadline. Page-level tracking is what makes that specific rather than generic, though it tells you where attention went and never why.

Stop automated reminders when the buyer replies. Change the cadence after two unanswered attempts. For enterprise deals, coordinate messages with the economic buyer, champion, legal reviewer, and procurement owner.

Every follow-up should support a decision: approve the scope, resolve a risk, validate the commercial case, or schedule the next review. These practical sales increase tactics are most useful when tied to a specific buyer action rather than a generic sequence.

A checklist before you send

Opening: names the customer's problem and desired outcome.
Solution: connects scope to that outcome without dumping every feature into the document.
Pricing: shows options, assumptions, payment terms, and totals clearly.
Proof: resembles the buyer's situation and uses only supported claims.
Decision path: names stakeholders, next steps, validity dates, and cancellation language where appropriate.
Accuracy: checks names, dates, links, signatures, calculations, and version control.
Readability: works on a phone and doesn't rely on separate attachments for essential information.
Walkthrough: includes a short recording when the offer is visual, complex, or likely to be reviewed asynchronously.
Delivery: sends the right version to the right stakeholders.

Before sending, run the email and attachment through a spam word checker, then read the proposal as the buyer rather than its author. If a claim needs evidence, add it. If a section only makes your company feel important, cut it.

Frequently asked questions

How long should a sample sales proposal be?

An SMB proposal may fit on one page, while enterprise or regulated purchases may need a longer main document and appendices. The right length gives the decision-maker enough evidence without making them hunt for it.

Should every proposal include prices?

Most should. If scope isn't defined, explain what is fixed, what remains unknown, and what the next estimate depends on.

What's the difference between a proposal and a quote?

A quote confirms products, quantities, and prices. A proposal frames the problem, solution, outcome, scope, proof, and commercial terms.

Can a sample proposal be reused?

Use it as a structural model, not a finished document. Replace customer assumptions, outcomes, proof, scope, dates, and terms every time.

Should you send a video with every proposal?

No. A walkthrough helps when the offer is visual, complex, or likely to be reviewed asynchronously. Send it after the buyer has confirmed the problem, decision criteria, stakeholders, and a credible next step, not merely because a demo ended.

---

LiveDocument lets you share a proposal and its short video walkthrough as one tracked link, with page-level engagement to guide follow-up. If your proposals keep disappearing into inboxes, visit LiveDocument and turn the next one into a guided review instead of another silent attachment.

Sample sales proposals: four formats and when each one wins