Strategic Identification of Quantum Software Inventions with Edd Cavanna
1. Background and Central IP Question
The Kipu Quantum Decision Case concerns a young technology company that makes existing quantum hardware useful for industrial applications through specialised software. Its commercial advantage combines problem-specific algorithms, hardware-adapted implementation, hybrid workflows, performance tuning and knowledge gained through industrial customer projects.
Value emerges from the interaction of these elements. An algorithm becomes commercially useful when it runs reliably on constrained hardware, integrates with classical processes and delivers a relevant result for the customer. The technical contribution that enables this performance may be located at several points within the system.
Growth brings recurring disclosure situations: research publications, customer discussions, investor reviews, interface documentation and new partnerships. Each creates a reason to identify potentially protectable contributions before technical information becomes public.
The original Decision Case asks which elements should be patented, kept confidential or secured through contracts, software access controls and ecosystem relationships.
The proposed solution developed with Edd Cavanna focuses on a specific part of this challenge:
How can Kipu identify strategically relevant inventions early and translate them into patent positions that support its commercial objectives?
2. Proposed Solution through Strategic Identification of Inventions
The central premise is that a quantum software portfolio creates commercial value when it captures the technical contributions that make the company’s offering useful, scalable and difficult to substitute.
For Kipu, such a contribution may emerge in problem representation, resource allocation, circuit simplification, hardware optimisation, error handling or the coordination of classical and quantum processing. Identifying it requires a shared understanding of the technology and the business.
Edd’s approach therefore begins with the relationship between the company and its patent advisers. Management should share the strategic overview before the attorneys meet inventors and development teams. The advisers need to understand which markets Kipu intends to serve, where its differentiation lies and why protection is being sought.
This context guides invention identification. It helps the team assess whether a potentially patentable development supports a product, a scaling step, a licensing opportunity or a future negotiating position. Close integration with the development process also makes it easier to capture relevant details while they are still available.
An Enabling Contribution Map can organise that dialogue around five dimensions:
| Dimension | Central question |
| Commercial function | Which capability of the customer offering does the contribution enable or improve? |
| Technical effect chain | How do processing steps, hardware interactions and outputs produce the relevant effect? |
| Competitive dependency | Which function would competitors need to adopt or replace to deliver comparable value? |
| Claim architecture | Which claim categories, implementation variants and fallback positions capture the contribution? |
| Evidence and timing | What supports the application, and which disclosure deadline determines the next action? |
The map connects invention identification with a documented commercial purpose. It also provides a basis for deciding which information should enter a patent application and which should remain confidential.
3. Finding the Contribution within the Quantum Software Architecture
Different types of innovation require different questions. The review should follow the technical contribution through the system and establish why it matters to the intended offering.
Hardware-adapted implementation. Where an invention is tailored to particular hardware, the adaptation itself may support inventiveness. Circuit compilation, qubit encodings, gate selection and implementation, error handling and calibration deserve detailed examination. The team should also assess whether the underlying mechanism works beyond the first implementation, so that the proposed scope reflects supported alternatives.
Problem-specific algorithms. The starting point is the industrial problem and the technical processing required to solve it. Kipu should document how data and model parameters are prepared, how the task is transformed for quantum execution and which effects follow. Greater efficiency, improved noise resilience, shorter runtime or reduced gate depth can indicate a contribution worth investigating. The application must explain how the mathematical operations contribute to a technical solution.
Hybrid workflows. Classical computation, quantum processing, data preparation and result validation interact through orchestration rules and handover points. A contribution may lie in when quantum processing is used, how resources are allocated or how results are reintegrated into an industrial process. These mechanisms may support capabilities that can be reused across applications.
Performance tuning and customer knowledge. The review should distinguish a generalisable technical mechanism from implementation parameters and accumulated experience. A mechanism may justify a patent assessment, while tuning values, benchmarking routines and deployment knowledge may call for confidential treatment. Customer contracts should clarify ownership and the right to reuse generic developments.
For each area, the practical question is:
Which technical improvement enables the customer benefit, and how widely can that improvement be applied?
4. A Quantum Invention Mining Gate before Disclosure
A Quantum Invention Mining Gate turns these questions into a repeatable decision. It should take place before planned publications, external demonstrations, customer trials, financing disclosures and joint development projects. Major roadmap changes can trigger an additional review.
Management, R&D, Business Development and the patent attorney examine five connected issues.
Gate 1 Commercial relevance. Which customer benefit, scaling step or negotiation advantage depends on the improvement? The team records the relevant offering, customers, hardware environments and intended use.
Gate 2 Technical causality. Which technical measure produces which effect? Evidence may concern runtime, accuracy, error rate, resource use, stability, energy consumption or integration effort. The technical description should explain the causal relationship and include relevant implementation details.
Gate 3 Competitive dependency. Which function would a competitor need to use or replace? The assessment considers alternatives, possible design-arounds and the visibility of future use. Patent advisers help identify the broader inventive concept and supported variants that could cover foreseeable workarounds.
Gate 4 Claim readiness. Which claim categories and fallback positions are appropriate? Methods, computer systems, computer-readable media, hybrid architectures and hardware-related embodiments may serve different purposes. The drafting strategy should take the intended jurisdictions into account from the outset.
Gate 5 Disclosure readiness. What will become visible, to whom and when? The team sets the filing deadline, assigns responsibility, identifies missing evidence and specifies what must remain confidential.
A contribution is ready for a filing decision when these issues have been sufficiently documented. Outstanding questions receive an owner and a deadline. The gate produces a clear decision on filing, further investigation, confidential treatment or release.
👉 Quantum Technology and the New Complexity of IP Decisions
5. Embedding Invention Identification in Daily Work
Kipu should organise invention identification as a short, regular dialogue. A monthly review can capture new algorithms, implementations, benchmarks, customer requirements and upcoming disclosures. An invention disclosure form helps developers record ideas early. Patent advisers can help design the form and explain what information is needed and why.
The responsibilities are complementary. R&D provides technical descriptions, alternatives and measurements. Product Management and Business Development explain customer value, reusability and commercial objectives. The IP team and external advisers assess prior art, develop the claim architecture and coordinate the protection decision. Executive management sets priorities and allocates resources.
A time-sensitive contribution may require an early priority filing. That application should contain adequate support for the protection sought. Further developments, data and variants can inform subsequent filings, with their timing and priority implications assessed by counsel. Edd emphasises the importance of adapting the attorney workflow to tight disclosure deadlines.
Before international filing decisions, Kipu should review target markets, sales models, likely acts of use and jurisdiction-specific requirements. Each patent family should have a defined role in the commercial roadmap.
A quarterly contribution review then connects new technical evidence with changes in products, hardware environments, partnerships and markets. It updates claims strategy, confidential assets, FTO findings and disclosure plans. Close involvement of the attorney team helps make this a continuous process.
Management receives a concise profile for each important patent family: the customer benefit, technical contribution, competitive relevance, intended markets and complementary protection measures.
6. Using FTO to Inform Technical and Commercial Choices
Freedom to Operate develops alongside the technical solution. Early landscape work identifies relevant actors and protection fields, including compilers, error correction, control systems and interfaces. As the product becomes more concrete, the analysis focuses on particular functions, countries and acts of use.
Edd highlights a practical weakness in this process: an initial finding of patents in an overlapping area can lead to major changes in technical or commercial strategy before the actual implications have been examined closely enough.
A detailed review can establish whether a smaller technical adjustment is sufficient, whether a different implementation remains available or whether a licence should be considered. Close third-party IP may also reveal a potential collaboration partner. The findings can therefore inform architecture, partnerships and commercialisation.
Joint projects require clear allocation of background IP, project results, software, data, know-how and improvement rights. Before work begins, the parties should agree which contributions may be reused, who controls filing decisions and which access rights survive the project.
For Kipu, these decisions affect its ability to build reusable capabilities across customer engagements and hardware relationships.
7. Coordinating Protection and Licensing across the Portfolio
The identified contribution should sit within a coordinated protection architecture. Different assets require different forms of protection and control.
| Asset or contribution | Protection and control approach |
| Reusable technical mechanism | Assess patent protection for the mechanism, system interactions and supported variants |
| Parameters and tuning routines | Confidential documentation, access controls and trade secret management |
| Software implementation | Copyright, licence terms and control of source code and distribution |
| Customer and joint development results | Ownership, access, improvement and reuse provisions in contracts |
| Deployment and benchmarking knowledge | Documented know-how, confidentiality and clearly defined licence packages |
Coordination begins during invention identification. The team must decide which information is needed to support the patent application and which complementary knowledge can remain confidential. Confidential treatment must remain consistent with adequate disclosure of the invention.
Edd also emphasises the commercial relevance of identifying IP beyond patentable subject matter. Software, know-how and other controlled assets may form part of a licensing package, provided they are clearly identified and the company has the relevant rights.
For Kipu, a patent family can describe a transferable technical capability, while software modules and documented know-how support its implementation. The resulting package gives partners a clearer understanding of what they can access and how it may be used.
👉 What Can Be Protected by IP Strategies
Conclusion
The proposed strategy is Strategic Identification of Inventions. Kipu should connect early invention identification with its business objectives, technical evidence and disclosure calendar. The Enabling Contribution Map structures the discussion, while the Quantum Invention Mining Gate turns it into a documented protection decision.
The approach depends on close collaboration between management, developers and patent advisers. It combines technical depth with an understanding of customer value, supported claim scope, international requirements and the complementary role of confidential knowledge, software and contracts.
Regular reviews keep the portfolio connected to changes in hardware, markets and partnerships. The central management question is:
Which technical contribution should Kipu capture today to support the commercial position it wants to build tomorrow?
Expert Profile Edd Cavanna
Edd Cavanna is a Partner and UK and European Patent Attorney at Mathys & Squire LLP. His practice includes drafting and prosecuting technically complex patent applications and managing international portfolios, particularly in quantum computing, software and related mathematical inventions. He holds an MPhys from the University of Leeds, where his final-year project concerned quantum information, and a PhD from the University of Cambridge on the thermal properties of cuprate superconductors.
Edd Cavanna at Mathys & Squire
His contributions to the CEIPI IP Business Academy platform make the connection between this technical background and his advisory approach visible. The announcement of his joint IP Business Talk with Daniel Speed introduced the challenge of locating an invention across hardware, software, protocols and enabling technologies. It placed particular emphasis on translating complex quantum developments into a coherent protection architecture.
The detailed dIPlex report on the talk of 15 July 2026 documents Edd’s perspective on invention mining and the need for patent advisers to understand the company’s commercial purpose. It also records his discussion of FTO, changing business plans and collaboration rights. These contributions provide a direct professional context for the approach proposed here: identifying the relevant technical contribution through dialogue and keeping protection connected to the company’s intended market position.
IP Business Talk Report: Protecting Quantum Innovation Across the Stack
The platform’s comparative article “Two Ways to Make Quantum IP Legible” provides further context at firm level. It describes Mathys & Squire’s emphasis on protection architecture, technical classification and differences between patent systems. This perspective helps explain the international drafting dimension of Edd’s proposed solution.
Two Ways to Make Quantum IP Legible
Beyond the platform, Edd and Daniel Speed’s publication “IP in the quantum industry: a global perspective on patent procurement” examines how jurisdictional differences affect patent strategy. Mathys & Squire’s follow-up article “Closing the Research-to-Patent Gap in Quantum Innovation” also develops themes from their CEIPI conversation.
IP in the Quantum Industry: A Global Perspective on Patent Procurement
