Chris Power, founder and CEO of Hadrian, explains how his company has opened six factories since 2022 — the latest 2.2 million square feet — to solve the core problem of U.S. contract manufacturing: no starting capacity exists, so you must build ahead of demand, standardize everything like GPU clusters, and operate with a level of execution risk that feels like an 80% chance of death until you hit ~$50B scale.
The Hadrian model: GPU-style factories, flexible capex, building ahead of demand
Hadrian treats factories like GPU clusters: standardized, modular stations that can be reconfigured so a high-mix, low-volume factory runs as efficiently as a low-mix, high-volume one.
The “GPU” metaphor means every station is software-defined and swappable; you manage peak capacity the way cloud providers manage GPU fleets.
Because the U.S. has no Shenzhen-style contract manufacturing base, customers cannot trust a slide deck — you must build ~1.2× your projected capacity before contracts exist, the way AWS built massive internal capacity before selling to Stripe.
This requires deploying billions in capex 2 years ahead of revenue; if you don’t, you have a 0% chance of winning production contracts, and if you do but miss the contract, the company dies — but at least you now have >50% odds instead of 0%.
The risk only retires when growth slows to ~20% YoY so cash flows catch up to capex bets; until then, every expansion bet is company-killing.
Risk philosophy: 80% death risk, sprinting through one-way doors, rolling hard sixes
Power estimates Hadrian has operated at a constant ~80% probability of death for years because the capex lead time (2 years) always exceeds the revenue curve; the only way to lower risk is to stop growing fast, which defeats the venture-return mission.
Capex and long engineering projects are one-way doors: you cannot undo a 9-month machine order. The solution is to over-hedge on the 20% of capex that is flexible (robot arms, etc.) and spend 30% more upfront to buy optionality, rather than wait for perfect certainty and miss the timeline.
“Sometimes you gotta roll a hard six” — in asymmetric, long-cycle businesses, there is no risk-management framework that eliminates the need to be right on high-stakes bets; you just have to execute at an extremely high level repeatedly.
Practical example: when building a factory, over-invest in foundations and electrical drops everywhere (e.g., spend $25M instead of $15M) so layout teams get 4 extra months of simulation time; unused drops are cheap insurance against lock-in.
Factory construction & operations: over-invest in infrastructure, design for failure, Motherrain software
Hadrian’s “Motherrain” software layer reprograms every machine’s API; early on they discovered vendors’ APIs were inconsistent, half-unimplemented, or returned errors in German — so they now assume every integration will fail and build hedges into every timeline.
Factory design must assume failure, not success: build “off-ramps” (slack capacity, buffer lanes) so a single machine breakdown doesn’t halt the whole line, the way a blown tire on a freeway needs a shoulder so traffic keeps moving.
This requires every station to be GPU-standardized so work can be rerouted instantly; software workflows must map 1:1 to physical layout (e.g., a dedicated fast-inspection lane for new-product introduction to close the feedback loop in minutes, not days).
There is a hard limit to software complexity that doesn’t rate-match the physical world; you must separate fast-response physical zones from steady-state production zones.
Surviving company-killing events: the rusted-machine crisis
Two years in, a reputable vendor silently switched a sub-component supplier; 40 new machines developed terminal rust. Vendor’s warranty plan: fix one-by-one by Thanksgiving (8 weeks) — which would have missed a critical delivery quarter and killed the fundraise.
Power spent a week forcing the vendor to fly in 30 engineers and fix all machines in 4 weeks; such existential crises happen ~once per quarter in manufacturing.
Scaling the organization: modular teams, cultural minimalism, hiring velocity
Org design: capability teams (weld, software, etc.) capped at 30–40 people with strong technical leads; teams communicate via APIs, not meetings, so adding headcount doesn’t create management bloat.
Culture: reduce values to 2–3 non-negotiables (e.g., pace and methodology) and fire anyone who violates them; everything else is a “luxury belief” that breaks at scale.
Hiring: build a single, company-wide technical test per role (e.g., weld engineering) so any passer is default-good; never rely on new managers to design interviews.
Recruiting is the longest lead-time constraint: 90 days to hire a recruiter, then 90 days for them to produce 4 hires — so you must bet on scale 6 months ahead and pause hiring later if needed.
Strategy: mission-first contract selection, government trust through honesty
Filter every opportunity through: (1) mission alignment (re-industrialization, defense), (2) “doors that open once and never reopen” (e.g., first contractor access to a DoD division in 50 years), (3) Lego-brick reuse (how many existing standardized modules does this program need?), (4) commercial efficiency (low-cost interceptors are profitable but abundant — defer them).
Government trust is built by not chasing contracts early: spent 2.5 years advising policy makers “we’re not ready, here’s how to think about manufacturing” — turning down revenue to prove honesty. When Hadrian finally said “we’re ready,” credibility was already established.
Saying no to winnable but low-value contracts compounds trust faster than saying yes; it’s the slow way to a $1B company but the fast way to a $100B company.
Capex-heavy businesses have two paths: customer prepayment (rare) or long-duration infrastructure debt. Hadrian architected its model from day one to hit the metrics (contract duration, capex useful life, uptime) that unlock cheap infrastructure credit.
Every fundraising round required teaching VCs manufacturing accounting: GAAP revenue recognition, capex depreciation, and gross-margin subsidies (engineering R&D and capex depreciation both depress near-term margins but are investments) — totally different from SaaS.
Cost accounting is first-principles: track exactly where costs sit in manufacturing vs. overhead; once investors see the detail matches public-company rigor, they outsource critical thinking to Hadrian.
Competitive advantages: flexibility and scale over speed
Early hypothesis: speed (2-week lead time vs. 12) would be the killer feature. Wrong: only SpaceX converts speed to value; everyone else values flexibility, total program cost, and scale.
Pivoted to optimizing for “Lego-brick” reuse across programs: 80% of capex (Fanuc arms, standardized cells) shared across missile, drone, turbine, etc.; only 20% program-specific.
Lower cost of capital is a derivative of execution excellence, not a standalone advantage.
Leadership: energy management, pulling in hard decisions, velocity over planning
Power manages personal energy, not time: knows which tasks drain him (high-context switching) and which fuel him (product/engineering); structures calendar accordingly.
Hard decisions (firing, tough conversations) must be actioned immediately — draft the email at midnight, send at 9 AM — because deferring burns a week of mental bandwidth.
“Fundraise ahead of the org” (Sam Altman): when demand is infinite, maximize organizational velocity (hiring, shipping, decision speed) and let the market reveal the ceiling; don’t plan a linear curve.
The treadmill speed keeps rising; the only sustainable algorithm is knowing your energetic limits, automating the painful stuff, and never taking organizational friction personally.
