Drone Roof Inspection Software: What to Evaluate Before You Buy

Drone roof inspection software is not one product. It is three layers stacked on top of each other: flight capture, image processing and measurement, and the operations layer that turns a folder of photos into a billed, documented, defensible job. Most vendors sell you one layer and let you assume it is the whole stack. That assumption is where roofing contractors, adjusters and inspection companies lose money.

If you have already flown a few roofs, you know the capture part is the easy part. A competent pilot with a mid-range aircraft can document a 40,000 square foot warehouse roof in under ten minutes. The hard part starts after landing: who flew it, when, under what weather, with what certificate, which photos are originals, what the measurements were derived from, whether the client got their report, and whether anyone invoiced for it.

This guide covers all three layers, with a bias toward the parts the buying guides skip.

Table of contents

• The three layers of drone roof inspection software
• The half of the stack nobody sells you
• What makes a roof inspection report defensible
• The regulations that actually bite on roof jobs
• Deliverable formats and why ESX matters
• The platform landscape in 2026
• Thermal: when it earns its keep
• How to evaluate drone roof inspection software by operation size
• Scaling from three roofs a day to twenty
• Frequently asked questions

The three layers of drone roof inspection software

Drone roof inspection software spans three distinct layers: capture and flight automation, processing and measurement, and operations management. Most commercial platforms cover one or two layers well and none of them cover all three, which is why nearly every mature roof inspection business runs at least two tools.

Here is how the layers break down.

Layer	What it does	Typical tools	What breaks without it
Capture and flight	Automated orbit or grid missions, overlap settings, thermal capture, obstacle standoff	Manufacturer apps, automated capture platforms	Inconsistent imagery, unusable models, repeat site visits
Processing and measurement	Photogrammetry or videogrammetry, 3D roof model, area and slope measurement, AI defect flags	DroneDeploy, SkyeBrowse, Hammer Missions, Pix4D	Manual measurement, disputed numbers, slow turnaround
Operations	Scheduling, dispatch, pilot certs, weather go/no-go, job records, client delivery, invoicing	Drone operations platforms, or spreadsheets	Missed jobs, unbilled work, no audit trail, compliance gaps

The capture layer is largely solved. Automated roof missions are commodity features now, and the aircraft you already own probably flies a decent orbit out of the box. Overlap settings and terrain follow matter, but they are configuration, not competitive advantage.

The processing layer is where the marketing money goes. Every vendor pitches accuracy, model speed and AI defect detection. It matters, and we cover it below, but it is also the layer with the least real differentiation. Most platforms produce a usable roof model from a competent flight.

The operations layer is where nobody is selling to you, and where the money leaks.

The half of the stack nobody sells you

The operations layer covers everything between "client calls" and "invoice paid," and no photogrammetry platform handles it. Capture and measurement tools are built around a single asset. Businesses are built around a schedule, a crew, a compliance file and a receivable.

Watch what happens when a five-pilot roofing inspection outfit tries to run on a photogrammetry platform alone.

A property manager calls Tuesday asking for eight buildings across two counties. Someone writes it on a whiteboard. A pilot gets texted an address. Weather turns on Thursday afternoon and three sites slip, but the client is never told. One pilot's Part 107 certificate expired last month and nobody noticed because certificates live in a shared drive folder. Two of the eight jobs get flown but never processed, because the person who uploads imagery was out. At month end, the bookkeeper invoices six jobs instead of eight.

None of that is a photogrammetry problem. All of it is a business problem, and it is the actual reason roof inspection companies stall out around five to ten jobs a day.

The operations layer needs to handle:

