Design Ownership & Development Rights
Define who owns the work and exactly what will be handed over.
Ownership is confirmed as the customer directs. The project agreement distinguishes existing customer IP, new development results and any third-party licensed content, then identifies the deliverables and handover responsibilities.
- Existing customer IP
- Project development
- Customer-designated owner
Customer-directed ownership, defined before development
Development ownership is confirmed as the customer directs. For joint development, once the agreed one-time development fee is paid in full, the project development results belong to the customer or the rights holder designated by the customer.
The project agreement identifies the intended rights holder, development scope, one-time development fee and deliverables. It also records the formats and arrangements for handing over files, tooling and technical information, so ownership and practical delivery are addressed together.
| Category | Ownership and use | What to confirm |
|---|---|---|
| Customer's existing IP | Customer-provided ideas, designs, content, files and other IP remain with the customer or the relevant rights holder. Access for project work does not authorize reuse elsewhere. | What is provided, who may use it and the permitted project purpose. |
| New project development results | The customer directs ownership. For joint development, the agreed project results belong to the customer or its designated rights holder once the agreed one-time development fee is paid in full. | The development scope, designated rights holder, agreed fee and handover obligations. |
| Third-party licensed content or technology | Any third-party material is identified and its applicable license terms are confirmed in advance. Its inclusion does not transfer rights beyond those terms. | The approved component or content, license permissions, restrictions and any required separate authorization. |
Agree what will be delivered, in usable formats
The handover list is confirmed for the actual project. It identifies the files, physical items, approved versions, formats, recipient and delivery arrangements included in the agreed scope.
| Delivery category | Items to define in the handover list |
|---|---|
| Industrial and structural design | Approved industrial design, structural design, CAD models and drawings, with the agreed editable and exchange formats. |
| Tooling and technical information | Moulds and tooling within scope, their identification and location, associated tooling files, and the agreed technical documents and transfer arrangements. |
| Electronic design files | The agreed schematics, circuit-board design files, production documents and associated electronic information. |
| Programs and firmware | Approved programs, production firmware, encrypted packages and agreed source files, with their version and delivery format recorded. |
| Audio and other product content | The approved audio and content files developed or supplied for the project, subject to the confirmed rights and license terms. |
| Packaging files | Approved packaging designs, artwork and production files in the agreed formats. |
Source code, production firmware and encrypted packages serve different purposes. Their delivery and manufacturing access are defined in the project scope. See secure programming and firmware protection for the related release and production controls.
Project access is not permission for other uses
Customer materials, designs, samples and development results are used only for the authorized project. Without the customer's written authorization, they must not be:
- Reused for another customer or an unrelated product.
- Resold, licensed or supplied to another party outside the authorized project scope.
- Disclosed beyond the people and approved external parties authorized to perform the project work.
- Shown publicly in a showroom, exhibition, website, social media post, photograph, video or other promotional material.
Approval to manufacture, inspect or subcontract a defined task does not by itself grant permission to publicize or otherwise exploit the customer's work. Any requested use outside the project purpose is discussed separately and requires written authorization.
Questions before you share the details
Clarify the protection, responsibilities and next step for your project.
Who receives ownership in a jointly developed project?
Development ownership is confirmed as the customer directs. For joint development, once the agreed one-time development fee is paid in full, the project development results belong to the customer or the rights holder designated by the customer.
Does the development fee automatically define every file we receive?
The agreed one-time development fee and the technical handover are documented together. Confirm the deliverable list, native or exchange formats, agreed source files, tooling and technical documents, timing and responsible contacts before work begins.
What happens to our existing IP and third-party content?
Your existing IP remains yours and is used only within the authorized project scope. Third-party software, content or components are identified and their license terms confirmed in advance; they are not represented as newly created customer-owned IP.
Can the design be reused or included in factory marketing?
Customer designs and project results are not reused, disclosed, resold, licensed or publicly displayed without the customer’s written authorization. This also applies to photos, samples, packaging and publicity.
Begin with a non-sensitive overview.
Describe the product, your starting point and the support you need. Request an NDA discussion before sharing detailed drawings, programs, keys or restricted commercial information.
This link preselects the NDA discussion request in the existing RFQ. It does not sign an NDA or send an inquiry.