Manufacturing OS for fusion teams to qualify superconducting magnet suppliers, trace build evidence, and de-risk first-of-a-kind builds.

1. Proxima is explicitly spending fresh capital on high-temperature-superconductor cable and magnet production, so software budget is moving from science tooling toward manufacturing readiness right now.
2. Google and RWE entering as strategic stakeholders means fusion teams now answer to future power buyers and operators who care about schedule confidence and acceptance evidence, not just physics milestones.
3. A named Alpha site near Munich, an early-2030s target, and a path to Stellaris turn fusion into a fixed-timeline build program where long-lead hardware mistakes become very expensive.
4. Hiring across engineering, manufacturing, and operations shows these execution workflows are being created now, creating a narrow window for a specialist system to become the system of record before spreadsheet-heavy habits harden.

Catalyst. Proxima’s €411 million round specifically earmarks Alpha, high-temperature-superconductor cable and magnet production, and operations hiring, while Google and RWE bring commercial power stakeholders into the build, making manufacturing proof urgent now.

The startup sits on top of PLM, QMS, lab data, and supplier portals to create a digital thread for every cable lot, coil, support structure, and cryogenic test tied to a magnet assembly. It tracks spec revisions across physics, mechanical, and manufacturing teams, flags when a supplier is building against the wrong baseline, and forces structured disposition of nonconformances before hardware ships. Program leaders get readiness dashboards showing supplier qualification status, test coverage, schedule risk, and missing evidence for each long-lead component. When utilities, strategic investors, insurers, or boards ask whether Alpha-class hardware is truly ready, the product auto-generates acceptance packs and exception logs instead of a scramble through email and SharePoint. Over time it becomes the operating dataset for which suppliers, designs, and process windows actually produce bankable fusion hardware.

What's different. Generic PLM and MES tools track drawings and shop-floor steps, but they do not unify supplier qualification, fusion-specific test evidence, and capital-release gates for first-of-a-kind superconducting assemblies. Nuclear QA systems are document-heavy, while engineering collaboration tools are too informal for hardware that can slip a billion-euro program. This company wins by turning each critical magnet into a bankable digital build book and learning which suppliers, deviation classes, and process windows actually predict on-time demonstrator delivery.

Jobs to be done

flowchart LR
  Buyer[Head of Magnet Systems] --> Pain[Fragmented supplier qualification and test evidence]
  Pain --> Product[Fusion Magnet Traceability OS]
  Product --> Outcome[Faster demonstrator builds with bankable acceptance packs]

Executive takeaways

• The credible wedge is not generic PLM; it is the bankability layer for HTS magnet procurement, deviations, and acceptance evidence now that Proxima, Tokamak, CFS, and Type One are turning fusion programs into dated industrial buildouts [1][31][38][54].
• The buying pain is already visible in public evidence: Proxima is building procurement infrastructure, CFS openly qualifies suppliers on quality and compliance, and FIA reports $434 million of 2024 fusion supply-chain spend with another 25% growth projected for 2025 [13][15][86].
• Near-term market size is narrow but urgent: the best initial accounts are the dozen-or-so magnet-intensive demonstrator and pilot-plant programs in Europe and North America rather than the full universe of industrial software buyers [1][38][54][70][76][123].
• Horizontal incumbents are formidable, but they stop short of a fusion-specific cross-company acceptance system that ties lot genealogy, nonconformances, test evidence, and release gates into one build book [24][106][107][109][111][112].
• This is strategically interesting only if the company expands from fusion into adjacent high-field systems after winning lighthouse programs, because fusion alone is a valuable but limited first beachhead [38][76][89].

Market definition

Initial market: software that manages supplier qualification, configuration drift, nonconformances, test evidence, and release gates for first-of-a-kind superconducting magnet assemblies, starting with European and U.S. fusion teams moving from research into demonstrator and pilot-plant execution [1][2][38][54][70][76].

Customer and buyer

Primary daily users are heads of magnet systems, supplier-quality managers, manufacturing engineers, and program-controls leads. The economic buyer is typically the COO, VP Manufacturing, or SVP Engineering once long-lead procurement and acceptance readiness become board-level schedule risks [13][15][1][39].

Buying triggers

• Long-lead HTS, cryogenic, or magnet procurement begins and leadership needs supplier qualification plus delivery and quality tracking before capital is committed. [1][13][15][86]
• A pilot plant or demonstrator reaches formal design review, site work, or partner diligence, turning acceptance evidence into a gating item. [40][54][71][72]
• Engineering organizations invest in digital twins, but supplier and quality data still sit outside the engineering stack. [24][42][106]

Willingness to pay

