Procurement passport OS that helps European drone OEMs qualify once and sell faster across multiple ministries.

1. A real software marketplace now lets ministries compare multiple drone vendors, so supplier data has to become structured and reusable instead of bespoke.
2. Interoperability has moved from a post-award integration problem into the purchasing workflow itself, raising the value of machine-readable proof.
3. With manufacturers from ten countries entering the same buying channel, smaller OEMs need software to normalize technical evidence across borders.
4. European drone sovereignty pressure makes ministries and suppliers more willing to adopt new procurement infrastructure quickly than in peacetime cycles.

Catalyst. Intelic's BASE launch, built with ministry input and linked to Nexus command-and-control software, shows European drone buying is moving into interoperable software workflows now.

The product connects to a drone OEM's existing technical documents, manuals, trial reports, and security paperwork and converts them into a structured catalog of capabilities. It generates buyer-specific response packs for different ministries, maintains an auditable version history, and highlights missing evidence before a tender is submitted. A lightweight test layer records compatibility results for common command-and-control and mission-data workflows so suppliers can prove interoperability instead of just asserting it. Over time, the platform becomes the system of record for what each product line can legally, technically, and operationally promise in each European market.

What's different. Marketplaces help buyers discover vendors, but they do not solve the supplier-side work of becoming procurement-ready across fragmented ministries. This company would own the structured evidence layer: normalized product data, reusable compliance artifacts, and a growing corpus of interoperability results linked to real buying workflows. That creates workflow lock-in with OEM capture teams and defensibility from the accumulating template library, buyer feedback, and test history.

Jobs to be done

flowchart LR
  OEM[Drone OEM capture lead] --> Pain[Manual tender packets and interoperability proof]
  Pain --> Product[Procurement passport OS]
  Product --> Outcome[Faster listing and award across ministries]

Executive takeaways

• Intelic's BASE launch is strong evidence that buyer-side defence-drone procurement is digitising now, but none of the visible platforms solve the supplier-side work of packaging reusable interoperability evidence across ministries.
• The pain is real because European drone procurement remains fragmented while authorities still require security-of-information, security-of-supply, and tender-specific annexes; that makes cross-border expansion disproportionately hard for sub-scale OEMs.
• Standards work is moving in the startup's favor: EDA INTERACT and NATO/STANAG efforts point toward machine-readable interoperability and open-architecture evidence becoming more valuable than static PDFs.
• Demand tailwinds are credible—European military spending rose sharply, EU programmes explicitly prioritise drones and counter-drones, and multiple countries are launching joint low-cost drone programmes—but the beachhead software TAM is still modest on its own.
• Competitive pressure is adjacent rather than direct: procurement suites, tender portals, and defence acquisition platforms exist, yet they generally optimize buyer workflow or generic compliance, not drone-specific supplier qualification.
• Go-to-market likely needs a high-trust, service-assisted first motion with EU-hosted or single-tenant deployment; self-serve SaaS is unlikely to clear defence-data trust barriers early.
• The venture case depends on expanding from passports into testing, ongoing compatibility evidence, and adjacent autonomous-systems qualification; otherwise the initial drone-OEM software market may be too small.

Market definition

Supplier-side defence procurement-readiness software for European drone OEMs: a structured product passport that turns specs, compliance artifacts, references, and interoperability results into reusable listing and tender packets. Geography is Europe, including UK- and Ukraine-linked supply chains selling to European ministries and NATO channels. Adjacent markets include buyer-side marketplaces, e-procurement suites, proposal automation, and C2/interoperability tooling. Excluded are civil-drone compliance software, pure tender-discovery portals, prime-led MALE aircraft programs, and post-award program management.

Customer and buyer

Initial ICP is a 50-200 person European ISR/FPV drone OEM expanding beyond one home-market defence buyer. The daily user is a capture or bid lead plus the product/integration lead who must answer technical annexes and prove compatibility. The economic buyer is typically the CEO, VP Sales, or head of business development because the problem spans revenue, engineering time, and market-entry risk. Budget is likely assembled from capture, sales operations, and compliance rather than core IT.

Buying triggers

• A live pre-qualification or framework tender creates an immediate need for ISO attachments, self-declarations, non-disclosure materials, and compliance matrices. [20]
• A ministry or procurement hub wants interoperable systems it can compare across suppliers, making reusable product data suddenly valuable. [1][2]
• Cross-border selling forces OEMs to show security-of-information and security-of-supply guarantees in addition to product performance. [6]