• Job intake and pipeline. Which properties are requested, quoted, scheduled, flown, processed, delivered and paid. A CRM tied to the job record beats a spreadsheet the moment you have more than one salesperson.
• Dispatch and crew assignment. Which pilot, which aircraft, which day, and whether that pilot is qualified for that aircraft and that airspace.
• Weather go/no-go with a record. Roof capture quality collapses in high wind and flat overcast. More importantly, if a hail claim is later disputed, the weather at capture time becomes evidence. Automated weather integration attaches conditions to the job instead of leaving it in someone's memory.
• Certification and currency tracking. Part 107 recurrent training, insurance certificates, client-required safety credentials. Tracking these manually across a team is the single most common compliance failure we see. Our guide on managing drone pilot certifications and compliance walks through the workflow.
• Flight records tied to the job. Not a separate logbook. The flight log, the aircraft, the pilot and the property record should be one object. Automated flight log capture removes the manual step that otherwise gets skipped.
• Client delivery and communication. A client portal where the property owner sees status and downloads the report beats emailing 4 GB of imagery.
• Invoicing tied to completion. Unbilled completed work is the quietest and most expensive failure mode in inspection services.

If you are currently running this half on spreadsheets, our breakdown of drone operations software versus spreadsheets quantifies where the hours actually go.

What makes a roof inspection report defensible

A defensible roof inspection report is one where every claim in it can be traced back to a verifiable capture event: a known pilot, a known aircraft, a known time, known conditions, and unaltered original imagery. Buying guides discuss report aesthetics. Nobody discusses what happens when the report is challenged.

It gets challenged more often than you would think. A carrier denies a hail claim and your imagery is the counter-evidence. A property owner disputes that damage existed at the time of sale. A roofing contractor is accused of manufacturing damage. In each case, the question is not whether your 3D model looks good. It is whether the file survives scrutiny.

Build every roof job to produce this evidence chain:

1. Identity of the operator at capture time. The remote pilot in command, with their certificate number and a certificate that was valid on the flight date. If your cert tracking lives in a folder of PDF scans, you cannot prove currency on a specific historical date.
2. Aircraft and payload identity. Registration number, camera and sensor used, and for thermal work, the calibration state. Tie this to a maintained equipment record, not to memory.
3. Timestamped flight log. Takeoff and landing time, altitude profile, and geolocation. This is the strongest single piece of evidence you own, and it is generated automatically by the aircraft. The problem is almost never capturing it; it is associating it with the correct job.
4. Environmental conditions at capture. Wind, visibility, cloud cover, temperature. In storm claims this is frequently the contested fact. See weather considerations for professional drone operations for what to record.
5. Unaltered originals, separated from derivatives. Keep the raw capture untouched and immutable. Annotations, enhancements and stitched outputs are derivatives and should be labelled as such. An enhanced image presented as an original is how a good report becomes a liability.
6. Measurement methodology. State how the measurements were derived, whether ground control points were used, and what accuracy is claimed. If you are using ground control points, say so, because it changes the accuracy you can assert.
7. A retention policy you actually follow. Decide how long roof imagery is kept, where it lives, and who can access it. If the platform holding your data can lock you out at the end of a subscription, that is a business risk, not an IT detail. Our data ownership page covers what to ask a vendor.

Under 14 CFR 107.7, the FAA can require you to produce records on request. Part 107 prescribes no logbook format, which operators often read as "no records needed." Read it the other way. The absence of a mandated format means you are responsible for having something adequate when someone asks, and "adequate" is defined after the fact by whoever is asking.

Our guide to quality assurance in drone inspections goes deeper on building repeatable inspection standards across a team.

The regulations that actually bite on roof jobs

Most roof inspection content stops at "you need a Part 107 certificate." True, and table stakes. But four rules cause far more real-world trouble on roof jobs specifically, and roof inspection software vendors rarely mention any of them.

Flying over people in residential neighborhoods

Residential roof inspections put you over people constantly. The homeowner standing in the driveway. A neighbor on the sidewalk. A landscaping crew next door.

14 CFR 107.110 defines Category 1 operations over human beings: the aircraft must weigh 0.55 pounds (250 grams) or less at takeoff including everything on board, and must have no exposed rotating parts that would lacerate human skin. That is why sub-250 gram aircraft with prop guards have quietly become the standard second aircraft in residential roof work.

