Deal-structured collaboration for scalable technology builds

Technology Development & Co-Development Agreements

Co-development can accelerate delivery, but it also intertwines contributions in ways that make ownership and commercialization hard to unwind. Under 35 U.S.C. § 262, default patent co-ownership can allow each co-owner to make, use, sell, and license without the other’s consent or accounting, unless your agreement says otherwise. That default can also limit enforcement leverage when a co-owner will not participate. Law Laguna builds technology development and co-development agreements as an operating system, defining scope, documenting contributions, allocating ownership, and controlling exploitation from day one.

Prevent uncontrolled licensing of jointly owned IP

Co-development agreements sit at the intersection of contract governance and intellectual property ownership rules, where default statutes fill gaps you did not intend to leave open. Copyright rules can create joint authorship when parties intend to merge contributions into a single work, with co-ownership consequences that are hard to reverse later, see 17 U.S.C. § 101 and 17 U.S.C. § 201(a). Patent inventorship can also produce joint inventorship even if teams do not collaborate directly, and inventorship drives ownership allocation in many deal frameworks, see 35 U.S.C. § 116. Because development teams iterate quickly, documentation, assignments, and decision rights must run in parallel with the build. The agreement needs to control prosecution, maintenance, licensing, and termination outcomes, not just define the project.

Law Laguna converts collaboration into a documented workflow: define the project, record contributions, and allocate foreground and background rights. We draft decision rights that prevent unilateral licensing, unmanaged prosecution costs, and abandonment without notice. We also build post-termination options that keep commercialization paths viable even if the relationship ends early.

  • Secure joint inventorship disclosures by requiring timely written invention reports tied to conception and reduction to practice milestones.
  • Control each party’s undivided interest by converting default exploitation rights into contract-based field of use and consent rules.
  • Run prosecution and maintenance like a project plan, including office actions sharing, counsel selection, and cost elections.

The objective is predictable ownership, decision rights, and commercialization pathways. The result is a collaboration that can ship product without creating avoidable leverage issues later.

Counsel for high-accountability development partnerships

Based in Laguna Beach and serving Southern California deal teams. Statewide remote support for California-based companies and cross-border collaborations.

General Counsel

You need a contract that maps joint inventorship and joint work outcomes to the business deal, not default rules. You are managing pressure from product teams while controlling prosecution and maintenance costs, foreign filing elections, and licensing approvals. You also need enforcement readiness, including plaintiff-joinder commitments where required for patents.

  • Partner insists it can license “its share” of joint IP without consent.
  • The parties disagree on whether a deliverable is background or foreground intellectual property.
  • A co-owner refuses to join an infringement suit, stalling enforcement leverage.

VP Engineering / Head of R&D

You want speed, but you also need a clean record of contributions so joint inventorship and authorship do not become a debate later. You need milestones, acceptance criteria, and feasibility testing requirements that match how engineering actually ships. You also need rules for non-commingling so sole and joint inventions are not mixed into one patent application.

  • Two teams merge code, then argue over what was pre-existing know-how.
  • A deliverable fails acceptance criteria, and the schedule slips without a change-control path.
  • Engineers file a patent disclosure late, complicating inventorship and ownership allocation.

Director of Business Development / Strategic Partnerships

You are negotiating commercialization pathways, including field of use, territory, channel rights, and consent-to-transfer controls for competitor risk. You also need economics that match revenue realities, including accounting mechanics if any profit share applies. You want termination outcomes that preserve go-to-market options and clarify assignment or license rights in joint IP.

  • Counterparty pushes for broad sublicensing rights across all channels.
  • The deal stalls over who controls prosecution and foreign filings.
  • Termination terms fail to address who can commercialize joint developments afterward.

General Counsel

You need a contract that maps joint inventorship and joint work outcomes to the business deal, not default rules. You are managing pressure from product teams while controlling prosecution and maintenance costs, foreign filing elections, and licensing approvals. You also need enforcement readiness, including plaintiff-joinder commitments where required for patents.

  • Partner insists it can license “its share” of joint IP without consent.
  • The parties disagree on whether a deliverable is background or foreground intellectual property.
  • A co-owner refuses to join an infringement suit, stalling enforcement leverage.

VP Engineering / Head of R&D

You want speed, but you also need a clean record of contributions so joint inventorship and authorship do not become a debate later. You need milestones, acceptance criteria, and feasibility testing requirements that match how engineering actually ships. You also need rules for non-commingling so sole and joint inventions are not mixed into one patent application.

  • Two teams merge code, then argue over what was pre-existing know-how.
  • A deliverable fails acceptance criteria, and the schedule slips without a change-control path.
  • Engineers file a patent disclosure late, complicating inventorship and ownership allocation.

Director of Business Development / Strategic Partnerships

