Evaluate a quantum-computing company by checking whether its technology works on a relevant task, whether customers pay and return, and whether its finances can support the next milestones. Qubit count alone is not a measure of commercial readiness. Use dated evidence from filings and results, distinguish company targets from achieved results, and treat market forecasts as estimates—not evidence that a particular stock will succeed.
Start with what the company sells
Classify the business before comparing it with peers: it may sell quantum hardware, cloud access to systems, software, services, or a mix. Identify the computing approach and the problem classes it targets. The addressable market should fit the product the company can actually deliver, the buyer, and the use case—not quantum computing in the abstract.
As an Amazon Associate I earn from qualifying purchases.
Different approaches can suit different problems. A single hardware statistic cannot rank companies across architectures. Rigetti’s 2025 annual report names performance, scale, speed, accessibility, software, workflow compatibility, price, finances, and talent among competitive factors. D-Wave’s 2024 annual report likewise describes evaluating systems against classical computing, reliability and availability, and commercial customer success. These are company-specific frameworks, not universal standards. Rigetti’s 2025 annual report; D-Wave’s 2024 annual report.
Free tools Windows power users keep installed
One-click scans. No signup required.
Test technical claims against useful evidence
For each claimed achievement, record when it was demonstrated, what task was run, which metric was measured, and whether a relevant classical baseline was used. Ask whether the result was independently reviewed and whether customers or researchers can access the system. A larger qubit count may matter to a roadmap, but it does not by itself establish useful performance, reliability, or an advantage over classical methods.
#1 Best Overall
- Performance: Is the metric relevant to the target problem, and is there a meaningful comparison with classical computing?
- Reliability and availability: Can users access the system consistently, and are uptime or availability results reported?
- Architecture-appropriate quality: Look for error, fidelity, or other measures suited to the company’s approach rather than comparing unlike metrics.
- Usability: Check software tools, access, pricing, and compatibility with classical workflows.
- Execution: Compare each dated roadmap milestone with what was actually delivered by that date.
A roadmap is a forecast, not a demonstrated capability. For example, D-Wave’s June 2026 update includes a company target for a 100,000-qubit annealing system by 2031 and gate-model milestones through 2032. Evaluate these as future targets and look for subsequent evidence of progress; do not treat them as delivered systems. D-Wave’s Q2 2026 results release.
Separate customer interest from adoption
Customer evidence has stages. A research engagement or pilot is not the same as a paid proof of concept; a paid trial is not necessarily production use; and one deployment does not prove repeat demand. Trace whether named use cases move into production, whether customers renew or expand, and whether revenue depends heavily on a small number of buyers or one-off system sales. Company announcements can establish that a company reports activity, but they are not independent proof of durable commercial demand.
Read revenue by source and, where disclosed, by customer. Examine contract duration, renewals, customer concentration, cancellations, backlog, and the definitions used for operating metrics. Timing of large system sales can make year-to-year comparisons look unusually strong or weak.
Bookings are not revenue
D-Wave defines bookings as customer orders received that it expects to generate net revenue in the future. For FY2025, the company reported $18.7 million in bookings and $24.6 million in recognized revenue. Bookings were down 22% from FY2024, which included an eight-figure first system sale. These figures describe different things: bookings are an order-based operating metric, while revenue is recognized under accounting rules. D-Wave’s FY2025 results release.
Assess runway, losses, and dilution risk
Revenue growth does not establish that a company can fund itself. Read the latest audited statements and risk factors in regulatory filings. Assess cash and short-term investments alongside operating cash use, capital expenditures, debt, and commitments for manufacturing, acquisitions, or other execution needs. Cash alone does not reveal runway unless it is considered against burn and financing assumptions.
- Track gross margin and what drives it, including the mix of services, access, and system sales.
- Review operating expenses, GAAP net loss, and any adjusted loss measure separately; read the reconciliation rather than treating non-GAAP results as interchangeable with GAAP.
- Check stock-based compensation, warrants, potential share issuance, debt terms, and the possibility that new financing could dilute existing shareholders.
- Consider whether the company has the resources to meet its manufacturing, hiring, and roadmap commitments.
D-Wave reported a FY2025 GAAP net loss of $355.1 million. Its results release says $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 remove the need to examine cash use, recurring operating costs, and future financing needs. D-Wave’s FY2025 results release.
Compare companies on the same dimensions
A consistent comparison helps prevent a headline metric or announcement from dominating the decision. Fill in each row from current filings and dated company disclosures; use “not stated” when a material figure is not disclosed.
Do these 3 things before closing this tab:
1Clear out junk files and repair common Windows errors2Scan for outdated or missing drivers - takes under a minute3Repair Windows errors before they cause bigger problems| Dimension | What to record |
|---|---|
| Approach and target | Computing approach, products sold, and the problem classes and buyers targeted. |
| Technical evidence | Dated results, task and metric, classical baseline, validation, and architecture-appropriate quality measures. |
| Availability and usability | System access, reliability, uptime, software, workflow compatibility, pricing, and delivery model. |
| Customer validation | Paid pilots, production deployments, repeat business, renewals, expansion, and customer concentration. |
| Commercial measures | Recognized revenue, bookings or backlog definitions, contract terms, cancellations, and one-time sale effects. |
| Financial capacity | Cash and investments, cash use, margins, losses, debt, commitments, and prospective dilution. |
| Execution | Management’s record against dated milestones and the resources needed to meet future targets. |
Put market forecasts in perspective
Market-size projections describe possible industry growth, not the likely revenue of an individual company or the return on its shares. McKinsey & Company’s 2026 Quantum Technology Monitor estimates worldwide quantum-computing-company revenue at more than $1 billion in 2025 and as much as $4.4 billion by 2028. It also estimates potential economic value of up to $2.7 trillion by 2035. These are McKinsey estimates, not audited industry totals, company forecasts, or guaranteed investor returns. McKinsey’s 2026 Quantum Technology Monitor.
Use a diligence checklist before making a decision
- Read the latest filings: Identify what the company sells, its risks, cash position, operating costs, and share-based compensation or warrant exposure.
- Build a dated milestone record: Separate demonstrated results from roadmap targets and note whether previous targets were achieved.
- Verify commercial progression: Distinguish trials from paid deployments and recurring production use; assess customer concentration and contract quality.
- Reconcile financial metrics: Keep recognized revenue separate from bookings, and GAAP results separate from adjusted measures.
- Compare on matched evidence: Use the same technical, commercial, and financial questions for every company rather than comparing qubit counts alone.
- Recheck volatile disclosures: Financial statements, roadmaps, and market estimates change. Use current filings and results for any investment decision.
This framework supports diligence, not a valuation or stock recommendation. No single metric or forecast can establish that a quantum-computing company is a sound investment.
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.
