How to Use Competitive Bids to Lower Software Prices

This article is part of our IT Contract Negotiation Strategy pillar. Competitive bidding builds on your BATNA — the alternatives you have evaluated are what give competitive bids their credibility and commercial power.

Why Competitive Bidding Works on Incumbent Vendors

Competitive bidding works for a simple commercial reason: incumbent software vendors have invested significant effort in retaining your account, and the threat of losing it — even partially — activates a fundamentally different commercial response than the threat of you negotiating harder on a renewal you will sign regardless.

Most enterprise software renewals involve the buyer negotiating against a vendor who knows the renewal is almost certain. The vendor's primary objective in these negotiations is to maximise the deal value from an account they will retain. But when a genuine competitive evaluation is underway, the vendor's primary objective changes: it becomes ensuring they retain the account at any commercially viable price. This psychological and commercial shift from "maximise" to "retain" typically unlocks 15–25% of additional discount beyond what was available in the purely bilateral renewal negotiation.

This effect persists even when everyone in the room understands that switching is unlikely. It is the credible uncertainty — not the certainty — of switching that generates the commercial response. See our guide on building a credible BATNA for the broader framework, and our analysis of vendor negotiation psychology for why urgency and threat perception drive vendor commercial flexibility.

Designing an Effective Software RFP

The quality of your RFP determines the credibility of your competitive process. A poorly designed RFP — one that clearly cannot be answered competitively, or that signals the incumbent will win regardless — produces no commercial leverage. A well-designed RFP creates genuine competitive tension.

Principles of an Effective Software RFP

• Vendor-neutral requirements: Requirements must be written against business outcomes, not incumbent-specific technical features. "User authentication that supports SAML 2.0 and OAuth 2.0" is vendor-neutral; "authentication using [specific vendor product]" disqualifies competitors by design.
• Realistic scope: The RFP must cover a scope that alternative vendors can genuinely address. An RFP that requires replication of 15 years of customisation in the incumbent's specific architecture is not credible as a competitive document.
• Explicit evaluation criteria: Include commercial evaluation criteria — total cost of ownership, pricing structure, escalation terms, exit rights — alongside functional and technical criteria. This signals that commercial terms will be evaluated, not just features.
• Defined timeline: A specific, plausible timeline for evaluation, decision, and implementation communicates that the process is real and that the alternative vendor has a genuine opportunity to win.
• Reference customer requirements: Requesting references from comparable deployments signals that the evaluation is substantive, not cosmetic.

What to Include in the Commercial Section

The commercial section of your RFP should request responses on: all-in pricing including implementation, training, and first-year support; annual pricing for years 1–3 of the proposed contract; annual escalation terms; volume discount structures; exit and termination rights; SLA commitments and financial remedies; and total 5-year cost of ownership. This level of commercial detail in the RFP forces alternative vendors to make specific commercial commitments — which in turn provides the incumbent with specific competitive pricing to respond to.

The 6-Phase Competitive Bidding Process

Managing the Incumbent's Response to a Competitive Process

Experienced enterprise software vendors have well-developed playbooks for responding to competitive threats. Understanding these responses — and how to manage them — is essential for maintaining the leverage generated by the competitive process.

The Incumbent's Pre-emptive Discount Offer

Almost every incumbent will offer an improved commercial position as soon as they learn a competitive evaluation is underway. The instinct for enterprise buyers is often to accept this offer — the incumbent has moved, the risk of disruption has been avoided. This is almost always the wrong response. The pre-emptive offer is typically the beginning of the incumbent's commercial flexibility, not the end. Accepting it prematurely closes off the additional 10–20% of value that the competitive process would have generated by month 6–7.

The appropriate response to a pre-emptive offer is acknowledgment without commitment: "We appreciate that you've updated your commercial position. We'll continue our evaluation process and be in touch with our decision by [date]."

The Relationship Escalation

When commercial concessions are not immediately effective, incumbent vendors frequently escalate the relationship — bringing in senior executives, customer success leadership, or regional vice presidents. The goal is to make the decision feel like a personal or relationship choice rather than a commercial one. Ensure that your executive team understands the strategy and is aligned not to make commitments in these conversations. Relationship escalation from the vendor is a signal that the competitive process is working.

The FUD Campaign

Fear, Uncertainty, and Doubt — FUD — about alternative vendors is a standard incumbent response to competitive threats. "That vendor doesn't have your implementation scale." "They've had significant customer churn in your industry." "The migration will take 18 months and costs three times what they quoted." Some FUD contains genuine information; most is strategically calibrated to reduce your confidence in alternatives. Validate all FUD claims through independent reference checks and technical assessment rather than accepting them at face value.

Typical Savings Achieved Through Competitive Bidding

Note: Savings are illustrative based on practitioner experience across comparable engagements. Actual outcomes vary by organisation size, commitment level, deal complexity, and negotiation quality.

Common Competitive Bidding Mistakes

• Using incumbents' proprietary requirements: Writing RFP requirements that only the incumbent can meet defeats the purpose of competitive evaluation and signals that the process is cosmetic.
• Accepting the pre-emptive offer: Taking the incumbent's first improved position closes off the additional value the full competitive process would generate.
• Starting too late: A competitive process needs 6–9 months to work effectively. Starting 60–90 days before expiry means you cannot complete genuine technical evaluation — and experienced incumbents know it.
• Sending mixed internal signals: If your IT or business stakeholders communicate to the incumbent account team that they will not switch, the commercial leverage evaporates. Maintain internal discipline on what is communicated to the vendor.
• Using only one alternative: A single alternative creates a bilateral dynamic. Two or three alternatives create a competitive market dynamic in which the incumbent is competing for retention rather than negotiating with a captive buyer.
• Not leveraging the RFP in contract negotiations: The competitive process generates leverage for contract terms — SLAs, exit rights, escalation caps — not just price. Failing to use this leverage for contract protections leaves long-term value on the table.

Vendor-Specific Competitive Dynamics

Oracle: PostgreSQL and Cloud Migration Are Powerful Competitors

Oracle is the incumbent vendor most susceptible to competitive bidding because genuine, credible alternatives exist for most workload types. The threat of migrating to PostgreSQL (with cloud-managed services like AWS Aurora or GCP AlloyDB), combined with the threat of moving Oracle Java workloads to OpenJDK, creates a multi-dimensional competitive pressure that Oracle's commercial teams are well-trained to respond to. See our Oracle negotiation guide for the full leverage framework.

Salesforce: Microsoft Dynamics Creates Genuine Competition

Salesforce is highly sensitive to competitive evaluation involving Microsoft Dynamics 365. Following Microsoft's investment in Dynamics' Copilot capabilities and its integration with the Microsoft 365 ecosystem, the competitive case for Dynamics at large enterprises has materially strengthened. Even organisations that ultimately stay on Salesforce consistently achieve better commercial terms when Microsoft has provided a credible competitive proposal. See our Salesforce vs Dynamics comparison for the detailed analysis.

VMware: Migration Threat Is the Primary Lever

In the post-Broadcom acquisition environment, VMware has limited pricing flexibility on its new subscription model. The primary competitive lever is the migration threat — to Nutanix AHV, to cloud-native alternatives, or to Microsoft Hyper-V for organisations with strong Microsoft relationships. See our VMware alternatives comparison and Broadcom VMware negotiation guide for the specific strategy.

Frequently Asked Questions