We signed the co-development deal on a handshake and a good forecast. The supplier's process made the component better than our drawing and cheaper than the quote. Legal sent an IP schedule; procurement filed it. Nobody read it, because the relationship was the kind you trust.
The deal that felt like trust
Eighteen months later we tried to carry the design into a new program. That is when we learned the supplier owned the tooling geometry, the process recipe, and the control software that lived only on their floor. We had bought the part. We had not bought the right to build it. The "good relationship" ended the week we asked to leave.
IP in supplier partnerships does not break in court. It breaks in the specification meeting, the day nobody writes down who owns what the work creates.
The second time, the clause read differently
The second time, the clause read differently. Background IP stayed with each side, but the license was scoped — our programs, our region, no surprises. Foreground IP, the hybrid the partnership produced, was allocated with a use grant, so either side could carry it forward without permission theater. The tooling: we held title, they held access, and the exit terms said where the die went if the business moved. Same supplier. Different outcome, because the ownership was decided before the volume was.
Three clauses that decide it
Three things decide it — and none needs a lawyer in the room:
- A background IP schedule with real scope, not a vague "mutual license."
- A foreground IP allocation that includes the right to reuse, not just shared ownership.
- Tooling and software ownership that names what happens next.
If you cannot rebuild it without them, you are not a partner — you are a tenant who forgot the lease.
The point was never to strip IP from the suppliers who earn it. It was to know, on paper, what you can do when the program changes. That is the distance between a partnership you steer and one that steers you.
