Scaling Drones into Fleet Infrastructure

Diving deeper into

Orest Pilskalns, CEO of Skyfish, on building autonomous drone infrastructure

Interview
Within six months, they bought a fleet of 50 and that was for several million dollars.
Analyzed 3 sources

This kind of jump from a $500K pilot to a 50 drone fleet shows that Skyfish was not selling a gadget, it was clearing a qualification gate inside a large agency. Once the demo proved the drone could carry the required sensor, survive field use, and fit a specific ISR workflow, the buyer moved from testing a few units to standardizing on a deployable fleet. That is how drone hardware turns into a multi million dollar program instead of a one off purchase.

  • The concrete signal in the story is speed of expansion. The agency first bought six or seven drones for about $500K, then expanded to 50 within six months, and later placed another fleet order. That pattern matches fleet procurement, where a successful pilot gets scaled across teams and mission sets.
  • What unlocked the deal was full stack control. Skyfish says it could integrate a hard to source sensor in six weeks because it controlled the firmware, controller, and data flow. For government buyers, that matters more than broad flexibility, because many teams want a fixed mission setup they can deploy repeatedly without swapping parts.
  • This also places Skyfish in a distinct lane from autonomy first players like Skydio. Skydio has built a larger business around self flying drones for public safety, defense, and industrial inspection, while Skyfish is leaning into high end engineering and mission specific inspection workflows where sensor quality, ruggedness, and measurement accuracy drive the purchase decision.

The next step is more buyers treating drone purchases like fleet infrastructure, not pilot projects. As restrictions on Chinese drones keep pushing agencies and infrastructure operators toward domestic vendors, the winners are likely to be companies that can turn one successful field deployment into repeat fleet rollouts, then layer in recurring software and autonomous dock networks on top.