Migration and provenance OS that gets utility drone teams off DJI without grounding inspections or tripling fleet costs.

1. Security-driven bans are turning a theoretical geopolitical concern into an immediate fleet-replacement program.
2. New DJI product restrictions create spare-parts and procurement continuity risk for teams already standardized on its aircraft.
3. Simply buying a Western brand does not remove supply-chain scrutiny because key components still come from China.
4. A 2-5x hardware premium makes software that de-risks migration and right-sizes fleet spend much easier to justify.

Catalyst. DJI is being squeezed by both Chinese and U.S. restrictions while replacements remain 2-5x more expensive and China-dependent, forcing operators to justify and execute swaps now.

The product ingests DJI flight histories, route templates, maintenance logs, and pilot records, then maps them into approved-fleet equivalents so teams do not restart operating procedures from scratch. It generates a procurement packet with component-origin attestations, security-policy mappings, and a documented gap list for any unresolved supplier exposure. The system also models mission-level economics so operators can see where they need premium aircraft versus where lower-cost compliant platforms work. Over time, the company becomes the migration and compliance layer sitting above multiple drone OEMs instead of competing as yet another hardware vendor.

What's different. This is not another drone OEM pitch. The company owns the ugly middle between field operations, procurement, and security policy by translating missions, packaging provenance evidence, and benchmarking cross-platform fleet economics. As migrations accumulate, it builds unique data on what approved hardware can actually replace specific DJI workflows, creating a defensible control layer for compliant fleet swaps.

Jobs to be done

flowchart LR
  Buyer[Utility UAS manager] --> Pain[DJI restrictions and costly replacement]
  Pain --> Product[Migration and provenance OS]
  Product --> Outcome[Approved fleet with inspections still running]

Executive takeaways

• The opportunity is real, but demand is being pulled by policy shocks and procurement reviews rather than by a clean greenfield software budget.
• Utility drone programs are already large enough that manual migration becomes painful once fleets, pilots, and inspection records have to move together.
• Incumbents split between hardware vendors and flight-ops software; the evidence base is thinner on neutral multi-OEM migration plus provenance workflows.
• Willingness to pay is helped by expensive hardware replacement, existing spend on flight/compliance systems, and the operational cost of grounding inspections.
• The biggest execution risk is not customer pain but OEM/API/data portability: if logs, route templates, or maintenance records are hard to normalize, work becomes services-heavy.
• Beachhead TAM in utilities looks modest on its own, so the investment case depends on expanding the same control layer into adjacent sovereign and critical-infrastructure fleets.

Market definition

U.S.-focused software and integration tooling for critical-infrastructure drone programs that need to migrate recurring DJI-based inspection operations onto approved non-DJI fleets while preserving mission continuity, auditability, and procurement evidence. The beachhead is electric utilities running transmission, substation, and storm-response flights; this excludes consumer drones, one-off aerial services, and hardware manufacturing.

Customer and buyer

Primary users are utility UAS program managers and flight-operations leads; economic buyers are transmission operations, asset-management, or security leaders; procurement and cyber-risk teams become co-approvers once fleet provenance and approved-equipment policy are involved.

Buying triggers

• A board, cyber, or procurement review forces a move away from DJI or freezes new DJI purchases. [2][8]
• A hardware refresh or spare-parts concern turns fleet replacement into an urgent budgeting event while approved alternatives remain materially more expensive. [2][3]
• Scaling into BVLOS, operations over people, or controlled-airspace workflows increases the documentation burden around waivers, authorizations, and operating procedures. [5][6][7][16]

Willingness to pay

The strongest willingness-to-pay evidence is indirect: non-DJI hardware is reported at a 2-5x premium versus DJI, while utilities already pay for fleet/compliance software and large programs like PG&E use dedicated operations tooling. A migration layer that compresses revalidation and procurement work can ride on that existing spend rather than invent a new budget line. [3][21][22][25]

Category dynamics

Growth signal Replacement wave likely concentrated over 24-36 months rather than a smooth market CAGR

Validation signals

