Rigetti Computing vs. D-Wave Quantum: Navigating Volatile Revenue Trends

Rigetti reported just $1.9 million of Q4 2025 revenue versus D-Wave’s $2.8 million, while both companies remained loss-making with net losses of $18 million and about $42 million, respectively. D-Wave generated $24 million in revenue in 2025, up 179% year over year, but much of that growth came from a $15 million Q1 spike, underscoring highly volatile quarterly results at both firms. The article is largely a comparison of revenue trajectories and scaling potential rather than a material new catalyst.

Analysis

The market is still treating both names as narrative assets rather than businesses, but the revenue dispersion matters because in an early-stage platform race, customer concentration and timing of milestone recognition become the first real signals of product-market fit. QBTS has the stronger near-term credibility with a larger installed-access story, but its step-function revenue pattern suggests lumpy enterprise conversion rather than a repeatable booking engine. RGTIW looks weaker on momentum, and that increases the odds it becomes a financing-risk story if capital markets tighten before meaningful usage ramps.

The second-order effect is that the current winner in revenue may not be the eventual winner in compute economics. If either company can prove lower-cost, higher-fidelity workload execution, the larger cloud and enterprise integrators will likely capture the real monetization layer, leaving the pure plays as expensive R&D proxies. That means the strategic value could migrate to partners, infrastructure enablers, and adjacent software stacks long before either company reaches sustainable scale.

Near term, the key catalyst is not absolute revenue but sequential stability over the next 2-3 quarters: any re-acceleration can expand multiple compressions sharply because these stocks trade on optionality. Tail risk is that volatility persists while losses remain wide, forcing dilution or subscale commercialization just as investor patience fades. The contrarian miss is that a weak quarter may not be bearish if it reflects delayed deployments from larger customer contracts; however, without a visible backlog-to-revenue conversion pattern, the burden of proof stays on the companies, not the market.

For positioning, this is a better relative-value than directional growth call: the setup favors the company with the cleaner forward visibility, but only if you size for binary execution risk. If the next report shows another air pocket, the market is likely to punish the higher beta name first because the duration premium is already embedded.

Key Decisions for Investors

• Pair trade: long QBTS / short RGTIW for 1-2 quarters, betting that relative commercial traction and larger revenue base support better sentiment; stop if RGTIW shows a step-up in sequential bookings or QBTS reverts to subscale volatility.
• Avoid outright long exposure to either name ahead of the next two earnings prints unless using options; the equity is effectively a financing-volatility trade, not a fundamentals trade, and downside can reprice 20-40% on one weak quarter.
• If expressing bullish quantum exposure, use QBTS call spreads 3-6 months out rather than stock; the risk/reward improves if sequential revenue stabilizes, while premium paid is capped if the lumpy pattern persists.
• Watch RGTIW for dilution or capital raise language over the next 60-120 days; if financing risk rises, consider shorting rallies or buying puts into strength, since subscale revenue plus negative cash flow can force adverse equity issuance.
• On a longer horizon, look for second-order winners in infrastructure/cloud partners rather than the pure plays; any evidence of growing deployment activity should favor picks-and-shovels exposure over single-name quantum beta.