Skip to main content
DoneThat

AI Adoption GuideProcurementSelect

Competitive pressure analysis

AI surfaces how peer benchmarks and competitor pricing compare to the selected supplier's quote, flagging negotiation leverage points.

Procurement processRequestApproveSourceEvaluateSelectOrderReceiveReview

By Don, DoneThat’s AI coach · updated

Pressure exists only if you can actually switch

Name the alternative before you name the gap. Competitive pressure analysis is the check a negotiator runs after a preferred supplier is in view: does this quote sit above should-cost, above other qualified bids, and still look cheap once you add the cost of leaving? If you cannot name a second source that is already allowed to receive the award this cycle, you do not have pressure. You have a spreadsheet.

Two qualified sources is pressure. A scraped list price is not. Qualification means the plant or distributor can take the volume under the same spec, insurance, and quality gates you would use on an award, not that a model found a similar company on the web. Names from ai supplier discovery are a longlist. Until supplier quality, legal, and the plant have marked a row as invite-ready, treating that row as a walk-away is a bluff. The incumbent will test it.

Marketplace list prices fail the same test. Amazon Business, or any public catalog, is a common false peer set for MRO and indirect. Pack quantity, mill certs, lot traceability, freight, payment terms, and whether anyone will stand behind a quality escape are not the same as a contracted industrial bid.

The same warning applies to single-source risk flagging. Concentration tells you that you may need a second source. It does not create one. Write the status of each alternative: awarded last cycle, quoted this event and qualified, in qualification, or discovery-only. Only the first two count as pressure this week.

The comparison usually lives in the sourcing suite that already holds the event: SAP Ariba, Coupa, Keelvar, Jaggaer, or the bid file exported from them. Those systems collect competing returns, event history, and, where you use them, auction logs. They do not know your switching cost unless you put it in. Your job is to mark the rows, not to accept a ranked savings label.

Compare the quote to should-cost, other bids, and switching cost

Run three comparisons on the same basket, line by line where the lines are actually comparable. Then write the BATNA in one sentence you could execute this cycle.

Should-cost. Pull the range you built before the RFQ from market price benchmarking: indices, conversion, your own history. If this quote sits inside that range, the gap is not automatically "the supplier is high." The range may have been optimistic, the spec may have moved, or freight and payment terms may have been left out. If the quote sits above the range, name the drivers (index, yield, labor, logistics, margin) instead of a single delta. Do not invent a BATNA percentage from the gap. A printed "room" figure is a guess at the concession.

Other qualified bids. Overlay only returns from suppliers who could take the award. Normalize units, Incoterms, payment days, tooling amortization, and which SKUs they actually bid. A lower total from a bidder who skipped the proprietary or high-volume lines is not a competing offer. Where baskets differ, compare the overlap and keep unique lines on a separate sheet.

Switching cost. Add what it would take to move volume this cycle: first-article approval, consignment or VMI unwind, dual inventory, plant training, EDI setup, and the operations hours to run two sources. If switching cost eats the price gap on the overlapping SKUs, you do not have a cheaper alternative. You have a cheaper unit price with a more expensive landing.

Write the BATNA as one executable sentence: if they will not [specific concession on named lines or terms], we will [specific award or split you can actually issue this cycle]. "We have room" is not a BATNA. "We will auction this" is not a BATNA unless the event is already approved and staffed.

Feed that sentence, the three comparisons, and the evidence you are willing to show into negotiation position generation. The briefing is a place to argue, not a script and not a supplier-facing file.

Worked example: fasteners with two distributors and a messy basket

This walkthrough is illustrative, not a measured result, and it does not claim a savings rate.

A discrete manufacturer is awarding the annual fasteners basket. The incumbent quoted the full list: catalog items plus made-to-print parts on the plant's drawings. Two other distributors are already on the approved list, carry the grades the plants will accept, and both returned bids. Neither covered the made-to-print set in full. A fourth name appeared from a discovery run: not on the approved list, no insurance on file, no quality gate. It is not a dual source. Naming it in the room would be a bluff.

The category lead lined up three views, not a single gap number.

Should-cost on the catalog SKUs used steel index movement, the last award's conversion, and freight to the plants. The incumbent sat above that range on a handful of high-volume SKUs and inside it on the rest. The made-to-print lines have no honest peer. The should-cost there is last year's price plus index, not a scraped catalog number.

The other qualified bids undercut the incumbent on much of the catalog overlap, not on the basket, because the basket includes parts they did not quote. The useful comparison is the overlap only, plus a note that moving catalog volume does not move the made-to-print volume.

Switching cost on catalog SKUs is dual stocking, EDI, and plant habit. On the made-to-print parts it is first-article, possible tooling, and a quality sign-off the others have not started. The catalog price gap does not pay for requalifying the specials this quarter.

BATNA, one sentence: if the incumbent will not meet the qualified second bid on the overlapping catalog SKUs, those SKUs go to Distributor B, and the made-to-print parts stay with the incumbent until a second source is actually qualified.

What the lead does not say: that Amazon lists the same hex cap cheaper, that a discovery name is ready, or that a reverse auction is next week.

Do not threaten a reverse auction you cannot run

An auction is an event with rules, a bidder field, and a reserve you are prepared to live with. It is not a sentence in a negotiation. If legal, the category playbook, or the plants will not allow an auction, do not mention one. If you have only one qualified bidder, an auction is theater. Threatening an event you then fail to open tells the incumbent the rest of the brief is also a bluff.

When an auction is a real option, it is a separate design problem: lotting, reserve, whether the field will show up, and how you stop bid shading. That work sits in reverse auction ML optimization, in the same class of sourcing tools already named above. Do not skip from a high quote to an auction because a dashboard suggested tension. Confirm the field, the policy, and operations' appetite first. Until the event is scheduled, it is not part of the BATNA sentence.

Keep the comparison off the incumbent's desk

The pack is for the negotiation team: the three comparisons, the BATNA sentence, and the evidence you are willing to show. It is not a leave-behind.

Sending the analysis to the incumbent is a common leak. The file usually contains the other bidder's prices, your should-cost range, and your switching-cost estimate. Once they have that, they can price just inside your walk-away, attack the second source, or stall qualification. If you need a supplier-facing ask, send only the lines and terms you are challenging, with evidence you would be comfortable seeing in their inbox: index movement, volume, a should-cost range that does not name the other bidder. Do not paste the overlay.

Mark the pack internal. After the meeting, record which challenges were used and which concessions actually arrived. That is how the next brief stays honest.

If you cannot name a second qualified source, stop calling the exercise competitive pressure. Close the award, or start qualification, but do not run a negotiation you cannot leave.

Is this worth automating for you?

Whether this pays back depends on how much time it takes your team today. Most teams estimate that from memory, and the estimate is usually wrong in one direction or the other.

DoneThat reconstructs where the time actually went, with no timers to forget, so you can measure the baseline before committing to a project and check the gain afterward.

Measure the baseline first