What would make a quantum pilot worth the money?

A logistics manager does not need a quantum circuit. She needs a delivery plan that arrives on time, respects the rules and costs less to operate. That hypothetical example captures a useful starting point for any business considering a quantum pilot: define the decision before choosing the technology.

NTT DOCOMO BUSINESS and Classiq announced an October 8 memorandum of understanding aimed at enterprise quantum adoption in Japan. NTT DOCOMO BUSINESS plans to propose and sell Classiq’s platform and help identify, develop and validate use cases. Classiq will provide software and technical expertise. The announcement describes intended collaboration; it does not report a customer quantum advantage or quantified return on investment.^[1]

The partnership provides a reason to ask what a successful engagement would have to show. The answer reaches beyond whether a circuit can run. A useful pilot needs a defined problem, a serious comparison and a result someone can act on.

Write down the decision

Start with a sentence a business owner can understand: we want to improve this decision, using these inputs, within this time limit and with this tolerance for error. An industry label such as finance or drug discovery is too broad to serve as that definition.

In the delivery example, a route must account for the constraints the business actually faces. A technically interesting solution to a simplified toy problem can teach a team something, but the business case still depends on whether the real constraints survive. An attractive visualization does not answer that question.

It helps to separate three pilot outcomes: learning, technical feasibility and business value. A project can teach staff new methods while discovering that deployment would be premature. That finding is useful if the pilot was designed to inform a decision, rather than to produce a success story at any cost.

Compare against the real alternative

The comparison should give the existing approach a fair chance. Use a capable classical method, comparable data and the same output requirements. If a proposal claims improvement over a deliberately weak solver, readers have learned little about the alternative a customer would actually buy.

The time budget also needs a beginning and an end. Include preparing the data, running the computation, checking the answer and producing a decision-ready output. A fast calculation that requires extensive manual repair may not improve the overall workflow.

For an illustrative pilot, suppose the new method finds a slightly better route but misses the dispatch deadline. Whether it has value depends on the business context. Conversely, a faster method might be useful even without the best possible mathematical answer if it meets the required quality reliably. The success criterion should make that trade-off explicit before results arrive.

Software can reduce friction; the result still needs scrutiny

The companies describe Classiq’s platform as supporting high-level models that are synthesized into quantum circuits, with access to simulators and several quantum hardware approaches. That can make development more accessible. It does not make different hardware targets equivalent or guarantee a useful result for a particular task.^[1]

A team should record where each result was obtained. Was it a classical simulation, a run on quantum hardware or a projection for a future machine? The distinctions belong next to the result. A simulator can be a useful development tool while providing no evidence that quantum hardware improves the customer’s task.

Changing hardware can also change the practical problem. A platform may help translate a model, but the team still needs to document which operations, limitations and execution conditions apply. Portability is valuable when it makes the alternatives clearer; it is less useful when it hides their differences.

End with an action the evidence supports

A good pilot finishes with a decision. Continue because the evidence supports the next test, pause because the resources remain impractical, or adopt because the workflow meets the agreed requirements. Each conclusion should follow from the same success criteria established at the start.

For a reader assessing a partnership announcement, three follow-up questions carry most of the weight: what customer problem was tested, what strong alternative was used and how did the result change the decision? These questions turn an abstract adoption story into something a non-specialist can evaluate.

The NTT DOCOMO BUSINESS–Classiq agreement is a route to experimentation. Its most valuable future chapter would explain a complete engagement: the original decision, the measured outcome, the costs included and the next action. That is what would make a quantum pilot worth the money.