# Shared Software > Shared Software means software, firmware, and middleware in object and source code forms, crucial for running a business. **Term:** Shared Software **Last updated:** 2026-07-29 ## Definition ## What Shared Software Means in a Contract Shared Software is a defined term used mainly in transactional agreements, such as carve-outs, spin-offs, and business separations, to identify software that both the seller and buyer, or a departing entity and the remaining group, continue to need after a deal completes. It typically covers applications, firmware embedded in hardware, and middleware that connects systems, whether delivered in object code or source code form. The concept exists because businesses rarely operate on isolated software stacks. Enterprise resource planning tools, communication platforms, and internal databases often support several business units or legal entities at once. When one part of the business is sold or separated, the parties must agree on how Shared Software will continue to function, who owns or licenses it, and for how long each side can keep using it. In practice, the term signals that the drafting parties anticipate a transition period during which shared reliance on the same code base must be managed contractually rather than assumed informally. ## How Shared Software Is Defined or Measured Most definitions of Shared Software focus on function rather than form. The test is usually whether the software is crucial for running a business, meaning that without continued access, day to day operations of one or both parties would be disrupted. This functional framing avoids the need to list every application by name, though schedules often do so for clarity. Definitions commonly specify the technical forms covered, distinguishing object code, which is compiled and generally unreadable without reverse engineering, from source code, which is human readable and editable. Firmware and middleware are frequently included because they sit between hardware and application layers and are easy to overlook if a definition only references end user programs. - Whether the software is owned outright, licensed from a third party, or developed in house - Whether use by multiple entities is already permitted under an existing license - Whether the software must be duplicated, migrated, or accessed under a transitional arrangement These distinctions matter because a license permitting one entity to use software does not automatically extend that right to an affiliate or successor once ownership structures change. ## Where Shared Software Appears in Agreements Shared Software provisions appear most often in business separation agreements, asset purchase agreements, and transitional services agreements connected to a broader transaction, including a [Business Acquisition Agreement](https://www.genieai.co/en-us/template-type/business-acquisition-agreement) or a [Business Purchase Agreement](https://www.genieai.co/en-us/template-type/business-purchase-agreement). These documents typically include a schedule listing the identified Shared Software, along with terms governing continued access, cost sharing, and eventual separation of systems. The concept also surfaces in technology focused agreements. A [Software Development Agreement](https://www.genieai.co/en-us/template-type/software-development-agreement) may reference Shared Software where custom code will be used across multiple business units, and a [Software Maintenance Agreement](https://www.genieai.co/en-us/template-type/software-maintenance-agreement) may need to address ongoing support obligations for tools jointly relied upon by separating parties. Industries with complex, interconnected technology estates, such as technology, finance, and manufacturing, tend to encounter Shared Software issues more frequently, since these sectors often run integrated systems across several divisions or subsidiaries before any separation occurs. ## Why the Exact Wording Matters Ambiguity in a Shared Software clause can leave one party without a system it depends on, or expose both parties to a dispute over licensing rights they assumed were included. If the definition is too narrow, essential firmware or middleware might be excluded, creating an operational gap after closing. If it is too broad, a party may be forced to share code that was never intended to be jointly used. Precise wording also affects cost allocation. Contracts should state clearly who pays for continued licensing fees, upgrades, or migration costs tied to Shared Software, and for how long the arrangement lasts. Vague transitional language often leads to disputes when one party believes support should have ended and the other still expects access. Because source code carries different risks than object code, particularly around confidentiality and modification rights, the exact form of Shared Software referenced in the contract shapes what protections, such as escrow or restricted access, are appropriate. ## Drafting Considerations Drafters should attach a specific schedule identifying each item of Shared Software, rather than relying solely on a general functional definition, to reduce later disagreement about scope. The schedule should note whether each item is licensed from a third party, developed internally, or embedded in hardware as firmware. Where source code access is contemplated, parties sometimes look to protections similar to those discussed in a [source code license agreement](https://www.genieai.co/blog/drafting-a-source-code-license-agreement), ensuring that any shared access to source code is limited, monitored, and consistent with confidentiality obligations under the law governing the contract. Finally, the clause should address the end state, specifying whether Shared Software will eventually be separated into distinct instances, migrated to new platforms, or continued indefinitely under a joint licensing arrangement, so that neither party is left assuming an open ended commitment that was never intended. ## Context ### Relevant circumstances - Acquisition of a business where the shared software is crucial for operations. - Licensing of software to another party for a specified period. ### Relevant sectors - Technology - Banking and Financial Services - Telecommunication ## Relevant contract types - [Business Acquisition Agreement](https://www.genieai.co/en-us/template-type/business-acquisition-agreement) - [Business Purchase Agreement](https://www.genieai.co/en-us/template-type/business-purchase-agreement) - [Software Development Agreement](https://www.genieai.co/en-us/template-type/software-development-agreement) --- This is the Markdown representation of [https://www.genieai.co/en-us/define/shared-software](https://www.genieai.co/en-us/define/shared-software), provided for AI agents and crawlers. The HTML page is canonical. See [/llms.txt](https://www.genieai.co/llms.txt) for the full content map.