A quantum software company completes a promising customer project. Its team has found a better way to prepare a problem, adapt a computation to available hardware or integrate the result into an industrial workflow. The next customer has different requirements. A hardware partner changes its architecture. Management must decide which capabilities can travel with the company as it grows, and which rights make that possible.

This is the business situation behind the CEIPI examination case on quantum software IP strategy. The lecture explores how a company can protect reusable technical capabilities while collaborating with customers and hardware providers. It treats existing partnerships and technical expertise as the foundation for the next stage of development. The central question concerns control of future value across a changing network of relationships.

The decisions inside a protection strategy

A useful starting point is to separate the reusable technical mechanism from the circumstances of its first implementation. A customer may contribute confidential information, while the software company develops a method that could serve several applications. Hardware-specific tuning may complement a more portable architecture. These distinctions influence what can be patented, kept confidential, licensed or reused under agreed conditions.

The Layered IP Strategy framework helps organise these choices. Patent assessment should connect a defensible technical contribution with commercial relevance and realistic evidence of use. Confidential treatment requires practical measures to preserve secrecy. Software ownership and licence conditions govern distribution and access. Publication needs its own decision because it can support adoption while affecting future protection choices. Each mechanism has a purpose and a cost.

Established theory makes the choices easier to explain

Teece’s work on profiting from innovation explains why returns depend on protection and access to complementary assets. A software company may need hardware, integration skills and market access that other organisations control. The resource-based view adds a question about which capabilities remain valuable and difficult to imitate. Dynamic capabilities then explain the importance of adapting those capabilities as technical and commercial conditions change.

Together, these perspectives support concrete decisions. Management can identify the capability that creates customer value, assess the dependencies surrounding it and determine which rights preserve its usefulness. The IP in Business Ecosystems Deep Dive develops this analysis of partner roles and access. It helps turn a list of relationships into an assessment of where the company can act independently and where it needs continued cooperation.

Q-CTRL shows a software layer in use

Q-CTRL’s Fire Opal packages proprietary error suppression as a software service that works with quantum hardware. Its integration into IBM’s Qiskit Functions gives users an accessible route to these capabilities. IBM’s February 2026 update reports industrial research use by E.ON and Mitsubishi Chemical. This provides evidence of implementation and access to users beyond the software provider itself.

The transferable lesson concerns the delivery mechanism: customers can use a capability through an interface while the provider retains control over its implementation. The evidence establishes deployment, rather than product profitability or a general quantum advantage. Public sources also leave private contract terms and the contribution of individual patents unresolved. These boundaries matter when using the case to inform a younger company’s choices.

Arm shows the economics of repeated technology use

Arm provides a complementary example. Its established licensing business enables partners to integrate design IP into their products, with royalties connecting Arm’s earnings to subsequent shipments. Its FY2026 annual report records $2.613 billion in royalty revenue and $2.307 billion in licence and other revenue. The company describes a combination of patents, software rights, confidential knowledge and contractual protection.

For quantum software, the useful principle is a defined technology package that supports repeated use and a clear basis for payment. Arm’s scale and mature ecosystem limit direct comparison, and its revenues cannot be attributed to patents alone. Arm also announced expansion into production silicon in March 2026. The lecture therefore examines its demonstrated licensing mechanism without presenting its corporate model as static or universally transferable.

What the two cases mean for the next customer project

Q-CTRL illustrates a software provider’s position inside another organisation’s computing platform. Arm demonstrates substantial recurring revenue from technology that partners use in their products. Both invite a practical question: what must remain under the technology provider’s control so that another deployment strengthens its future business? The answer requires a clear view of the capability, the access arrangement and the benefit for the partner.

In a customer project, this means documenting existing assets and distinguishing generic improvements from customer-specific information. Ownership, permission to reuse results and access after the project ends deserve separate treatment. A right to reuse a module has little practical value if essential platform access disappears. Conversely, broad platform access cannot resolve restrictions on confidential customer information. These decisions need to work together.

Trade secret management provides methods for controlling valuable internal knowledge. IP roadmapping with the SAILS methodology connects future scenarios to portfolio priorities. Making Quantum IP Legible explains how these choices can become understandable to management, investors and partners. The lecture brings these resources together around a repeatable review of capabilities, dependencies and evidence.

Expert solutions add the case-specific judgement

Two model solutions are already published. Edd Cavanna’s approach develops strategic invention identification through dialogue between management, developers and patent advisers. Sebastian Greding’s approach connects technical contribution and business relevance with the ability to detect and demonstrate competitive use. They provide different entry points into the same broader management problem.

Further model solutions in draft form examine selective protection, technical translation layers, transferable project learning and future strategic options. Their additional value lies in explaining how these priorities interact when a company chooses a coherent architecture for the examination case. The lecture below provides the foundations for that discussion. Explore the slides to compare the industrial mechanisms, examine their limits and use the six linked readings to develop your own reasoned IP strategy.