Pricing is usually the section of a proposal that gets the least design thought and the most buyer scrutiny. A confusing pricing page doesn't make a service look more premium — it just makes the buyer's job harder, right at the point where they're deciding whether to move forward.

Overview

The goal of a pricing section isn't to make numbers as small as possible or to disguise cost. It's to make the commercial logic clear enough that a buyer — and anyone they forward the proposal to — can understand what they're paying for and why the structure makes sense, without a follow-up call just to explain the pricing page.

The problem

Pricing sections tend to fail in a few specific ways:

  • Numbers appear with no explanation of what drives them — a single flat fee with no breakdown, or a rate card with no sense of what a typical engagement actually costs.
  • Multiple pricing options are presented with no guidance on which one fits the buyer's situation, leaving them to guess.
  • The pricing section is visually disconnected from the rest of the proposal, as if it were bolted on at the end rather than designed as part of the same document.
  • There's no answer to the obvious next question: what happens if scope changes mid-engagement?
Key point
Storydoc's research found that proposals with a clear next step converted 27% better than those ending in a vague close — the same logic applies inside the pricing section itself: clarity about what a number includes and what happens next outperforms a technically accurate but confusing breakdown. (Storydoc proposal statistics)

A better approach

A few practical adjustments that consistently make pricing sections clearer:

  • State what's included, not just what it costs. A number without scope invites the buyer to assume the worst about what's missing.
  • If there are multiple options, recommend one. "Most teams your size choose the standard tier" is more useful than three unranked columns.
  • Explain the pricing logic in one sentence. Whether it's value-based, scope-based, or usage-based, naming the logic helps the buyer defend the number internally.
  • Address scope changes proactively. A short note on how additional work is handled prevents a harder conversation later.
  • Keep the pricing section visually consistent with the rest of the document. A pricing table that looks like it was pasted from a spreadsheet undercuts the credibility of everything before it.

Example

An agency used to present pricing as a bare table: three tiers, three numbers, no other context. After adding one line under each tier explaining who it's typically right for, plus a short note on how scope changes are priced, their proposals generated noticeably fewer "can you explain the pricing" follow-up emails — buyers had the context they needed the first time through.

Questions

Should pricing always be included, or held back for a call? If the engagement scope is reasonably clear from discovery, including pricing upfront tends to build trust rather than erode leverage — buyers are often comparing multiple proposals and reward the ones that don't make them chase for basic information.

How much detail is too much detail? Enough to answer "what am I paying for and why is it structured this way" — a full itemized breakdown of internal costs is rarely necessary and can invite unproductive line-item negotiation.

What about custom or highly variable pricing? Even when an exact number can't be given upfront, explaining the variables that drive the range helps the buyer understand what would move the number up or down.