Latest / The Buyer's Side with Fexingo: Procurement, Sourcing, and B2B Purchasing Decisions / When a Supplier Owns Your Patent Strategy
Transcript
- Lucas: Luna, you've probably heard the expression "your supplier might become your competitor." But today I want to talk about a version of that I think is sneakier: your supplier might end up owning your next patent. Luna: That sounds like a nightmare scenario. How does that even happen? Lucas: It happens more often than most procurement teams realize. A supplier helps you develop a new component — maybe they're co-engineering a custom chip, a proprietary alloy, a medical device subassembly. You assume you own the resulting intellectual property because you paid for the development. But the supplier's legal team files the patent first. Luna: And you don't find out until you try to license it to another supplier or switch vendors. Lucas: Exactly. There's a specific case I want to walk through. A mid-sized medical device company — let's call them MedCore — outsourced the development of a new sensor module to a specialty electronics manufacturer. The contract had a standard 'work for hire' clause, but the supplier's terms included a carve-out: anything the supplier 'independently invented' during the project belonged to them. Luna: That's a huge loophole. How do you define 'independently' when you're collaborating daily? Lucas: That's the problem. The supplier's engineers came up with a novel way to reduce signal noise in the sensor. It was developed in the context of MedCore's project, using MedCore's specifications and test data. But the supplier argued it was their own innovation because they conceived the idea during a 'quiet period' between formal meetings. They filed a patent in their own name. Luna: So MedCore lost control of the core technology of their own product. Lucas: Worse — they lost the ability to source the sensor from anyone else. The supplier now owned the patent, so MedCore either had to pay licensing fees or stay locked into that supplier. The procurement team had never flagged IP ownership as a risk in their supplier evaluation. Luna: What was the outcome? Lucas: MedCore ended up settling. They negotiated a royalty-free license but only for that specific product line. Any future products using a similar sensor would trigger additional payments. The procurement director told me afterwards: 'We thought we were buying a component. We accidentally gave away our R&D pipeline.' Luna: That's a tough lesson. So what should procurement teams do differently? Start with the contract? Lucas: Start before the contract. Do an IP due diligence on the supplier. Have your legal team review their standard IP clauses before you even issue an RFP. But the real fix is in the definitions. The clause that matters is 'pre-existing intellectual property' versus 'foreground IP.' You need to define foreground IP as anything developed using your specifications, funding, test data, or confidential information — regardless of who conceived it. Luna: So you're closing that 'independently invented' loophole by broadening the scope. Lucas: Right. And add an 'assignment of inventions' clause that automatically transfers ownership of any foreground IP to you, with the supplier obliged to execute any paperwork needed to perfect that assignment. You also want a disclosure obligation — the supplier must notify you of any patent filings they make during the project, ideally within 30 days. Luna: That way you can challenge it early if they try to claim something as their own. Lucas: Exactly. Another practical step: require an IP audit at the end of the project. Both sides list what was developed and who contributed. This creates a paper trail that prevents disputes years later. MedCore didn't have that — they had no record of which engineer had what idea on what date. Luna: And I imagine this isn't just a problem for hardware or medical devices. Software procurement has similar risks. Lucas: Absolutely. Any time a supplier is customizing code for you, the same issues apply. I've seen cases where a supplier took the custom module they built for one client and patented the algorithm, then sold it to the client's competitor. The first client had no recourse because the contract said 'deliverable code only' — not the underlying method. Luna: That's brutal. So what's the one clause you'd add to every supplier development contract starting tomorrow? Lucas: A 'data rights' clause. Clearly state that any data you provide — specifications, test results, customer feedback, performance metrics — remains your confidential information, and any IP derived from that data belongs to you. The supplier can't claim independent invention if they used your data to get there. Luna: That's smart. It ties the IP ownership back to the inputs you control. Lucas: And it's surprisingly common for procurement teams to skip this. They focus on price, delivery, quality — the classic triple constraint. But IP ownership is becoming a fourth constraint, especially as more companies co-innovate with suppliers. Luna: Speaking of co-innovation — I wonder if there's a way to turn this into a positive. Could procurement use IP ownership as a bargaining chip for better terms? Lucas: That's a great point. Some companies negotiate a 'joint ownership' model with a clear licensing framework. You share the patent, but each party gets a royalty-free license for their own field of use. That can align incentives — the supplier is motivated to improve the technology because they can use it elsewhere, and you protect your core product. Luna: But that requires a lot of trust and a very detailed agreement. Lucas: It does. And it's not right for every relationship. For strategic suppliers you've worked with for years, joint ownership can work. For a one-off project, you probably want full ownership. The key is to make a conscious decision, not default to a standard template. Luna: I think that's the underlying theme here — procurement needs to stop treating IP as a 'legal thing' and start treating it as a core part of the sourcing strategy. Lucas: Exactly. And that's part of why we do this show, honestly. These conversations — about contract design, risk allocation, strategic thinking — they're the kind of professional development that doesn't always come through formal training. A lot of what we've learned in procurement comes from shared experience. Luna: Yeah, and I think that's worth saying. If you're listening and these episodes have helped you think differently about a negotiation or avoid a pitfall, consider supporting the show. It keeps us independent and ad-free. Lucas: Absolutely. No pressure at all — but if it's added value, you can support at buy me a coffee dot com slash fexingo. That's buy me a coffee dot com slash fexingo. Every bit helps us keep digging into cases like this one. Luna: Alright, back to IP. One more thing I want to touch on — how do you audit a supplier's existing patent portfolio before signing a contract? Lucas: Great question. You can ask for a patent landscape report as part of the due diligence. Some procurement teams include a clause requiring the supplier to warrant that their existing IP doesn't block your intended use. If it does, they need to grant a license upfront. Luna: So you're shifting the burden of disclosure to them. Lucas: Exactly. And if they're evasive about it, that's a red flag. I'd also recommend a 'freedom to operate' analysis for any critical component. That's a legal opinion that your product doesn't infringe on any third-party patents. It's an extra cost, but it's cheap compared to losing your entire product line. Luna: Freedom to operate — that's a term I don't hear often in procurement circles. Lucas: It's more common in R&D and legal, but procurement should own the process because you're the one selecting the supplier. If the supplier's technology is encumbered, you need to know before you commit to a multi-year contract. Luna: So to summarize: define foreground IP broadly, include an assignment clause, require disclosure of filings, do an end of project IP audit, and consider a freedom to operate analysis for critical parts. Lucas: That's a solid checklist. And one more thing — train your category managers to spot the warning signs. If a supplier starts talking about 'their proprietary process' during negotiations, that's the moment to ask: who owns it? And who will own any improvements we develop together? Luna: It's about asking the right question at the right time. Lucas: Exactly. Because by the time the patent is filed, it's already too late.