Skip to content
Delewarellc

IP holding company

A separate entity that holds intellectual property and licenses it to operating entities.

IP holding companyDelewarellcGLOSSARYENTITYIP holding companyDEFINITIONA separate entity that holds intellectual property and licenses it to operating entities.
IP holding company: A separate entity that holds intellectual property and licenses it to operating entities.

Definition

IP holding company is a structure where intellectual property (trademarks, patents, copyrights) is held in a separate entity and licensed to operating entities. Provides asset protection and can offer tax planning benefits.

Context

Delaware LLCs commonly used as IP holding companies due to favorable law and contractual freedom.

Example

A founder holds trademark and software IP in a Delaware LLC and licenses it to the operating Delaware LLC. Royalty payments flow between the two LLCs.

Common pitfalls

  • Transfer pricing rules for intercompany royalties.
  • Substance-over-form risk if IP holding lacks economic substance.

What an IP holding company actually does day to day

The core glossary entry describes an IP holding company as a separate entity that holds intellectual property and licenses it to operating entities. To make that concrete for a non-resident founder, picture two distinct legal persons. One owns the brand name, the logo, the codebase, the domain, and any patents or design rights. The other talks to customers, takes payments, signs contracts with suppliers, and employs or contracts the people who do the work. The holding entity rarely touches a customer. Its job is to own valuable rights and to permit the operating entity to use them under a written license in exchange for a royalty.

On a normal week, an IP holding company does very little visibly. It does not run a checkout, ship a product, or answer support tickets. What it does instead is administrative and contractual. It keeps the registrations current, it records new assignments when fresh code or artwork is created, and it issues an invoice to the operating company for the agreed royalty. That quiet profile is the point. By keeping the valuable rights away from the entity that signs day to day contracts and faces customers, the founder reduces the chance that an operating dispute reaches the assets that took years to build.

For a single founder this can feel like overhead at first. The benefit shows up later, when the business has revenue worth protecting, when an investor wants a clean chain of title, or when a buyer asks who actually owns the trademark. Setting the structure up early, while everything is small and uncontested, is far simpler than untangling ownership after the fact.

Why the structure matters more for a foreign founder

A non-resident running a Delaware LLC carries a few risks that a domestic owner may not feel as sharply. The founder is often the sole human in the business, frequently building the product personally before any company exists. That means a large share of the company value lives in a single person's head and hard drive. If that intellectual property is never cleanly moved into a company, it sits in a legal gray zone where the founder personally owns it while the operating LLC merely uses it. An IP holding company gives that value a clear, durable home.

There is also a practical distance issue. A founder who lives outside the United States cannot easily walk into a bank or a courthouse. Disputes, contract reviews, and registrations all happen remotely and slowly. The cleaner the ownership structure, the fewer surprises arrive by mail. When the brand and the code belong to a dedicated entity with its own records, questions from banks, payment processors, and future partners get shorter and clearer answers, which matters a great deal when the founder is in a different time zone and cannot resolve things in person.

None of this is unique to Delaware, but Delaware's contractual freedom and predictable entity law make it a comfortable place to park rights. The same flexibility that draws operating companies to the state also makes it a reasonable home for a holding entity. This is general information and not legal advice, so a founder weighing the structure should confirm specifics with a qualified professional before committing.

How it applies to a single-member foreign-owned LLC

Most readers of this entry will not start with two companies. They will start with one Delaware LLC, single-member, owned by a person living abroad, taxed by default as a disregarded entity for US federal purposes. In that starting position there is no separate IP holding company at all. The same single LLC both owns the rights and runs the business. That is a perfectly normal beginning, and for a brand new project it is often the sensible one. The holding structure is a step the founder grows into, not a box to tick on day one.

When the founder does decide to separate, the cleanest version for a solo operator is two single-member LLCs with the same owner, or a parent and subsidiary where the holding entity owns the operating one. The holding LLC owns the trademark, the software, and the domain. The operating LLC signs a license and pays a royalty. Because both are typically disregarded entities owned by the same non-resident, the federal tax picture often does not change dramatically, but the paperwork certainly does. Each entity now needs its own formation, its own EIN, its own records, and frequently its own bank account.

The single-member detail also shapes the federal filing duties. A foreign-owned single-member LLC that is disregarded is generally treated as a reporting corporation for the limited purpose of Form 5472, filed together with a pro forma Form 1120. That obligation does not disappear because the entity is a passive holding company. If anything, an entity that exists mainly to receive intercompany royalties will have related-party transactions to report, which is exactly what Form 5472 is built to capture.

