Qualification graph for defense component factories to approve alternate sources and ship traceable parts without months of tribal rework.

1. Investors are funding supplier roll-ups because the failure point is fragmented certified capacity, not just prime-level demand planning.
2. Qualification cycle time is becoming a tracked business outcome, creating room for a focused workflow product rather than another generic factory tool.
3. The pain is concentrated in mission-critical components where a single delay can hold up large defense programs and justify urgent spend.
4. Factory acquisitions only pay off if qualification knowledge moves across sites, which makes network-grade manufacturing software newly valuable.

Catalyst. Amca’s funding, supplier roll-up, and claim of a 67% qualification-time reduction show that compressing approval cycles in sub-tier defense manufacturing has become urgent and budget-worthy.

The product ingests drawings, process plans, prior build history, test artifacts, and quality exceptions from each factory, then maps them into a capability graph by part family, machine, material, and supplier. When a customer asks for a second source, faster release, or design change, the system shows which evidence can be reused, what gaps remain, and which internal or external shop is most likely to qualify. It then generates the approval packet, routes required signoffs, and keeps a traceable record of why a source or deviation was approved. Over time, the graph becomes the fastest way for a supplier or prime to see latent capacity inside a fragmented certified network without waiting for months of manual discovery.

What's different. Generic MES, ERP, and QMS tools store records but do not understand whether old evidence is sufficient to approve a new part, source, or change. This product's core asset is a reusable qualification graph that links process capability, test history, exceptions, and program context across multiple certified shops. As more factories and approvals run through the system, it becomes harder to replace because it accumulates the hidden decision logic that today sits in a few veteran engineers and supplier-quality leads.

Jobs to be done

flowchart LR
  Buyer[Defense component supplier GM] --> Pain[Slow source qualification and release decisions]
  Pain --> Product[Qualification graph workflow]
  Product --> Outcome[Faster approved capacity and traceable shipments]

Executive takeaways

• The pain is real: defense readiness still breaks at lower-tier component suppliers where qualification knowledge is fragmented across people, files, and buyer-specific templates.
• The beachhead is narrow but sharp: alternate-source qualification, deviation control, and first-article evidence reuse inside mid-sized AS9100/ITAR shops.
• Incumbents already monetize adjacent QMS, PLM, and MES workflows, but the market still lacks a neutral cross-factory qualification-memory layer.
• Compliance burden is a feature as much as a hurdle: once a system becomes the trusted place to assemble and defend approval packets, replacement gets harder.
• The best near-term wedge is event-driven: shortages, acquisition integrations, rate increases, and prime requests for backup capacity.

Market definition

Software that helps aerospace and defense component manufacturers decide whether an alternate source, process change, deviation, or site transfer is approvable, while generating the supporting packet and audit trail required by primes and government buyers.

Customer and buyer

Primary buyer is a VP Quality, site GM, or operations leader at a 50–250 employee U.S. aerospace-defense component supplier; the day-to-day champion is usually supplier quality or quality engineering. Secondary stakeholders are OEM supplier-development teams and roll-up operators trying to move qualified work across sites faster.

Buying triggers

• A prime or government customer requires a qualified source before award or delivery, forcing the supplier to assemble proof quickly. [5][9][10][12][36]
• A nonconformance, concession, or planned deviation must be adjudicated under time pressure, and email-based routing becomes the bottleneck. [6][16][17]
• A cybersecurity or export-control review turns supplier onboarding into a cross-functional compliance project rather than a simple file exchange. [8][13][35]

Willingness to pay

Aerospace manufacturers already budget for category software around quality, supplier collaboration, and compliance. SoftwareConnect shows defense-specific QMS categories and estimated per-user spend, while MES platforms like Tulip publish monthly entry pricing and Arena packages GovCloud tiers with supplier-quality and analytics features. That suggests budget exists inside existing quality/ops software lines if the product can clearly cut packet cycle time and engineer labor. [19][29][30]

Category dynamics

Growth signal Approx. 8.6% annualized growth in AS-series certifications from 2023 to 2025

