Latest / The Buyer's Side with Fexingo: Procurement, Sourcing, and B2B Purchasing Decisions / How One Buyer Cut Costs with Supplier Scorecards
Transcript
- Lucas: So last month I spent some time with a mid-sized manufacturer outside Cincinnati, and they did something that sounds almost boring on paper but delivered an eleven percent cut in procurement costs over two quarters. Luna: Boring on paper but eleven percent lower costs? That's the kind of boring I could get behind. What did they do? Lucas: They implemented supplier scorecards. Not the kind that sit in a spreadsheet and never get looked at, but a working system where every vendor gets scored monthly on five weighted metrics: on-time delivery, quality defects, responsiveness, pricing competitiveness, and compliance. Luna: So they were basically grading their suppliers like teachers grade students. Did the suppliers actually care? Lucas: That's the key. They didn't just collect data—they made the scores matter. Top performers got longer contract terms and early payment options. Underperformers got put on a sixty-day improvement plan. And if they didn't hit the targets? They were off the approved vendor list. Luna: That's a real incentive structure. So the eleven percent—where did that actually come from? Was it mostly price renegotiation, or did the other metrics drive it? Lucas: Interesting thing, they told me the price piece was maybe only three points of that eleven. The bigger chunk came from reduced expediting costs, fewer emergency shipments, less rework, and lower administrative overhead because they stopped having to chase late deliveries and resolve quality disputes. Luna: So the scorecard essentially made hidden problems visible, and fixing those problems was the real savings. Lucas: Exactly. And the way they designed the scorecard was pretty deliberate. They started with six metrics, then dropped one because it was too hard to get reliable data on it. They kept the five I mentioned, and each one has a clear definition so there's no ambiguity about what 'on-time' means, for example. Luna: What did they define as on-time, out of curiosity? Lucas: They settled on delivered to the dock by the agreed date, plus or minus one day. Anything outside that window counted as late. Simple, objective, easy for both sides to verify. They also made it a point to share the scorecard with suppliers every month, not just once a quarter. Luna: Monthly feedback for suppliers—that's pretty frequent. Did the suppliers push back on that at first? Lucas: Some did, yeah. A couple of long-time vendors were skeptical. They saw it as another bureaucratic burden. But the buyer did something smart: they brought the suppliers in before the rollout, explained the goals, and asked for their input on the metrics. That early involvement made a huge difference in buy-in. Luna: So it wasn't just a top-down mandate. Lucas: Not at all. And it's something that I think any procurement team can learn from. The scorecard wasn't designed in a vacuum; it was a collaborative tool. That's part of why it worked. Luna: Before we get deeper into the design, I want to say something about this show. If these conversations have moved your work forward in some small way—maybe a technique you tried, or a framework that changed how you think about a category—that's exactly why we make it. And listener support is what keeps it ad-free and independent. If you value that, you can support the show at buy me a coffee dot com slash fexingo. Just a small gesture, if it feels right. Lucas: Yeah, and it genuinely helps us keep doing this. We appreciate anyone who's able to chip in. Now, back to those scorecard metrics—I think the weighting is where a lot of teams go wrong. Luna: What did they weight most heavily? Lucas: They put on-time delivery at thirty percent, quality at twenty-five, responsiveness at twenty, pricing at fifteen, and compliance at ten. The thinking was that a supplier who can't deliver on time wreaks havoc on production schedules, so that had to carry the most weight. Luna: Pricing only fifteen percent? That's interesting given the show's focus on cost cutting. Lucas: Right, and that was a deliberate choice. They realized that chasing the lowest unit price often led to higher total costs elsewhere. By weighting price lower, they were signaling that they cared about total cost of ownership, not just the sticker price. Luna: So the scorecard actually helped shift the conversation from price to value. Lucas: Exactly. And they tied that into their supplier tiering program. Suppliers who scored above ninety for six consecutive months were moved to a 'preferred' tier. That came with benefits like longer contract terms, priority for new business, and access to early payment discounts. Luna: And what happened to the ones who didn't make the cut? Lucas: They got a ninety-day window to improve, with a focused improvement plan. If their score didn't come up, they were transitioned out over the next quarter. They actually only had to do that with one supplier, but just seeing that it could happen kept everyone else on their toes. Luna: So the scorecard became a real driver of supplier performance, not just a report card. Lucas: It did. But to get there, they had to solve the data problem. The biggest hurdle was that their ERP system didn't have a clean way to capture all the metrics. They had to pull data from multiple sources: the warehouse management system, the quality system, and their email records for responsiveness. Luna: That sounds like a lot of manual work. Did they automate it? Lucas: Partially. They started with a shared spreadsheet and a monthly manual update. It took about two days of work per month. But once they proved the concept, they invested in a lightweight procurement analytics tool that could pull the data automatically. That cut the administrative time down to about two hours per month. Luna: So the initial investment was really just time and discipline. Lucas: Exactly. And the payoff was quick. Within the first quarter, they saw a noticeable improvement in on-time delivery. The supplier that was consistently late started hitting a ninety-five percent on-time rate by month three. Luna: What about the supplier that got cut? Did that cause any disruption? Lucas: They had a backup supplier already qualified, so the transition was smooth. That's another lesson: always have a qualified alternative. The scorecard helped them identify the weak link before it became a crisis. Luna: So, in the end, the eleven percent savings wasn't a short-term negotiation win—it was a structural improvement. Lucas: That's a great way to put it. The savings came from better planning, fewer fire drills, and more predictable operations. And those changes are sustainable, unlike a one-time price cut that might get reversed next year. Luna: I think the most surprising part for me is that something so straightforward can have such a big impact. Lucas: It's one of those things that sounds almost too simple to matter, but the discipline of measuring, reviewing, and acting on the data is what drives the improvement. Any team could do this. Luna: What would you say is the first step for a procurement team that wants to try this? Lucas: Start with just three metrics that map to your biggest pain points. Don't overcomplicate it. Then, share the scorecard openly with suppliers, and be ready to adjust the weights based on what you learn. It's an iterative process. Luna: And if you do it right, you might end up like that Cincinnati manufacturer—eleven percent savings and a more reliable supply chain. Lucas: Yeah, and that's a win-win. The suppliers who improved also became more competitive, which helps them in their own markets. So the scorecard wasn't just a cost cutting tool—it was a relationship builder. Luna: That's a nice note to end on. Maybe next time we can dig into how to handle the data side more comprehensively. Lucas: I'd like that. There's a lot more to unpack there.