Evaluate quantum-computing companies by checking whether dated technical results support their claims, whether customers pay and return, and whether the company can fund its next milestones. A qubit count, a large market estimate, or a headline revenue figure cannot answer those questions alone. The framework below helps compare evidence without turning it into a stock pick.
Start with the business the company actually sells
Quantum-computing companies may sell hardware, cloud access, software, services, or a combination. Identify the computing approach and the problem classes the product targets, then ask whether the claimed market matches the deliverable, buyer, and use case. Different approaches can have different strengths; comparing companies by one hardware statistic can conceal more than it reveals.
Build a basic profile for each company before judging its claims:
- Product: hardware, cloud access, software, services, or a mix.
- Approach and target: the computing architecture and problem types it says it can address.
- Buyer and delivery: who pays, how the system is accessed or delivered, and what the customer receives.
- Commercial stage: research engagement, pilot, paid proof-of-concept, production use, repeat purchase, or expansion.
Test technical claims against dated evidence
For every major technical claim or roadmap milestone, record when it was made, what was actually demonstrated, which metric was used, and whether a relevant classical comparison exists. Distinguish a published target from a result already achieved. Look for independent review where available, and check whether earlier milestones arrived on schedule.
#1 Best Overall
Qubit count is not a standalone measure of commercial capability. Rigetti’s 2025 annual report lists performance, scale, speed, accessibility, software, workflow compatibility, price, finances, and talent among competitive factors. D-Wave’s 2024 annual report describes an evaluation framework that includes performance relative to classical computing, system reliability and availability, and commercial customer success. These are company disclosures, not a universal investment standard.
Match the metric to the architecture and intended task. Depending on the claim, useful evidence may include performance on a relevant problem, reliability, availability or uptime, and appropriate error or fidelity measures. Also assess system access, software tools, workflow compatibility, and whether the company’s result is useful under realistic conditions rather than only in a narrow demonstration.
Roadmaps remain forecasts. In its June 2026 Q2 results release, D-Wave set a company target for a 100,000-qubit annealing system by 2031 and described gate-model milestones through 2032. Treat those dates as management targets, not achieved capabilities; compare them with later results and the company’s record against previous dated milestones.
Look for customers, not just demonstrations
A technical demonstration shows that a company reports an activity or result; it does not by itself establish durable demand. Trace each customer example through the stages that matter commercially:
Recommended Free Tools
- Research engagement or pilot: Is there a named customer, a defined problem, and a concrete scope?
- Paid proof-of-concept: Is payment disclosed, or is the work described only as a collaboration or evaluation?
- Production use: Is the system being used in an operating workflow, rather than tested in a limited trial?
- Repeat business and expansion: Has the customer renewed, increased use, or bought additional services or systems?
Read customer announcements as evidence of what the company says has happened, not independent confirmation that adoption is broad or persistent. Where disclosures allow, examine revenue by source and customer, contract duration, renewals, customer concentration, cancellations, and the time between pilot and production. A few named projects can be meaningful, but they do not establish a diversified customer base unless the filings or results support that conclusion.
Separate bookings from recognized revenue
Bookings and revenue are not interchangeable. D-Wave defines “Bookings” as customer orders received that are expected to generate net revenues in the future. An order may not become recognized revenue in the same reporting period, and bookings should not be described as revenue already earned.
D-Wave’s release reporting fiscal year 2025 showed the distinction: it reported $24.6 million in revenue and $18.7 million in bookings. The company said bookings were down 22% from FY2024, a comparison affected by FY2024’s eight-figure first system sale. When comparing periods, check the company’s definitions and whether an unusually large system sale or its timing distorts the trend.
Review backlog or bookings definitions, cancellations, delivery schedules, and revenue sources alongside recognized revenue. A rising bookings figure can indicate future orders under the company’s definition, but it does not prove those orders will be delivered, recognized, renewed, or profitable.
Assess runway, losses, and financing risk
Revenue growth alone does not establish financial sustainability. Read the latest audited financial statements and risk factors in regulatory filings. Assess cash and short-term investments against operating cash use, capital expenditures, debt, and commitments required for manufacturing, system delivery, or acquisitions. Cash on hand is not a runway estimate unless considered alongside cash burn and financing assumptions.
Examine gross margins and their drivers, operating expenses, GAAP net loss, any adjusted loss measure, stock-based compensation, warrant effects, customer concentration, and likely financing needs. Keep GAAP and non-GAAP figures distinct and review any reconciliation rather than relying on a company’s preferred headline measure.
D-Wave reported a FY2025 GAAP net loss of $355.1 million. Its 2026 release reporting that year said $270.5 million in non-cash, non-operating warrant remeasurement charges and losses from warrant exercises affected the result. That context matters when interpreting the headline loss, but it does not make operating cash needs or future financing risk disappear.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Compare execution and competitive position consistently
Use the same comparison criteria for every company rather than letting each company’s preferred metric set the terms. Rigetti’s 2025 annual report describes a broad range of competitive factors, while D-Wave’s 2024 annual report includes technical performance, reliability, availability, and customer success in its framework. Neither is a sector-wide rule; the point is to assess the business across multiple dimensions.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
| Dimension | What to record |
|---|---|
| Approach and target | Architecture, intended problem classes, buyer, and product actually offered. |
| Technical evidence | Dated results, metric, relevant classical baseline, validation, reliability, and availability. |
| Customer evidence | Named use cases, paid deployments, repeat business, expansion, and concentration. |
| Commercial model | Pricing or delivery model, revenue sources, bookings definition, and timing of system sales. |
| Integration | Software tools, access, and compatibility with customer workflows and classical systems. |
| Financial capacity | Cash and investments, cash use, margins, expenses, debt, dilution, and milestone funding needs. |
| Execution | Management’s record against dated milestones and the status of current targets. |
For market context, McKinsey & Company’s 2026 Quantum Technology Monitor estimated worldwide quantum-computing-company revenue at more than $1 billion in 2025 and as much as $4.4 billion by 2028. It also estimated potential economic value of up to $2.7 trillion by 2035. These are estimates, not audited industry totals, guaranteed company revenues, or investor returns; a broad estimate of economic value does not tell you which company will capture it.
Turn the evidence into a decision
Before comparing securities, write down what evidence would change your view. For example, specify which technical milestone must be demonstrated, what kind of customer conversion would count as validation, and what level of financing or dilution risk you consider acceptable. Then revisit the same criteria when new filings and results arrive.
- Technology: Is there a dated, relevant result with a meaningful baseline, rather than only a target or qubit count?
- Demand: Do disclosed customer relationships progress to paid, repeat, or expanding use?
- Economics: Can the company fund execution, and do its revenue and margin disclosures support a plausible path beyond ongoing losses?
- Execution: Does the record against earlier milestones strengthen or weaken confidence in current targets?
- Risk: Are concentration, financing, dilution, and delivery risks acceptable given the evidence?
If key answers depend mainly on company forecasts or promotional announcements, treat them as unresolved rather than filling the gaps with market-size estimates. This is a general diligence framework, not a company valuation or personalized investment recommendation; financial statements, roadmaps, and industry estimates can change.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