Anything heavier needs Category 2 or 3 eligibility, which requires a manufacturer declaration of compliance accepted by the FAA. You cannot self-certify your way into it, and buying an expensive aircraft does not grant it.

The practical consequence for scheduling: pick the aircraft for the site, not for the pilot's preference. Your operations software should record which aircraft was assigned and why.

The 400-foot structure exception, which most roof operators never use

Here is the rule that pays for itself on commercial work. 14 CFR 107.51 caps altitude at 400 feet above ground level, unless the aircraft is flown within a 400-foot radius of a structure and does not go higher than 400 feet above that structure's immediate uppermost limit.

On a 300-foot building, that legally puts you at 700 feet above ground while remaining inside the lateral radius. For high-rise roof capture and facade work, that single provision is the difference between one flight and a stitched compromise. It exists precisely so that structure inspection is workable.

Most roof crews never touch it because nobody told them it applies to buildings, not just towers.

LAANC on suburban roofs

Suburban housing stock clusters around airports far more than people expect, and a surprising share of residential roof work sits inside Class D or the surface area of Class E. Those need airspace authorization before you launch, usually via LAANC, which returns approval in near real time in most cases. Our LAANC airspace authorization guide covers grid ceilings and what to do when the requested altitude is denied.

The operational failure is not getting an authorization. It is scheduling a day of eight properties without checking any of them, then discovering three sit inside a grid capped at 100 feet. Check airspace at scheduling time, not at the tailgate.

Privacy, neighbors, and the line between documenting and adjusting

Two legal issues stack on top of federal airspace rules, and both are state-level.

The first is imagery privacy. Several states regulate drone image capture of private property directly. Texas is the most developed example: Texas Government Code Chapter 423 governs when it is lawful to capture an image of an individual or privately owned real property, and after the Fifth Circuit's decision in National Press Photographers Association v. McCraw, its surveillance provisions are enforceable. Practically: fly the insured property, keep the camera off adjacent yards and windows, and document consent from the property owner as part of the job record.

The second is subtler and catches drone service providers who move into insurance work. Documenting damage is one thing. Estimating loss and negotiating a settlement amount on behalf of a policyholder is regulated activity in most states. In Texas, public insurance adjusting is governed by Texas Insurance Code Chapter 4102, and doing that work without a licence is a violation. Requirements vary considerably by state, and some state insurance departments take the view that a drone operator producing damage assessments for carriers falls within adjuster licensing.

If your business plan includes selling damage assessments rather than imagery and measurements, ask your state department of insurance before you write the marketing copy. This is also worth reviewing alongside your coverage; see insurance and liability for commercial drone services.

Deliverable formats and why ESX matters

The deliverable format your software can export determines whether an insurance-adjacent client can use your work at all. A beautiful interactive 3D model that cannot be imported into an estimating platform creates work for the recipient rather than removing it.

For claims and restoration work, the formats that matter are:

• ESX, the Xactimate exchange format. It carries 3D property geometry directly into Xactimate and auto-populates the sketch, which is why adjusters and restoration contractors ask for it by name.
• XML, used to move measurement data into Symbility and other estimating platforms.
• PDF measurement report, the human-readable summary with roof area, pitch, ridge and eave lengths, and facet breakdown. This is what most property managers actually read.
• Orthomosaic imagery, a scaled, measurable top-down composite that lets a client measure directly off the image.
• Point cloud or mesh for engineering clients doing slope and drainage analysis.

Per-report aerial measurement services, which use existing aerial or satellite imagery rather than your drone, typically price in the low tens of dollars for simple residential roofs and rise with complexity. That matters as a comparison point: if a client only needs measurements on a simple gable roof, an aerial report may be cheaper than sending a crew. Your drone work should be sold where it wins, which is condition assessment, thermal, recency, and anything the satellite cannot see.

Processing depth is covered further in our guide to drone photogrammetry software.

