Pricing is not a separate exercise from the rest of a proposal. It is part of the argument. Most teams treat the price as a number to disclose and the technical solution as the persuasive part, then wonder why a lower price does not win. The price has to be presented, not just stated – aligned to the evaluation criteria and connected to the value the buyer is scoring.

A price without context is an invitation to compare on cost alone. A price with context is a case for value.

Read the pricing instructions exactly

Before you think about the number, read the pricing instructions as carefully as the technical requirements. Pricing format is frequently mandatory, and failing it can disqualify an otherwise strong bid.

  • Format and structure: which workbook, which line items, which currency, taxes included or excluded.
  • Pricing basis: fixed price, rates, ceilings, options, or a combination.
  • Required assumptions and conditions, and where they go.
  • Any instruction not to deviate from the prescribed format – which means do not “improve” it.

Treat these like compliance requirements. They are pass/fail, and they are checked mechanically. They belong in the compliance matrix alongside the technical requirements.

Price to the evaluation criteria

Buyers publish how they will score, and price is weighted differently in every procurement. Presenting the price is therefore a strategic choice:

  • If price is weighted heavily, the commercial case must be competitive and clearly reasoned; the narrative should explain the basis of estimate rather than apologise for cost.
  • If technical merit dominates, the price narrative should reinforce the value story and make the cost feel proportionate to the outcome, not a figure to defend.
  • If both are weighted, make sure the technical and commercial sections tell the same story about trade-offs and what is included.

Where the procurement is decided on best value rather than lowest cost, the job is to show that the buyer gets more for the price – not merely to be cheap. For how the price connects to your themes, see Win Themes.

Present value, not just cost

A price lands well when the buyer understands what it buys. Presenting value means:

  • Connecting the price to outcomes the buyer said they care about – the scoring criteria, not generic benefits.
  • Showing cost of ownership, not just purchase price: what it costs to run, change and support over the contract term.
  • Framing options clearly where the buyer allows them, so they can see the difference in value between tiers rather than guessing.
  • Quantifying where you can – a defensible total cost over the term beats a headline number with no context.

The discipline is to answer the question the evaluator is scoring, which is usually value for money, not the lowest figure on the page.

Make your assumptions explicit

Hidden assumptions become disputes after award. State the basis of your price plainly:

  • What is included and what is excluded.
  • The conditions the price depends on – volumes, timelines, scope boundaries, third-party costs.
  • The validity period and how changes would be priced.
  • Any client responsibilities the price assumes, such as access, data or approvals.

Explicit assumptions protect you commercially and reassure the evaluator that the number is grounded. Fewer assumptions mean more risk absorbed silently into the price; stated assumptions are a sign of a considered bid, not a hedge.

Keep pricing and narrative consistent

The most damaging pricing error is a contradiction between the commercial volume and the technical narrative. Every commitment made in the technical response – staffing, timelines, service levels, extra work – must be affordable within the price you submit, and the two documents must tell one story.

Run a specific consistency check before submission:

  • Does the staffing in the technical volume match the resource cost in the price?
  • Do the service levels and timelines in the narrative match the commercial terms?
  • Are the same terms, units and definitions used in both?
  • Does the price narrative match the price workbook, line for line?

Contradictions between formats are a frequent, avoidable reason to lose. For the review that catches them, see Red-Team Your Proposal.

A pre-submission pricing checklist

Pricing errors are cheap to prevent and expensive to make. Run this checklist before the final compliance review.

  • Format obeyed exactly – workbook, units, currency, tax treatment, sheet order, no deviations.
  • Every required line item present, including options, licenses and any item the buyer asked to be priced separately.
  • Assumptions stated – inclusions, exclusions, conditions, validity period and change-pricing.
  • Consistent with the technical volumes – staffing, timelines and service levels all match.
  • One set of definitions used across narrative, questionnaire and price workbook.
  • Value narrative answers the scoring – price framed against the buyer’s criteria, not defensively.
  • Reviewed by someone who did not build it – a second pair of eyes catches format and consistency slips.
  • Basis of estimate documented internally so the number is defensible if challenged after award.

