What enterprise clients actually require from drone contractors — a breakdown of what changes when you move up from small commercial work
If you've been doing commercial drone work for a year or two and you're starting to look at the bigger contracts — utilities, telecom, insurance carriers, large general contractors — the requirements feel different in ways the marketing materials don't quite explain.
I've spent the last few weeks researching what's actually different and talking to operators currently doing this work. Posting what I've found in case it's useful to anyone else thinking about this move. Not selling anything, no product, just trying to map the landscape.
The pattern, simplified: small clients buy the photos. Enterprise clients buy the documentation around the photos. The technical flying may not be much harder. The administrative layer on top of it is what changes.
Five things show up in nearly every enterprise contractor specification:
1. Higher and structured insurance. $1M is fine for small commercial work. Utility and large construction contracts commonly require $2M-$5M; some specify $10M. But the dollar amount isn't the main thing that changes. Enterprise certificates require the client listed as additional insured, waiver of subrogation, specific endorsements for night/over-people/BVLOS operations, and a real aviation liability policy (not a drone rider on a general business policy — standard CGL almost always excludes aviation). App-based on-demand drone insurance usually doesn't meet these contract terms; operators discover this when their certificate gets rejected at COI review.
2. Verified personnel. Part 107 is the baseline. Enterprise clients verify recurrent training currency (the 24-calendar-month requirement), check for relevant waivers when applicable, sometimes require industry training (OSHA 10/30 for construction, NESC awareness for utility work, confined space for industrial), and for critical infrastructure work require background checks. NERC CIP-004 personnel training and access requirements come into play when you're doing work that touches Bulk Electric System assets.
3. Documented equipment. Part 47/48 registration, Remote ID serial recorded, maintenance records. For some federal and critical infrastructure work, the make and model of the aircraft is restricted — Blue UAS list or similar.
4. Specified deliverables. This is where the variation between clients gets visible. File formats (GeoTIFF, LAS/LAZ), coordinate systems (state plane with specific zone, NAD83 vs NAD2011, NAVD88), naming conventions tied to client asset IDs, metadata standards, accuracy/GSD requirements, specific submission methods. The same flight captured the same way can be accepted by one client and rejected by another because the deliverable structure differs.
5. Audit-readiness. Every job leaves a record that, six months later, can show exactly what happened — who flew, with what aircraft, under what authorization, following what checklist, with what evidence of currency. For small commercial work the deliverable IS the artifact. For enterprise work, the deliverable is one item in a documentation packet.
The pattern across industries: utilities, telecom, insurance carriers, large GCs — the specifics differ but the structure of the requirements is similar. Five things appearing repeatedly, with each client having slightly different specifics. The cumulative weight of managing all five for every job, for every client, is what makes this hard. It's not any single requirement.
What I'm learning from operators currently doing this work: the ones who handle it best have evolved their workflow to make these requirements close to invisible during day-to-day operations — encoded into templates and processes that run automatically. The ones who struggle have the technical capability to fly the missions but lose contracts at the procurement or audit stage because the paperwork doesn't quite hold together.
Genuinely curious whether this matches what others have seen. If you're doing enterprise drone work and any of this is wrong or incomplete, please correct me — I'm trying to get this right.
Particularly interested in:
- What enterprise client surprised you the most with their requirements?
- What's the requirement that took the longest to figure out how to meet?
- Which client management/documentation tools (if any) actually help vs. just adding overhead?
Happy to share what I've heard from other operators in DMs if it's useful.