A worked example with two Delaware LLCs

Consider a founder in Lagos building a SaaS product. She first forms one Delaware LLC, Brand Holdings LLC, paying the $110 Certificate of Formation filing fee. Into that entity she assigns the trademark application, the source code repository, and the product domain, using a written assignment. Brand Holdings now owns the rights but does not sell anything. A few weeks later she forms a second Delaware LLC, App Operations LLC, again paying the $110 filing fee, and this is the entity that will run subscriptions, sign the payment processor agreement, and contract any freelancers.

The two entities then sign a license. Brand Holdings grants App Operations the right to use the trademark and the software in exchange for a royalty, say a percentage of subscription revenue, documented in a real agreement with a real rate. Each month App Operations records the royalty as an expense and Brand Holdings records it as income. Because both are disregarded single-member LLCs with the same foreign owner, the combined federal income picture nets out in many cases, but the intercompany flow still has to be priced and documented as if the two were independent parties.

Both entities owe the $300 flat Delaware franchise tax due each year on June 1, so the founder now budgets $600 annually for that line alone. Both need an EIN, obtained free by filing Form SS-4, which for an applicant without a US taxpayer ID generally takes around 8 to 10 business days. And both will need to handle Form 5472 reporting where related-party transactions occur, with the $25,000 penalty for failing to file looming over each return.

Getting the IP into the holding company in the first place

An IP holding company is only as strong as the chain of title behind it. A common and costly mistake is to form the entity, declare that it owns the brand, and never actually transfer anything. Ownership of intellectual property does not move because a founder believes it should. It moves through a written assignment, signed and dated, that names the specific rights being transferred. The related glossary terms assignment of rights and work for hire exist precisely because this step is so often skipped or done loosely.

For a non-resident founder there are usually two waves of IP to capture. The first wave is everything the founder personally created or registered before the company existed, such as the domain bought in a personal account, the early prototype code, or a logo commissioned years ago. Each of these needs an explicit assignment from the individual to the holding LLC. The second wave is everything created after formation, especially work done by contractors. A contractor does not automatically hand over rights just by being paid, so the founder needs a work-for-hire clause plus an assignment in every contractor agreement, then a path for that work to land in the holding entity.

Some rights also require recordation with a government office to make the transfer effective against third parties. Patents and recorded trademarks are the usual examples. A founder who assigns a registered mark but never records the assignment may find the public record still points to the old owner, which can complicate enforcement and any future sale. Treating assignment as a paperwork chore rather than a one-line statement is what keeps the holding company genuinely in control of what it claims to own.

Royalties, transfer pricing, and the arm's length idea

The economic engine of an IP holding company is the royalty the operating company pays to use the rights. That royalty cannot be a number invented to suit the founder's mood. The principle that governs it is transfer pricing, the linked glossary term, which asks whether related parties dealt with each other on the same terms two unrelated parties would have accepted. A royalty that is wildly high or suspiciously round invites the question of whether it reflects real value or merely shifts money between pockets the founder controls.

For a solo founder, the discipline here is to set a defensible rate and write it down before money starts moving, not after a tax authority asks. A defensible rate usually rests on something observable, such as what comparable licenses charge in the same industry, or a reasoned split of the profit the IP helps generate. The founder does not need a thick valuation report to begin, but they do need a rationale that a reasonable outsider could follow, and they need the actual payments to match the written agreement rather than drifting away from it over time.

The pitfalls the core entry names, transfer pricing rules and substance-over-form risk, both live here. If the royalty is mispriced, the pricing can be challenged. If the holding company has no real activity, no records, and no genuine ownership beyond a label, the whole arrangement can be looked through as form without substance. Keeping invoices, keeping the rate reasonable, and keeping the entities genuinely separate are what turn the structure from a label into something that holds up.

How it connects to the formation steps

An IP holding company is not a special product a founder buys. It is an ordinary Delaware LLC used for a particular purpose. So every formation step that applies to a normal operating LLC applies here too. The founder files a Certificate of Formation for $110, names a registered agent in Delaware, and adopts an operating agreement. The difference is purely in what the entity is built to do, which is to own rights and license them, rather than to sell to customers directly.

