The First Quote that Set the Price: How an Anchor Inflated a Software Procurement
A real-world example of Anchoring in action
Context
A mid-sized retail chain planned to modernize its inventory system and allocated a preliminary budget based on a single vendor’s pitch. The procurement team had limited time and pressure from executives to move quickly so stores could use the new system before peak season.
Situation
The procurement lead received an initial proposal from a well-known software vendor quoting $1.2 million for licensing, implementation, and first-year support. Rather than running a broad RFP, the team invited two additional vendors but continually compared offers back to the $1.2M figure.
The bias in action
The procurement team treated the $1.2M proposal as the implicit market price and evaluated later proposals relative to that anchor instead of on absolute value or modular cost components. When a second vendor proposed $980,000, the team framed it as a significant saving and cut deeper into requirements to justify acceptance. A third vendor presented a modular option at $820,000, but discussions kept comparing missing features against the anchored $1.2M package instead of assessing cost per needed capability. Anchoring also influenced the negotiation reserve: negotiators aimed for offers 5–10% below the anchor rather than benchmarking to independent cost estimates.
Outcome
The chain selected the $980,000 vendor after trimming desired customizations, believing they had captured good value relative to the anchor. Six months after rollout, hidden integration costs and several required custom modules raised total spend to $1.06M, only ~12% under the original anchor but ~30% above an independently benchmarked solution that would have met most needs. The rushed, anchor-driven decision delayed full functionality by three months and required a supplementary contract to fix data synchronization issues.