Latest / The Buyer's Side with Fexingo: Procurement, Sourcing, and B2B Purchasing Decisions / How Buyers Capture Supplier Innovation
Transcript
- Lucas: Let’s talk about the most expensive mistake procurement teams make today, which isn’t about price per unit or payment terms. It’s about giving away the intellectual property generated during the fulfillment process for free. In September 2026, we’re seeing a sharp shift where leading buyers are inserting what I call innovation capture clauses into their master service agreements. Luna: You mean when a supplier figures out a better way to pack, ship, or assemble something while working on your contract? That sounds like a slippery slope for vendor relations. Lucas: It’s not a slope if you define the boundary clearly. The standard approach has always been that the supplier owns their proprietary methods. But if a supplier uses your specific data, your unique volume profile, and your quality standards to develop a new packaging algorithm or a routing optimization tool, that tool was co-created with your inputs. Without a clause stating otherwise, the buyer gets zero equity in that efficiency gain. Luna: So you’re arguing that because they used our data to build the tool, we should own a piece of it? That feels like a heavy lift legally. Lucas: It’s actually lighter than people think. We aren’t talking about owning their entire platform. We’re talking about a non-exclusive, perpetual license to use that specific improvement across all other suppliers in that category. If a logistics provider finds a way to reduce damage rates by two percent using your SKU dimensions, that knowledge belongs in your playbook, not just their portfolio. Luna: But won’t top-tier suppliers just walk away from those conversations? They protect their IP fiercely. Lucas: They will, unless you offer something in return. And this is where the dynamic shifts from adversarial to strategic. The trade-off is usually access. You grant them preferred status, longer contract durations, or higher volume guarantees in exchange for that license. It turns a transactional relationship into a joint development venture without the complexity of an acquisition. Luna: I’ve seen some tech companies do this with software vendors, but in physical goods? That seems risky if the supplier loses their competitive edge. Lucas: The risk is manageable if you limit the scope. You don’t take their core engine; you take the calibration settings derived from your specific load profiles. Think of it like this: if you hire a consultant to reorganize your warehouse, you own the floor plan they draw for you. Why shouldn’t you own the optimized picking path they invent while doing it? Luna: Because the consultant sells that picking path to ten other warehouses next week. Are you saying you want exclusivity? Lucas: No, exclusivity is a poison pill for suppliers. Non-exclusive is the sweet spot. You want the ability to implement that improvement yourself or direct another vendor to do it. It prevents the first supplier from holding your future efficiency hostage after you’ve helped them refine the method. Luna: That makes sense for large enterprises with scale, but what about mid-market buyers who can’t promise volume guarantees? Lucas: Even mid-market buyers have leverage if they frame it right. It’s not about volume; it’s about data richness. A smaller buyer with highly complex, low-volume custom orders provides more unique data points than a giant buying commodities. Suppliers crave that specificity to test new technologies. You can trade data access for IP rights quite easily. Luna: So the lesson is to treat every contract as a potential R&D partnership rather than just a purchasing order? Lucas: Exactly. Most procurement teams operate in a silo where they think their job ends when the invoice is paid. But the real value creation happens in the execution phase. If you ignore the innovations that occur there, you’re leaving money on the table that you effectively helped generate. Luna: Does this require legal teams to be deeply involved in every renewal, or is there a template approach? Lucas: There is a template approach, and it’s surprisingly simple. You need three distinct components in the clause. First, a definition of background IP, which remains owned by the creator. Second, a definition of foreground IP, which is any new tool created specifically to fulfill your contract. Third, the license grant, which gives you a royalty-free, non-exclusive right to use that foreground IP. Luna: Foreground IP. That’s a clean term. Does it cover things like predictive maintenance algorithms for equipment you lease? Lucas: Yes, absolutely. If a vendor manages your fleet and develops a predictive model based on your usage patterns, that model is foreground IP. You might not own the code, but you should own the right to use that insight to extend asset life or reduce downtime elsewhere in your organization. Luna: What stops the supplier from hiding their best innovations in a separate subsidiary so they aren’t captured by the main contract? Lucas: Affiliation clauses handle that. You require disclosure of any related entities developing solutions relevant to your supply chain. If they try to ring-fence the innovation, you lose the benefit. Transparency is key here. You’re asking for visibility into their improvement pipeline, not ownership of their corporate structure. Luna: That’s a fair balance. But let’s say a supplier pushes back hard, saying this violates their trade secrets. How do you negotiate that friction? Lucas: You offer a confidentiality carve-out. You agree that the specific source code or raw methodology remains secret, but the of that methodology to your business needs becomes yours. It’s like buying a recipe. You don’t get the chef’s personal notes, but you get the dish and the right to serve it in your own restaurants. Luna: I like that analogy. It separates the art from the product. Have you seen any industries where this is already standard practice? Lucas: Pharmaceuticals and aerospace have done this for decades. They require contractors to assign patent rights for any invention arising from the work. The difference now is that this logic is migrating into general B2B services, logistics, and IT support, where it hasn’t been common until recently. Luna: So it’s an arbitrage opportunity for early adopters. They’ll lock in efficiencies while everyone else is still paying full price for basic services. Lucas: Precisely. And the financial impact compounds. If you save five percent on logistics costs through shared innovation over a ten-year contract, that’s not just a line-item saving. That’s margin expansion that flows directly to the bottom line without raising prices for customers. Luna: It also de-risks your operations. If you understand the innovation behind your supply chain, you’re less dependent on one vendor’s goodwill. Lucas: Dependence drops significantly. You become interoperable. If Vendor A leaves, you can hand those improvement protocols to Vendor B because you own the license. That’s operational resilience built into the contract language itself. Luna: This feels like a much smarter play than trying to merge with a small supplier to get their tech. Less capital, less risk. Lucas: Mergers are messy and slow. Contractual licensing is fast and scalable. You can roll this out across fifty suppliers in a quarter. It’s agile capital allocation without the balance sheet hit. Luna: Do you think CFOs are starting to notice this? Or is this still purely a procurement conversation? Lucas: CFOs love it because it shows up in EBITDA before revenue grows. When procurement brings down COGS through shared innovation, it looks like organic growth. Finance teams are increasingly asking procurement to prove value beyond discounting. This is a concrete metric they can track. Luna: So the takeaway is to audit current contracts for missing IP protections and start negotiating these clauses now? Lucas: Start small. Pick one high-volume category. Draft a pilot clause. Test it with your best relationship partner. If it works, scale it. If they refuse, you know that category isn’t ripe for innovation capture yet, and you can pivot elsewhere. Luna: Practical advice. Don’t boil the ocean, just secure the wins where the data is richest. Lucas: Right. And remember, you’re not stealing their ideas. You’re ensuring that the value you create together doesn’t vanish when the contract ends. It’s about fairness, transparency, and long-term stability. Luna: Fairness and stability. Those are good words for a department often accused of being too aggressive. Lucas: Aggression comes from weakness. Strength comes from clear rules that benefit both sides. When suppliers see you’re willing to invest in their innovation through volume and data, they reciprocate with openness. It builds trust faster than any dinner meeting ever could. Luna: I’m going to try framing my next negotiation around this joint development angle instead of just pure cost cutting. Lucas: You will find the conversation changes immediately. You stop being a buyer and start being a partner. And partners share the spoils. Luna: Speaking of partners and keeping things running smoothly, if these conversations have moved your work forward in some small way, consider supporting the network directly. A couple of dollars a month is genuinely what keeps these going — buy me a coffee dot com slash fexingo. It helps us keep the research deep and the ads out. Lucas: We appreciate every listener who chooses to chip in. It allows us to dig into these niche topics without compromising on quality or depth. Luna: Thanks for listening, and thanks for helping us stay independent. Lucas: Back to the contract. One final thought on implementation: document every instance of innovation capture. Track the savings, the time saved, the defects reduced. Build a case study internally. Next year, when you renegotiate, you won’t just be asking for rights; you’ll be showing proof of mutual value. Luna: Proof beats promises every time. Data-driven negotiations are just harder to argue against. Lucas: Exactly. So ask yourself, what hidden efficiencies are sitting in your current supplier relationships that you haven’t tried to capture yet?