Latest / The Buyer's Side with Fexingo: Procurement, Sourcing, and B2B Purchasing Decisions / How One Buyer Cut Cost Overruns with a Supplier Escalation Clause
Transcript
- Lucas: You know, we've spent the last twenty episodes talking about cutting costs from every angle imaginable. But there's one conversation that comes up in every procurement office that we haven't touched: what happens when your supplier raises prices mid-contract. Luna: Oh, that's the dreaded price increase notice. The email that makes every buyer's stomach drop. Lucas: Exactly. And this week I talked to a procurement director at a mid-sized industrial parts manufacturer. He was getting hit with surcharges every quarter — raw material, freight, energy. By the end of the year, his actual spend was running nine percent over what he'd signed off on. Luna: Nine percent. That's not a rounding error. That's a whole project's budget gone. Lucas: Right. And his first instinct was to fight each surcharge individually. But that's exhausting and it breeds bad blood. So instead, he went back to his master service agreement and added something he'd never used before: a formal escalation clause tied to a published index. Luna: So not just a 'we reserve the right to raise prices' line. What did it actually say? Lucas: The key was that it linked price adjustments to a specific, verifiable benchmark. In his case, he used the producer price index for industrial metals. Every quarter, they'd look at the index movement. If it moved more than two percent from the base, the contract price would adjust accordingly — but only by that percentage, and only with a cap and a floor. Luna: A cap and a floor. So the supplier is protected if their costs spike, but you're not exposed to unlimited increases. Lucas: Exactly. In his case, the cap was plus or minus five percent over the contract term. The floor was actually more important than the cap, because when metals prices dropped, the clause forced the supplier to pass those savings back to him. Luna: That's the part people forget. Escalation clauses run both ways. It's not just a price increase mechanism. Lucas: Right. And that's what changed the negotiation dynamic. He told me that once the clause was in place, the quarterly conversations stopped being adversarial. Instead of the supplier coming in with a demand, they were both just looking at the same index number and doing the math. Luna: It becomes a data conversation instead of a power conversation. Lucas: Yeah. And that shift alone saved him about nine percent in year one. But what's interesting is that the savings didn't all come from price adjustments. Some of it came from the supplier's behavior changing before the clause ever kicked in. Luna: How so? Lucas: When the contract was being renegotiated, the supplier had to be honest about their cost structure because the index was going to be the referee. They couldn't pad their quote as much, because if they priced in a buffer and the index didn't move, they'd look overpriced. So the initial quotes came in lower. Luna: So the clause actually reduced the chance of getting gouged upfront. That's a double win. Lucas: It is. But he also told me about a couple of mistakes he made along the way. His first draft had the index tied to a broad measure like CPI, which didn't reflect his actual inputs. So the adjustments were always out of sync. Luna: Right, you need a benchmark that tracks what you're actually buying. CPI moves differently than copper or resin. Lucas: And his second mistake was that he didn't set a review date. The clause was in the contract, but nobody remembered to actually check the index every quarter. So it sat dormant until a supplier sent a notice, and then they had to scramble to apply it retroactively. Luna: So it's not just about writing the clause. It's about building a calendar reminder and actually having the conversation. Lucas: Exactly. And that's where the real discipline comes in. You have to be willing to have the conversation even when prices are stable, because that's when you build trust. Luna: I want to jump in here because this reminds me of something from our own experience. We've been lucky to keep this show ad-free, and that's only because listeners who find these conversations useful occasionally decide to support it. If this episode saves you from a nine percent overrun, maybe consider that. Lucas: Yeah, it's a small gesture that keeps us going. If you're inclined, you can find us at buy me a coffee dot com slash fexingo. No pressure, just knowing that the work matters is enough. Luna: And we get back to the topic. So, Lucas, what about the psychological shift? You mentioned that the supplier stopped padding quotes. Was that a one-time thing or did it persist? Lucas: It persisted, because the clause changed the incentive structure. Once the supplier knew that any cost increase had to be justified by the index, they stopped trying to sneak in surcharges. They knew we'd just pull up the data and say, 'Actually, the index is down two percent, so your price should be lower.' Luna: That must have felt great. Like the scales finally tipped back to the buyer's side. Lucas: It did. And it's a lesson that applies beyond just raw materials. I've seen escalation clauses work for logistics, for energy contracts, even for software licensing when the pricing is tied to usage metrics. Luna: So what's the one thing our listeners should take away from this episode? Lucas: If you're not using an escalation clause tied to a relevant index, you're leaving money on the table. But the real insight is that it's not just a financial tool — it's a relationship tool. It turns a zero-sum negotiation into a collaborative check-in. Luna: And remember, you need the right benchmark, a cap and a floor, and a calendar reminder. Otherwise the clause is just a piece of paper. Lucas: Exactly. So next time you're drafting a supplier agreement, don't just think about the price. Think about how you're going to handle the price three quarters from now.