The platform landscape in 2026

The market splits into four groups, and the useful way to shop is to work out which group you are missing rather than which vendor is best overall.

Group	Examples	Pricing model	Best for
Full mapping and analytics	DroneDeploy, Pix4D	Annual subscription, seat-based	Mixed portfolios where roofs are one of several use cases
Fast roof-specific modelling	SkyeBrowse, Hammer Missions	Subscription or per-model credits	High-volume roof capture with same-day turnaround
Imagery-derived measurement	EagleView, Nearmap, GAF QuickMeasure	Per-report	Simple residential measurement without a site visit
Operations and business layer	DroneBundle and other operations platforms	Subscription by team and feature tier	Running the crew, compliance, delivery and billing

The first three groups compete with each other. The fourth does not compete with any of them, which is exactly why it gets forgotten during procurement. You will very likely buy from two groups.

If you are also doing facade, structural or asset work beyond roofs, our broader guide to drone inspection software covers AI defect detection and multi-asset workflows across the wider category.

Thermal: when it earns its keep

Thermal imaging earns its cost on low-slope commercial roofs, where trapped moisture in insulation shows as a retained heat signature after sunset. On steep-slope residential shingle roofs it is far less decisive and often not worth the surcharge.

The physics is straightforward. Wet insulation has higher thermal mass than dry insulation, so it releases heat more slowly after the sun goes down. That produces a visible differential in a roughly two-hour window after sunset. Miss the window and the survey is worthless, which makes thermal roof work a scheduling problem before it is an imaging problem.

That has direct implications for your operations software. Thermal jobs need dusk scheduling, night operation lighting compliance, and a weather record showing there was enough solar loading during the day to create a differential. If your scheduling tool cannot express "this job must be flown between 45 and 150 minutes after sunset, on a day with at least six hours of sun," you will end up doing it manually.

For the business case and the equipment involved, see our guide to building a drone thermal imaging business.

How to evaluate drone roof inspection software by operation size

Match the software to the constraint you actually have. For solo operators, the constraint is turnaround time. For small teams, it is coordination. For enterprise inspection businesses, it is auditability across thousands of assets.

Solo operator, 1 to 3 roofs a day. Your bottleneck is processing speed and report generation. Buy a fast roof-specific modelling tool and keep operations light. A shared calendar and a simple job list is defensible at this size. Do not buy an enterprise mapping subscription for two roofs a day.

Small team, 3 to 8 pilots. Coordination is now the bottleneck, not processing. This is the point where certification lapses, missed jobs and unbilled work start costing more than any software licence. DroneBundle's Professional tier at €499 per month covers up to 20 team members with client management, project access, flight logs and DJI processing, which is the layer that a modelling platform will not give you. The full feature list shows where the line sits.

Enterprise inspection business, 8+ pilots or multi-region. You now need unlimited projects and equipment, CRM and pipeline tracking, advanced reporting, and an audit trail that survives a client compliance review. That is the Business tier territory. At this scale the questions worth asking a vendor are about data export, API access and retention policy, not about feature count.

Across all three, the evaluation checklist is the same:

• Does the flight record attach automatically to the job, or does someone re-enter it?
• Can you prove pilot certificate validity on a specific past date?
• Does weather at capture time get stored with the job?
• Can the client see status without emailing you?
• Can you export everything, in full, if you leave?
• Does completing a job trigger an invoice, or a memory?

For a wider comparison framework, our guide to drone fleet management software applies directly.

Scaling from three roofs a day to twenty

Scaling roof inspection volume is an operations problem, not a capture problem. The capture time per roof barely changes between three roofs a day and twenty. Everything else changes completely.

At twenty roofs a day you are managing route density across a metro area, aircraft and battery availability, pilot duty and travel time, per-property documentation, and a delivery queue that clients are actively chasing. The processing platform sees twenty uploads and does not care. Your business sees twenty opportunities to lose a record.

