Running a drone-capture business without a stack of ten tools
Talk to enough capture operators and a pattern shows up. The flying is the easy part. The hard part is everything around it: chasing the lead, writing the proposal, scheduling the shoot, processing the data, getting the deliverable approved, and collecting the money — usually across half a dozen disconnected tools.
Every handoff between those tools is a place where context gets dropped. The proposal doesn't know about the capture. The invoice doesn't know about the proposal. The customer record is a row in a spreadsheet that nobody updates after the first call. That's not a discipline problem; it's a structural one.
The capture and the customer are one object
The fix is to stop treating the imagery and the relationship as separate systems. A capture isn't a file that lives in a processing tool — it's part of a job, which belongs to a customer, which carries a proposal, a schedule, and an invoice. When the scene is the customer record, nothing has to be re-keyed from one app into another.
Concretely, that means accepting a proposal spins up the job and the deposit automatically. Processing a capture attaches the deliverable to the same job. Collecting the balance closes the loop on the record you started with. The operator sees one through-line instead of five dashboards.
Simple surface, complex core
Consolidating tools is only a win if the result is simpler, not a single app with ten times the settings. The goal is that you never learn the system — each surface is one obvious path, and the machinery (reconstruction, pricing math, e-signature audit trails) hides in the engine.
You get the drawings your trade is asked for, not a panel of SfM parameters. You get a signed proposal, not a separate e-sign subscription to reconcile. The complexity is real, but it belongs to the platform, not to your afternoon.
Keep reading
One capture pipeline: a phone, a supported drone, or a 360 camera
Universal ingest means you capture with whatever is in your hand and let the platform sort out the rest. Here's how it works and where each input shines.
Read the post →Gaussian splats vs photogrammetry: two outputs from one capture
A splat is the scene you walk through; a photogrammetry mesh and point cloud are what you measure on. You shouldn't have to choose — here's why you get both.
Read the post →Ready to turn a capture into a job?
Set up in minutes. Your first capture can be today's job.
First month free · Pay only for what you process · Cancel anytime