• UPI and TNW both describe a real policy shock around DJI, not just speculative anti-China rhetoric.
• Dominion Energy is cited using Skydio under a BVLOS waiver for power-facility inspections, showing utilities already operate in advanced regulatory regimes.
• AirData cites PG&E and a fleet of over 120 pilots, evidence that enterprise utility-adjacent drone programs are large enough to need dedicated operations software.
• Skydio announced a $3.5B U.S. manufacturing commitment, reinforcing momentum behind domestic drone supply narratives.
• Wingtra markets NDAA and DIU approval posture directly, indicating replacement demand is already being sold on compliance as well as performance.
• FlyFreely publicly references power-sector case studies, showing dedicated governance software has already found utility-like demand.

Regulatory & technical constraints

• Remote ID applies to registered-drone operations and adds a baseline compliance requirement to any new fleet selection.
• Part 107 waivers and operations-over-people rules mean some missions cannot simply be ported without checking aircraft- and operation-specific eligibility.
• Controlled-airspace access depends on LAANC and approved UAS service suppliers, which adds another system dependency during migration.
• Approved-aircraft and provenance expectations are increasingly shaped by Blue UAS and adjacent procurement-security frameworks.
• Data portability is feasible but imperfect: existing tools import DJI logs, yet that does not guarantee full route, payload, or maintenance parity across OEMs.
• Open-source mission tooling exists, which lowers switching costs for technical teams but increases support, integration, and audit burdens.

Competition is fragmented. OEMs such as Skydio, Wingtra, Freefly, and FLIR sell the replacement aircraft; workflow vendors such as DroneDeploy, Aloft, AirData, and FlyFreely sell pieces of inspection, compliance, or fleet recordkeeping; and sophisticated teams can fall back to open-source or in-house tooling. The proposed wedge is the neutral migration-and-provenance layer that sits above those stacks.

Why incumbents do not win by default

• Drone OEMs. Skydio, Wingtra, Freefly, and FLIR can win aircraft refresh spend, but each is structurally biased toward its own hardware and does not default to being the neutral system of record for multi-OEM route portability and provenance packets.
• Inspection workflow platforms. DroneDeploy is strong on inspection workflows and visual data capture, but the fetched pages do not position it as a cross-OEM migration and procurement-attestation layer.
• Flight-ops and compliance software. Aloft, AirData, and FlyFreely already manage logs, teams, approvals, and imports, but their positioning is ongoing operations governance rather than one-time fleet transition plus provenance generation.
• Open source / in-house. QGroundControl, Mission Planner, MAVProxy, and PX4 lower software barriers, but they push integration, support, and auditability work back onto the utility or SI, which weakens them for time-sensitive approved-fleet migrations.

DJI restrictions in both China and the U.S. are turning fleet choice into a procurement and continuity issue for U.S. utility drone programs already standardized on DJI. The first customer is the UAS program manager at a mid-size electric utility that must refresh or justify a DJI fleet after a board, cyber, insurer, or procurement review. The product wedge is a software-plus-integration layer that ingests DJI logs, route templates, maintenance records, and pilot qualifications, then outputs approved-fleet equivalents plus a provenance packet for sign-off. This is a better first wedge than a general drone-ops suite because utilities already have recurring inspection routes, multi-stakeholder approvals, and enough pilots and records that manual migration becomes expensive. The research supports willingness to pay indirectly: replacement aircraft cost 2-5x more than DJI and utilities already spend on fleet and compliance software, so compressing revalidation and procurement time is budget-relevant. The utility beachhead is real but modest, with researched estimates of $20.4M SAM and $3.6M year-3 reachable SOM, so the company must prove that the same control layer expands into other sovereign and critical-infrastructure fleets. The largest disconfirming risk is that OEM APIs and exported data are too inconsistent to automate enough of the workflow, turning the business into low-margin services. Research does not yet quantify how many utilities are under active approved-equipment review today, so the first 90 days must test trigger frequency, budget ownership, and translation accuracy before scaling headcount.

Problem

• Utility drone teams adopted DJI for economics and reliability, but new sales restrictions and security reviews make that installed base a liability.
• Replacing DJI is not a simple aircraft purchase because recurring routes, SOPs, maintenance logs, pilot records, waivers, and procurement evidence all have to move together.
• Approved alternatives cost materially more and may still carry China-linked component exposure, so buyers need a defensible migration and sourcing case before budget is released.

Solution