You are negotiating commercialization pathways, including field of use, territory, channel rights, and consent-to-transfer controls for competitor risk. You also need economics that match revenue realities, including accounting mechanics if any profit share applies. You want termination outcomes that preserve go-to-market options and clarify assignment or license rights in joint IP.

  • Counterparty pushes for broad sublicensing rights across all channels.
  • The deal stalls over who controls prosecution and foreign filings.
  • Termination terms fail to address who can commercialize joint developments afterward.

Co-Development Deal Architecture

Law Laguna drafts and negotiates development agreements that operate like a build plan and an intellectual property control system. We align scope, governance, and commercialization with how teams actually execute.

Master Agreement and Governance

  • Joint Development / Co-Development Master Agreement drafting. Define governance, scope, economics, the intellectual property framework, and termination mechanics in one controlling document. Convert collaboration into decision rights, escalation paths, and clean handoffs so the project does not rely on informal understandings.
  • Statements of Work and project plans. Set milestones, timelines, feasibility testing requirements, and acceptance criteria that match engineering delivery. Tie payments, change control, and deliverable definitions to objective acceptance procedures to reduce schedule and scope disputes.
  • Exploitation and licensing controls. Allocate field of use, territory, and channel rights, and require consent for transfers to competitors where needed. Document revenue-share and accounting mechanics if agreed, including timing, recordkeeping, audit rights, and interest.
  • Termination and post-termination outcomes. Specify whether joint intellectual property continues as joint ownership, assigns to one party, or converts to exclusive or non-exclusive licenses with scope limits. Preserve commercialization paths while preventing unintended carryover rights.

Intellectual Property Ownership Architecture

  • IP ownership architecture for foreground and background IP. Allocate ownership by inventorship, authorship, origination, or other agreed rules, and define how know-how is treated during and after the project. Elect governing law for inventorship and authorship determinations where relevant to reduce ambiguity in cross-border collaborations.
  • Documentation of contributions. Require written records, disclosures of joint contributions, and a structured disclosure process for inventions and works. Build an audit trail that supports inventorship, authorship, and ownership classifications when products evolve quickly.
  • Employee and contractor assignment obligations. Identify the operational requirement to obtain assignments that match the ownership allocation, and flag implementation steps for your teams. Coordinate with the dedicated implementation workflow through our Employee, Founder and Contractor IP Assignment page when needed.
  • Patent claim separation and non-commingling. Structure disclosure and drafting practices to avoid mixing sole and joint inventions in a single application. Reduce downstream prosecution disputes by keeping claim sets aligned to the intended ownership buckets.

Prosecution and Maintenance Operations

  • Prosecution and maintenance framework. Allocate decision rights, select counsel, and define cost sharing for filings, responses, and renewals. Require sharing of substantive communications and office actions, and set consultation duties before lapse or abandonment.
  • Foreign filing elections and non-participation handoff mechanics. Define jurisdiction-by-jurisdiction elections, and specify what happens if one party declines to file or maintain in a country. Use assignment in the non-file jurisdiction with a paid-up non-exclusive license or covenant not to sue back when appropriate.
  • Disagreement resolution for prosecution decisions. Establish an escalation path, including independent intellectual property counsel or arbitration for filing scope and abandonment disputes. Prevent missed deadlines by giving one party a timed step-in right under defined conditions.
  • Cost allocation and reimbursement mechanics. Set invoicing, approval thresholds, and timing for shared prosecution spend. Control budget variance by requiring advance notice for major scope changes and responses.

Enforcement, Defense, and Remedies

  • Enforcement and defense playbook for joint IP. Define notice obligations, cooperation duties, control of actions, settlement approval rights, and damages allocation. Add plaintiff-joinder commitments where legally required, so enforcement does not depend on goodwill later.
  • Restrictions on exploitation and transfers. Draft consent-to-transfer, anti-competitor transfer controls, and sublicensing limits that match the commercialization plan. Treat exclusive license grants versus restrictive covenants as a deliberate structure choice, not a template fill-in.
  • Revenue share and accounting for profits. State the obligation or waiver expressly, and define reporting cadence, audit rights, and payment timing. Avoid default outcomes by documenting whether any accounting is owed for exploitation of jointly owned rights.
  • Quality control for joint marks. Implement coordinated usage standards, sample approvals, inspection rights, governance review, and mutual approval of licensees. Confirm that goodwill inures to both parties and protect against inconsistent use that can undermine mark validity.

Undivided interests and unilateral licensing under 35 U.S.C. § 262

Patent co-ownership is not automatically a shared-control relationship, it is often a shared-title relationship with separate exploitation rights. Under 35 U.S.C. § 262, each joint owner may make, use, sell, offer to sell, and license the patented invention without the consent of the other joint owners, and without accounting, absent an agreement to the contrary. That default can create misalignment when one party wants exclusivity, controlled field-of-use commercialization, or a unified licensing program. It also changes negotiating leverage if a partner can license around your business model.

