makhana mornings!

A little context. A lot to think about.

BUSINESS. PEOPLE. THE BIGGER PICTURE.

Clarity for a world that doesn’t slow down.

IBM’s quantum roadmap needs more than a bigger qubit count

3 minutes

IBM’s Nighthawk plans distinguish programmable qubits from physical totals. Reliable connections and comparable workloads matter as much as scale.

Conceptual illustration of two abstract processor modules joined by a blue bridge, with a verification symbol; not actual IBM equipment.

A larger quantum processor is an engineering milestone, not a complete answer to a business problem. The useful question is what it can calculate reliably, how long the entire job takes and what an alternative method would cost.

The Breakdown

On November 11, IBM announced a Nighthawk r3 design with 520 programmable qubits and 2,034 total physical qubits, targeting 10,000 quantum operations. It plans to connect two r3 processors into a 1,040-programmable-qubit system in 2027. These are development plans, not a newly operational machine.

The two counts should not be treated as interchangeable measures of computing capacity. Nor should either be relabelled as error-corrected logical qubits. IBM’s current Nighthawk r2 has 120 programmable qubits. Its reported workload speedups are relative to earlier IBM quantum hardware, not every classical alternative.

Connecting chips is part of the calculation

An October 21 research preprint by IBM researchers describes four links connecting two older Nighthawk r1 processors. The experiment reported average quantum-state transfer fidelity of 99.00%, with the best link reaching about 99.29%. Fidelity measures how closely a transfer matches its intended result; that figure is not the accuracy of an entire computation.

The same paper reports a different, lower measure for operations involving qubits on separate processors. Moving a quantum state and performing a joint operation are different tests. The preprint demonstrates interconnect work, not the completed r3 system or independent confirmation of its future performance.

That distinction is useful beyond this announcement. Joining two modules is not simply adding the numbers on their labels. The connection must also support the operations the calculation requires, with errors controlled well enough for the result to remain useful.

Why India should watch the workload

India already has a concrete connection to this ecosystem. A May 2, 2025 TCS exchange filing described plans with IBM and Andhra Pradesh for an Amaravati Quantum System Two installation using a 156-qubit Heron processor, alongside algorithm and application development.

That dated plan does not establish today’s installation status or an Indian deployment of Nighthawk r3. It does show why Indian researchers and businesses have reason to evaluate the technology beyond headline processor counts.

For example, a materials-research team assessing a calculation would need to define the required accuracy before comparing approaches. A faster intermediate step is not necessarily a faster complete project if preparation, repeated measurements or subsequent processing take longer. This is an evaluation framework, not a claim that a particular Indian project has achieved or missed those targets.

The Big Picture

A credible comparison starts with the same problem and an explicit standard for a usable answer. It then examines the full workflow, including the classical computing involved, rather than selecting the most flattering hardware statistic. Access costs and repeatability matter alongside runtime.

The Crunch

Quantum roadmaps become more meaningful when the milestones can be tested. Count the qubits, but also ask what was demonstrated, what remains planned and how the complete calculation compares.

Leave your thoughts

You might also like…