Validation signals

• GAO says DOD relies on more than 200,000 suppliers while still lacking visibility into most raw-material and parts suppliers.
• Net-Inspect explicitly markets supplier deviation management as a replacement for email chaos in aerospace supply chains.
• Defense-specific QMS and MES buyer guides already segment the market and publish pricing anchors, implying real software budget and category maturity.
• Amca’s funding round and messaging center directly on faster qualification and modernized critical-component manufacturing.

Regulatory & technical constraints

• Qualification requirements can require approval before award and force suppliers through formal approved-source paths.
• Nonconforming product cannot simply be waved through; acceptance must be technically and contractually justified.
• DFARS electronic-part rules push counterfeit avoidance, authorized sourcing, and contractor-approved supplier logic through all tiers.
• Defense suppliers handling controlled data increasingly need NIST/CMMC maturity before rich workflow collaboration is acceptable.
• Prime-specific quality manuals and FAI requirements still shape the packet structure buyers expect.

Competition is fragmented. Prime portals and supplier manuals define the rules. QMS, PLM, and MES vendors store records and execute workflows. A few aerospace-specific vendors handle deviations or FAI. But the proposed startup is differentiated if it becomes the neutral layer that reuses prior evidence across factories and suppliers rather than just documenting a single site’s transactions.

Why incumbents do not win by default

• Cloud PLM / QMS stacks. These systems are strong systems of record for BOMs, changes, quality events, and supplier documents, but they do not win by default because qualification decisions still depend on buyer-specific evidence reuse and approval logic across multiple factories.
• MES / digital-thread suites. Internal genealogy and as-built traceability are useful inputs, yet these platforms are optimized for running owned operations, not brokering approved-source decisions across independent certified shops.
• Prime supplier portals. Primes set the templates and flowdowns, but their portals are buyer-specific endpoints rather than reusable cross-customer qualification memory for suppliers.
• Vertically integrated operators. Players like Amca can solve the problem inside an owned manufacturing network, but that does not automatically create a neutral SaaS control point for independent shops or OEM supplier-development teams.

Defense Subtier Qualification Graph is a workflow and data layer for U.S. AS9100 and ITAR-compliant component suppliers that need to qualify alternate sources, approve deviations, and transfer work between certified shops without rebuilding evidence from scratch. The first sale is to a 50-250 person electromechanical supplier facing a rate increase, shortage, engineering change, or post-acquisition site transfer. Instead of replacing ERP, QMS, or PLM, the product ingests exported records, identifies reusable proof, and generates ready-to-submit approval packets with auditable signoffs. Research supports a $57.5M SAM and a plausible $2.4M year-three SOM for this narrow beachhead, so the venture case depends on later expansion into OEM supplier-development teams, roll-up operators, and broader multi-factory readiness workflows. The go-to-market system is event-driven: founder-led sales into urgent qualification events, paid pilots scoped to one packet type and one program, and conversion to annual per-factory subscriptions once cycle time improvement is proven. Defensibility comes from accumulating reusable approval logic across parts, processes, materials, machines, and exception histories that incumbent systems currently store but do not operationalize. The main investor risk is that data mapping, security controls, and customer-specific templates could make the business too services-heavy before recurring software value is obvious. Key diligence gaps remain around real budget ownership, acceptable levels of digital packet automation, and how many packet sections primes will accept without manual rewriting.

Problem

• Qualification evidence for alternate sources, deviations, and site transfers is fragmented across email, spreadsheets, ERP or QMS records, PDFs, and veteran engineer memory, so each event restarts packet assembly from scratch.
• In mission-critical power, sensor, avionics, and flight-control assemblies, a delayed approval packet blocks revenue, shipment, and readiness at exactly the factories primes need to expand qualified capacity.

Solution

• A qualification graph normalizes drawings, process plans, prior build history, test artifacts, machine and material constraints, and exception history into reusable evidence objects by part family and factory.
• The workflow engine identifies which proof can be reused, flags missing evidence, generates buyer-ready approval packets, routes required signoffs, and creates a traceable record for future qualification events.