California deal teams often assume co-development means joint governance, but federal intellectual property default rules can override that assumption when the contract is silent. A California choice-of-law clause does not remove the need to address federal patent and copyright defaults directly. Law Laguna drafts California-governed agreements that still allocate federal inventorship and exploitation outcomes in contract terms. That approach supports diligence, commercialization planning, and clean termination outcomes for California-based operators.

  • Define foreground and background intellectual property with examples, including software, data, specifications, inventions, works of authorship, and know-how.
  • Require contribution documentation and joint disclosure timing so inventorship and authorship can be evaluated before filings or releases.
  • Allocate exploitation rights by field of use, territory, and channel, and replace default unilateral licensing with explicit consent requirements.
  • Set prosecution and maintenance decision rights, cost allocation, office actions sharing, and step-in rights before any lapse or abandonment.
  • Commit all joint owners to plaintiff joinder where required, and specify control of actions, settlement approval, and damages allocation.
  • Design termination outcomes that address assignment, continued joint ownership, or licenses, and define what happens to improvements and derivative works.

The agreement should include operational compliance hooks so documentation, disclosures, and prosecution communications occur as defined, not as best efforts.

officebgposter-1.jpg

California Regulatory Compliance

Technology collaborations regularly create patentable inventions, copyrightable works, and brand assets, and each category carries different default ownership and enforcement rules that your agreement should address explicitly. Patents turn on joint inventorship under 35 U.S.C. § 116, and co-ownership rights default to 35 U.S.C. § 262 unless you contract around unilateral exploitation and licensing. Copyright can shift to joint authorship under 17 U.S.C. § 101 and 17 U.S.C. § 201(a), while work made for hire rules can vest initial ownership under 17 U.S.C. § 201(b), and termination of transfers can arise under 17 U.S.C. § 203 and 17 U.S.C. § 304(c).

Where collaborations touch trademarks, the agreement should address coordinated usage and enforcement because standing and ownership matter in dispute posture. The Lanham Act addresses registrant standing to sue on a registered mark under 15 U.S.C. § 1114(1), and concurrent registration concepts can inform how parties separate rights in similar marks under 15 U.S.C. § 1052(d). For joint branding, quality control and goodwill allocation should be built into governance so the mark continues to function as a reliable source identifier.

Flexible Legal Counsel

Project-Based Deal Build

  • Define the scope, deliverables, and commercialization goals in a structured intake aligned to your product roadmap.
  • Draft or redline the master agreement and statements of work with an integrated intellectual property and governance framework.
  • Close the deal with execution-ready compliance hooks for disclosures, assignments, and prosecution coordination.

Ongoing Collaboration Counsel

  • Run scheduled check-ins to manage change control, milestone resets, and issue escalation before disputes harden.
  • Support day-to-day licensing approvals, transfer consents, and prosecution and maintenance decision points as they arise.
  • Maintain an audit trail for contributions, disclosures, and office action circulation to keep enforcement readiness intact.

Dispute and Renegotiation Support

  • Assess the contract and contribution record to identify leverage points tied to ownership, field of use, and enforcement commitments.
  • Negotiate amendments, standstills, or termination transition terms that protect commercialization pathways and confidential know-how.
  • Coordinate with intellectual property counsel on prosecution posture and claim separation when ownership or inventorship is contested.

Law Laguna structures the work to match how development teams operate and how rights are enforced. The goal is a collaboration that stays executable when priorities change.

California Intellectual Property Network

Build a deal stack that keeps control, commercialization, and enforcement aligned

Technology Development & Co-Development Agreements FAQs

Do joint development agreement IP ownership clauses need to be specific?

Yes, ownership clauses should be specific, and they should list the assets covered, including inventions, patent rights, works of authorship, source code, documentation, data, know-how, and trademarks. The agreement should control how foreground and background intellectual property are defined, how contributions are documented, and whether ownership follows inventorship under 35 U.S.C. § 116 or authorship concepts under 17 U.S.C. § 101 and 17 U.S.C. § 201(a). The hidden risk is that silence invites default co-ownership rules that can expand exploitation rights and reduce control over licensing and prosecution. Law Laguna drafts ownership architectures that map each deliverable and contribution type to a clear ownership and license outcome, with operational documentation requirements.

Can a co-owner license jointly owned patents without consent?

It depends, and the answer turns on whether your agreement modifies default rights for patents, inventions, and patent applications. Without a contract that restricts exploitation, 35 U.S.C. § 262 provides that each joint owner may make, use, sell, offer to sell, and license the patented invention without the consent of the other owners, and without accounting. The hidden risk is that unilateral licensing can undermine exclusivity, pricing, channel strategy, and investor expectations, even if both parties assumed “joint” meant shared approval. Law Laguna structures exploitation controls, consent requirements, and field-of-use allocations to replace default unilateral licensing with business-aligned decision rights.

