Article · Quantum pitch
The five questions every quantum VC asks, phrased differently.
A quantum VC has roughly five things they need to believe before they wire money. The wording mutates from one partner meeting to the next, but the underlying questions don't. Prepare for the five. Ignore the surface.
You walk out of a partner meeting and replay it. They asked about TRL. They asked about your founding team again. They circled back to that one customer LOI three times. Different angles, different vocabulary, but if you mapped the transcript to a checklist, you'd see five buckets and forty surface forms.
Quantum VCs aren't being clever. They're triangulating. Each surface question is a probe at one of five core anxieties they need resolved before IC. Founders who answer each surface form fresh, on the fly, run out of time. Founders who recognize the underlying bucket give the answer once, with calibration, and move on.
01Technological maturity
"Is this a science project, or is there a wedge?"
Surface forms
Where are you on TRL?
What's your timeline to a useful machine?
When does this stop being a science project?
What's the narrowest demo you'd sign your name to?
What they're actually asking
Is this a 10-year science bet I have to hold past the fund's life, or is there a wedge product in the next 36 months? In quantum, the gap between "physics works in the lab" (TRL 4) and "a customer pays for predictable performance" (TRL 7+) is often where the fund's patience runs out.
Common failure mode
Founders pitch the moonshot (utility-scale fault-tolerant quantum, 2030+) when the VC needs to underwrite the on-ramp. Either you have a near-term wedge with paying customers, or you have a credible plan to bridge the next two milestones with non-dilutive capital and limited equity dilution. Not both. Not neither.
Bring to the call
Your TRL today, the next two TRL milestones with dates, the capital required to clear each, and a one-line statement of what each milestone unlocks commercially. If you're at TRL 5 and pitching a TRL 9 outcome with no intermediate revenue, you're asking for a 7-year hold. Say so explicitly, or close the gap.
02Hardware architecture
"Why this modality, and why won't the giants outspend you?"
Surface forms
Why superconducting / trapped-ion / neutral-atom / photonic / spin?
What's your moat over [competing modality]?
What's the path to fault tolerance?
Why won't IBM / Google / a $10B player just outspend you?
What they're actually asking
Is this architecture's ceiling high enough to matter, and is your team's edge defensible against an incumbent two years from now? Most modalities have at least one giant player with 10x your cash. The VC needs a reason your architecture isn't just a slower path to the same place.
Common failure mode
Defending the modality on physics elegance. VCs don't underwrite physics elegance. They underwrite cost per logical qubit, error budget, manufacturability, and the slope of your roadmap versus the slope of the field's. "Better fidelity in our published paper" is an artifact, not a moat.
Bring to the call
A one-page modality comparison that's honest about the trade-offs — yours included. Cost trajectory per logical qubit, expected error rates at scale, what breaks first if you're wrong. Bonus: a slide where you say "if we're wrong, here's the leading indicator we'll see in the data first." That kind of self-skepticism closes more rounds than another fidelity number.
03Customer pipeline
"Who's paying you today, and who'll pay you in 24 months?"
Surface forms
Walk me through the design-partner list.
What's a real LOI vs an email of interest?
What does revenue look like in 24 months?
Could this be sold without the quantum advantage?
What they're actually asking
Are you commercializable before the science is done, or are you a research lab disguised as a startup? Quantum's hardest commercial fact: most "customers" are paid pilots that look more like grants than recurring revenue. The VC needs to know which of yours are real.
Common failure mode
Counting MOUs as pipeline. Counting government pilots without a renewal clause as recurring revenue. Counting a Microsoft Azure marketplace listing as "Microsoft as customer." A quantum VC has read 200 of these decks. They will sort it out faster than you'd like.
Bring to the call
A pipeline split into three columns — paid pilot (with PO number and amount), unpaid POC (with timeline to convert), warm conversation. Annotate each row with the buyer's name, budget owner, and the trigger that converts it to recurring. If 90% of your $5M ARR projection relies on three logos closing in Q4, say so. Honesty wins the call. A 4-color hockey stick loses it.
04IP & freedom-to-operate
"If you become valuable, can someone stop you?"
Surface forms
Walk me through your patent estate.
What's the patent landscape look like?
Are you blocked by anyone?
Who owns the IP from your time at [university / national lab]?
Have you done a freedom-to-operate analysis?
What they're actually asking
If you become valuable, can someone with deeper pockets stop you, sue you, or extract you? Quantum hardware sits on top of dense academic IP, often co-owned with universities or national labs under terms founders haven't fully read. The VC's nightmare is funding you to a $200M valuation and discovering MIT owns the core patent.
Common failure mode
"We have 12 patents pending." That's not the answer. The answer is: of the dozen patents that matter for our architecture, three are ours, four are publicly held by [competitor / academic group] with terms we've reviewed, two are held by our spin-out university with an exclusive license already executed (here's the term), and three are held by [larger company] but their claims don't read on our implementation because [specific reason]. If you can't say it like that, do the FTO analysis before the next call. It's $25–50K. Cheap insurance.
Bring to the call
License agreements with any university or lab the founders came from. A short FTO summary, or, if you don't have one yet, an honest "we're scheduling it." Patent counts are a vanity metric. Patent landscape understanding is a moat metric. Know the difference, and don't pretend the first is the second.
05Team
"Can this team build it, and can you hire the next ten?"
Surface forms
Tell me about the team.
Why are you the right founder for this?
Who's the technical lead and what's their unfair advantage?
How will you hire the next ten quantum engineers?
What happens if your CTO leaves?
What they're actually asking
Two things. First — does this team have the depth to actually build the thing they're describing, or is one person carrying the whole physics? Second — can they recruit against Google, IBM, NVIDIA, and the academic labs they came from, in the most concentrated talent market in tech?
Common failure mode
Lifting up the founders as "world-class" without saying what's world-class about them. VCs reference. They will call your former PI, your last manager, the postdoc who left your group two years ago. Resumes don't carry the round; specific reputational evidence does. Concrete, citeable, recent.
Bring to the call
Three names of senior people you can credibly recruit in the next 12 months and what would close them. The two-line summary of what your CTO's PhD work proves about their unfair advantage in your modality. A real plan for hiring quantum engineers that isn't "post on LinkedIn." If you're a solo founder in hardware, address it head-on — most quantum VCs will ask the question even if they don't say it out loud.
Five questions. Forty surface forms. The pattern repeats whether the partner meeting is in Boston, Munich, Tel Aviv or Singapore.
The fastest founders we've worked with answer each bucket in under two minutes, with one anchoring number and one anchoring artifact. The slowest answer each surface question fresh, sound impressive on most of them, and run out of session before the IC question gets asked.
Build a five-bucket prep doc once. Reuse it for every partner call. Update the artifacts every quarter. The work compounds.
Sanity check
Want a sanity check on your five answers before the next partner meeting?
The 2-minute Fundraise Readiness audit is built around exactly these five buckets, plus a sixth (financial defensibility) the directory was built to address. Score, three specific gaps, plan in your inbox.