What Enterprises Actually Do With Quantum Computers Today

Let me start by clearing up something that confuses almost everyone the first time they look into this: no company is running its supply chain on a quantum computer. Nobody's pricing derivatives on one in production. If a vendor tells you otherwise, ask them what "production" means to them, because I guarantee the answer involves an asterisk.

What's actually happening is more interesting than either the hype or the dismissal gives it credit for. So let's walk through it — not "quantum will change everything," and not "quantum is a decade-away curiosity," but what teams are literally doing on Monday mornings right now.

The workflow nobody talks about: building the team before the machine is ready

JPMorgan Chase runs the largest quantum effort of any US bank through a unit called FLARE — the Future Lab for Applied Research and Engineering. What's notable isn't the qubit count. It's the sequencing.

Marco Pistoia, who leads the group, has said the point of investing now is becoming "quantum-ready," not quantum-productive. That's a real distinction, and it's the first thing I want to sit with: in this field, the workflow often precedes the payoff by years.

JPMorgan has poured $100 million into Quantinuum, built an internal bench of over fifty physicists and mathematicians, and published peer-reviewed work on portfolio optimization and Monte Carlo acceleration — all while publicly acknowledging that an internal study found limited practical advantage so far.

That combination — real budget, real publications, honest limits — is what a mature enterprise program looks like. Compare that to Goldman Sachs, which has taken a visibly smaller, slower path on the same technology. Two banks, same tools available, very different bets on timing.

The actual day-to-day work in these teams looks like: pick a narrow, well-defined subproblem (constrained portfolio optimization, say), formulate it as a quantum circuit using a toolkit like Qiskit, run it on rented time on a trapped-ion machine — JPMorgan has used Quantinuum's H1 and H2 systems — and compare the output against a classical baseline. Most weeks, classical wins. The team publishes anyway, because the point is building institutional muscle memory for the day the comparison flips.

The workflow in pharma: quantum as one stage in a much longer pipeline

Drug discovery gives you a cleaner picture of the actual research process. IBM and Cleveland Clinic recently ran a variational quantum eigensolver — a hybrid algorithm that splits work between a quantum processor and classical density functional theory — on a 303-atom mini-protein, using IBM's 156-qubit Heron chip. That's a genuinely new capability: the first protein-scale quantum chemistry simulation of its kind.

The workflow there is: classical methods handle the bulk of the molecule, and the quantum processor gets called in specifically for the electron interactions that classical approximations handle badly. Boehringer Ingelheim runs a similar partnership with Google Quantum AI.

AstraZeneca has reported a 20x speedup on a specific drug-discovery workflow segment using IonQ hardware through AWS — not an end-to-end simulation, but one stage of a much longer pipeline getting meaningfully faster.

What I actually tell you to take away

If there's one pattern across finance, pharma, logistics, and materials science, it's this: nobody is replacing their classical stack. They're identifying the one subroutine in an existing workflow where classical methods hit a wall — a combinatorial explosion, an electron correlation problem, a search space too large to brute-force — and inserting a quantum step there, then handing the result back to classical infrastructure. Hybrid isn't a compromise; right now, it's the entire architecture.

I'll admit I used to find this unsatisfying — I wanted the clean story where quantum computers just start winning outright. It took me longer than I'd like to accept that the actual value right now is optionality: teams that built this muscle in 2023 and 2024 are the ones positioned to move fast whenever the hardware crosses the threshold. The teams that waited for proof before starting are, by definition, starting later. In a field where the talent takes years to build and the useful hardware window is still genuinely uncertain, being early and wrong for a while is cheaper than being right but late.