Quantum computing has a qualification problem. For years, the industry has identified promising areas for quantum computing that we hear on repeat. The usual, but non-exhaustive, suspects are drug discovery, materials science, financial modeling, logistics, optimization, and machine learning. These use cases help us understand where quantum computers have the potential to create value. But “potential” is not yet a guarantee of application, and it is certainly not evidence that a quantum computer will outperform the best available alternative on a problem an enterprise actually needs to solve.

‍

This distance is the quantum applications gap. This gap is not evidence that quantum computing has failed to progress. In many ways, it is a consequence of progress. As hardware improves and credible paths toward fault tolerance become clearer, the question is what, precisely, we should do with increasingly capable quantum computers. Answering that question requires a level of rigor that broad use-case discussions rarely provide.

A Use Case Is Not Yet a Quantum Application

Consider “molecular simulation.” It is one of the most compelling areas for quantum computing because molecules are quantum mechanical systems and their accurate simulation can become prohibitively difficult for classical methods. Yet molecular simulation describes an enormous problem space. Which molecule? Which property? At what level of accuracy? How is the result used in a larger scientific workflow? What classical approximation is used today, and what would a better answer be worth?

‍

A credible quantum application must connect the full chain from enterprise need to computational execution. At minimum, it should answer five questions:

‍

1. What is the problem? The task must be defined at the level of a relevant problem instance, required accuracy, operating constraints, and desired outcome.

‍

2. What is the best classical baseline? A quantum approach should be compared with the strongest practical classical method.

‍

3. What is the complete quantum workflow? The assessment must account for data loading, state preparation, the core algorithm, measurement, repetition, and classical pre- and post-processing.

‍

4. What resources will it require? Logical qubits and gate counts are only part of the answer. Error-correction overhead, physical qubits, runtime, sampling costs, and supporting classical computation can determine whether an apparent advantage survives implementation.

‍

5. What threshold would create value? Technical performance matters only in relation to an organizational objective, whether that is reducing time to solution, improving accuracy, lowering cost, enabling a previously inaccessible calculation, or changing the quality of a decision.

‍

This is why a promising algorithm, a successful small-scale experiment, or an asymptotic speedup is not sufficient on its own. Constants matter. Input and output costs matter. Error correction matters. Classical computing continues to improve. An advantage visible in one step of an algorithm can disappear when the entire workflow is considered.

‍

End-to-end resource estimation provides a way to connect these layers before we have the required hardware. It takes a specific customer problem and turns it into the qubits, operations, error-correction assumptions, runtime, and classical resources needed to solve it. Just as importantly, it exposes where an application depends on an untested assumption or an immature component.

Why the Gap Persists

Application development is difficult because it sits across disciplines. Domain experts understand which problems matter. Quantum algorithm researchers understand where speedups may exist. Hardware and error-correction experts understand what it would take to execute those algorithms. Enterprise teams understand data, integration requirements, economics, and operational constraints. A useful assessment needs all four perspectives at once.

‍

It is also a moving target. Better hardware can reduce resource requirements, but so can a better algorithm or a more efficient error-correcting code. At the same time, improvements in high-performance computing, AI, and classical algorithms can raise the bar a quantum solution must clear. A conclusion that was reasonable two years ago may no longer hold in either direction.

‍

The work is consequently slow and expert-intensive. In our recent work with NVIDIA, we noted that benchmarking even one class of quantum algorithms can require years of effort spanning domain modeling, algorithm design, and hardware resource estimation. DARPA’s Quantum Benchmarking program similarly treated the evaluation of potential applications and the estimation of the hardware resources needed to run them as distinct but interdependent challenges. The bottleneck, then, is developing a repeatable way to move from potential to evidence.

Why Enterprises Should Care Now

The familiar argument for enterprise action is that quantum computing is approaching, and organizations that wait will be left behind. After years of shifting timelines, skepticism toward that message is understandable. A stronger reason to act now is that application readiness itself takes time.

‍

McKinsey’s 2026 Quantum Technology Monitor estimates that quantum computing could create $1.3 trillion to $2.7 trillion in economic value by 2035. Yet a market projection cannot tell an enterprise which of its problems is quantum-amenable or when the economics will work. That requires problem-level analysis.

‍

The same report identified more than 300 companies already engaging with quantum computing. Among a selection of large global companies, one-third allocated more than $10 million to quantum initiatives in 2025. Most of that spending went toward application development, integration, and internal capability building rather than hardware development. In other words, the competition is already forming at the application layer.

‍

Enterprises do not need to make an all-or-nothing bet on when fault-tolerant quantum computing will arrive. They can build application intelligence now: identify high-value problems, establish and continually update classical baselines, determine the performance thresholds that matter, map technical dependencies, develop internal expertise, and understand where proprietary data or workflows could create defensible intellectual property.

‍

This work produces useful answers even when the conclusion is “not yet” or “not for this problem.” It prevents expensive proofs of concept built around weak assumptions. It helps organizations direct scarce talent and capital toward the opportunities most likely to survive technical scrutiny. And when hardware crosses a relevant threshold, the enterprise already knows what to test and why it matters.

From Quantum Possibility to Evidence

Closing the quantum applications gap will require the ecosystem to treat application development as a discipline of its own. That means moving beyond lists of industries and isolated algorithm demonstrations toward systematic discovery, rigorous benchmarking, end-to-end resource estimation, and business-level validation.

‍

At Zapata Quantum, we believe the future of the field will be determined by how efficiently the ecosystem can discover and qualify the applications that hardware should run. In the next articles in this series, we will examine what a fully evaluated quantum application looks like, where common assessment approaches fall short, and how more systematic workflows can accelerate the path from a promising idea to a defensible application.