• A migration workspace that ingests DJI and adjacent ops-system artifacts, maps them to approved-fleet equivalents, and highlights what still needs manual validation.
• A procurement packet generator that assembles component-origin attestations, policy mappings, and unresolved exceptions so security and sourcing teams can approve staged fleet replacement faster.
• Mission-level fleet economics that show where premium compliant aircraft are required and where lower-cost approved options are sufficient.

Why we win

• The company sits above OEMs and ops tools as a neutral control layer, which matches the buyer need for multi-stakeholder sign-off better than a single hardware vendor pitch.
• Each migration creates proprietary route-portability, provenance, and replacement-performance data that improves future recommendations and raises switching costs.
• The beachhead workflow is narrow enough to productize quickly because utilities already run recurring transmission and substation inspections with formal compliance records.

Milestones

flowchart LR
  Wedge[Utility DJI migration wedge] --> MVP[Artifact ingest and provenance packet MVP]
  MVP --> Proof[Paid pilots and faster procurement approval]
  Proof --> Expansion[Multi OEM compliant fleet system of record]

Founding team

Experiment roadmap

Risk assessment

What must be true

• At least 30% of contacted target utilities must report an active DJI replacement review or budgeted refresh in the next 12 months.
• The product must auto-translate enough logs, routes, and records to eliminate at least 30% of manual migration effort in the first two pilots.
• Procurement teams must accept the provenance packet as part of actual approval workflows rather than treating it as supplemental documentation.
• At least two approved OEM stacks must expose enough data and APIs to support repeatable route and record mapping.
• The company must show credible demand for the same control layer outside utilities before the utility beachhead saturates.

Open diligence questions

• How often are utilities facing mandatory approved-equipment reviews versus optional long-term refresh planning?
• Which exact data artifacts can customers export today from DJI, AirData, Aloft, and in-house systems without custom engineering?
• Who signs the first contract when the pain spans UAS operations, procurement, and cyber-risk?
• How much of the workflow can be standardized across Skydio, Wingtra, Freefly, and FLIR before services dominate?
• What evidence shows adjacent verticals will buy the same product with similar urgency?

Model sanity

• Revenue engine. Base-case Y3 revenue comes from 18 paying accounts compounding from $50K pilots into roughly $198K-$246K production accounts, not from broad SMB volume.
• Must go right. OEM and adjacent-system data has to normalize enough for gross margin to move from 60% in Y1 to about 70% steady state.
• Model breaks if. If sales cycles stretch by a quarter and ARPU lands 10% low, downside Y3 revenue falls to about $2.5M and cash cushion compresses toward $340K.
• Next-round proof. The next financing is justified by reaching 10 production utility sites, four integrations, and one adjacent paid design partner inside the pre-seed runway.

Scenarios

Sensitivity

flowchart LR
  Leads[Target utility accounts] --> Discovery[Qualified discovery]
  Discovery --> Pilots[Paid pilots]
  Pilots --> Production[Production accounts]
  Production --> Expansion[Second-site expansion]
  Expansion --> Revenue[Revenue]
  Revenue --> GrossProfit[Gross profit]
  GrossProfit --> Cash[Cash runway]

Flags: The model assumes the $2.3M pre-seed closes at the start month; without it the company runs out of cash before enough pilots convert. · Y3 revenue already leans on most of the researched utility SOM, so non-utility adjacency should be viewed as upside to the next round, not hidden base-case revenue. · Gross margin improvement is the key model risk because the research repeatedly warns that weak OEM/API portability could turn this into a lower-margin services business. · CAC and churn remain heuristic because the company has not yet observed a full renewal cohort or scaled partner-led acquisition channel.

• OEM integration gaps. If approved drone vendors expose limited APIs or incompatible formats, migration automation could stall and turn into services-heavy work. Mitigation: Start with the highest-value export and log formats, package expert-led migration services, and partner with OEMs that want accelerated replacement wins.
• Uneven policy urgency. Some operators may delay replacement if restrictions stay fragmented or grandfathered fleets remain usable for longer than expected. Mitigation: Target accounts with active security reviews and sell procurement-speed, provenance, and fleet-cost optimization rather than relying only on ban headlines.
• Compliant hardware shortages. Customers may want to switch but still struggle to source approved aircraft, batteries, or motors at scale. Mitigation: Stay hardware-agnostic, integrate multi-OEM availability data, and help customers phase migrations by route criticality instead of promising instant full replacement.