Part IX. Company and Investing · Chapter 78
Supply-Chain and Infrastructure Diligence
Every quantum computer in the world runs on dilution refrigerators, control electronics, lasers, and packaging that somebody else built. This chapter is about the companies selling those parts — and how to tell a real bottleneck from generic quantum exposure.
In this chapter 9 sections
Translate customer roadmaps into units demanded per installed system, validate qualification and substitution constraints, model concentration and inventory cash, and stress demand across at least three hardware-adoption scenarios before valuing the apparent picks-and-shovels position.
Picks-and-shovels language can hide a leveraged demand forecast. A control, cryogenic, laser, packaging, test, or fabrication supplier may sell a necessary component, yet its volume still depends on system shipments, units per system, qualification, substitution, lead time, customer concentration, and the cash needed to build inventory.
Demand starts with bills of materials
Demand is computed from a bill of materials: systems delivered per customer and scenario, multiplied by qualified units per system and price. Capacity, yield, inventory days, receivables, gross margin, and concentration then translate demand into cash. An unsigned customer roadmap remains a scenario input, never booked demand.
Supplier dossier: qualification, capacity, concentration
| Claim under review | Source chain |
|---|---|
| Quantum hardware systems depend on control, measurement, cryogenic, packaging, and software infrastructure beyond the qubit device. | |
| Device benchmarks do not directly forecast production volume or supplier revenue. | |
| Open interfaces and reproducible acceptance tests can reduce qualification friction at some stack boundaries. | |
| Public technology assessments identify infrastructure and scale dependencies as material development constraints. |
The full-stack and GAO sources establish the surrounding infrastructure burden. Randomized benchmarking illustrates that acceptance evidence requires a declared protocol. OpenQASM, Qiskit, and Cirq identify interface points for some suppliers; ACM supports reproducible qualification artifacts. None forecasts supplier volume or validates an undisclosed customer relationship.
A cryogenic-control forecast meets unit economics
| Scenario field | Base value | Unit | Evidence class |
|---|---|---|---|
| Systems delivered | 40 | systems/year | scenario |
| Units per system | 8 | qualified units | bill of materials |
| Unit price | 2500 | USD/unit | contract input needed |
| Largest customer | 70 | percent revenue | concentration assumption |
In the illustrative base case, 40 systems need 8 control units each at 2,500 dollars, producing 800,000 dollars of revenue. A single customer contributes 70 percent. Even the high-deployment scenario remains a concentrated option, and additional inventory magnifies cash needs. The table keeps attractive technical fit and fragile demand structure visible at once.
def model(dossier, scenario_name, concentration_limit, working_capital_limit):
errors = []
if not dossier.get("source_ids") or type(dossier.get("units_per_system")) is not int:
errors.append("sources_or_units_per_system")
price = dossier.get("price", {})
if type(price.get("value")) is not int or price.get("unit") != "USD/unit":
errors.append("price_schema")
scenario = dossier.get("scenarios", {}).get(scenario_name, {})
expected = {"systems": "systems", "largest_customer_share": "fraction",
"working_capital_share": "fraction"}
for name, unit in expected.items():
item = scenario.get(name, {})
if type(item.get("value")) not in (int, float) or item.get("unit") != unit:
errors.append(name + "_schema")
if errors:
return {"decision": "invalid", "errors": sorted(set(errors)), "revenue_usd": None}
units = scenario["systems"]["value"] * dossier["units_per_system"]
revenue = units * price["value"]
constrained = (scenario["largest_customer_share"]["value"] > concentration_limit or
scenario["working_capital_share"]["value"] > working_capital_limit)
return {"decision": "constrained-option" if constrained else "qualify",
"errors": [], "units": units, "revenue_usd": revenue}
dossier = {"scenario": "cryogenic-control supplier", "source_ids": ["scenario:customer-BOMs"],
"units_per_system": 8, "price": {"value": 2500, "unit": "USD/unit"},
"scenarios": {
"base": {"systems": {"value": 40, "unit": "systems"},
"largest_customer_share": {"value": 0.70, "unit": "fraction"},
"working_capital_share": {"value": 0.35, "unit": "fraction"}},
"high": {"systems": {"value": 80, "unit": "systems"},
"largest_customer_share": {"value": 0.65, "unit": "fraction"},
"working_capital_share": {"value": 0.42, "unit": "fraction"}}}}
base_result = model(dossier, "base", 0.50, 0.30)
bad_result = model({**dossier, "price": {"value": 2500, "unit": ""}}, "base", 0.50, 0.30)
high_result = model(dossier, "high", 0.50, 0.30)
deconcentrated = {**dossier, "scenarios": {**dossier["scenarios"], "base": {
**dossier["scenarios"]["base"],
"largest_customer_share": {"value": 0.45, "unit": "fraction"},
"working_capital_share": {"value": 0.25, "unit": "fraction"}}}}
improved_result = model(deconcentrated, "base", 0.50, 0.30)
assert base_result["units"] == 320 and base_result["revenue_usd"] == 800000
assert bad_result["decision"] == "invalid" and "price_schema" in bad_result["errors"]
assert high_result["decision"] == "constrained-option" and improved_result["decision"] == "qualify"
print(f"PASS: 78 supplier workbook units={base_result['units']} revenue=${base_result['revenue_usd']} invalid={bad_result['errors']} high={high_result['decision']} diversified={improved_result['decision']}")Artifact contract. A dated customer/unit/capacity/cash table with executable concentration and scenario analysis. Units reconcile from systems to components; no unsigned roadmap becomes booked demand; customer concentration and working-capital effects remain visible in all scenarios.
Exact validation command: python3 tools/validate_briefs.py --briefs data/editorial_briefs_64_87.json --from 64 --through 87 --check-rewritten-sources --execute-artifacts
Substitution risk can dominate technical quality
Request qualified alternatives, failure rates, customer acceptance records, capacity commitments, and who finances inventory. Model loss of the largest customer and a unit-count reduction from architectural change. A technically superior component may justify a partnership, but valuation should reflect correlated system roadmaps and the time needed to qualify a substitute.
Stress a supplier under three adoption paths
Prompt. Model an infrastructure supplier under low, base, and high system-deployment paths.
Deliverable. Customer assumptions, systems per year, units per system, price, gross margin, capacity, inventory days, concentration, and substitution trigger.
Pass condition. Every demand line multiplies explicit units, high-case revenue is not treated as probability-weighted fact, and concentration and cash needs are reported beside margin.
Model answer: attractive component, concentrated option
Format. Three-scenario control-electronics supplier model with concentration-adjusted conclusion.
The model answer calls the component attractive and the company concentrated. Unit arithmetic reconciles to 320 units and 800,000 dollars in the base scenario. The concentration gate fails at 70 percent, so high growth does not erase the risk. The next evidence event is a second qualified production customer or a binding capacity-backed order, not another system roadmap slide.
Verification. The fixture reconciles unit demand and shows that the high-growth case still breaches the declared concentration or working-capital limit.
Companion work
Artifacts for this chapter
These entries resolve to checked-in local source. Commands are reproduced exactly from the chapter manifest, and source-embedded fixtures are exported as direct downloads.
diligence dossier
Quantum supplier demand sensitivity model
Reproduce or test
python3 tools/validate_briefs.py --briefs data/editorial_briefs_64_87.json --from 64 --through 87 --check-rewritten-sources --execute-artifacts
Provenance
Sources and review
- U.S. Government Accountability Office. Quantum Computing and Communications: Status and Prospects. GAO. 2021government technology assessment
- OpenQASM Technical Steering Committee. OpenQASM 3 specification. Linux Foundation Joint Development Foundation. 2026official technical specification
- IBM Quantum. Qiskit documentation. IBM. 2026official documentation
- Google Quantum AI. Cirq documentation. Google. 2026official documentation
- Association for Computing Machinery. Artifact Review and Badging. ACM Publications. 2026official reproducibility policy
- Easwar Magesan, J. M. Gambetta, and Joseph Emerson. Scalable and robust randomized benchmarking of quantum processes. Physical Review Letters. 2011primary paper
- Lieven M. K. Vandersypen et al.. A look at the full stack. Nature Reviews Physics. 2021peer-reviewed perspective
- Timothy Proctor et al.. Benchmarking quantum computers. Nature Reviews Physics. 2025peer-reviewed perspective
The load-bearing claims in the chapter are mapped inline to this registered source set. A citation supports only the bounded claim beside it.