Can My Enterprise Customer Let Its Subsidiaries Use My Software?

“They want to add their European subsidiary. Do you get paid for that, or did you already give it away?”

You closed a big enterprise deal. Now the customer’s legal team wants the word “Affiliates” added to the license grant. It looks like a tiny edit.

It is not. That one word can decide whether a customer’s 20 subsidiaries use your product for the price of one. You usually find out at renewal, when the leverage is gone.

“Customer” Usually Means One Company

A license grant covers whoever the contract names. If the contract names one legal entity, only that entity can use the software. Its parent, its sister companies, and its subsidiaries are not included unless the contract says so.

“Affiliate” Can Mean Almost Anything

Most affiliate definitions turn on “control.” How that word gets defined decides who gets in:

• a majority-owned subsidiary
• a 20% joint venture
• a sister company under the same parent
• a company the customer buys next year

A loose definition hands your product to entities you never priced.

Scope Is a Pricing Decision

Every added user base is revenue you either charge for or give away. Seats, usage caps, and per-entity fees only work if the contract says who counts. Leave it vague and the argument surfaces at renewal, when the customer already depends on you.

Big Vendors Fight Over This Too

In March 2025, VMware sued Siemens and several of its U.S. subsidiaries in federal court in Delaware. VMware alleged that a renewal request listed thousands of copies Siemens had never licensed. Its position was that the parent company was responsible for every download and deployment across the group. If a company that size can land in court over group-wide use, your contract needs clear lines.

Common Founder Mistakes

• Accepting “Affiliates” Without a Definition: Founders see the word and assume it means a couple of related entities. It rarely stays that small. Without a tight definition, the customer decides who counts.
• Forgetting About Acquisitions: Your customer buys a competitor, or gets acquired by a giant. You ask yourself:
• Does the new parent get access?
• Does the acquired company get access for free?
• Can the license transfer without your consent?

If the contract is silent, you may have licensed a company 10 times the size you priced.

• Giving Away Usage Rights You Cannot Track: Many founders grant broad affiliate rights with no reporting or audit right. You cannot enforce a limit you cannot see. You build in a way to confirm who is actually using the product.

10-Minute Self-Check

Before you sign an enterprise license with affiliate language, you work through this:

• Does your contract name exactly which legal entities can use your software?
• If “Affiliates” appears, is it defined with a clear ownership threshold?
• Does your pricing charge for added entities, seats, or usage?
• Do you know what happens to the license if your customer is acquired?
• Can the customer assign the license without your written consent?
• Do you have a reporting or audit right to confirm actual usage?

If you cannot answer yes to all of these, you are not ready to sign that license grant yet.

Bottom Line

The license grant is where your pricing either holds or quietly leaks. Every enterprise customer will push to widen it, and that is normal. The founders who protect their revenue decide in advance who counts, what it costs, and how they will know.

Want to Know Which Agreements My Product Needs Before My Next Enterprise Deal?

Join our upcoming Product Launch Master Class on September 29th, 2026. You will learn how to identify legal risks before launch, understand which agreements and policies your business may need, and prepare your company for customers, investors, and future growth.

Register now: https://primumlaw.com/product-launch-master-class/