Run the checklist with someone outside the commercial team. A fresh reader catches format and consistency errors that the people who built the price no longer see.

Common mistakes

  • Treating format as flexible. Pricing instructions are usually pass/fail; “improving” the format can disqualify the bid.
  • Contradicting the technical volume. Promised staffing or timelines that the price cannot fund are a common loss cause.
  • Hiding assumptions. Unstated assumptions become disputes after award and read to evaluators as an incomplete bid.
  • A price with no value context. A bare number invites comparison on cost alone.
  • Discounting without a rationale tied to the criteria. An unexplained discount signals the original price was padded.

Options, tiers and presenting choices

Where the buyer allows options, structure them so the choice is easy to score. Present a clear base with clearly bounded options, each with a defined scope and a stated difference in value – not a menu that pushes the decision back to the buyer.

  • Keep the base complete. An option should add value, not fill a gap in the core offer.
  • Make the trade-off legible. State what the buyer gets for the difference, in their terms.
  • Do not price options as hidden discounts. Padding the base to make an option look cheap is transparent to experienced evaluators.

Options are a chance to show that you understand the buyer’s priorities, not just to upsell. A well-designed structure of base and options demonstrates that you have thought about the buyer’s decisions, not merely about maximizing revenue. Where the buyer has signaled budget pressure, offer a leaner base with clearly priced additions rather than a full base with deep discounts; where the buyer has signaled a preference for a single accountable partner, offer a complete base and price the extras as optional depth. Read the signals in the solicitation and shape the structure to match them. For how the price connects to your differentiators, see Win Themes.

Frequently asked questions

How should you present pricing in a proposal?

In the exact format the buyer requires, aligned to the evaluation criteria and connected to value. State your assumptions, keep the number consistent with the technical narrative, and make the commercial case in the buyer’s terms rather than defending cost.

Should you be the cheapest bid?

Only if price is the decisive criterion and you can deliver at that price. In best-value procurements, being cheapest without a value story can signal risk rather than saving. Match your pricing strategy to how the buyer is scoring.

What is price-to-win?

A method for estimating a competitive, defensible price using the buyer’s budget signals, the evaluation weighting and competitive intelligence, rather than cost-plus. It informs where to position the price before the submission is finalised.

What are common pricing mistakes in proposals?

Using the wrong format, contradicting the technical volume, hiding assumptions, presenting a number with no value context, and discounting without a rationale that fits the evaluation criteria.

Where does pricing belong in the response process?

It is scoped during qualification, planned in the storyboard, drafted with the technical volumes so the two stay consistent, and verified at the red-team and final compliance review.

How do you handle a price you cannot match?

Do not drop the price below a deliverable level to compete. Instead, adjust the scope or terms to close the gap – reduce optional items, phase the work, or reset the contract length – and make the trade-off explicit. If the buyer is scoring on lowest cost and you cannot deliver at that cost profitably, the honest answer is that the opportunity was a no-bid.

Should you present the lowest price to win the bid?

Only when price is the decisive criterion and the price is deliverable. In best-value procurements, a low price with no value story can read as risk – evaluators ask why it is so cheap and whether you understood the scope. Match the pricing strategy to the evaluation weighting, and make the value case in the buyer’s language.

Next step

Price is scored, not merely received. Read the instructions as compliance, align the number to the evaluation criteria, and make the value case in the buyer’s language. If you want your pricing section pressure-tested, get a pricing-section review and we will check format, consistency and value framing before you submit.

Sources

  • APMP, Body of Knowledge and Foundation Study Guide: price-to-win, cost and pricing data, and aligning price with strategy and customer budget.
  • APMP, Winning Business Ecosystem: aligning pricing with strategy, win themes and customer budget.

Good-practice claims are cited from their sources; no statistic in this article is invented.