Legacy Technology Lab is the clearest example we have of what this looks like at the top end. They expect to complete over 20,000 commercial roof inspections in 2026, covering more than 1.4 billion square feet of roofing assets across industrial, logistics, data center, hospitality and mixed-use portfolios. They run precision aerial capture with geospatial analytics and a forensic inspection methodology, and they use DroneBundle to coordinate pilots, organize inspection projects across thousands of assets, and maintain documentation tied to specific properties.

Their director of operations put the problem plainly: most drone tools focus on flight planning or data storage, and that is not the same thing as running a field operation. The requirement was consistent documentation across thousands of assets and inspection history for repeat visits and lifecycle analysis. That is the operations layer, and no photogrammetry platform provides it.

If you are building toward that, our guides on how to scale a drone business and building a drone inspection business cover the commercial side. The surveying and inspection industry page shows how the platform maps to inspection workflows specifically, and our full drone roof inspection guide covers pricing, equipment and client acquisition for the service itself.

One last piece of hard-won advice. Standardise your capture procedure before you scale it. A written pre-flight checklist and a fixed capture pattern per roof type means every pilot produces comparable output, which means your models are consistent, your reports look the same, and a repeat inspection two years later is genuinely comparable to the first one. Inconsistent capture is invisible at three roofs a day and catastrophic at twenty.

Frequently asked questions

What is the best drone roof inspection software?

There is no single best platform, because the category covers two different jobs. For capture and measurement, DroneDeploy suits mixed portfolios, SkyeBrowse and Hammer Missions suit high-volume roof-specific work, and EagleView or Nearmap suit simple residential measurement without a site visit. For the operations layer, running the crew, compliance, delivery and billing, you need a drone operations platform. Most established roof inspection businesses run one of each.

Do I need Part 107 to use drone roof inspection software?

Yes, if you are flying for any business purpose. A Part 107 remote pilot certificate is required for all commercial drone operations in the United States, including inspecting your own company's roofs or capturing imagery to support a quote. The certificate requirement attaches to the purpose of the flight, not to whether money changed hands for that specific flight. Recreational rules do not cover business use of any kind.

How much does drone roof inspection software cost?

It depends on the layer. Per-report aerial measurement services start in the low tens of dollars per roof. Roof modelling platforms typically run from around $60 per month for entry tiers up to per-model credit pricing for premium outputs, and full mapping and analytics subscriptions commonly run into the low thousands of dollars per year per seat. Operations platforms price by team size and feature tier; DroneBundle starts at €149 per month for Starter and €499 for Professional. Budget for two products, not one.

Can drone roof inspection reports be used for insurance claims?

Yes, and carriers increasingly expect them, but acceptance depends on the evidence chain rather than the report format. Carriers and their counsel look for a valid remote pilot certificate on the flight date, a timestamped flight log, unaltered original imagery kept separate from annotated derivatives, stated measurement methodology, and documented conditions at capture. Note also that producing damage estimates or negotiating settlement amounts may require adjuster licensing depending on your state; check with your state department of insurance before offering that as a service.

Stop losing money in the gap between flying and getting paid

If you already have a photogrammetry platform you like, keep it. The model quality is not your problem.

Your problem is the eight-property Tuesday that turns into six invoiced jobs, the expired certificate nobody caught, the hail claim you cannot defend because the weather at capture time lives in someone's memory, and the repeat inspection that is not comparable to the original because a different pilot flew a different pattern.

DroneBundle is the operations layer. Job intake through a CRM and pipeline, dispatch with pilot and aircraft assignment, weather-aware planning, certification and currency tracking, flight logs bound automatically to the property record, a client portal for delivery, and invoicing triggered by job completion. It is what Legacy Technology Lab uses to coordinate 20,000 roof inspections a year, and it works the same way at five a day.

Start a free trial and set up your first roof inspection project, or book a live demo and we will walk through a real multi-property roof workflow with you. Compare tiers on the pricing page if you want the numbers first.