Drones integrated into agency workflows
Enterprise sales director at Skydio on drones as first responders
This points to drones being sold into government as components inside a larger workflow, not as a standalone software environment. In practice, agencies often flew Skydio hardware for capture and autonomy, then pushed maps, imagery, and incident data into existing systems like Esri, CAD, video management, evidence, or records platforms. That kept the drone useful without forcing a police department, utility, or federal team to replace the software where dispatchers, analysts, and supervisors already worked.
-
The split was roughly 50/50 between using native software and integrating outward. The main handoff was into the agency system of record, with post processing often done in Pix4D or Bentley. That suggests Skydio won deals first on flight performance and compliance, then had to fit into downstream reporting and mapping workflows already in place.
-
Esri mattered because it let agencies use their own base maps, annotations, and location layers while flying. But the stickiest integrations were deeper vertical systems, like public safety CAD and video platforms, because those are what turn a small pilot into a citywide or agencywide deployment.
-
This also explains why cloud hosting was a friction point. Many government buyers wanted data in their own private environment, not just in a vendor managed cloud. A drone vendor could not just provide capture and storage, it needed APIs, security controls, and deployment options that matched government IT rules.
Going forward, the winning drone platforms in government will look more like infrastructure than gadgets. The hardware still opens the door, especially when autonomy and domestic supply chain matter, but the larger contracts will go to vendors that can slot cleanly into dispatch, evidence, mapping, and private cloud systems that agencies already trust.