Latest / The Buyer's Side with Fexingo: Procurement, Sourcing, and B2B Purchasing Decisions / How a Buyer Used Supplier Collaboration to Cut Lead Times 30 Percent
Transcript
- Lucas: If you've been listening to this show for a while, you know we talk a lot about leverage — how buyers can use contracts, payment terms, or competitive tension to get better deals. But there's a different approach that doesn't rely on leverage at all. It relies on collaboration. Luna: Collaboration sounds nice. But in procurement, 'nice' doesn't always cut it. Lucas: Fair point. But today's case is from a mid-sized electronics manufacturer — let's call them CircuitCo, not their real name — that used structured supplier collaboration to cut lead times by 30 percent. And they did it without increasing inventory or paying a premium. Luna: Wait, 30 percent? That's massive. How? I'm picturing joint planning, but there's got to be more to it. Lucas: There absolutely is. Before we dive in — and I don't want to break the flow — but these deep-dive episodes exist because we deliberately don't run ads on the show. If that kind of approach matters to you, and you want to support the ad-free choice, the link is buy me a coffee dot com slash fexingo. Luna: Yeah, I think that's part of why these conversations feel substantive. No product pitches interrupting the story. Lucas: Exactly. So, CircuitCo's procurement lead, a woman named Sarah, had a problem: their lead times for a critical custom component had stretched from 8 weeks to 14 weeks. The supplier was a small family-owned manufacturer in Ohio, and they were blaming raw material shortages and machine capacity. Luna: Standard story. Most buyers would either find a second source or push for a contractual penalty. She didn't do either? Lucas: She did not. Instead, she proposed a formal collaboration project. She asked the supplier's owner — let's call him Mike — to form a joint planning team. That team would meet weekly, share demand forecasts 13 weeks out, and identify bottlenecks together. Luna: But that requires sharing your own production forecasts. That's sensitive. I imagine a lot of buyers would be nervous about giving a supplier that level of visibility. Lucas: And Mike was nervous too, on his side. He didn't want CircuitCo to see his margins or his other customer commitments. So they signed a mutual non-disclosure agreement that specifically covered forecast data and production schedules. That was the foundation. Luna: So they created a safe space. Then what? Joint planning meetings — those can easily become talking shops. Lucas: Sarah made sure they didn't. She assigned a senior buyer and a production scheduler to the team, and Mike assigned his plant manager and a purchasing lead for raw materials. They met every Wednesday for 45 minutes. The agenda was standardized: forecast changes, material shortages, machine downtime, and action items from last week. Luna: That's very structured. How long did it take before they saw results? Lucas: The first real win came in week six. The joint team spotted that a raw material — a specific grade of steel — was consistently arriving late from Mike's supplier. Because CircuitCo had visibility into that, they were able to use their own purchasing volume to negotiate a faster delivery with that steel supplier. That alone shaved 3 weeks off the lead time. Luna: So the buyer helped the supplier with their upstream supply chain. That's a different dynamic — you're solving the problem together, not just complaining about it. Lucas: Exactly. And they didn't stop there. The next bottleneck was machine setup time. Mike's plant had two CNC machines that produced CircuitCo's component, but they switched over to other jobs twice a week. Sarah proposed that CircuitCo would guarantee a minimum monthly volume if Mike would dedicate one machine exclusively to their parts. Luna: That's a volume commitment. That's real skin in the game. But it also reduces Mike's flexibility. Lucas: It does. But Mike calculated that the guaranteed volume — which was about 70 percent of his existing orders — was worth more than the potential loss of other jobs. So he agreed. That eliminated setup time entirely for those parts, cutting lead time by another 2 weeks. Luna: So now they're down from 14 weeks to about 9. Still not 30 percent yet. Lucas: The third piece was the most controversial. Sarah offered to co-locate a CircuitCo quality engineer at Mike's plant for 3 months. The engineer would inspect parts in real time, so there was no back and forth on defects. Mike was hesitant — felt like surveillance — but Sarah framed it as a way to reduce his rework costs. Luna: And did it work? Lucas: Yes. The engineer caught a recurring tolerance issue within the first week. Mike's team adjusted the machining process, and the defect rate dropped by 60 percent. That eliminated the need for re-inspection at CircuitCo's receiving dock, saving about 5 days of transit and handling time. Luna: So that gets them to around 8 weeks — a 30 percent reduction from 14. That's the math. But what did it cost CircuitCo in terms of time and trust? Lucas: Sarah spent about 10 hours a month in those planning meetings for the first six months, plus the engineer's salary for 3 months. So maybe $40,000 in direct costs. But the savings in reduced inventory carrying costs — because lead times dropped — and avoided expedited shipping fees came to about $200,000 in the first year. Luna: Five-to-one return. That's a strong argument. But I wonder: could this work with a larger supplier? Or a supplier that's not in a relationship where the buyer is a big customer? Lucas: Great question. Sarah's supplier was small — CircuitCo was about 25 percent of Mike's revenue. That gave her some influence, but she never used it as leverage. She led with data and joint problem-solving. For a larger supplier, you'd need even more structure — maybe a formal joint business plan with shared KPIs and regular executive sponsorship. Luna: And what about the risk of the supplier using the forecast data to raise prices? If they see you're growing, they might think they can charge more. Lucas: That's a real concern. Sarah addressed it by including a price stability clause in the collaboration agreement. Prices would be reviewed quarterly based on agreed cost drivers — raw material indices, labor rates — not on demand. So the supplier couldn't raise prices just because CircuitCo's volume increased. Luna: That makes sense. So collaboration doesn't mean you drop your guard — you still have contracts. But you're adding a layer of joint effort. Lucas: Exactly. And I think the key lesson from Sarah's project is that it's not about being nice. It's about aligning incentives so that both parties win. The supplier gets predictable volume and lower rework costs. The buyer gets faster lead times without paying a premium. Luna: I can think of a dozen scenarios where this would apply — custom parts, packaging, even software development. But I suspect it only works if both sides are willing to be transparent. Lucas: That's the hard part. And Sarah said the most difficult moment was the first meeting, when she had to share CircuitCo's 13-week forecast and Mike had to show his production schedule. Both were nervous. But once they saw that the data was used to solve problems, not to blame, the trust built quickly. Luna: So the first step is to find one supplier where you have a real pain point — like lead times or quality — and where there's a mutual dependency. Then propose a structured pilot. Lucas: Right. Start with a single component, a single supplier, and a 3-month pilot. Define clear metrics: lead time, defect rate, on-time delivery. Meet weekly, share forecasts, and commit to solving one bottleneck at a time. That's the playbook. Luna: And if the supplier says no? Lucas: Then you know where you stand. And you can make a different choice — dual source, negotiate harder, or invest in automation. But if they say yes, you've started a relationship that can deliver compounding returns. Luna: I like that framing. It's not about being soft. It's about being smart about where you invest your relationship capital. Lucas: Exactly. And in Sarah's case, that investment paid for itself in three months. Two years later, she told me the collaboration had expanded to three more suppliers, and their overall lead time volatility dropped by half. Luna: So what's the one thing a buyer should do Monday morning if they want to try this? Lucas: Pick one critical component, call your supplier contact, and say: 'I want to understand your biggest bottleneck. Let's work on it together.' Not 'I want to negotiate a lower price.' Start with curiosity, not demand. Luna: That's a good note to end on. Curiosity over leverage. Lucas: Thanks for listening to The Buyer's Side. We'll be back next week with another story from the front lines of procurement.