How do you price a deal that has a hidden multi-year volume commitment embedded in the procurement language?
Brief
Procurement hides volume commitments in "minimum purchase," "seat reservations," or "usage tiers"—extract them before pricing locks in.
Detail
Hidden volume commitments cost $500K-$2M per deal when reps miss them in legal review. Procurement inserts volume gates into:.
- Minimum purchase: "Minimum 500 users or minimum $250K annual spend"
- Seat reservations: "1,000 licenses reserved for 12 months; overage billed at $X; unused seats non-refundable"
- Usage tier gating: "Consumption tier 1: 0-1M API calls. Tier 2: 1-5M API calls at 2.5× price; auto-escalate if you exceed"
- Data volume: "1TB data transfer included; overages at $0.15/GB. Projected monthly usage: 5TB = $600K annual overage"
Four Places Procurement Hides Volume
| Location | Language Signal | Extraction |
|---|---|---|
| RFP Appendix B | "Minimum seat commitment" | Ask: "Is this firm minimum or budgetary estimate?" |
| MSA Schedule | "Usage overage pricing" | Calculate: Average customer usage + projected growth = Year 1 overage liability |
| Statement of Work (SOW) | "Implementation success criteria" | Look for: "Adoption target: 70% of licensed users by Month 6" |
| Service Level Agreement (SLA) | "Overage support tiers" | Note: Higher SLA = premium per-seat cost not mentioned in base pricing |
Pricing Extraction Playbook
Week 1: Uncover Hidden Commitments
- Ask procurement directly: "You've listed 500-seat minimum. If customer uses 300 seats for first 12 months, do they pay for 500 or 300?"
- If "they pay for 500," calculate true Year 1 cost: (Quoted price × seat minimum) not (Quoted price × expected adoption)
- Flag to sponsor: If customer projected to use 300 seats, true cost is $250K higher than "sticker price"
Week 2: Negotiate Volume Floors
- Offer tiered commitment: "400 seats Year 1 (firm), 450 Year 2, 500 Year 3" instead of "500 immediately"
- Trade for procurement win: "We'll lock 500-seat minimum; you approve pilot in 30 days at 300 seats trial pricing"
- Add claw-back clause: "Unused seats over 70% adoption target credit toward Year 2"
Week 3: Lock Pricing
- MSA must state: "Minimum commitment: [X] seats/usage. Overages billed at [$/unit]. Customer invoiced for minimum OR actual usage, whichever is greater."
- Pricing schedule: Year 1 $X, Year 2 $X+Y (growth increment), Year 3 $X+Z
Red Flag Questions
- "Are there hidden consumption metrics in the SOW?" = Data transfer, API calls, concurrent users
- "Does the MSA define 'annual' as Jan-Dec or anniversary date?" = Matters for Year 2 true-up
TAGS: pricing,procurement,hidden-commits,volume-gates,seat-minimums,usage-tiers,msa,deal-math
FAQ
Where does procurement typically hide volume commitments in contract language? Four places: the RFP Appendix B as a "minimum seat commitment," the MSA Schedule as "usage overage pricing," the SOW as "implementation success criteria" like a 70% adoption target, and the SLA as "overage support tiers." Each can carry costs not shown in the base price.
How much can a missed hidden volume commitment cost on a single deal? The article puts hidden volume commitments at $500K-$2M per deal when reps miss them in legal review. A 500-seat minimum against a customer who only uses 300 seats can make true Year 1 cost $250K higher than the sticker price.
What's the key question to ask when you see a seat minimum? Ask procurement directly whether the customer pays for the minimum or actual usage: "If the customer uses 300 seats for the first 12 months, do they pay for 500 or 300?" If the answer is 500, you calculate true cost as quoted price times the seat minimum, not expected adoption.
How do you negotiate a volume floor instead of an immediate full commitment? Offer a tiered ramp such as 400 seats firm in Year 1, 450 in Year 2, and 500 in Year 3 rather than 500 immediately. You can trade a 500-seat minimum for procurement approving a 30-day pilot at 300-seat trial pricing, plus a claw-back that credits unused seats over the adoption target toward Year 2.
What red-flag questions surface hidden consumption metrics? Ask whether the SOW contains hidden consumption metrics like data transfer, API calls, or concurrent users, since a projected 5TB against a 1TB allowance at $0.15/GB is a $600K annual overage. Also ask whether the MSA defines "annual" as Jan-Dec or the anniversary date, because that determines the Year 2 true-up.