Willingness to pay

Budget exists in adjacent workflows: public-sector procurement platforms sell compliance and workflow automation to institutions and suppliers, defence acquisition software wins large software contracts, and defence-drone OEMs themselves are raising or deploying significant capital. Still, direct willingness to buy a standalone supplier passport remains unproven and should be validated before heavy buildout. [17][18][19][22]

Category dynamics

Growth signal Europe military spending +14% in 2025

Validation signals

• Intelic launched a European defence-drone procurement hub linking supply discovery to operational software.
• EDA completed a standards-oriented project specifically aimed at interoperability for military unmanned systems.
• The European Commission is funding dozens of defence projects and explicitly prioritizing drones and rapid innovation.
• Five European countries launched a joint low-cost drone and drone-defence programme (LEAP).
• Europe's military expenditure rose sharply in 2025, increasing urgency to spend faster and better.
• France publicly acknowledged it was behind on light-drone acquisition and is investing heavily through 2030.
• Tekever's UK contract and £400m investment plan show supplier-side growth in the addressable ecosystem.
• NSPA framework activity shows NATO channels are formalizing small-UAS procurement.

Regulatory & technical constraints

• Defence buyers can require guarantees for classified-information handling and security of supply.
• Interoperability expectations are moving toward open architectures and standard interfaces rather than bespoke claims.
• Airworthiness and integration requirements such as STANAG-aligned certification raise the bar for what evidence is credible.
• Real tenders still demand declarations, prudence/non-disclosure forms, and compliance matrices that vary by buyer.
• Secure hosting and vendor-security posture will matter early because defence customers will compare the startup to established compliance vendors.

The direct category is still thin, but adjacent competition is intense. Intelic proves buyer-side procurement marketplaces can become a new distribution channel; JAGGAER and similar suites own generic public-procurement workflow; Govini shows defence acquisition software can command real budgets; tender portals like Mercell move discovery and compliance artifacts; and many OEMs will default to internal document stacks plus consultants. The startup wins only if it becomes the neutral evidence layer across multiple marketplaces, tenders, and command-software environments.

Why incumbents do not win by default

• Buyer-side marketplaces. Marketplaces like Intelic BASE can aggregate supply and buyer demand, but they do not automatically author or maintain the reusable supplier evidence package that OEMs need across multiple ministries; the startup can sit underneath them as the neutral passport layer.
• Public procurement suites. Suites such as JAGGAER are strong at compliant workflow and supplier management, but they are generic and do not encode drone-specific interoperability tests, C2 compatibility, or defence-grade product claims.
• Defence acquisition software. Govini shows budgets exist for defence software, yet its wedge is government-side acquisition intelligence and workflow, not helping small OEMs produce auditable product passports for European cross-ministry sales.
• Tender portals and in-house processes. Portals and consultants help respond to one opportunity at a time, but they do not compound a reusable corpus of annexes, proofs, and test results; the startup can win if reuse rates improve materially after the second or third ministry bid.

This company should start as the supplier-side procurement passport for sub-200-person European ISR and FPV drone OEMs that are expanding beyond one home-market ministry. The immediate pain is not drone discovery; it is the repeated, engineer-heavy work of assembling ministry-specific technical annexes, security documentation, and interoperability proof every time a new buyer appears. Intelic's BASE launch is useful validation because it shows procurement is moving into software-led comparison workflows, but the researched gap remains the supplier evidence layer underneath that workflow. The first product should therefore focus on reusable product passports, buyer-specific tender packet generation, and auditable interoperability evidence for a small set of recurring ministry corridors rather than on a broad marketplace or generic proposal software. Go-to-market should be founder-led and service-assisted around live tenders, because the research shows trust, deployment posture, and bespoke annexes are the main early adoption blockers. The strongest proof point is a first customer that cuts submission-prep time materially and reuses a majority of evidence across a second ministry bid without pulling engineering into the full process again. The biggest disconfirming risk is that ministries remain too bespoke for software reuse to matter, which would turn the business into low-margin services. Market demand is real, but the initial software TAM is modest and direct willingness to pay for a standalone passport product is still unproven, so the company should be run as a narrow wedge with explicit expansion into testing, ongoing compatibility evidence, and broader autonomous-systems qualification only after beachhead pull is demonstrated.