Why we win

• QMS, PLM, MES, and prime portals store records but do not answer the supplier-side question of whether an alternate source, deviation, or cross-site transfer is approvable now with evidence already on hand.
• Once the system captures which packets were accepted, by whom, and under what process constraints, it becomes a sticky approval-memory layer that is harder to replicate than generic workflow software.

Milestones

flowchart LR
  Wedge[Alternate-source and deviation wedge] --> MVP[Qualification graph MVP]
  MVP --> Proof[Accepted packets and shorter cycle time]
  Proof --> Expansion[Multi-factory and OEM network expansion]

Founding team

Experiment roadmap

Risk assessment

What must be true

• Target buyers spend more than 80 quality or engineering hours and more than 30 elapsed days on a typical alternate-source or site-transfer packet.
• The first customer can realize a 30%+ cycle-time reduction using exported data before full secure-system integration is required.
• A VP Quality or site GM controls enough discretionary budget to fund a pilot during a shortage, rate increase, or acquisition integration event.
• Prime and government packet requirements are reusable enough across events for accepted-history data to compound into product advantage.
• At least 30% of initial customers have a second-factory or adjacent-program expansion path within 12 months of the first annual contract.

Open diligence questions

• What were the last five alternate-source, deviation, or site-transfer packets at target accounts, and how long did each take?
• Which executive actually signs the software budget when a qualification delay threatens shipments or revenue?
• Which packet sections can be auto-populated from existing records in pilot one, and which sections still require manual rewriting?
• What level of controlled technical data can the vendor host without triggering unacceptable ITAR or CUI friction for smaller suppliers?
• How often does the first customer face a qualifying event severe enough to justify annual subscription rather than project-by-project services?

Model sanity

• Revenue engine. Base-case revenue is driven by expanding active factory sites from 4 at M12 to 24 at Q4Y3 at roughly $100K steady-state site ACV, not by aggressive seat-based monetization.
• Must go right. The first customers must expand to second factories and accept secure exported-data deployment in under 6 weeks, because that is what makes the jump from 8 sites in Y2 to 24 in Y3 believable.
• Model breaks if. If security review and packet templating keep deployments bespoke, the downside case compresses cash toward roughly $195K and the business drifts into services-heavy economics.
• Next-round proof. The next financing is justified once the company shows 6-8 live factory sites, at least one second-factory expansion, and one OEM or roll-up pilot on a repeatable deployment playbook.

Scenarios

Sensitivity

flowchart LR
  Leads[Urgent qualification events] --> Pilots[Paid pilot sites]
  Pilots --> Sites[Active factory sites]
  Sites --> Revenue[Subscription and program revenue]
  Revenue --> GrossProfit[Gross profit after deployment COGS]
  GrossProfit --> Cash[Cash runway]
  Sites --> Expansion[Second-factory expansions]
  Expansion --> Revenue

Flags: The base case is still EBITDA-negative in Y3, so the next round depends on proof of repeatable expansion rather than near-term profitability. · Revenue per FTE remains below classic SaaS benchmarks because forward deployment, security, and template work are still meaningful parts of delivery. · Gross margin only reaches the 70% target by Y3; if secure deployments stay bespoke, the model will miss the planned buffer. · The direct supplier beachhead is only a $57.5M SAM, so investor upside still requires OEM, roll-up, or multi-workflow expansion beyond the first wedge.

• Data capture friction. Legacy factories may not have clean digital records, making the first implementation slower than buyers expect. Mitigation: Start with one qualification workflow, combine software with guided evidence mapping, and prove time savings before broad rollout.
• Incumbent system overlap. Buyers may assume ERP, QMS, or homegrown trackers already cover the problem well enough. Mitigation: Position around cross-factory qualification reuse and approval generation, which incumbent systems store but do not automate.
• Slow defense sales cycles. Even painful factory problems can move slowly if budget authority sits with conservative operators or prime customers. Mitigation: Sell first into acquisition integrations and urgent source-expansion events where delay has visible program and revenue consequences.