---
name: sales-proposal
description: Use when asked to write or review a sales proposal — a formal document proposing a specific solution, scope, and price to a prospective buyer, often in response to a buyer's [[request-for-proposal]] — distinct from a [[statement-of-work]], which governs execution once the deal is won.
---

# Sales Proposal

A sales proposal is a formal document a seller sends to a prospective
buyer, proposing a specific solution to a specific need at a specific
price. It's a persuasive, commercial document written to win a deal —
often the direct response to a buyer's [[request-for-proposal]], but
sometimes sent unsolicited after a sales conversation has already
surfaced the buyer's need.

## Key components

- **Understanding of the need** — a restatement, in the buyer's own
  terms, of the problem they're trying to solve. This is what proves
  the seller actually listened rather than sending a form letter, and
  it's usually the first thing a buyer checks for.
- **Proposed solution** — what the seller is offering and how it
  addresses the stated need, tied explicitly back to that need rather
  than presented as a generic capability list.
- **Scope** — what's included and, just as important, what's excluded,
  so both sides share the same picture of the engagement's boundaries.
- **Pricing** — the cost, structured clearly (one-time vs. recurring,
  tiers, options) and given enough context (what drives the number,
  what's included at that price) that it reads as reasoned rather than
  arbitrary.
- **Timeline** — key milestones and an expected start and end date, or
  the cadence for an ongoing engagement.
- **Why us** — the differentiation section: relevant experience,
  references, or capabilities that make this seller the right choice
  over competitors also responding to the same opportunity.

## Sales proposal vs. statement of work

These serve different stages of the same deal:

- **Sales proposal** — the document that wins the deal. Persuasive,
  written for a buyer who is still deciding, and often produced under
  competitive pressure against other bidders.
- **[[statement-of-work]]** — the document that governs execution once
  the deal is won. More detailed and operational: specific deliverables,
  acceptance criteria, roles, and schedules, written for the people who
  will actually do and manage the work rather than for the buyer's
  decision-making committee.

A proposal that promises something vague ("comprehensive support") is
fine for winning the deal, but that vagueness has to get resolved into
specifics in the SOW before work starts — otherwise the ambiguity just
moves downstream into a dispute about what was actually promised.

## Responding to an RFP

When a proposal answers a [[request-for-proposal]], the buyer usually
scores every response against stated evaluation criteria. Structure the
proposal to explicitly map onto those criteria — using the RFP's own
section headings and terminology where possible — rather than
submitting the seller's standard boilerplate and trusting the buyer to
find the relevant parts. A technically stronger proposal that's hard to
score against the stated criteria can lose to a weaker one that's easy
to score.

## Common pitfalls

- **Doesn't address the RFP's evaluation criteria** — a proposal that
  reads well on its own but doesn't map onto how the buyer said they'd
  score responses gets marked down or excluded on a technicality,
  regardless of the underlying quality of the offer.
- **Pricing with no context** — a number presented with nothing
  explaining what drives it reads as arbitrary and invites the buyer to
  simply negotiate it down rather than evaluate it.
- **Generic boilerplate** — a proposal that could have been sent to any
  prospect, with the buyer's name swapped in, signals that the seller
  didn't actually engage with this buyer's specific need.
- **Scope left implicit** — failing to state what's excluded as clearly
  as what's included sets up a scope dispute later, once work is
  underway and expectations diverge.
- **No clear next step** — ending without a specific call to action
  (sign by a date, schedule a follow-up call) leaves momentum to fade
  after the buyer finishes reading.

## Learn more

- [[request-for-proposal]] for the buyer's document a sales proposal
  often responds to.
- [[statement-of-work]] for the operational document that governs
  execution once the proposal wins the deal.
- [[sales-pitch]] for the shorter persuasive narrative that often
  precedes a full written proposal.
- [[competitor-analysis]] for understanding the rivals a proposal is
  usually competing against.