Problem

• Cross-border defence-drone sales force small OEMs to rebuild technical annexes, security declarations, and interoperability claims for each ministry from Word, Excel, PDFs, and engineer screenshots.
• Buyer-side marketplaces, tender portals, and consultants help discover or submit bids, but they do not create a reusable, auditable system of record for supplier evidence across ministries.

Solution

• Create a procurement passport that ingests a drone product line's specs, manuals, references, security paperwork, and test results into a structured evidence model with version control and permissions.
• Generate ministry-specific listing and tender packets from that evidence core and attach standards-aligned interoperability proof for common C2 and mission-data workflows.

Why we win

• The wedge is narrower than a marketplace: win the supplier workflow that recurs before every cross-border bid, where reuse and time savings are measurable after the second ministry sale attempt.
• Defensibility comes from accumulated annex mappings, interoperability test history, and buyer feedback across multiple ministries and software environments, not from generic document automation.

Milestones

flowchart LR
  Wedge[Live tender passport for one drone line] --> MVP[Structured evidence and packet generation]
  MVP --> Proof[Shorter bid prep and higher evidence reuse]
  Proof --> Expansion[More lines, more ministries, interoperability layer]

Founding team

Experiment roadmap

Risk assessment

What must be true

• At least 60% of required supplier evidence is reusable across two target ministry workflows for the same product line.
• OEM capture leaders will pay from sales or capture budgets before a procurement hub mandates the passport.
• EU-hosted single-tenant deployment is acceptable for the majority of early customers handling unclassified but sensitive material.
• Interoperability evidence is becoming part of supplier qualification rather than remaining only a post-award integration task.
• A neutral passport layer can partner with marketplaces and C2 vendors instead of being displaced by them.

Open diligence questions

• Which two ministries share the highest overlap in annexes and declarations for small-UAS bids?
• What do OEMs spend today on consultants, engineering time, and bid operations for one cross-border submission?
• How often does a second ministry bid happen within 12 months for the target OEM profile?
• What deployment posture do the first five serious prospects require before uploading sensitive technical evidence?
• Will Intelic, framework operators, or C2 vendors expose onboarding points that make the passport part of their workflow?

Model sanity

• Revenue engine. Base-case revenue is driven by growth from 4 to about 15 active product lines at roughly $81.6K blended annual revenue per line through founder-led live-tender sales.
• Must go right. Paid pilots have to convert into annual subscriptions after a second-bid reuse event or CAC stays too high for the model to scale.
• Model breaks if. If ministries remain bespoke and the model shifts to the downside case, cash falls to about $69K before seed-ready proof points are reached.
• Next-round proof. The next round is justified once Intelic shows 8-12 active product lines, first partner-backed interoperability evidence, and gross margin sustainably above 65%.

Scenarios

Sensitivity

flowchart LR
  Leads[Target OEM accounts] --> Pilots[Paid live-bid pilots]
  Pilots --> ActiveLines[Active product lines]
  ActiveLines --> Revenue[Subscription + evidence revenue]
  Revenue --> GrossProfit[Gross profit]
  GrossProfit --> Cash[Ending cash]

Flags: The model relies on a high blended ARPU relative to research's ~$50K line estimate, justified only if onboarding and interoperability packages attach consistently. · Revenue per FTE remains below typical SaaS benchmarks by Y3, which argues for holding the team lean until proof of repeatability is stronger. · Monthly churn is a heuristic because renewals and second-bid reuse have not yet been observed in the market. · Cash stays positive in the base case, but the downside case leaves almost no room for sales-cycle slippage or an on-prem deployment requirement.

• Ministry requirements stay too bespoke. If each ministry keeps unique document formats and review logic, standardization value could be weaker than expected. Mitigation: Start with the repeating 60-80% of supplier evidence, then layer country-specific templates and service-assisted onboarding for the first markets.
• Platforms or primes bundle the feature. A procurement hub or large defense integrator could add basic supplier-document tooling. Mitigation: Win as the neutral system of record across multiple hubs and command-software environments before any one platform can lock the market.
• Defense data trust barrier. OEMs may resist uploading sensitive technical artifacts to a startup system. Mitigation: Offer EU-hosted and on-prem deployments, strict field-level permissions, and workflows that avoid storing classified payload data.