Joint Development And Contracted Development Are Not The Same
When companies partner with each other, or when business firms collaborate with academia, the line between joint development and contracted development sometimes blurs. One side thinks of it as joint development while the other thinks of it as contracted development, and trouble follows when it comes time to draw up the contract. Or the two parties sign a contract without ever clarifying which of the two it is, a mismatch surfaces partway through development, and the project falls apart on the spot.
Using joint development and contracted development well matters
Very few companies today build their business entirely on in-house development. Relying solely on contracted development also creates funding problems, so knowing when to use joint development instead is, I think, an important point of technology strategy.
Partly to organize my own thinking, I put together the slides below. Please read through the slides first. I’ll add some supplementary notes afterward.
The Difference Between Joint Development and Contracting from Yuichiro Kuzuryu (Kuz)
Below are a few points that, in my personal view, deserve particular caution.
Point to watch ① Don’t “just start” joint development
In joint development, it’s common to see both sides say, “Let’s just start with everyone pitching in their own effort,” while the arrangements for intellectual property and licensing fees stay undefined.
If the work never becomes substantial enough to commercialize, both sides can simply present the results internally and call it done. But once commercialization becomes a real possibility, each side’s expectations swell all at once. So no matter how tedious it is, settling these things properly in advance is extremely important.
In that sense, the arrangement I’d recommend most is
- rights to whatever comes out of the joint development project belong to both parties, but both parties also hold the right to use it
- neither side touches the profit generated by the other’s own business
This is an arrangement you can agree to immediately, any time. Though of course it rarely goes that smoothly in practice.
Point to watch ② “Get clarity first”
When someone who thinks they’re doing joint development and someone who thinks they’re doing contracted development end up talking past each other, the conversation naturally fails to connect at all.
Rights to the deliverables
In contracted development, the rights typically transfer to the party commissioning the work (in exchange for payment), whereas in joint development they almost always remain with each party respectively.
Cases where no money changes hands fall clearly into the latter category (nobody is generous enough to hand over results for free). But when payment is involved, both sides need to align carefully on what exactly that payment covers and what it’s being paid for.
Point to watch ③ “Academia shedding its skin”
In many cases, academia’s default approach is joint research. This is because being joint, rather than contracted, preserves the freedom to set the direction of the research.
This often becomes an obstacle to industry-academia collaboration. Business firms expect results even from research, and those results need to be results in practical business terms, not merely academic achievements.
Commitment to the business
Naturally, there’s risk in partnering with an academic side that won’t commit to the business. This pushes the decision-makers approving such deals toward a conservative stance, which in turn shrinks what academia actually gets out of it. To be clear, “not committing to the business” doesn’t mean academia lacks a sense of responsibility or mission. Academic institutions are organizations oriented toward academic contribution. Given that orientation, they simply aren’t well positioned to share in business-side benefits. If the partnership were instead between two business firms, it would be easy to set up a “profit-sharing” scheme — using each other’s technology in their respective products to generate profit, or splitting the profit proportionally once it materializes.
That’s why, overseas, many research labs break away from their universities to start companies. Taking on a corporate form makes it much easier to build a scheme for sharing business-side benefits.
But in most cases, things settle into something small: running joint experiments based on research results achieved up to that point. That has value in its own right. But it inevitably isn’t a framework aimed at pursuing drastic new results through fresh research, and that in turn creates the problem that large research budgets rarely get moved.
How academia can design joint development that aligns itself with business firms remains a major challenge.
Originally published in Japanese at https://clazytech.com/2021/10/810/. Translated with LLM assistance and reviewed before publication.