How Quantum Software Companies Can Build an IP Strategy
A successful pilot can give a quantum software company something it can sell again. Whether it can do so depends on what the pilot produced, what the company can protect, and which rights it carries into the next project.
The practice question with Daniel Volz
The CEIPI IP Business Academy case presents a young company that develops specialist software to make existing quantum hardware useful for industrial customers. Its advantage comes from problem-specific algorithms, hardware adaptation, performance tuning and integration into customer workflows. It now wants to attract investors, expand its partnerships and enter new markets.
What should the company patent? Which know-how should it keep confidential? Which capabilities should it secure through software rights, access controls, customer agreements or its position in the ecosystem? Dr Daniel Volz, co-founder and former CEO of Kipu Quantum, brought the industry perspective. Decisions about publication, patenting and secrecy had come up in discussions with his management team and investors. Read the original practice question with Daniel Volz
The CEIPI lecture on quantum software IP strategy
The lecture builds on a practical question. Which capabilities will still create value when the company moves to another customer, application or hardware platform? It uses a layered IP strategy to examine patents, trade secrets, software rights, licensing and publication together. It also considers what access the company needs from hardware providers and other partners to put those capabilities to work.
Two examples make the distinction tangible. Q-CTRL’s Fire Opal shows how customers can access a proprietary capability through IBM’s Qiskit Functions. Arm illustrates how a clearly defined package of design IP can be licensed for repeated use in partners’ products. Together, the examples bring two choices into view for the case company. What can it offer repeatedly, and what must it control to keep that offer viable? Explore Quantum Software IP Strategy – Protecting Reusable Capabilities and Market Access
Four model solutions to the same case
Edd Cavanna on finding the invention early
Cavanna starts with how the company identifies inventions. Patent advisers first need to understand where the business is going and which capabilities give it an advantage. They can then work with the developers to trace a customer benefit back to the mechanism that produces it. That mechanism might be a new way of encoding an industrial problem or coordinating classical and quantum processing. A review before a paper, demo or partner discussion helps the team capture supporting evidence in time to make an informed protection decision.
Read Strategic Identification of Quantum Software Inventions
Sebastian Greding on designing for enforceability
Greding asks which of those inventions can support a commercially meaningful patent position. His approach tests the technical contribution, its relevance to the business and the evidence that could show a competitor is using it. Relevant evidence might appear in a documented interface, system behaviour or a measurable output. The assessment also considers how a competitor could design around the proposed claims. For an internal process that would be particularly difficult to observe, the team has a concrete reason to weigh confidential treatment before disclosing it in a filing. Read From Technical Effect to Assertable Quantum Software Positions
Sebastian Schmidt on protecting the translation layer
Schmidt looks at where the industrial problem becomes executable on real quantum hardware. A critical contribution may sit in the way the software prepares the problem, maps it to the constraints of a particular architecture or integrates the output into an industrial process. Mapping those transitions helps the company see where it has a capability that competitors would struggle to replace and where its own ability to deliver depends on a hardware partner. That analysis gives management a basis for prioritising technical control points.
Read Protecting the Translation Layer
Johannes Trapp on protecting what can be reused
Trapp starts with what the team learns in a customer project. A delivery may contain confidential customer data and project-specific work alongside a technical mechanism that could serve other customers. A transferability test helps distinguish the two. The practical consequence is contractual as well as technical. The company needs to identify its existing IP, define who can use project results and secure the permissions needed to reuse general improvements in future applications. Read Protect the Transferable Core
How the four approaches change the same decision
Suppose a pilot for an industrial customer produces a method that reduces circuit depth by adapting how a problem is encoded for a particular processor. The following comparison applies all four approaches to that hypothetical development.
| Approach | What the team investigates | Decision it informs |
| Cavanna | What mechanism reduces circuit depth, and when will the team disclose it? | Document the contribution and assess protection before exposing the implementation. |
| Greding | What would reveal that a competitor uses the mechanism, and what alternatives could they adopt? | Assess whether a patent would be commercially useful and practical to enforce. |
| Schmidt | Which part of the mapping depends on the processor, and which part can travel across hardware? | Identify the interface or technical layer where the company should seek control. |
| Trapp | Which improvement can the team reuse, and what do the customer and hardware agreements allow? | Define the reusable capability and secure the rights needed to deploy it again. |
The same pilot can therefore produce several IP decisions. The company might assess a patent for the reusable mapping mechanism, keep processor-specific tuning confidential and agree which improvements it may take into its next project. The patent decision depends on what the team can substantiate and what it could later observe. The growth decision also depends on the rights and platform access the company can se