Willingness to pay is credible because active fusion programs now sit on multi-hundred-million capital bases, supply-chain spending is growing rapidly, and buyers already purchase enterprise PLM/QMS software on custom pricing. A tool that prevents a late magnet slip or shortens acceptance-pack assembly can sell against schedule protection, not generic IT efficiency. [1][39][70][86][106][112][115]

Category dynamics

Growth signal 25% projected 2025 YoY growth in fusion supply-chain spend

Validation signals

• Proxima raised €411 million specifically to build Alpha, expand HTS cable and magnet production, and hire across engineering, manufacturing, and operations.
• Alpha Alliance is coordinating manufacturing, system integration, and supply-chain capacity across more than 30 companies for one named demonstrator.
• CFS publicly qualifies suppliers on financial health, quality systems, technical capability, and compliance, which validates the workflow problem.
• Tokamak launched TE Magnetics and raised $125 million to commercialize both fusion and HTS magnet technology.
• Type One has both a formal plant design review and a stellarator-specific HTS magnet test campaign underway, showing the problem is no longer theoretical.

Regulatory & technical constraints

• U.S. fusion oversight now depends on NRC authority over byproduct material produced by fusion machines, so evidence systems must support traceable material and safety compliance across jurisdictions.
• ITER-style procurements require accepted quality plans, approved special processes, and verifiable records before manufacturing starts.
• Magnet systems remain a major cost and reliability driver; the National Academies notes they can account for roughly one-third of core machine cost and require high reliability and maintainability.

Competition is fragmented. Teamcenter-, ENOVIA-, Arena-, and MasterControl-class products each cover parts of the workflow, while some fusion teams are assembling digital-twin and procurement overlays internally. The opening is a narrow system of record for magnet-specific supplier genealogy and acceptance evidence rather than another all-purpose PLM or QMS suite [24][42][106][107][109][111][112].

Why incumbents do not win by default

• Enterprise PLM suites. Teamcenter and ENOVIA already manage product and supplier data, but they are horizontal platforms that require substantial configuration to fit fusion magnet acceptance workflows.
• Cloud PLM/QMS. Arena is better aligned to fast-moving product teams and supplier collaboration, but it is still a generic cloud PLM/QMS layer rather than a magnet build-book system.
• Quality and compliance suites. MasterControl is strong on regulated change and quality events, but it centers on QMS rather than the engineering-supplier digital thread for each superconducting assembly.
• Digital-twin and engineering platforms. CFS and Tokamak are investing in digital twins to accelerate engineering, yet those initiatives optimize design and simulation more than supplier qualification or acceptance evidence.
• In-house procurement and document stacks. Many teams still default to procurement hires, portals, and ad hoc document rooms because those are flexible, but they do not create a reusable cross-program acceptance dataset.

Fusion programs entering demonstrator buildout are now judged on whether HTS magnets and supporting evidence clear dated release gates, not just on plasma science. We start with European magnet-intensive demonstrator programs because Proxima, Tokamak, Renaissance, and UK-backed commercialization activity create a concentrated cluster of buyers, suppliers, and public-program infrastructure. The product is an overlay on PLM, QMS, lab data, and supplier portals that tracks baseline revisions, lot genealogy, nonconformances, and acceptance evidence for each critical superconducting assembly. This wedge is narrower than a general manufacturing OS, but it is exactly where existing Teamcenter, ENOVIA, Arena, and MasterControl deployments stop short of a board-ready build book. Research estimates a $64.8M TAM, $18.0M SAM, and $3.6M year-3 SOM, which makes the fusion beachhead commercially attractive only if it expands into adjacent high-field hardware after lighthouse wins. The first proof point is not broad ARR; it is whether one funded program and its first supplier cohort can reduce acceptance-pack cycle time and catch release-blocking evidence gaps before hardware ships. The biggest disconfirming risk is that buyers treat this as services or configuration work inside existing PLM/QMS stacks rather than as a new system of record with budget authority. Research still leaves one critical gap: the first signing budget owner and acceptable initial ACV need direct validation with target accounts before the company commits to a heavier integration roadmap or a seed-sized team.

Problem

• Heads of magnet systems and supplier-quality leads manage HTS tape, coil, cryogenic, and test evidence across PLM exports, spreadsheets, SharePoint, and email, so no one system proves a critical assembly is being built against the current approved baseline.
• When a design review, partner diligence event, or board update arrives, teams manually compile acceptance packs and often discover late nonconformances or missing genealogy only after schedule risk is already material.

Solution

• Overlay existing PLM, QMS, lab, and supplier systems to assign every cable lot, coil, deviation, and cryogenic test to the live spec baseline and block release until required evidence is closed.
• Provide supplier workspaces, readiness dashboards, and auto-generated acceptance packs so program leaders can qualify vendors, close exceptions, and explain build readiness to investors, utilities, insurers, and plant partners without replacing core engineering tools.

Why we win