Running two entities instead of one roughly doubles the recurring obligations. Two Certificates of Formation mean two filing fees up front. Two entities mean two $300 franchise tax bills each June 1. Two entities mean two EIN applications, each free via Form SS-4 and each taking the same 8 to 10 business days for a non-resident without a US taxpayer ID. A founder weighing whether to split early should price this honestly, because the structure earns its keep through protection and clean ownership, not through saving money on filings.

It is worth noting that a flat formation package, such as a $297 one-time setup, generally covers one entity. Forming a separate holding company is a second engagement with its own costs, not an add-on that comes free with the first. Planning for that from the outset prevents the unpleasant surprise of discovering, mid-build, that the protective structure costs more than the single LLC the founder originally budgeted for.

Banking the holding and operating entities

Once two entities exist, the royalty has to flow somewhere real. That means the holding company generally needs its own bank account, separate from the operating company's account, so that intercompany payments can actually move and be traced. Mixing the money defeats the separation the structure is built to create. If royalties never leave a single shared account, an outsider can reasonably argue the two entities are really one, which undercuts both the asset protection and the tax treatment the founder is relying on.

Non-resident founders commonly open US business accounts with fintech providers such as Mercury, Wise, Relay, Lili, or Payoneer, since these can be opened remotely without a US visit. A founder running a holding and operating pair will often want an account for each entity, using the entity's own EIN and formation documents during onboarding. Some providers are more comfortable than others with passive holding entities that show little customer activity, so it is worth checking expectations before applying rather than after a holding-company application stalls.

The flow then becomes routine. Customer payments land in the operating company's account. Each month the operating company pays the agreed royalty into the holding company's account against an invoice. That single recurring transfer is the visible heartbeat of the structure, and keeping it clean, dated, and matched to the license agreement is what gives the arrangement credibility if anyone ever looks closely.

Tax filings the structure creates

Adding a holding company multiplies federal filing duties for a foreign owner. Each foreign-owned single-member LLC that is disregarded generally has to file a Form 5472 together with a pro forma Form 1120 to report transactions with its owner and with related parties. With a holding and operating pair, the very thing the structure depends on, the intercompany royalty, is a reportable related-party transaction. So both entities are likely to have Form 5472 obligations, and the $25,000 penalty for a missed or incomplete filing applies to each return separately.

This is where the convenience of a single LLC and the protection of a two-entity structure pull against each other. One entity means one set of forms. Two entities mean two sets, two deadlines, and twice the exposure to that penalty if something slips. A founder who is comfortable with the discipline of timely, accurate filing can manage this, but a founder who already struggles to file one return on time should think hard before doubling the work. The protection is real, and so is the added compliance load.

Because tax outcomes depend heavily on the founder's home country, any tax treaty, and the specific facts, this section is general information rather than advice. Whether the royalty is also subject to US withholding, and at what rate, can turn on treaty provisions and on paperwork like the relevant withholding form. A founder setting up cross-border royalty payments should confirm the treatment with a qualified tax professional before assuming a particular result.

Beneficial ownership reporting and the holding company

Founders who researched US compliance a couple of years ago may remember the beneficial ownership information requirement under the Corporate Transparency Act, which originally asked many small entities to report their owners to FinCEN. For a two-entity structure that once implied two separate reports, one for the holding company and one for the operating company, each naming the same beneficial owner behind both.

That picture changed for US-formed entities. Under the FinCEN Interim Final Rule of March 26 2025, domestic entities such as LLCs formed in Delaware are exempt from the beneficial ownership information reporting requirement, with the obligation refocused on entities formed abroad that register to do business in the United States. So a non-resident founder operating two Delaware LLCs, a holding and an operating company, generally does not file beneficial ownership reports for those US-formed entities under the current rule. This removes one piece of duplicated paperwork the two-entity structure would otherwise have created.

Rules in this area have shifted before, so a founder should treat the exemption as the present state rather than a permanent guarantee and confirm the requirement still applies when forming. The broader lesson is that a holding structure does not automatically multiply every compliance duty. Some obligations, like Form 5472, do scale with the number of entities. Others, like beneficial ownership reporting for US-formed LLCs under the 2025 rule, currently do not apply at all. Knowing which is which keeps the founder from either over-filing or missing something that matters.

Operating LLC versus holding LLC as a structural choice

The IP holding company is one expression of a wider pattern captured by the related term operating LLC versus holding LLC. The general idea is to separate entities that do risky, customer-facing work from entities that quietly own valuable things. Intellectual property is one kind of valuable thing, but the same logic applies to real estate, to equity in other companies, and to large cash reserves. A founder who grasps the holding pattern in the IP context can apply it elsewhere as the business grows.

