Sovereign BOM OS for European defense OEMs to replace exposed components and prove resilient supply before contract ramp.

1. BAE, EIF, and Keysight entering Fund II means strategic and technical stakeholders are now helping shape which startups win capital, raising the premium on operational credibility.
2. Expeditions is explicitly funding Europe’s critical capability gaps and industrial resilience, which makes supply resilience a budgeted priority rather than an internal housekeeping problem.
3. At least half of Fund II is reserved for follow-on tickets, so teams that can show a scalable, resilient path to production should have an advantage in raising the next round.
4. Expeditions says the next wave is moving toward supply-chain security, creating a timely wedge around component substitutions and resilience evidence instead of yet another drone workflow tool.
5. Investors are prioritizing technologies with immediate operational relevance, so faster board-level revalidation and release readiness directly map to what the market is rewarding.

Catalyst. Expeditions' Fund II explicitly targets Europe’s capability gaps, industrial resilience, and supply-chain security, so startups that can prove resilient sourcing will win budget and follow-on capital faster.

The product ingests BOMs, approved vendor lists, supplier declarations, test reports, and engineering-change tickets from the systems teams already use. It scores component exposure, surfaces prequalified alternates, and routes the exact validation tasks needed before a board or subsystem can be released again. For each configuration, it generates a resilience dossier that a prime, ministry, investor, or lender can review without asking the team to rebuild the evidence manually. Over time, the company compounds a network dataset of accepted alternates, supplier risk patterns, and program-specific evidence requirements that makes every new build faster.

What's different. Generic PLM, ERP, and vendor-risk tools track parts, but they do not translate component exposure into defense-specific resilience evidence that a prime, ministry, or strategic LP will accept. This company wins by building a living graph of acceptable alternates, supplier declarations, and configuration-level approval outcomes across European defense programs. Over time, each approved substitution and rejected supplier makes the next customer’s dossier faster and more credible.

Jobs to be done

flowchart LR
  Ops[Defense OEM ops lead] --> Pain[Fragile BOM and manual supplier proof]
  Pain --> Product[Sovereign BOM OS]
  Product --> Output[Approved alternates and resilience dossier]
  Output --> Outcome[Faster contract ramp and follow-on capital]

Executive takeaways

• European defense policy and capital now explicitly reward industrial resilience, faster procurement, and sovereign capacity, making BOM sovereignty a budgeted issue rather than an operations afterthought.
• The pain is real at the component level: long-lived defense systems collide with short semiconductor lifecycles, while drone programs remain exposed to China-linked component chokepoints and manual alternate qualification work.
• The sharpest initial wedge is electronics-heavy European small-UAS and secure-communications OEMs entering first production, where one blocked component can stall both contract ramp and financing credibility.
• Competition is adjacent rather than direct: BOM-risk data, PLM, and supplier-compliance tools exist, but they do not turn a defense BOM change into an accepted resilience dossier by default.
• The software TAM is modest on its own, so the venture case depends on expanding from workflow into a cross-program dataset of accepted alternates, supplier declarations, and buyer-specific approval patterns.

Market definition

Supplier-side sovereign-BOM workflow software for European defense OEMs: a control plane that flags exposed components, orchestrates alternate qualification, and assembles configuration-level resilience dossiers for primes, ministries, and investors [4][5][6][8][10][13][14][15][18].

Customer and buyer

Primary daily users are supply-chain, NPI, quality, and program leads at 75-300 person European drone or secure-communications OEMs preparing low-rate production. The economic buyer is usually the COO or VP Operations because a blocked part directly delays build release, delivery, and financing credibility [10][11][12][15][16][21][22][23][24].

Buying triggers

• A pilot-to-production transition or release-to-build milestone forces the team to prove alternate sources, resilient supply, and interoperable evidence under severe time pressure. [10][11][12][14][21][22][23]
• A part EOL notice, trade restriction, or geopolitical exposure triggers urgent alternate qualification and export-control review across a live BOM. [13][15][16][17][18][19][20][39]
• A financing, prime, or ministry diligence process elevates sovereign sourcing and resilience evidence from an engineering concern to an executive gating item. [1][2][3][4][5][6][7]

Willingness to pay

Adjacent budgets already exist around enterprise PLM and supply-chain risk tools: Z2Data, Exiger, Siemens, PTC, and Supplyframe all sell demo- or quote-driven platforms tied to BOM risk, compliance, traceability, or supply intelligence. But a standalone sovereign-BOM layer will only clear budget when sold against avoided schedule slips, engineer labor, and procurement delay rather than generic visibility. [28][29][30][31][32][33][34][35][36][37][38]

Category dynamics

Growth signal 19% YoY EU defence spending growth in 2024

Validation signals