• We target the cross-company magnet acceptance layer that horizontal PLM/QMS tools leave fragmented: supplier qualification, lot genealogy, nonconformance closure, and release-gate evidence for first-of-a-kind HTS assemblies.
• The defensible asset is a cross-program dataset on supplier performance, deviation patterns, and lot-to-test outcomes across repeated HTS build programs and supplier nodes, which in-house stacks and generic platforms do not aggregate.

Milestones

flowchart LR
  Wedge[European HTS demonstrator magnet workflow] --> MVP[Overlay for supplier qualification and acceptance packs]
  MVP --> Proof[Faster release gates and fewer missing evidence gaps]
  Proof --> Expansion[Supplier cohorts, U.S. programs, adjacent high-field sectors]

Founding team

Experiment roadmap

Risk assessment

What must be true

• Lighthouse programs manage at least 4 critical external suppliers and enough design or evidence churn to make manual build books fail repeatedly.
• The COO, VP Manufacturing, or SVP Engineering will fund the product from active program or manufacturing-systems budget before full plant commissioning.
• Critical suppliers will participate in lightweight evidence workflows without requiring the startup to sell every supplier a full PLM seat.
• A pilot can reduce acceptance-pack or release-prep cycle time by 25%+ or surface missing evidence early enough to avert a meaningful schedule slip.
• The same data model can win at least one adjacent high-field hardware segment after fusion, because fusion-only market size is not sufficient for a large software outcome.

Open diligence questions

• Which exact budget owner signed the last supplier-quality or PLM-adjacent software purchase at the target account?
• How many suppliers, baseline revisions, nonconformances, and acceptance packs does one active magnet work package generate per quarter?
• What is the current manual cycle time to assemble a board- or partner-ready acceptance pack, and who feels the pain first when it slips?
• Can the product land as an overlay on Teamcenter, Arena, QMS, and lab systems in weeks rather than months?
• What prevents Teamcenter, Arena, MasterControl, or the internal digital-twin team from covering enough of this workflow in-house?

Model sanity

• Revenue engine. Base revenue is driven by converting 3 developer programs and attaching supplier cohorts plus premium evidence modules until mature account value reaches about $1.2M and the researched $3.6M Y3 SOM.
• Must go right. The first two pilots must convert inside about four months and supplier cohorts must activate with them, or the sales-cycle and ARPU sensitivities erase most of Y3 EBITDA.
• Model breaks if. If demonstrator timelines slip or onboarding stays bespoke enough to cap gross margin near 67%, the downside case pushes cash toward low hundreds before seed proof.
• Next-round proof. A seed case is earned once 3 paying programs, 5-6 supplier cohorts, and one accepted live acceptance-pack review show the wedge can repeat beyond a single lighthouse.

Scenarios

Sensitivity

flowchart LR
  TargetPrograms[Target demonstrator programs] --> PaidPilots[Paid lighthouse pilots]
  PaidPilots --> AnnualContracts[Annual developer contracts]
  AnnualContracts --> SupplierCohorts[Supplier cohort attach]
  SupplierCohorts --> PremiumModules[Premium evidence modules]
  PremiumModules --> Revenue[Revenue]
  Revenue --> GrossProfit[Gross profit]
  GrossProfit --> Cash[Cash and runway]

Flags: The model reaches the researched Y3 SOM with only 3 paying developer programs, so one delayed program materially changes revenue and cash. · The $1.5M ask sits below the BP's $2-4M headline range only because pilots are assumed to be paid by M6 and scale hiring stays delayed; if conversion slips, funding need moves back toward the original range. · Gross margin reaches about 72% only if supplier evidence collection and data mapping standardize; prolonged bespoke integrations would push results toward the downside case. · customersEop counts paying developer programs, while supplier-cohort and premium-module revenue is treated as expansion inside those accounts, so the headline customer count understates paid workflow units. · Cash is modeled as EBITDA and does not capture enterprise collection timing, deferred revenue, or connector capex that could move real cash earlier or later.

• Category timing risk. Fusion demonstrator schedules can slip, delaying deployments and shrinking near-term software budgets. Mitigation: Start with the best-capitalized European programs and their magnet suppliers, price against avoided rework on active long-lead procurements, and expand into adjacent superconducting hardware markets.
• Workflow replacement resistance. Engineering teams may stick with PLM, QMS, and spreadsheets because adding another system feels slower than living with the current mess. Mitigation: Land as an overlay that ingests existing tools and wins one workflow first: supplier qualification plus acceptance-pack generation for HTS magnet assemblies.
• Customer concentration. A small number of fusion developers could dominate early revenue and weaken pricing power if one major program cancels or builds internally. Mitigation: Sell to both developers and critical suppliers, and design the schema so tokamak, accelerator, MRI, and grid-superconductor programs can reuse it quickly.