A Delaware C-corporation starts as a new legal person, and formation documents do not transfer intellectual property into it. The corporation does not acquire code, patent rights, trademarks, or domain names merely because founders issue stock or continue the same business. A separate assignment, contribution, sale, or license must move each relevant asset.
A founder usually owns software created as a personal side project unless an employment agreement, consulting agreement, or other obligation gives someone else a claim. An inventor may initially own patent rights even when the startup plans to commercialize the invention. Trademark ownership generally follows actual use and control of the brand, so a founder or existing foreign company may own the relevant rights before the Delaware company exists.
A foreign operating company may own work created by its engineering employees under local law or signed invention agreements. In some countries, individual employees retain certain rights or compensation claims despite broad contract language. You need to review the applicable employment rules and agreements rather than assume the U.S. parent owns work produced by the foreign team.
A contractor-built MVP creates another common ownership gap. Under U.S. law, an independent developer generally owns the copyright in code unless a written agreement assigns it, and a contract label describing the work as “work made for hire” may not solve the problem. Foreign law can produce a different result, but incorporation in Delaware changes neither outcome.
Investors call the documented ownership history the “chain of title.” Each link should show how rights moved from the person or entity that created or owned them to the Delaware corporation. For example, a startup cannot establish clean ownership of its current platform if a freelancer retained rights in the original codebase that later employees expanded. Investor counsel may then require corrective assignments, local-law analysis, or a license before financing can proceed.
A foreign operating company must transfer or license its IP through signed agreements. Delaware formation documents and board resolutions alone do not change ownership. The transaction should identify the relevant software intellectual property, patent rights, trademarks, domains, documentation, and related contracts.
A capital contribution transfers the IP to the U.S. company in exchange for equity or as an additional contribution to capital. In some reorganizations, the foreign company receives shares. When the Delaware company already owns the foreign company, the parties may record the transfer as additional paid-in capital. An intellectual property assignment agreement completes the legal transfer. Founders often use a contribution when they intend the Delaware company to hold the IP permanently and the applicable tax rules support that structure.
An asset sale transfers the IP for cash or a promissory note. The parties should establish an arm’s-length price through a defensible valuation, especially when the same shareholders control both companies. A note can help when the Delaware company lacks cash, but deferred payment does not necessarily defer taxes. The foreign company may recognize taxable gain, and the transaction may trigger withholding or indirect taxes.
A license leaves ownership with the foreign company while giving the Delaware company specified rights. The license should address exclusivity, territory, sublicensing, improvements, duration, and termination. Founders may choose licensing when local law restricts a transfer or when tax planning requires a staged reorganization. U.S. investors usually examine whether the Delaware company can operate, raise capital, and complete an acquisition without losing access to the licensed technology.
Consider a software startup whose foreign company employed the engineers who built its platform. The Delaware company could receive the code through a contribution, purchase it under a note, or obtain an exclusive license. Each option gives the U.S. company different rights and creates different tax and valuation consequences. None fixes missing assignments between the engineers and the foreign company, so the startup must confirm that chain of title first.
Cross-border IP transfers require coordinated legal and tax review. U.S. counsel can prepare the transfer documents and Delaware corporate approvals. Home-country counsel should confirm local approval procedures, registration requirements, and any restrictions on transferring employee-created inventions. Tax advisers should review transfer pricing, taxable gain, foreign withholding, and treaty treatment before the parties sign. A template chosen without that coordination can move the wrong rights or create an unexpected tax liability.
Contribution best fits a restructuring in which the foreign owners will receive or already hold equity in the U.S. parent.
Sale best fits a foreign company that needs documented consideration and can support the purchase price.
License best fits a staged restructuring or a business that must retain foreign ownership for tax, regulatory, or commercial reasons.
U.S. and home-country counsel should review any structure before signing because local transfer rules can change the tax and ownership result.
A founder IP assignment agreement transfers ownership of specified intellectual property from a founder to the company. The document should cover source code, inventions, patent rights, trademarks, domains, product designs, technical documentation, and related rights. It should use present assignment language rather than a promise to assign rights later. Incorporating a Delaware company or issuing founder stock does not complete this transfer unless the signed documents expressly say so.
Pre-incorporation work requires particular attention because the company did not exist when the founder created it. For example, a founder who built an MVP before formation generally owns that software until a written assignment transfers it. Investors commonly request the signed assignment and a schedule identifying the transferred software intellectual property, patent filings, and other assets.
Post-incorporation work needs separate protection. Each founder should sign an invention and confidentiality agreement that assigns future work created within the founder’s role. Without that ongoing assignment, the company may own the original MVP but lack clear ownership of later improvements.
A basic template may work when one founder created all relevant IP independently, no foreign law applies, and no third party may claim rights. The template should still identify the parties and transferred assets, state the consideration, address further documents needed to record ownership, and include any locally permitted waiver of moral rights.
Founders should involve counsel when prior employment, university research, joint development, or foreign law affects ownership. A former employer may claim inventions related to the founder’s earlier job. A collaborator may own part of a jointly developed product. A U.S. assignment form may also fail to satisfy execution, inventor compensation, or recordation rules in another country. Zecca Ross can review the chain of title and coordinate the assignment with home-country counsel before investor diligence begins.
A startup cannot assume that a contractor-built product belongs to the company that paid for it. Under U.S. copyright law, an independent contractor generally owns the code unless a signed agreement transfers ownership. Calling software “work made for hire” may not solve the problem because commissioned software often falls outside the limited categories that qualify.
Suppose an offshore development shop builds your MVP before the Delaware corporation exists. The contract should state that the shop “hereby assigns” all rights, title, and interest in the software to the designated company. The assignment should cover code, documentation, inventions, patent rights, later modifications, and related deliverables. It should also require the shop to obtain equivalent assignments from every employee and subcontractor who contributes. Any preexisting tools retained by the shop should appear on a schedule and include a license broad enough for your company to operate and modify the product.
Cross-border assignments require review under the law governing the contractor and the agreement. Local law may restrict transfers of future rights or moral rights, require specific payment or formalities, or preserve rights for individual developers. A U.S. assignment copied from a template may therefore leave gaps even when everyone signed it.
Before fundraising, collect the signed agreement, project scope, payment records, and subcontractor assignments. If any contributor signed only a confidentiality agreement or promised to assign rights later, U.S. and local counsel should determine what corrective documents will establish a defensible chain of title.
A U.S. employee invention assignment agreement gives the company contractual ownership of work that an offer letter often leaves unaddressed. The agreement should assign relevant inventions and software intellectual property when the employee creates them, rather than merely promise a future transfer. It should also protect confidential information and require the employee to sign later documents needed for patent filings or ownership records.
Foreign employment law can narrow or override a U.S.-style blanket assignment. Some jurisdictions in Europe and Latin America preserve statutory inventor rights, restrict assignments to work connected with employment, or require additional compensation for certain inventions. A Delaware parent cannot assume that its standard U.S. agreement extinguishes those rights. Local counsel should adapt the agreement to the employee’s work location and applicable law.
The employee’s legal employer also affects the chain of title. If engineers work for a foreign subsidiary, local law may place ownership with that subsidiary rather than the Delaware parent. The subsidiary may need localized employee agreements and a separate intercompany assignment or license transferring the resulting IP to the parent. If the U.S. company employs staff abroad directly, counsel should review local employment and tax requirements alongside the invention assignment.
Inventorship identifies the individuals who conceived the claimed invention, while patent ownership identifies the person or entity entitled to control the patent rights. Founders cannot choose inventors for convenience or replace them with the company. Ownership, however, can move through a written assignment.
A Delaware corporation does not acquire a patent application merely because the inventors founded or joined it. If an individual founder filed a provisional or nonprovisional application, that founder must assign the application and related rights to the corporation. If a foreign company owns the filing, the foreign company must execute the transfer with the corporate approvals and local formalities its home jurisdiction requires.
A patent assignment should cover more than the existing filing. Depending on the transaction, the document may need to include priority rights, later applications based on the same invention, continuations, issued patents, and enforcement rights. You should also record the assignment with the relevant patent offices so the public record reflects the ownership change. Transferring a foreign patent application does not create U.S. patent protection. Patent rights remain territorial, and U.S. filing deadlines may apply.
Unassigned and jointly owned patents create recurring problems during IP due diligence. An investor’s counsel will compare the named inventors, assignment records, employment agreements, and corporate approvals. Under U.S. law, a joint owner may generally use or license a jointly owned patent without the other owner’s permission unless an agreement changes that rule. Incorrect inventorship requires a separate correction. An ownership assignment cannot cure it.
A foreign company that used or registered a brand before the U.S. entity existed may own the related trademark rights. Forming a Delaware corporation does not transfer those rights. The U.S. company needs a written assignment that transfers the mark and its associated goodwill. Counsel should also record the change with the relevant foreign trademark office and the USPTO when a U.S. application or registration exists.
A foreign trademark registration does not automatically provide U.S. protection. Certain foreign applications and registrations can support a U.S. filing, but eligibility, deadlines, and documentation depend on the filing basis and applicable treaties. The U.S. entity must also appear as the correct applicant or obtain the rights through a valid assignment.
A USPTO application usually relies on either current use in U.S. commerce or a genuine intent to use the mark. A use-based application requires evidence showing how customers encounter the mark, such as a software product page that permits purchasing or downloading. An intent-to-use application can establish an earlier filing date, but the USPTO will not issue the registration until the applicant proves qualifying use. Federal law also restricts assignments of intent-to-use applications before that proof, except with the transfer of the related ongoing business.
Each application identifies specific classes of goods or services. A SaaS company may need coverage for downloadable software, hosted software services, or both, depending on how it delivers the product. Filing early helps create a documented ownership record and reduces the risk that another party claims conflicting U.S. rights while investors conduct IP due diligence.
Open-source compliance affects whether the U.S. company can use and commercialize its software as investors expect. A startup may own every line written by its developers while still violating licenses attached to third-party components. Investor counsel therefore reviews open-source use alongside assignments and other chain-of-title records.
Permissive licenses such as MIT and Apache generally allow code to appear in proprietary products if the company follows notice, attribution, and other license requirements. Apache licenses may also carry patent-related terms. Copyleft licenses can impose broader obligations. GPL code may require disclosure of corresponding source code when covered software is distributed, depending on how the component is combined with the product. AGPL can extend similar obligations to software accessed over a network.
Copyleft code does not automatically make an entire product open source. The risk depends on the license, integration method, modifications, and how customers receive or access the software. For example, a separate GPL development tool may create less concern than an AGPL library incorporated into a proprietary SaaS application.
A basic audit should produce an inventory of open-source components, versions, licenses, and locations in the codebase. The review should record how each component is used, modified, distributed, or deployed. Your data room should also include required notices, available source-code offers, internal approval policies, and a remediation log for components that must be replaced, isolated, relicensed, or brought into compliance. Automated scanning helps identify dependencies, but legal and engineering review must evaluate how license terms apply to the actual product.
Bring in U.S. and home-country counsel when a foreign company owns the IP, foreign employees or contractors created it, or the transfer may trigger tax or regulatory consequences. A domestic founder assignment may support a limited cleanup. A cross-border contribution, sale, or license usually requires advice in both jurisdictions.
U.S. counsel structures the transfer under Delaware corporate law and evaluates U.S. tax treatment. U.S. counsel also prepares board approvals, transfer documents, and financing disclosures. Home-country counsel confirms that local law permits the transfer and identifies required approvals, registrations, or currency controls. Local advice also covers employment law, statutory inventor compensation, and formalities for patents or trademarks.
Both counsel should review tax treaty questions and transfer pricing before anyone signs the documents. They should use the same valuation, effective date, IP schedule, and transaction structure. For example, a Delaware company might sign an IP purchase agreement that fails because the foreign seller never obtained a required shareholder approval. A U.S.-style employee assignment may also leave statutory inventor rights unresolved under local law.
Zecca Ross Law Firm handles Delaware flips and cross-border restructurings for international founders. The firm can coordinate the U.S. corporate and tax work with home-country counsel so each adviser addresses the same transaction. A defined scope and flat-fee or capped-fee structure can provide senior-attorney involvement with predictable pricing when the work permits it.
IP ownership problems are usually fixable when you address them before fundraising. Early review gives you time to obtain missing assignments, secure corporate approvals, value transferred assets, and coordinate tax treatment across jurisdictions.
Once a term sheet arrives, investor counsel will expect a clear chain of title on a financing timeline. Missing signatures, disputed ownership, or foreign transfer requirements can then require urgent work across several countries, which raises cost and may delay diligence.
Zecca Ross Law Firm helps international founders manage Delaware flips and cross-border IP transfers with direct attorney involvement. The firm can coordinate U.S. corporate and tax work with home-country counsel while giving founders predictable scope and fee options.
Legal clarity starts here. Partner with Zecca Ross Law Firm to transform complexity into opportunity.