Fixed fee
Best when scope is clear, deliverables are concrete, and timeline is known. Vendor carries scope risk and may price defensively. Avoid for genuinely uncertain scope; vendors will pad pricing or push scope disputes to change orders.
Section: 07 / PricingSection Deep Dive
Section Guide / Pricing
Structuring the RFP Pricing Section So Proposals Are Comparable
The pricing section is where vendors hide differences in scope assumptions and where evaluators get anchored before they finish the technical review. A pricing format that gets line items right, separates cost from technical, and locks change-order rates at the proposal stage eliminates most of the post-award pricing disputes that follow from a free-form cost narrative.
The Five-Category Line-Item Structure
The cost section should require vendors to break out costs into the same five categories so proposals become directly comparable. Without a defined structure, vendor A quotes a single all in number, vendor B itemises every line, and the evaluation team spends hours normalising the comparison. The structure to require:
| Category | What it covers | Format requested |
|---|---|---|
| 1. One-time implementation | Labour by phase, software licences purchased outright, infrastructure provisioning | Per phase: hours by role, blended hourly, total cost |
| 2. Recurring subscription / SaaS | Annual subscription per user / per module / per platform | Year 1, year 2, year 3 with renewal escalation disclosed |
| 3. Optional add-ons | Premium support, additional licences, deferred features, accelerated delivery | Per-unit price + validity period (typically 90 days from proposal) |
| 4. Travel and expenses | Travel for project work above standard remote / on-site mix | Capped or estimated; preapproval threshold; T&E policy applied |
| 5. Third-party costs | Pass-through costs (Stripe fees, AWS infrastructure, third-party APIs) | Pass-through at cost or with disclosed markup; vendor identifies billed party |
For a 3 year SaaS engagement, the line items collapse into a total cost of ownership model. Year 1 typically includes high implementation + subscription. Years 2 and 3 are subscription only plus expected renewal escalation. The standard 7 to 10 percent annual renewal uplift compounds: a 7.7 percent average uplift turns a $200K year-1 contract into a roughly $290K year-5 contract before discount. Negotiate renewal caps in the RFP.
The Sealed Cost Envelope and Why Federal Practice Uses It
Federal procurement under FAR Part 15 separates technical and cost evaluation. Technical evaluators do not see the cost proposal; cost evaluators do not see the technical proposal until after technical scoring is complete. The practice exists because evaluators who know the price tend to score the cheaper proposal higher on technical, even when they think they are being objective. The bias is well documented and the GAO has reviewed many bid protests where cost contamination of technical scoring was the issue.
Private sector procurement does not have to adopt full FAR Part 15 discipline but should adopt the principle. Three practical patterns:
- Separate documents. Vendors submit a technical proposal document (containing no pricing) and a separate sealed cost proposal. Evaluators score technical first; cost is opened after technical scoring is signed off.
- Separate evaluators. Technical evaluators and cost evaluators are different people. Technical scoring is locked before cost is shared.
- Hybrid model. Cost is included but evaluators are asked to score technical before they review cost. Less rigorous but reduces friction for smaller procurements.
FAR Part 15 reference: acquisition.gov/far/part-15 covers contract by negotiation. GAO bid protest decisions on cost contamination are searchable at gao.gov/legal/bid-protests.
Fixed Fee, T&M, Blended Rate, and When Each Applies
The fee structure shifts risk between client and vendor. Fixed fee puts scope risk on the vendor; the vendor must price defensively. T&M puts scope risk on the client; the vendor invoices for the hours actually worked. Blended rate sits in between. The RFP should ask the vendor to propose against the structure that fits the engagement and disclose the alternative structures.
Time and materials (T&M)
Best for exploratory or genuinely uncertain scope. Vendor invoices actual hours at agreed rates. Client carries scope risk. Always include a not-to-exceed cap and weekly burn reports.
Blended rate
Single rate that averages across roles. Simpler to invoice. Hides the partner / associate / staff leverage so client cannot tell if junior or senior time is being delivered. Demand the underlying tiered rate even when proposing blended.
Tiered rate card
Different rate per role (partner, senior, manager, staff). More transparent. Easier to negotiate. Standard for legal and consulting; less common in technology delivery.
Phased (fixed + T&M)
Discovery phase priced fixed; delivery phase priced T&M or rescoped after discovery. Useful when discovery output materially changes the delivery scope. Common in technology projects with significant upfront unknowns.
Capped fee
Fixed price up to a ceiling; T&M below the ceiling. Vendor stops at the cap. Avoid race-to-the-cap dynamics by agreeing what triggers the cap (delivery of named milestones, hours worked, or both).
Outcome / success fee
Some or all of the fee tied to a measurable outcome. Pure success rare and difficult to operate; partial (20 to 40 percent on outcomes) more common. Outcome must be attributable to the vendor's work, not externally driven.
Per-unit / per-transaction
Common for high-volume repeatable work (per-contract review, per-ticket support). Scales naturally with usage; budgeting requires forecast accuracy.
Optional Adds Priced at Proposal Stage
Most projects discover during planning that one or two scope items the client thought were nice to have are actually important enough to include. By that point negotiation leverage is gone; the vendor knows you have signed. The fix is to require option pricing at the RFP stage. Each potential add is listed as a priced line item with no obligation to purchase. The client can include or exclude during contract finalisation, exercising the option at the pre signed price.
Common options to ask for:
- Extended warranty (typically 6 months at 15 to 25 percent of base implementation fee)
- Premium support tier with faster SLAs
- Additional named users / additional modules / additional countries
- Deferred features the client may want in phase 2
- Accelerated delivery (compressed timeline with premium pricing)
- Additional training cycles for change management
- Post launch maintenance retainer (monthly fee)
- Data migration of additional historical data beyond standard scope
Each option includes per unit price, conditions under which it would be invoked, and a validity period (typically 90 days from proposal submission). Demand a longer validity (180 days) for capital-intensive projects where contract negotiation runs months. Useful reference on cost element structure: GAO Cost Estimating and Assessment Guide.
Frequently Asked Questions
Q.Why use a sealed cost envelope?+
A.To prevent cost-anchored scoring. When evaluators see the price before they finish technical scoring, the highest-scoring proposal often becomes whichever vendor's price they noticed first. FAR Part 15 federal procurement practice separates technical from cost so technical evaluators score blind. Private-sector procurement increasingly adopts the same discipline. Even when evaluators try to be objective, knowing the price colours the technical assessment.
Q.Should the RFP include a budget range?+
A.Yes, in most cases. The Hackett Group benchmark shows that RFPs sharing budget ranges receive 40 percent more compliant proposals than RFPs that hide the budget. Hiding the budget guarantees one of: every vendor anchors at the highest plausible number they think you can pay; junior vendors propose half the scope you need and senior vendors disqualify themselves. State a range (commonly plus or minus 25 percent of target) so vendors can size proposals appropriately.
Q.What goes in a pricing line-item breakdown?+
A.Five categories at minimum. One-time implementation cost (labour by phase, software licences, infrastructure). Recurring subscription / licence / hosting. Optional add-ons (priced separately so the client can include or exclude). Travel and expenses (capped or estimated). Third-party costs (passed through with markup disclosed). The breakdown lets you compare apples to apples even when vendors have different bundle structures.
Q.How do I handle option pricing?+
A.List options as separate priced line items with no obligation to purchase. Common options: extended warranty, premium support tier, additional user licences, deferred features, accelerated delivery. Each option includes the per-unit price, the conditions under which it would be invoked, and a validity period (typically 90 days from proposal submission). Option pricing lets you negotiate the final scope after award without renegotiating each item from scratch.
Q.Should pricing include change-order rates?+
A.Yes. Include the rate card the vendor will use for change orders and out-of-scope work, by role / level. Locking the change-order rate at RFP stage prevents the surprise of premium-priced change orders six months in. Common practice: change orders priced at the same blended rate as the base engagement plus a small markup (typically 5 to 10 percent) to compensate for the disruption of changing scope mid-engagement.
Q.What does 'best and final offer' mean?+
A.BAFO is the negotiation round after initial proposals have been scored. Top-scoring vendors are invited to submit a best and final offer, typically a revised price with any updated scope or terms. BAFOs are useful when two or three proposals are close on technical scoring and price negotiation will move the decision. They are unhelpful when the initial proposals already establish a clear winner; BAFOs in that situation are sometimes seen as predatory pricing-pressure with no genuine open scope question.