• Expeditions explicitly frames Europe’s next defense-tech wave as capability gaps, industrial resilience, and supply-chain security rather than only more drone applications.
• EU and UK policy now treats drone scale-up and industrial readiness as urgent, funded priorities rather than experimental side programs.
• TEKEVER, Quantum Systems, Auterion, and Delair are all pushing multi-vendor, multi-region, or rapid-scale operating models that increase the cost of weak alternate-source workflow.
• Z2Data, Exiger, Siemens, PTC, Supplyframe, and Sourcengine already monetize adjacent BOM-risk, PLM, and sourcing budgets, proving that budget lines exist around the problem.

Regulatory & technical constraints

• Dual-use export controls can disqualify otherwise attractive components, suppliers, or technical transfers, especially for electronics, information-security, sensing, navigation, and aerospace items.
• Programs increasingly need interoperable unmanned-system standards and evidence that can move across vendors, control stations, and allied operators.
• Obsolescence, counterfeit risk, and grey-market fallback raise the burden of proving source authenticity and acceptable substitutes.
• Many buyers will require sovereign or tightly controlled deployment patterns before they let supplier and BOM evidence leave core systems.

Competition is intense but mostly indirect. Z2Data goes deepest on part, supplier, and compliance intelligence; Exiger pushes nth-tier mapping and alternative supplier discovery; Siemens and PTC own PLM and digital-thread budgets; Supplyframe and distributors monetize market intelligence; and many buyers still default to spreadsheets, distributor emails, and sourcing consultants. The startup wins only if it becomes the defense-specific approval-memory layer that these tools do not natively provide [15][28][29][30][31][32][33][34][35][36][37][38][39].

Why incumbents do not win by default

• Electronics intelligence platforms. Z2Data, Supplyframe, and similar tools surface lifecycle, compliance, and supplier risk, but they stop at insight and do not own ministry-ready alternate-approval workflow or accepted-dossier memory.
• Broad supply-chain risk platforms. Exiger proves that defense buyers value nth-tier mapping, provenance, and alternative supplier discovery, yet its lens is broader third-party risk rather than board-level revalidation and configuration release.
• PLM and ALM suites. Teamcenter, Polarion, and Windchill already manage traceability, configuration control, and change governance, but they do not win by default because sovereign-source scoring, supplier evidence gathering, and buyer-specific resilience packets live outside their native workflows.
• Drone operating-system and interoperability stacks. Quantum Systems and Auterion show the market moving toward interoperable, software-defined unmanned fleets, but command-and-control progress does not automatically solve supplier qualification, alternate approval, or sovereign-BOM evidence.

European defense capital and procurement are now rewarding industrial resilience, so sovereign sourcing has moved from an operations nuisance to a board-level gate for startups trying to reach low-rate production. The sharpest first customer is a 75-300 person European small-UAS OEM with 50-plus critical electronic components and a build release, pilot-to-production down-select, or financing diligence inside the next 180 days. Today alternate-source approval still lives across PLM tickets, spreadsheets, distributor emails, and consultant decks, which means one exposed controller, RF part, or sensor can stall both contract ramp and follow-on capital. The product should start as a sovereign-BOM control plane that ingests BOM, supplier, and test evidence, flags exposed parts, routes board-level revalidation, and outputs a configuration-level resilience dossier. Go-to-market, pricing, and onboarding should all center on one live product line and one imminent release milestone: founder-led sales to the COO or VP Operations, a services-assisted first deployment, and annual pricing per active product line rather than per seat. The moat only becomes real if repeated deployments build an accepted-alternate graph and a country-specific dossier template library faster than PLM and supply-risk incumbents can imitate the workflow shell. This is a plausible company, but not yet a partner-meeting case, because the modeled software TAM is modest and budget ownership for a standalone overlay is still unproven. Two gaps should be treated as validation priorities rather than assumed away: how much dossier structure is actually reusable across German, Polish, and French programs, and how much early value can be delivered on sanitized data before full on-prem deployment becomes mandatory.

Problem

• European small-UAS OEMs entering first 100-500 unit runs must prove that critical electronics have acceptable alternates, compliant suppliers, and traceable evidence, yet the underlying data remains fragmented across PLM, ERP, email, and manual sourcing work.
• Obsolescence, China-linked dependencies, and dual-use or export-control constraints turn a single part EOL or geopolitical flag into weeks of manual revalidation, delaying release-to-build and weakening financing or procurement credibility.
• PLM, ERP, and part-risk tools can show parts lists or risk signals, but they do not produce the buyer-specific resilience dossier or approval memory that primes, ministries, and investors actually ask for at the gating moment.

Solution

