How to Price a Proposal: Tiers, Anchors, and What to Itemize

One number invites a yes-or-no. Three tiers invite a different question - "which one?". Here's how to structure the pricing section so the conversation is about value, not cost.

Quick answer: Price a B2B proposal in two or three tiers with the recommended one marked, anchor the top tier first, itemize what each tier includes in a table, separate one-time setup from recurring costs, and put payment terms next to the price - not in an appendix. The goal isn't to hide the number; it's to give the buyer a decision to make that isn't "yes or no".

Why a single price loses

A single number gets compared to two things: other vendors' single numbers, and zero (doing nothing). Both comparisons happen without you in the room. Tiers change the frame: now the buyer compares your options against each other, and the internal conversation becomes "do we need the full build or the starter?" - a conversation where every answer is a yes.

Two tiers work; three are better; four postpone decisions. Past three, buyers defer "until we understand the differences" - and deferred proposals die.

Anchoring: order matters

Present the top tier first. Not because you expect to sell it every time, but because everything after it reads as reasonable. The classic structure:

• The full build - everything, priced accordingly. Sets the ceiling.
• The recommended tier - what you'd actually pick for them, marked as such ("most teams start here"). This is where the outcome you promised in the proposal lives.
• The entry point - real value, visibly lighter. For cautious buyers and procurement games. It must be genuinely useful, not a decoy that insults the reader.

Mark the recommended tier visually and say why it's recommended for this client specifically - one sentence tying it to their problem.

Itemize, but itemize outcomes

A pricing table where each row is an activity ("6 workshops", "12 pages") invites line-item haggling. Rows that name outcomes ("Working outbound sequence to 2,000 matched accounts", "CRM wired to your inbox replies") price the result, not the hours. Itemize enough that the tiers' differences are visible at a glance - and no more.

Two things always separated:

• One-time vs recurring. Setup fee and monthly retainer/licenses on different lines. A buyer who discovers the recurring part at invoice time is a churned client with a story to tell.
• What's excluded. One short line ("does not include: paid media budget, copywriting in languages other than EN/IT") saves the relationship the argument later.

Terms live next to the price

Payment schedule, invoicing dates, what happens when scope moves, validity date. On the same page or the facing one - never in an appendix. Objections that surface at signature kill more deals than the number itself; terms next to the price mean the objections surface while you're still in the room.

Keep the machinery honest

Tiered pricing multiplies the places a copy-paste error can hide: an old client's number surviving in tier two, a currency mismatch, a total that doesn't match its rows. If your proposals are hand-assembled documents, this will eventually happen in front of a buyer. In AthonBound Studio the pricing lives as structured line items - the totals compute, the currency is one setting, and the PDF regenerates consistent every time.

The pricing section is one part of a document with a fixed argument order - problem, outcome, plan, price, proof. The full structure is in our proposal template guide, and the writing itself in how to write a proposal that wins. After it's sent, the follow-up cadence does the closing.

FAQ

How many pricing options should a proposal have?

Two or three. One invites yes/no and vendor comparison; four or more postpone the decision. Mark the recommended tier and make differences visible in a table.

Should I show prices in the proposal at all?

Yes. A proposal without a price is a brochure - the buyer can't decide anything with it. If the engagement genuinely needs discovery before pricing, price the discovery.

How do I present a retainer in a proposal?

Separate lines: one-time setup, then the monthly retainer with what it covers each month. Never blend them into one number - the buyer will un-blend it at renewal, on their terms.

Should proposal prices be itemized?

Itemize outcomes per tier, not hours per activity. Enough rows that tier differences are obvious; few enough that nothing invites line-item negotiation.

What's price anchoring in a proposal?

Presenting the highest tier first so the recommended one reads as reasonable. It's not manipulation - it's giving the buyer context for what the full solution costs before showing them the sensible middle.

Assembling pricing tables by hand? Get in touch - we'll show you proposals where the numbers compute themselves, no pitch.