Is it true that all patent co-owners must join an infringement lawsuit?

It depends, and the issue is enforcement of patent rights for jointly owned patents and related damages claims. In many situations, enforcement can require participation by all co-owners as plaintiffs, which can create a practical veto if a co-owner refuses to join, even when infringement is clear. The hidden risk is that a non-participating co-owner can reduce enforcement leverage and settlement options, and the default framework under 35 U.S.C. § 262 can compound the problem by allowing separate exploitation. Law Laguna builds enforcement playbooks with notice duties, cooperation clauses, and joinder commitments where required, plus control and settlement approval mechanics.

How do we write milestones and acceptance criteria in a Statement of Work?

You can and should write milestones and acceptance criteria so they govern concrete deliverables, including prototypes, specifications, test results, code drops, and documentation. The Statement of Work should control timelines, feasibility testing requirements, change control, acceptance procedures, and consequences for failed acceptance, and it should link deliverables to the intellectual property allocation for foreground and background rights. The hidden risk is that vague milestones create disputes over whether work is “done,” whether a contribution counts toward joint inventorship under 35 U.S.C. § 116, and whether payment triggers or ownership transitions occurred. Law Laguna drafts Statements of Work that read like an execution plan and integrate directly into the master agreement’s governance and IP framework.

How do we prevent a partner from licensing jointly owned IP?

You can prevent unilateral licensing by contract, and the agreement should cover patents, copyrights, trade secrets, know-how, and trademarks. Operationally, you control exploitation through consent requirements, field-of-use and territory allocations, sublicensing limits, and consent-to-transfer rules, converting default co-ownership exploitation into defined permissions. The hidden risk is that if you leave joint patent rights to the default rule under 35 U.S.C. § 262, a co-owner may license without consent and without accounting, and that outcome is difficult to fix after product launch. Law Laguna drafts restrictive covenants or exclusive license structures that match your commercialization plan and provide enforceable approval mechanics.

What should a joint R&D termination clause say about IP assignment and licenses?

The clause should address ownership and post-termination rights in foreground intellectual property, background intellectual property, improvements, know-how, and associated registrations such as patents, copyrights, and trademarks. The agreement should control whether joint IP remains jointly owned, assigns to one party, or converts into exclusive or non-exclusive licenses with defined scope, along with prosecution and maintenance handoffs and access to documentation needed to commercialize. The hidden risk is that termination without a clean IP outcome can strand a product with unclear rights, while defaults like 35 U.S.C. § 262 can still permit unilateral exploitation by a co-owner. Law Laguna negotiates termination outcomes that preserve commercialization options and define prosecution, enforcement, and confidentiality continuity.

How do joint works work for software, documentation, and other content?

Joint work” can apply to software, documentation, designs, marketing copy, audiovisual materials, and other works of authorship when parties intend their contributions to merge into a unitary whole. Under 17 U.S.C. § 101 and 17 U.S.C. § 201(a), joint authors can become co-owners, while 17 U.S.C. § 106 describes exclusive rights that the contract may allocate through licenses and restrictions. The hidden risk is that teams may jointly create content without aligning intent, assignments, and licensing boundaries, resulting in co-ownership that complicates product distribution and derivative works. Law Laguna defines authorship intent, work-made-for-hire positions under 17 U.S.C. § 201(b) where applicable, and licenses that match release and update cycles.

Do we need special terms for joint branding or joint trademarks?

Yes, joint branding needs explicit terms covering marks, usage standards, approvals, and enforcement, and it should identify the assets involved, including registered and unregistered trademarks, logos, composite marks, and goodwill. Operationally, the agreement should implement coordinated quality control, mutual approval of licensees, sample reviews, and inspection rights, and it should clarify registrant standing and enforcement roles consistent with 15 U.S.C. § 1114(1). The hidden risk is that inconsistent quality control can weaken the mark’s source-identifying function, and unclear composite mark rules can create implied rights in the other party’s individual marks. Law Laguna drafts joint mark governance, composite mark protections, and concurrent-rights concepts informed by 15 U.S.C. § 1052(d).

lagunabgposter-1.jpg

Stop unilateral licensing and enforcement deadlocks

When co-development documents leave ownership, exploitation, and prosecution to default rules, the collaboration can drift away from the business deal. Uncontrolled licensing and unclear decision rights can force renegotiations midstream, often at the moment the technology becomes valuable. Enforcement constraints for jointly owned patents can reduce leverage when infringement or competitive pressure appears.

We start with a structured intake on scope, contributions, milestones, and commercialization intent, then convert that into governance, IP allocation, and enforcement-ready terms. You receive drafts that integrate the master agreement and Statements of Work into a single operating framework.