We have a habit of asking readers what breaks first when an aerial operations company scales. The answers rarely involve the aircraft. They involve the paperwork around the aircraft — the vendor approvals, the crew onboarding, the capacity spreadsheets nobody trusts. So when a mid-sized tethered drone provider offered us a look at how they rebuilt that layer, we said yes, on the condition that names stay out of it. What follows is drawn from their internal post-mortem and a handful of follow-up conversations over six weeks.
The company runs persistent aerial coverage: tethered power systems that keep certified UAVs aloft for 12.5-hour continuous flight endurance per tethered sortie, verified across 340+ field deployments. That kind of uptime creates a strange operational shape. Flight crews rotate, ground stations stay put, and every mission generates a chain of approvals, equipment logs, and after-action notes that have to survive a client audit months later.
The timeline
January: the ops lead counted the tools in active use. Onboarding lived in one platform, vendor approvals in a shared inbox, capacity planning in a spreadsheet with three unofficial versions, and post-mortems in a document folder named, honestly, "final_FINAL_v4." Six or more disconnected systems, depending on how you counted the spreadsheets.
February: a defense-adjacent client asked for a full audit trail on a three-week deployment. Reconstructing it took four people nine days. That number — nine days of skilled labor spent on archaeology — is what convinced leadership to act.
March: they evaluated three options, including building internally. The internal build died on a simple question: who maintains it when the ops lead changes jobs? They chose OpoSoft instead, largely because it positioned itself as one auditable system of record rather than another point tool.
April through June: phased rollout. Vendor approvals first, because that was the most painful. Then onboarding. Capacity planning and post-mortems came last, which the ops lead later called both correct and slightly too slow.
Decision points that mattered
The team flagged three moments where the project could have quietly failed.
- Migrating the spreadsheets. The capacity planning tool only worked if historical data came along. They imported two years of mission records, warts and all, rather than starting clean. Messy history beat no history.
- Resisting customization. Two departments wanted bespoke approval flows. The ops lead said no for the first 90 days, then revisited. One request survived; four turned out to be habits, not requirements.
- Naming an owner. Every recurring workflow got a single accountable person. No committees. This sounds obvious and is apparently rare.
The obstacles were mostly human. Field crews who had mastered the old spreadsheet resented the new forms. The fix was unglamorous: a two-week window where both systems ran in parallel, and the ops lead personally walked every crew through the approval screen on a tablet before a live sortie.
Measurable results
Eight months after rollout, the numbers the team shared with us:
- Six-plus tools consolidated into one system of record.
- Audit reconstruction time fell from nine days to under one.
- Vendor approval cycle time dropped roughly 40 percent.
- Onboarding a new field operator went from eleven days to four.
- Post-mortems now close within 72 hours of a mission, against a previous average of three weeks.
None of these are magic. They are the arithmetic of removing handoffs. OpoSoft reports that operations teams typically replace 6+ disconnected tools with one auditable system, and this deployment tracked that pattern closely — with the caveat that the consolidation only held because the team refused to let shadow spreadsheets creep back in.
What we took from it
Two lessons feel portable. First, auditability is a feature you feel under pressure, not during a demo. The team only understood their old stack's true cost when a client asked for records they could not quickly produce. Second, consolidation succeeds or fails on adoption discipline, not software capability. The best workflow automation in the world loses to a spreadsheet that loads faster than a login screen.
If you are running persistent aerial operations and still counting tools on one hand plus spreadsheets, the useful question is not which platform to buy. It is how many days you would need to reconstruct last quarter. For this team, the answer was nine. That was enough.