• Ingest BOMs, approved vendor lists, supplier declarations, test reports, and engineering-change tickets into a secure overlay for one active product line.
• Score exposed components, surface prequalified alternates, and route the exact validation tasks, signatures, and evidence attachments needed before a board or subsystem can be released again.
• Generate a configuration-level resilience dossier for primes, ministries, and financing diligence, then use every approved substitution to build a reusable accepted-alternate graph.

Why we win

• The wedge is tied to a named release-to-build or diligence event, so the buyer, trigger, and ROI are clearer than in generic supply-chain visibility software.
• An overlay architecture works with existing PLM, ERP, and quality systems, which is more realistic for security-sensitive defense teams than a rip-and-replace motion.
• Repeated approvals create a proprietary memory of which alternates, suppliers, and evidence packages were actually accepted by which buyer or program.
• Starting in European drone production targets the segment with the clearest policy urgency, fastest industrial ramp, and most visible China-linked component pressure.

Milestones

flowchart LR
  Wedge[Small-UAS sovereign BOM wedge] --> MVP[BOM ingest and dossier MVP]
  MVP --> Proof[Faster alternate approval and release readiness]
  Proof --> Expansion[More product lines then tactical-radio expansion]

Founding team

Experiment roadmap

Risk assessment

What must be true

• At least 4 of the first 10 target OEMs confirm that sovereign-sourcing evidence is a funded priority tied to a live release or diligence event in the next 12 months.
• Two paid design partners convert to annual contracts above $150k ACV within 12 months.
• The first 2 deployments reduce alternate-approval or dossier-preparation cycle time by at least 30% versus the customer's manual baseline.
• A reusable core covers 60% or more of required dossier fields across German, Polish, and French small-UAS programs.
• Standard EU single-tenant or on-prem deployment patterns clear security review on the first 3 accounts without bespoke architecture.

Open diligence questions

• Which named release, procurement, or financing milestone owns the budget on the first 10 target accounts?
• How much dossier structure is genuinely common across German, Polish, and French small-UAS programs, and where does reuse break?
• What BOM, supplier, and test data can stay sanitized in early deployments, and what must remain on-prem from day one?
• How many engineer-hours and calendar days does one critical component substitution consume today on a real account?
• Can one PLM or ERP connector and one quality-document ingest path be deployed in under 6 weeks without custom middleware?

Model sanity

• Revenue engine. Base-case Y3 revenue comes from 10 paying product lines at $180K recurring ARPU plus $50K onboarding on three late-period additions, not from outsized services pull-forward.
• Must go right. The company must keep pilot-to-subscription conversion near one month and reuse dossier templates well enough to hit the 70% gross-margin target.
• Model breaks if. If security review and bespoke evidence work slow additions to 8 lines and cap margin near 67%, the downside case ends with roughly -$80K of cash.
• Next-round proof. The next financing is justified only if the seed round produces 5-7 paying lines across 3 customers, measurable template reuse, and one partner-sourced deployment before the Series A process.

Scenarios

Sensitivity

flowchart LR
  Accounts[Target OEM accounts] --> Audits[Qualified resilience audits]
  Audits --> Pilots[Paid design partners]
  Pilots --> AnnualLines[Active annual product lines]
  Pilots --> Onboarding[Onboarding fees]
  AnnualLines --> Recurring[Recurring software + monitoring]
  Onboarding --> Revenue[Revenue]
  Recurring --> Revenue
  Revenue --> GrossProfit[Gross profit]
  GrossProfit --> EBITDA[EBITDA after R&D, GTM, and G&A]
  EBITDA --> Cash[Ending cash]

Flags: Base-case Rule of 40 is still below 40 in Y3, so the next round needs either faster second-line expansion or better delivery leverage. · The model reaches exactly the researched Y3 SOM of 10 paying product lines, so the venture case still depends on later tactical-radio or prime-facing expansion. · Holding headcount flat at 8 FTE after Q4Y2 is efficient but leaves little room for a faster GTM ramp without another raise. · If the one-month pilot-to-subscription conversion slips to two months, the downside case turns cash negative even before adding more headcount.

• Budget ownership ambiguity. If the product is treated as another engineering tool instead of a production gate, buyers may defer purchase until contracts are already at risk. Mitigation: Sell against a named release milestone and quantify the cost of one delayed lot or failed sourcing review to anchor the buyer case.
• Evidence standards vary by program. Different ministries and primes may ask for different sourcing, provenance, and deviation artifacts, which can weaken a generic dossier. Mitigation: Start with German, Polish, and French UAV and tactical-radio workflows, ship template packs for specific programs, and expand only after repeated acceptance.
• Incumbent PLM bundling. Large PLM or QMS vendors could add basic alternate-source fields and compress the surface feature gap. Mitigation: Build the moat in defense-specific supplier acceptance data, benchmarked alternates, and cross-company resilience workflows that incumbents cannot aggregate quickly.