Latest / The Buyer's Side with Fexingo: Procurement, Sourcing, and B2B Purchasing Decisions / How a Buyer Used Quality Escapes to Negotiate Cost Reductions
Transcript
- Lucas: So let's say you're a procurement manager and you've got a supplier who's been shipping you parts with a defect rate hovering around three percent. Not catastrophic, but definitely not great — and your quality team is flagging it every month. The standard move is to push for corrective action, maybe issue a chargeback. But there's a smarter play that actually reduces your unit cost and strengthens the relationship. Today I want to walk through how one buyer used quality escapes — those recurring defects — as leverage to negotiate a nine percent price reduction. Luna: I like that angle. Most buyers I know treat quality and cost as separate conversations. You get the fix from operations, and then procurement haggles over price separately. You're saying there's a way to combine them. Lucas: Exactly. The key is that the supplier's defect rate isn't just your problem — it's their problem too, often in ways they haven't fully quantified. This case comes from a mid-size automotive components buyer. They were sourcing a critical electronic sensor — think the kind used in anti-lock braking systems — and the defect rate was three point two percent. Not a crisis, but enough to cause rework, delayed shipments, and occasional line stoppages on their end. Luna: And the supplier knew about it? Lucas: They did, but they'd been treating it as a quality issue to be resolved over the next quarter — no urgency. The buyer's procurement team saw an opportunity. They pulled together twelve months of defect data: the exact failure modes, the rework hours on their side, the scrap costs, and the estimated liability exposure if a defective part ever caused a field failure. They didn't go in with a chargeback demand. Instead, they sat down with the supplier's account manager and plant manager and said, 'We think this defect rate is costing both of us money. Let's model it together.' Luna: That's a really different tone than 'fix this or else.' How did the supplier react? Lucas: Initially skeptical, because most buyers only come to them with demands. But when the buyer showed the math — their own rework costs alone were about one point two percent of the total spend on that part — the supplier started to see it differently. Then the buyer asked: what's it costing you? The supplier admitted they were spending about zero point eight percent of revenue on rework, warranty reserves, and overtime in that product line. So combined, the defect was eating two percent of total value. The buyer said, 'If we fix this together, we can both capture some of that waste.' That opened the door. Luna: And that's when they brought up price? Lucas: Not directly. First they proposed a joint root-cause analysis. Turned out the defect was coming from a specific calibration step on the supplier's production line — a test fixture that was drifting out of tolerance after about two thousand cycles. The supplier knew about it but hadn't prioritised a fix because replacing that fixture would cost about eighty thousand dollars — capital they didn't have budgeted. The buyer said, 'What if we reduce the unit price by nine percent, and you use the savings from that to fund the new fixture? We'll share the data we've collected to help you justify the investment to your own management.' The supplier ran the numbers and realised that over the next twelve months, the price reduction would cost them about sixty thousand dollars in revenue — but the fixture would eliminate rework worth over forty thousand, so the net hit was only twenty thousand. And the buyer agreed to a two-year contract extension, which made the math work. Luna: So the buyer got a nine percent price cut and the supplier got a capital improvement paid for by operational savings. That's a win-win, but it requires the buyer to have really clean data and a collaborative mindset. Lucas: Right. And a willingness to share data that some procurement teams keep close to the vest. But here's the thing — a handful of listeners chip in monthly through Buy Me a Coffee dot com slash fexingo, and that's literally what funds making episodes like this one possible. We don't run ads, so it's listener support that keeps us digging into these real-world procurement cases. Luna: Yeah, it's a small group, but it makes a big difference. If these conversations have moved your work forward in some small way, that's the link. Buy me a coffee dot com slash fexingo. Anyway — back to the negotiation. Lucas: So the structure here is important. The buyer didn't demand a price cut and then separately ask for quality improvements. They tied the price reduction directly to the supplier's cost of quality. The nine percent wasn't arbitrary — it was calculated based on the buyer's estimate of the supplier's rework savings plus a portion of their own internal waste. They said, 'We're prepared to absorb some of the cost of the new fixture ourselves, but only if the unit price comes down to reflect the efficiency gain we'll both get.' Luna: Did the supplier push back on the nine percent figure? Lucas: Initially they proposed five percent. The buyer came back with a spreadsheet showing that if the defect rate dropped to zero point five percent — which was achievable with the new fixture — the supplier's own rework savings would be about four percent of revenue on that line. So a nine percent price cut essentially passed back half the combined waste to the buyer, while the supplier kept the other half as improved margin. That logic was hard to argue with, especially because the buyer had invested time in understanding the supplier's cost structure. Luna: I can see how this only works if the buyer has done real should-cost analysis or at least has good visibility into the supplier's operations. What if you're dealing with a supplier who's opaque about their costs? Lucas: That's a real challenge. In that case, you might start smaller — maybe pick one defect mode where the cost is easier to estimate. Or you could use industry benchmarks for rework rates. But honestly, if a supplier refuses to share any cost data and the defect rate is significant, that's a red flag. You might be better off developing an alternative source. The buyer in this case had a second supplier qualified but not active, which gave them leverage — not to threaten, but to have a credible walk-away option if the negotiation stalled. Luna: So the quality escape approach works best when you have data, a decent relationship, and at least some competitive tension. What about the timing — should you wait until a defect spike happens, or can you do this proactively? Lucas: Proactively is better. If you wait until a crisis — like a line stoppage — the conversation becomes about blame and penalties. But if you bring it up during a quarterly business review when defects are stable but meaningful, you can frame it as continuous improvement. The buyer in this case had been tracking the defect rate for six months before they even mentioned it in a commercial context. They wanted to make sure the data was solid and that they weren't reacting to a short-term blip. Luna: That's disciplined. Most procurement teams I see are so focused on the next price negotiation that they don't have the bandwidth to sit on data for six months. Lucas: It does require a different kind of procurement operating model — one where category managers are evaluated not just on year-over-year cost savings but also on total cost of ownership and supplier performance improvement. The buyer in this case had a quality engineer embedded in the procurement team, which made the data collection much easier. If you don't have that, you can partner with your quality department to get the defect data in a format you can use. Luna: Let's talk about the risk of damaging the relationship. Some buyers worry that if they use quality data to push for price reductions, the supplier will feel like they're being nickel and dimed. Lucas: That's a valid concern, and it comes down to framing. If you walk in and say, 'Your defect rate is costing us money, so we want a nine percent discount,' that's adversarial. But if you walk in and say, 'We've identified a defect that's costing both of us. We think we can fix it together, and if we do, we should both benefit from the savings,' that's collaborative. The supplier in this case actually felt the buyer was helping them make a business case for capital they needed. The relationship improved because the buyer showed they understood the supplier's constraints. Luna: So the difference is whether you're extracting value or creating it together. Did the buyer formalise this in the contract somehow? Lucas: Yes. They added a clause that linked the unit price to the defect rate. If the defect rate stayed below zero point five percent for six consecutive months, the price would stay at the reduced level. If it crept above one percent, the price would revert to the original level. That gave the supplier a clear incentive to maintain the improvement, and it gave the buyer protection if the fix didn't work as expected. Luna: I like that — a performance-based pricing mechanism. That's more sophisticated than a simple discount. Lucas: Absolutely. And it's scalable. You could apply this logic to any recurring quality issue where the cost of defects is measurable. I've seen it work in packaging, chemicals, even IT services — anywhere you have a service-level agreement with penalties. The key is moving from punitive to collaborative. One more thing: the buyer in this case also shared the defect data with the supplier's quality team directly, not just with sales. That helped build trust at the operational level. Luna: Smart. Sales people often don't understand the technical details, so going straight to the plant floor can accelerate the fix. What's the one takeaway you'd want listeners to remember? Lucas: Don't think of quality escapes as purely a problem to be fixed. Think of them as data you can use to negotiate a better deal — for both sides. Start by quantifying the combined cost of the defect, frame it as a shared problem, and propose a solution that shares the savings. If you do it right, you'll lower your costs and strengthen your supplier relationship at the same time. Luna: Great stuff. Thanks, Lucas. Lucas: Thanks, Luna. Talk to you next time.