An acquisition group needs a documented connection between the owner of an asset and the business using it. Software, trademarks, domains and customer data can sit in different entities and carry different restrictions. A holding-company chart does not explain those rights on its own.
Start with the operating plan: which businesses need access, who maintains the technology and what the group may sell separately later. Our acquisition company and deal-structuring service connects those questions with ownership, financing and the purchase documents.
Build a rights and consents inventory before choosing entities
For each asset, record the current owner, intended user, source document and any consent needed. Add an owner and deadline for missing evidence. Use the table below as a printable preparation worksheet; it is not a licence or an entity recommendation.
| Asset or function | Ownership evidence | Usage and change questions |
|---|---|---|
| Existing platform software | Identify the owner and contributors; check assignments and third-party components. | Name permitted group users, support obligations and rights after a business leaves. |
| Technology acquired with a target | Distinguish owned code from licensed products and customer-owned developments. | Check transfer/change-of-control conditions before extending use to affiliates. |
| Brand, marks and domains | Match registrations, contractual rights and domain control to the seller. | Document permitted use, quality standards, existing licences and transition at exit. |
| Customer and operational data | Identify collection terms, contractual restrictions and applicable privacy obligations. | Assign access, permitted purposes, security responsibilities, retention and exit handling. |
| Shared operating services | Identify the entity actually providing each service and the people performing it. | Record scope, cost methodology, approvals and the process for adding or removing a business. |
Mark unknowns explicitly. A repository, invoice or registration entry may answer part of the ownership question without establishing every right needed for the transaction. The IP assignment and chain-of-title guide covers the acquisition-side investigation in more detail.
Choose ownership around operations, financing and exit plans
A parent can own IP used by subsidiaries; an operating company can retain its own assets; or a separate entity can hold specified rights. Compare the alternatives against the actual contracts and plans. A separate entity adds administration, agreements and potential consent or financing questions. It is not a universal requirement.
Draw ownership and usage as different relationships. An equity line shows who owns a company. A licence explains who can use an asset and on what terms. A services agreement identifies work to be performed. Add loans, security interests and guarantees separately so the chart does not conceal obligations crossing entity boundaries.
Illustrative decision: a group expects to sell one operating business while retaining software used by several businesses. The question is what access the sold business needs after closing, who can grant it and how ongoing support will work. The answer belongs in the transaction and licence documents, not just in the ownership chart.
Review the structure with the tax adviser and financing parties before transferring assets or setting affiliate charges. No particular entity arrangement establishes a tax saving, a QSBS result or immunity from creditor claims by itself.
Separate acquired ownership from permission to use
For owned software and content, review the chain of assignments from founders, employees, contractors and other contributors. For licensed products, review the rights granted by the actual owner. A buyer needs to know which category each component belongs to before describing it as a platform asset.
Under 17 U.S.C. § 204, a transfer of copyright ownership generally requires a signed writing, subject to the statutory exception for transfers by operation of law. Match the agreement to the rights being transferred and the party authorized to sign.
Trademark transfers require their own analysis. 15 U.S.C. § 1060 connects assignment of covered marks with the associated goodwill and includes conditions and restrictions. The USPTO's ownership-transfer guidance explains recording changes and checking the resulting records. A database update should not be mistaken for resolving all underlying contractual rights.
For third-party contracts, distinguish assignment from change of control. An asset deal and an equity deal can trigger different provisions. Check affiliate-use restrictions, user counts, territories, sublicensing and limits on transferring customer contracts or data. An acquisition does not automatically expand a licence to the entire buyer group.
Translate the operating plan into licence terms
- Parties and assets: name the owner, licensee, covered software or marks and relevant asset schedules.
- Permitted use: identify covered businesses, users, territory, affiliates and any right to sublicense.
- Maintenance and development: allocate support, updates, improvements and ownership of new work.
- Charges and approvals: document the commercial basis and who approves affiliate transactions; assign tax and pricing analysis to the appropriate advisers.
- Brand controls: identify permitted presentation, quality standards, monitoring and correction procedures.
- Duration and change: address new acquisitions, transfers, change of control, termination and a business leaving the group.
Use the holding-company governance checklist to identify approvals and owner conflicts. Where a rollover seller owns equity in one business, related-party charges and licence termination rights can affect that investment. Review them alongside the seller rollover terms.
Document services and data responsibilities alongside the licence
Permission to use software does not itself commit an entity to provide payroll, IT support, billing or management services. Identify the actual provider, service scope, performance expectations, cost allocation and exit support. A single agreement can include multiple schedules where parties and obligations align; different providers or asset owners may require separate documents.
Customer information and operating data need a permissions analysis rather than a blanket assertion that the group owns all data. Review collection notices, customer contracts, confidentiality terms and applicable privacy duties. Specify access and permitted purposes, security responsibilities, incident cooperation, retention and export or deletion when a business leaves.
The multi-entity integration guide connects these arrangements with the wider operating model. For decisions and contracts that continue between acquisitions, discuss outside general counsel for acquisition companies.
Test the documents against a separate business sale
Before closing the first acquisition, test two future events: a subsidiary leaves while the group keeps the IP, and the group sells technology while retaining operating businesses. Identify what each continuing business would need to operate and who would remain responsible for support.
Check whether existing licences survive, can be assigned or require consent. If a replacement or transition licence is needed, address its scope, term, charges, support, data export and termination. For a brand separation, set out the agreed transition and removal or replacement obligations. Do not assume an incoming buyer accepts the group's current affiliate terms.
Review security documents too. A lender's rights or restrictions may affect a transfer or licence. Put unresolved approvals into the transaction checklist while there is time to obtain them, rather than treating them as routine paperwork after signing.
Carry the rights record into the next acquisition
The closing record should identify executed assignments, licences, consents, asset schedules, approval records and any open items. Assign responsibility for registrations, renewals, access changes and continuing reporting. Keep evidence of completion with the underlying agreement.
When another business joins, confirm that its proposed use fits existing rights and that the correct entities sign any joinders or new agreements. Reuse a documented process while rechecking the new target's facts. An existing group licence is useful only to the extent its scope actually covers the next business.
For an engagement assessment, start with a short description of the ownership structure, the first or next transaction, assets involved and deadline. Identify existing advisers and documents so the legal work can be scoped around the decisions still open.
Questions before the documents are signed
Does an acquisition platform need a separate IP holding company?
Not automatically. Compare ownership, investor expectations, financing, operating needs, administration and intended exits. A separate entity adds agreements and ongoing obligations. It does not itself transfer IP, guarantee protection from creditors or establish a tax benefit.
Does buying a company let every group company use its software?
Not necessarily. Check whether the target owns the software or uses it under a licence, which entities and users the licence covers, and any assignment or change-of-control conditions. Owning shares in a company is different from giving its affiliates contractual permission to use a third party’s technology.
Can one agreement cover both shared services and software licensing?
An agreement can address multiple functions if it identifies the right parties and rights clearly. Services, software use, brand use, data handling and ownership still need separate analysis. Where different entities own assets or provide services, separate agreements or schedules may better reflect the actual arrangement.
What happens to group licences when a subsidiary is sold?
That depends on the signed terms and transaction. Review whether the buyer needs an assignment, consent, replacement licence or transition arrangement. Address continued access, fees, brand removal, data export and exit assistance before closing so the sold business can operate on the agreed basis.
What should we send for an initial assessment?
Begin with the current ownership structure, the business being acquired or sold, the software and brands involved, existing licence or service arrangements and the next deadline. Explain which businesses need access and whether separate future sales are contemplated. A short summary is sufficient to start the scope discussion.
General information for planning a discussion with counsel. The appropriate structure and documents depend on the parties, governing law and transaction. An assessment request does not create an attorney-client relationship.