Latest / The Buyer's Side with Fexingo: Procurement, Sourcing, and B2B Purchasing Decisions / How a Buyer Used the Martec Law to Cut Innovation Costs
Transcript
- Lucas: So earlier this week, I was talking to a procurement director at a mid-size industrial manufacturer — about 2 billion in revenue — and he told me something that stopped me cold. Luna: What'd he say? Lucas: He said: 'We cut innovation costs twenty-two percent over eighteen months. And we did it by saying no to more things.' Now, that sounds counterintuitive, right? We usually think innovation is about saying yes. But he was applying something called the Martec Law — and it's a concept I think every buyer should know. Luna: Martec Law — I've heard the name. Isn't that the principle that technology evolves exponentially, but organizations evolve logarithmically? Lucas: Exactly. It was coined by marketing professor Scott Brinker around 2013. The idea is simple: technology changes at an exponential rate — think Moore's Law, AI capabilities doubling every few months — but organizations, with their hierarchies, processes, and people, change at a much slower, logarithmic pace. So there's this growing gap between what's possible technologically and what an organization can actually absorb. Luna: And that gap is where a lot of procurement innovation spending goes to die. We've all seen it — a supplier pitches a shiny new platform, the buyer buys it, and then it sits unused because the team wasn't ready. Lucas: Right. And that's exactly the problem this buyer tackled. He realized his team was approving supplier-led innovation projects — new materials, new software, new processes — at a pace that far exceeded the organization's ability to implement them. So they were bleeding money on initiatives that never delivered. Luna: And before we go deeper — you know, conversations like this are exactly why we keep this show ad-free. We don't want any sponsor telling us what topics to cover or what angles to take. If these episodes help you think differently about your work, and you want to support that independence, there's a link: buy me a coffee dot com slash fexingo. No pressure, just an option for people who find value here. Lucas: Yeah, we mean that. It's a small thing that lets us keep the focus on what actually works in procurement, not on selling ad slots. So back to the Martec Law — let's talk about how this buyer operationalized it. Luna: What was his framework? Lucas: He built a three-part process. First, technology scouting — but not in the usual firehose way. Instead of having every supplier pitch their latest innovation, he created a structured intake. Suppliers had to submit a one-page brief answering two questions: What specific problem does this solve? And what organizational changes are required to implement it? Luna: That second question is the key. Most suppliers only talk about the benefits, not the implementation burden. Lucas: Exactly. So if the answer to 'what organizational changes are needed' was three paragraphs long, that was a red flag. The second step was an organizational readiness assessment. For each innovation, the procurement team would evaluate: Does our current team have the skills? Do our processes support it? Is our IT infrastructure compatible? They scored each dimension on a one-to-five scale. If the average was below three, they'd either reject the innovation or put it on a twelve-month hold while they built readiness. Luna: So they were effectively matching the adoption pace to the organization's actual change velocity, not the technology's potential. Lucas: Right. And the third step was staged implementation. Instead of a full rollout, they'd run a pilot with one team or one facility. If the pilot succeeded, they'd document the lessons learned, then expand to a second site. Only after two successful pilots would they consider a broader rollout. That staged approach meant they could kill failing projects early, before they'd spent millions. Luna: What kind of innovations were they evaluating? Was it mostly software, or also materials and processes? Lucas: All of the above. They had suppliers pitching new composite materials for their products, predictive maintenance software for their factory equipment, even a blockchain-based traceability system. Under the old approach, they'd have greenlit half of those within a month. Under the new framework, they approved only about thirty percent of proposals. But the ones they approved had an implementation success rate of over eighty percent, compared to maybe forty percent before. Luna: That's a huge swing. So the twenty-two percent cost reduction came from not wasting money on innovations that would never get adopted. Lucas: Exactly. They calculated that over eighteen months, they saved about four point seven million dollars. Not by cutting innovation spend overall — they actually increased their budget for approved projects — but by eliminating waste on projects that were doomed from the start because the organization wasn't ready. Luna: I love that they didn't just say 'we're going to innovate less.' They innovated smarter. Lucas: Precisely. And this gets to the heart of the Martec Law. The buyer told me: 'We used to think our job was to pick the winning technology. Now we realize our job is to pick the winning technology that our organization can actually adopt.' That's a fundamental shift in mindset. Luna: It also changes how you evaluate suppliers. A supplier with a great technology but a terrible implementation plan becomes less attractive than a supplier with a good technology and a realistic onboarding process. Lucas: Absolutely. And some suppliers adapted. One of their key software vendors actually redesigned their implementation methodology after the buyer shared their readiness criteria. They created a 'light' version that could be deployed in two weeks instead of six months. That vendor ended up winning more business because they aligned with the buyer's adoption pace. Luna: So the Martec Law isn't just a theory — it's a practical tool for procurement. What would you say is the one takeaway for a buyer listening who wants to apply this? Lucas: I'd say start with a simple two-question test for any innovation proposal. First: What is the specific problem this solves? If the answer is vague, kill it. Second: What changes does our organization need to make to use this effectively? If that list is longer than three items, put it on hold. That alone will filter out most of the noise. Then, once you have a shortlist, pilot small, learn fast, and scale only when the organization is ready. Luna: And don't be afraid to say no. Saying no to the wrong innovation is often more valuable than saying yes to the right one. Lucas: Exactly. The buyer I spoke with said his team's new motto is: 'Innovation is about adoption, not acquisition.' And I think that's a powerful lens for any procurement team looking to cut costs without cutting progress. Luna: Great episode. Thanks, Lucas. Lucas: Thanks, Luna. Talk to everyone next time.