Qualify a quantum supplier against the specific product, delivery conditions and support obligations you intend to purchase. Research results, funding and institutional partnerships become useful procurement evidence when they can be connected to rights, repeatable performance and responsibilities that the supplier can document.
Purchase scope, rights and performance
The starting point is the proposed purchase. An experimental processor, a control module and a supported computing service impose different obligations. Describe the configuration, operating environment, interfaces, delivery location and support period before assessing the company. A supplier can be suitable for a jointly developed prototype while remaining unproven for repeat deliveries. Record that distinction in the procurement decision. Supplier qualification for a defined purchase is distinct from formal certification; the evidence required should match the proposed scale of delivery.
Establish which entity can supply and support the technology. For a university spin-out, a patent list is only the beginning. WIPO’s guidance on technology-transfer agreements explains that licence rights can be restricted by territory, field of use and permitted activity, and that licensing differs from ownership. Ask for evidence that the relevant rights cover your intended deployment, manufacturing arrangements and maintenance. Identify restrictions that could affect an acquisition of the supplier or the appointment of a replacement service provider. Where confidential contracts cannot be disclosed, request a suitably scoped confirmation from the parties or their advisers.
Connect performance claims to the product that will actually be delivered. A useful test record identifies the hardware or simulator, software version, operating conditions, workload and treatment of unsuccessful runs. The distinction matters even in authoritative research: NIST’s BenchQC publication explicitly describes simulator-based calculations and the parameters varied. That evidence has a defined scope. A buyer should similarly establish whether a vendor result demonstrates an algorithm under simulated conditions, a laboratory device or the contracted configuration. Agree how the result will be reproduced during acceptance, including the buyer’s access to the underlying records.
Repeatability, delivery and manufacturing access
Ask how performance changes across units and over time. A single successful demonstration leaves open the frequency of recalibration, the variation between production batches and the effort required to restore operation. Request the observations available for the relevant product, with sample sizes and exclusions stated. If only one unit exists, record that limitation and structure the next commitment around generating the missing evidence. Do not convert an absence of data into either a zero failure rate or a presumption that the technology cannot work. It determines how much deployment risk remains unresolved.
Verify delivery claims from the customer side where possible. EuroHPC’s October 2024 announcement of the Euro-Q-Exa procurement contract identifies IQM as the selected vendor, the intended host and the integration requirement. It establishes a signed procurement relationship at that date. It does not, by itself, prove later installation, acceptance or sustained availability. For a reference deployment, seek those subsequent records separately and determine whether its configuration and operating demands are comparable to yours. Customer identity alone cannot establish equivalence.
Map the dependencies required to fulfil the order. Request the manufacturing and test locations, access arrangements for externally owned facilities, critical components and responsibility for integration. The European Commission’s Quantum Europe Strategy treats production infrastructure and supply-chain development as distinct industrial priorities. For an individual purchase, the practical question is whether the supplier has the access necessary for your delivery schedule. An announced partnership or planned facility expansion should be distinguished from a confirmed allocation. Where alternatives are proposed, ask what requalification and customer approval they would require.
Support, funding and procurement conditions
Define support as an operating commitment. Establish who will respond to a fault, where spare parts are held, how remote access is authorised and what happens when a software dependency changes. Record the boundary between the supplier, system integrator and host organisation. A repair promise has limited practical value if the necessary expertise resides with one founder who is not contractually available. Request an escalation route and a continuity arrangement proportionate to the installation’s importance. Include the buyer’s own staffing, facilities and maintenance responsibilities in the same discussion.
Examine financing in relation to contractual work. The amount raised does not establish that resources are available for your delivery and support period. Ask how production, installation and warranty obligations are funded and which milestones precede payment. Consider the consequence of a delay for both parties: additional engineering effort, facilities costs and a later acceptance payment may occur together. Financial information that remains confidential can be addressed through agreed evidence and contract terms rather than an unsupported public estimate of the company’s survival horizon.
The resulting decision should identify what can be purchased now, what still requires demonstration and which conditions would justify a larger commitment. A bounded pilot may be appropriate when the central uncertainty is measurable and the next decision is explicit. A larger deployment needs evidence covering its actual scale and support requirements. Preserve the dated documents behind the decision and reopen it after material changes in product configuration, ownership, manufacturing access or delivery terms. This produces a qualification record that can be updated as the supplier’s capabilities develop.
Sources
WIPO — Technology Transfer Agreements
NIST — BenchQC: A Benchmarking Toolkit for Quantum Computation
EuroHPC JU — Euro-Q-Exa procurement contract, 15 October 2024
Email newsletter
Quantum Finance Monitor
Quantum Finance Monitor follows the contracts, manufacturing dependencies and financing that determine whether an emerging quantum supplier can sustain delivery.
