Joint development manufacturing: designing the product with the factory that will build it

Why a buyer accepts shared ownership at all

Nobody sets out wanting a product they only partly own. The trade gets accepted because the alternatives are worse: paying full development cost for a design that must then be adapted to whatever equipment the eventual maker happens to own, or adopting a catalogue product that does not do the job. Bringing the manufacturer in during design collapses the distance between what was drawn and what can be run, and it usually reduces the cash the buyer has to find before anything sells. Speed and manufacturability are bought with freedom spent later.

Background and foreground: the distinction everything rests on

Development agreements separate what each party brought with them from what the collaboration produced. Background rights — the maker's existing process know-how, your existing formulations or platforms — stay with whoever arrived holding them, licensed only as far as the project requires. Foreground, meaning whatever the joint work creates, has to be allocated deliberately: assigned to one party with a licence back, or divided by subject matter so the buyer takes the product and the maker keeps the process. Joint ownership sounds even-handed and works poorly, since in many jurisdictions each co-owner needs the other's consent to license or to enforce, which converts every future decision into a negotiation.

Development cost is recovered somewhere, and you should know where

Three structures dominate. The buyer pays development as a fee and keeps a freer hand over the outcome. The maker funds it and recovers through unit price, converting a capital decision into a per-piece charge that outlives its payback and resists unwinding. Or both contribute and recovery is blended. What matters is less which structure you pick than whether the recovery is visible and finite. Development quietly folded into a price with no stated endpoint is the most expensive of the three, because it never stops and nobody can identify the clause that would stop it.

Exclusivity is what the factory is really asking for

A manufacturer spending engineering time without an upfront fee expects protection, and it usually takes the shape of being sole producer for a period, a territory, or the life of the design. That is defensible. It turns dangerous when it carries no expiry, no volume condition and no performance trigger. Workable structures tie the protection to something the maker must keep delivering — conformity, capacity, an agreed price mechanism — and let it lapse when they do not. Buyers who accept indefinite sole supply in return for free development have bought a discount today and sold their negotiating position permanently.

Planning for the version that does not work

Most collaborative developments end without a product, which is ordinary rather than a failure of good faith, and should be anticipated as such. The agreement needs a stopping mechanism: defined stages with go or no-go criteria, a settled position on who holds what if the work halts midway, and a formula for tooling and materials already committed. Without it, an abandoned programme leaves both parties holding partial rights over something neither can use, plus a relationship soured enough to make the next attempt harder. Write the exit while everyone is still enthusiastic, because nobody will agree to it afterwards.

Frequently asked questions

Who owns a product developed jointly with a manufacturer?

Whoever the agreement says, which is precisely why the agreement has to say. Absent clear terms, default rules vary by country and by whether the work counts as an invention, a registrable design or simply know-how, and they seldom produce the outcome either side assumed. The pattern that tends to hold up divides by subject: the buyer takes product definition, appearance and brand, the maker retains its process methods, and each grants the other only the licence production actually requires.

Is co-developing worth it for a small brand with little engineering of its own?

Frequently yes, provided you enter knowing what is being traded. A small buyer without process engineers gains access to knowledge it could not otherwise afford and avoids discovering manufacturability problems late and expensively. The cost is dependence: the resulting product is shaped around one factory's equipment, and the exclusivity that funded the work narrows your options for years afterwards. Where the product is central to the business, paying a development fee to keep the design unencumbered is often the better bargain.

How do we stop a development programme running indefinitely?

Stage it, and attach a decision to each stage rather than a deadline. Every phase wants entry criteria, a defined deliverable, an agreed cost and an explicit review at which either party may stop. Open-ended development is usually a symptom of an unwritten requirement: nobody has stated clearly what the finished product must do, so each review generates another improvement. Settling the specification does more for the schedule than applying pressure to it ever will.