For most non-resident software or brand founders, intellectual property is the asset worth isolating first, because it is often the single most valuable thing the business owns and the easiest to move into a separate entity early. A holding company that owns the brand and the code, with an operating company that licenses them, is a focused version of the broader holding structure tuned to the realities of a digital business run from abroad.

The structural distinction also clarifies what each entity should and should not do. The operating company signs the messy real-world contracts and absorbs the operating risk. The holding company stays clean, owns the rights, and avoids signing customer or supplier agreements that could drag liability onto its assets. Blurring those roles, by letting the holding company start selling or letting the operating company quietly own the trademark, slowly dissolves the very separation the founder built the two entities to achieve.

Edge cases that complicate the simple picture

The clean two-entity diagram meets friction in real life. One common edge case is the founder who has already been operating a single LLC for a year or two and now wants to retrofit a holding company. Moving live IP out of an operating entity that already has contracts, customers, and revenue is more delicate than assigning rights at formation. Existing licenses, processor agreements, and any pledges to lenders may reference the operating entity as the owner, and each of those may need to be revisited so the chain of title stays consistent.

Another edge case is IP that is jointly created or partly owned by someone else, such as a co-founder, a former contractor who never signed an assignment, or an open-source component with its own license terms. A holding company can only hold what the founder genuinely has the right to transfer into it. If a co-founder retains a share of the code, or a contractor never assigned their work, the holding entity does not magically acquire those rights by declaring ownership. Cleaning up these gaps before consolidating IP is tedious but necessary.

A third edge case is the founder who registers a trademark or patent in their personal name in their home country while the holding company sits in Delaware. Cross-border registrations follow each country's own rules about who owns what and how transfers are recorded. The Delaware holding company may own the US rights cleanly while a foreign registration still points to the individual. Mapping out where each right is registered, and in whose name, prevents the false comfort of assuming one assignment covered the whole world.

Common misunderstandings founders carry into the structure

The most frequent misunderstanding is that creating a holding company by itself protects the IP. Forming the entity is the easy part. The protection comes from the assignment that actually moves the rights in, the license that governs their use, the royalty that is priced reasonably, and the separation that is maintained over time. An empty holding company with no assigned rights and no real records is a label, not a shield, and that is precisely the substance-over-form risk the core entry warns about.

A second misunderstanding is that the structure is primarily a tax trick. While intercompany royalties can play a role in tax planning, a two-entity setup mainly buys asset protection and clean ownership, and it does so at the cost of doubled franchise tax, doubled EINs, and doubled Form 5472 exposure. A founder who builds the structure expecting guaranteed tax savings, without checking their specific facts with a professional, may be disappointed. The honest framing is that the structure organizes risk and ownership, and any tax effect depends on circumstances.

A third misunderstanding is that once set up, the structure runs itself. It does not. The royalty has to be invoiced and paid, the records have to be kept, new IP has to be assigned in as it is created, the franchise tax has to be paid each June 1, and the federal filings have to be made on time. The founders who get real value from an IP holding company are the ones who treat the ongoing discipline as part of the deal, not as optional housekeeping they can skip once the entities exist.

Deciding whether and when to build it

Not every founder needs an IP holding company, and forcing the structure too early can add cost and paperwork without matching benefit. A reasonable way to think about timing is to ask what is actually at risk. A pre-revenue project with a half-built prototype and no contracts has little to protect and may be served perfectly well by a single Delaware LLC that owns everything. The protective separation earns its keep once there are real customers, real revenue, and real IP value that a dispute could threaten.

Three signals often suggest the structure is worth the added load. The first is meaningful revenue tied to a brand or codebase that would be painful to lose. The second is an approaching event that rewards clean ownership, such as raising money or selling, where a buyer or investor will scrutinize who owns the IP. The third is rising operating risk, like signing larger supplier contracts or entering markets where disputes are more likely. When one or more of these is present, the cost of two entities starts to look small against what they protect.

Whatever the timing, the decision deserves a real conversation with qualified legal and tax advisers who know the founder's home country and specific facts, since this entry is general information rather than advice. The structure is well understood and widely used, but the details that make it work or fail, the assignments, the pricing, the filings, and the upkeep, are where a thoughtful professional adds the most value for a founder running everything remotely from outside the United States.

Related terms

Related glossary terms & guides