Latest / The Buyer's Side with Fexingo: Procurement, Sourcing, and B2B Purchasing Decisions / How a Buyer Cut Costs with Supplier-Led Design Changes
Transcript
- Lucas: So we're recording this in mid August 2026, and there's a story that's been making the rounds in procurement circles that I think really gets at something we haven't talked about yet on the show. Luna: What's that? Lucas: It's about supplier-led design changes. A mid-sized manufacturer in the Midwest... let's call them Precision Components... managed to cut their annual procurement spend by 22 percent just by inviting their top twenty suppliers to come in and redesign their own parts. Luna: That's a big number. And it's not just about asking for a lower price, right? It's about changing the specifications themselves. Lucas: Exactly. The buyers didn't go back to suppliers and say, 'give me a discount.' They said, 'here's the part we're buying from you. Show us how you'd make it cheaper without sacrificing performance.' And the results were pretty dramatic. One supplier swapped a machined aluminum bracket for a stamped steel version... same function, 40 percent cheaper. Another redesigned a plastic housing so it could be injection molded in a single shot instead of two, cutting their own cycle time and passing some of that savings along. Luna: So the suppliers are the ones coming up with the ideas. But what's in it for them? I mean, if they redesign a part to be cheaper to make, wouldn't that just mean they get paid less? Lucas: That's the obvious tension, and it's probably why a lot of buyers don't even ask. But the company structured this as a kind of innovation challenge. They set a target cost reduction for each part, and any supplier that came in below that target got a share of the savings as a bonus. Not a lower price... an additional payment on top of the new contract price. So the supplier actually makes more money if they find a smarter way to make the part. Luna: So it's win-win. But how did they get over the IP hurdle? I mean, if a supplier brings a design idea, who owns it? Lucas: That was probably the hardest part. The company had to put together a pretty detailed IP agreement upfront. The way they structured it: the supplier retains ownership of any new manufacturing process they develop, but the buyer gets a non-exclusive, royalty-free license to use the design for the life of the contract. And if the supplier wants to take that design to other customers, they can, as long as it's not the exact same part with the buyer's name stamped on it. Luna: That seems fair. But I'd imagine some suppliers were just too worried about giving away their secrets to even participate. Lucas: Right, and that's why they made it voluntary. They invited the top twenty suppliers, but only about twelve actually came to the first workshop. The ones that did were mostly smaller shops that saw this as a way to strengthen their relationship with a big customer. And the buyer made it clear that participation wasn't a factor in future sourcing decisions... at least not officially. But, you know, it's hard to ignore a supplier that's actively helping you save money. Luna: I guess not. So what kind of design changes actually came out of this? I mean, beyond the bracket and the housing. Lucas: There were a few categories. One was material substitution... like switching from a brass fitting to a coated steel one that still met the corrosion specs. Another was standardizing fasteners across multiple parts so they could buy in bulk. And then there were a few that were really clever, like redesigning a component so it could be assembled with a snap-fit instead of needing screws. That cut assembly time on the buyer's line by probably fifteen seconds per unit. Luna: Fifteen seconds doesn't sound like much, but when you're making millions of units... Lucas: Exactly. At scale, that's huge. And that's the thing about supplier-led design... it's not just about the direct cost of the part. It's about the downstream impact on your own manufacturing and logistics. One supplier suggested a change to the packaging that reduced the shipping volume by 30 percent, which meant more parts per pallet and lower freight costs. The buyer hadn't even thought about packaging as a design element. Luna: So how did they actually run the program? I'm guessing it wasn't just one meeting and done. Lucas: No, it took about six months from kickoff to implementation. They started with a workshop where they walked each supplier through the parts they were currently producing... the specs, the volumes, the cost breakdowns. Then the suppliers went away and came back with proposals a few weeks later. The buyer's engineering team reviewed each proposal for feasibility and performance, and then they negotiated the new pricing and the sharing arrangement. Luna: And the savings were 22 percent across the board? Lucas: Across the parts that were redesigned, yes. But not every supplier came back with a win. Three of the twelve proposals were rejected because they would have required too much change on the buyer's side... like retooling their own assembly line or changing a spec that a customer had mandated. So they had to be selective. But the ones that worked, worked really well. Luna: I love this idea, but I'm wondering... how do you scale it beyond a one-off initiative? I mean, this sounds like a lot of work to set up. Lucas: It is, but you don't have to do it for every part. The key is to focus on the highest-spend categories where there's real engineering complexity. And you can also build it into your regular sourcing process. Instead of just sending out an RFP with a fixed spec, you ask suppliers to propose alternative designs as part of their bid. That's a way to institutionalize this without a separate program. Luna: That makes sense. But there's a risk, isn't there? If you're always asking for design changes, you might end up with a bunch of parts that aren't standardized across your entire product line. Lucas: That's a real concern. And that's why the buyer in this case was careful to designate certain parts as 'design-freeze'... no changes allowed, usually because they were already optimized or because regulatory requirements made any change too costly to re-certify. But for the rest, they gave suppliers a lot of latitude. Luna: So what's the one thing you'd tell a procurement team that wants to try this? I mean, besides the IP agreements and the incentive structure. Lucas: I think the biggest thing is to start small. Pick one category, maybe three or four parts, and run a pilot. Don't try to roll this out across your entire supply base on day one. Because you need to learn how your suppliers respond, what kind of proposals are actually useful, and how your own engineering team is going to handle the review process. That's the stuff you can't figure out from a case study. Luna: Yeah, that's solid advice. And you know, this is the kind of episode that I think a lot of our listeners will find genuinely useful... not just interesting, but actionable. I mean, if you're a procurement person, you're probably already thinking about which suppliers you'd invite to something like this. Lucas: That's the hope. And honestly, that's what keeps us going. If today's conversation gives you one idea that saves your company even a fraction of what Precision Components saved, that's a win. And if you're getting value out of these episodes, the way to keep them coming... and keep them ad-free... is listener support. You can head to buy me a coffee dot com slash fexingo. It's a small gesture, but it makes a big difference for us. Luna: Yeah, we really appreciate it. And we're already thinking about what's next... maybe a follow-up on how to measure the long-term impact of these design changes. Lucas: That's a good idea. But let's not get ahead of ourselves. We still have a lot to cover today. So let's talk about one of the trickier aspects: how do you handle the negotiation when a supplier comes back with a proposal that saves them money but also shifts some risk onto you? Luna: Ah, that's the flip side. Because not every cost-saving idea is a good idea for the buyer. Lucas: Right. For example, one supplier proposed switching to a lower-grade steel that would meet the spec but with a tighter tolerance on the manufacturing process. That meant the buyer would have to do more incoming inspections to make sure the parts were within spec. The savings on the part price were offset by the added quality control costs. So the buyer had to run the numbers and decide whether the net was still positive. Luna: So it's not just about the unit price. You have to think about total cost of ownership. Lucas: Exactly. And that's a lesson that applies beyond this program. But in the context of supplier-led design, it's especially important because the supplier has an incentive to make their own process cheaper, but they might not be thinking about the downstream impact on your operations. Luna: So how do you protect against that? I mean, you can't have your engineers review every single proposal in depth. Lucas: You can't, but you can set up a cross-functional team that includes procurement, engineering, quality, and maybe even manufacturing. That way, each proposal gets evaluated from multiple angles before you commit. In the Precision Components case, they had a weekly review meeting where a proposal had to get a thumbs up from all four functions before it was accepted. Luna: That sounds slow. How long did it take for a typical proposal to get approved? Lucas: About three to four weeks from submission to decision. And that was okay because they were dealing with a lot of parts at once. But if you're doing this on a rolling basis, you might want to streamline the process... maybe start with a technical feasibility check, and only bring in the full committee if it passes that. Luna: I see. So it's a balance between rigor and speed. Lucas: Exactly. And the other thing to remember is that this isn't a one-way street. The buyer also has ideas. Maybe they've seen a supplier in another category use a different material or process. They can bring that to the table too. It's a collaborative process, not just a demand on suppliers. Luna: So what would you say is the biggest mistake a buyer could make when trying to implement something like this? Lucas: I think the biggest mistake is to treat it as a pure cost-cutting exercise without thinking about the relationship. If you just demand that suppliers come up with savings and then you take all of it, they're not going to be eager to help you next time. You have to make it a genuine partnership... share the savings, give them credit, maybe even offer a longer contract term as an incentive. That's what builds the trust that makes this work over the long haul. Luna: And that's a good note to end on. I feel like we've given our listeners a lot to think about. Lucas: Yeah, and I hope some of them will give it a try. The 22 percent savings is compelling, but even half of that would be a huge win for most companies. Luna: Definitely. And if you've got your own story about supplier-led design, we'd love to hear it. You can reach us on social or through the Fexingo website. Lucas: Until next time, keep finding those savings.