Pricing proposals and cost volumes: how to present price in an RFP

RFP Tips

Author:

Chris Mabry

Short answer: A pricing proposal (also called a price proposal, cost proposal or cost volume) is the part of an RFP response that states what you'll charge and on what basis. Use the buyer's price form if one is provided, never change its structure, and fill every cell. Add a short price narrative that explains your pricing model, what's included and excluded, assumptions, and how long the price is valid. Make sure every number agrees with the technical volume: evaluators check that the price buys the work you described.

In Iris: when a project is finalized, Iris extracts the commitments written into your answers as obligations with due dates, so you can track every commitment your team made in writing, including the ones that affect cost.

Who this is for: proposal managers, pricing analysts, finance and sales leaders preparing the price volume of an RFP response.

On this page

  1. What is a pricing proposal?
  2. Which pricing model should you use?
  3. What should the price narrative include?
  4. Sample price table and narrative (fictional)
  5. How do evaluators assess price?
  6. Mistakes that disqualify or cost points
  7. FAQ

What is a pricing proposal?

Most formal RFPs separate price from the technical response so evaluators can score the approach without being swayed by cost. The pricing proposal usually has two parts:

PartWhat it isWho provides the format
Price schedule / price formThe numbers, in rows the buyer defined (line items, unit prices, quantities, years)Usually the buyer: a spreadsheet or form you must not alter
Price narrativeA short explanation of model, inclusions, exclusions, assumptions, discounts and validityYou, unless the RFP limits or forbids it

Some RFPs also ask for a cost breakdown (labor categories, hours, rates, materials, travel, overhead) so they can check realism. In US federal procurement, certain contracts require certified cost or pricing data; check the solicitation and current thresholds with your contracts team.

Which pricing model should you use?

Use the model the RFP specifies. If you have a choice:

ModelHow it worksGood forRisk sits with
Fixed priceOne price for defined scopeClear, stable scopeVendor
Time and materials (T&M)Hourly or daily rates × actual effort, plus materialsUncertain scopeBuyer
Capped T&M (not-to-exceed)T&M up to a ceilingUncertain scope, budget-limited buyerShared
Unit pricingPrice per unit (user, transaction, site, record)Volume that may changeShared
SubscriptionRecurring fee per period, often per user or tierSaaSShared
Milestone-basedPayments tied to accepted deliverablesProjects with clear phasesShared
Tiered / volume discountsUnit price falls as volume risesLarge or growing volumesShared

Rule of thumb: match the model to the scope certainty. Fixed price on a vague scope is how vendors lose money; T&M on a precise scope looks like you don't understand the work.

What should the price narrative include?

Copy and adapt. Keep it to one or two pages unless the RFP asks for more.

PRICE NARRATIVE: [RFP number], "[title]"

1. Pricing basis
   Our price is [fixed / T&M / unit / subscription] as required by
   [section]. All prices are in [currency], [exclusive / inclusive] of
   [taxes].

2. What the price includes
   [Deliverables / services / licences / support level], as described in
   Technical Volume sections [x–y].

3. What the price excludes
   [Item]; [item]. These can be provided at the rates in [table / exhibit].

4. Assumptions
   a. [Volume, users, sites] as stated in [RFP section].
   b. [Buyer responsibility] by [date / phase].
   c. [Any assumption that, if wrong, changes the price.]

5. Options and discounts
   [Optional items, multi-year terms, volume tiers, prompt-payment
   discount], priced separately in [table].

6. Payment terms
   [Milestones / monthly / annual in advance]; [net days].

7. Price validity
   Prices are valid for [number] days from the submission deadline.

8. Escalation (multi-year)
   [Fixed for the term / annual increase of [x]% / tied to [index]].

Sample price table and narrative (fictional)

Scenario: Linden Row Software (fictional) responds to a school district's RFP for a visitor-management system for 40 sites, three-year term. All figures are invented.

LineItemUnitQtyUnit priceYear 1Year 2Year 3
1Subscription, per siteSite/yr40$1,200$48,000$48,000$49,440
2Implementation (fixed)Lot1$18,000$18,000——
3On-site trainingDay4$1,500$6,000——
4Badge printers (optional)Each40$310Optional——
Total (excl. optional)$72,000$48,000$49,440

Assumptions: 40 sites as listed in Attachment B; the district provides network access at each site by week 2; Year 3 includes a 3% increase as allowed by RFP section 7.4. Exclusions: integration with the student information system, quoted separately at $[x] if required. Validity: 120 days from the closing date.

Why it works: the line items follow the buyer's structure, every assumption that drives the price is stated and referenced to the RFP, the optional item is clearly separated, and the escalation is justified by an RFP clause.

How do evaluators assess price?

CheckWhat they look for
CompletenessEvery line filled; no blank cells or "TBD"
ConsistencyPrice matches the technical volume's scope, staffing and schedule
ReasonablenessComparable to other bids and their estimate
RealismLow enough to win isn't the test; low enough to be credible for the work described is
Total evaluated priceOften all years and options combined, using the RFP's formula
Best valueIn tradeoff evaluations, whether a higher price is worth the technical advantages

Mistakes that disqualify or cost points

  • Altering the buyer's price form (adding columns, merging rows, changing formulas).
  • Blank cells or "TBD." Many buyers treat these as non-responsive.
  • Price in the technical volume when the RFP separates them.
  • Arithmetic errors between unit price, quantity and totals.
  • A price that doesn't buy the technical approach, for example fewer hours than the staffing plan implies.
  • Unstated assumptions that later become change orders and damage trust.
  • Missing validity period or one shorter than the RFP requires.

How Iris helps

Iris is AI software for RFPs, security questionnaires and proposals.

  • Track what you promised. Commitments written into answers (for example a delivery date or a service level) are extracted when a project is finalized, with due dates, and can be filtered by project, owner and status.
  • Know the rules before you price. The RFP Analyzer summarizes the RFP and pulls requirements, key dates and scoring criteria, each cited to the source, so the pricing team sees the instructions that affect them.
  • Excel stays Excel. Iris works on Excel questionnaires across multiple tabs and writes answers back into the original workbook.

Iris is rated 4.8/5 on G2 from 92 reviews (November 2026). Try Iris free on an RFP you've already answered.

FAQ

What's the difference between a price proposal and a cost proposal?
In practice, often nothing. Strictly, a price proposal states what the buyer pays; a cost proposal breaks down your underlying costs (labor, materials, overhead, profit) so the buyer can analyze them.

Should I include price in the executive summary?
Only if the RFP allows it. Many formal RFPs require price to appear only in the price volume.

Can I offer alternative pricing?
Only if the RFP permits alternates. If it does, price the compliant option first and the alternative separately and clearly labelled.

How long should my price be valid?
At least as long as the RFP requires. Ninety or 120 days is common in public-sector bids, but follow the solicitation.

What if the price form doesn't fit my pricing model?
Ask a clarification question before the deadline. Don't alter the form.

See it live

Respond to RFPs
without the grind.

Book a demo and see your real auto-fill rate on a translation
RFP from your pipeline.