Business Case: Why Complex UAS Programs Often Fail
Updated: Oct 21
The larger (> Group 1) UAS programs that collapse usually aren’t the ones where the aircraft couldn’t perform. We’ve watched capable systems clear flight testing, earn their regulatory approvals, and prove themselves in the field, and then die anyway. The technology matured. The regulatory path held. The budget and program expectations are what failed.
That pattern doesn’t hit every program, but it repeats often enough that it’s become a fallacy baked into how the industry sees these efforts. Not every program followed this path, but even the successful ones have experienced elements of this example. Buyers keep entering believing they’ve purchased a product when they’ve actually committed to a journey, and the gap between those two things is where the money goes.
The budget was built on a story
Consider a composite drawn from real programs. A large customer envisions one-day replacing manned aircraft inspection of its sites with UAS. A provider offers a price that looks competitive against the cost of the conventional methods it would eventually retire. The operator runs a capital-cost comparison, the new number wins, and the program gets its green light.
What the operator doesn’t see is the shape of the provider’s own model. To win the work and get the first site flying, the provider prices the development, maturation, and regulatory-approval phase at a deliberate loss. The plan is to recoup that loss later, through recurring revenue once the system replicates across dozens of the operator’s locations. The opening price was never a stable unit cost. It was an entry point that only ever penciled out at full scale.
Why the provider stretched the story
Put yourself in the provider’s seat. It believed it was acting in good faith, playing a long game in which scale would eventually make everyone whole. To the customer, the distinction barely registered and didn’t matter much: this was the price it had been quoted, and that was that. But the provider still had to win the business. So it shaped the economics into something the customer could accept, a version digestible enough to sign. That was a band-aid over a wound that would never stop bleeding on its own.
Vet the company before the green light
The buyer’s defense is vetting, and not the surface kind. Before any go or no-go decision, understand who the company is: how they’re funded, how they make money, and what it has delivered before. Understand the aircraft it builds and the real complexity of the system wrapped around that aircraft system. Talk to their supply chain. Ask others in the industry about their reputation. The aim is to know exactly what you’re buying into, the company and the technology both, before you commit a dollar, instead of discovering it months/years into the program.
When the gap closes
Maturation runs longer than planned. The regulatory work, legitimate and necessary, costs more in time and people than anyone budgeted. The provider, still underwater from the first phase and bleeding faster than recurring revenue can cover, reaches the point where it either raises prices or goes insolvent. It raises prices.
The buyer, years in and already frustrated by a program that has tracked nothing like the early narrative, reads the increase as a bait-and-switch. Now it faces the worst version of a sunk-cost decision: to write off the millions already spent or press on resentful into a deal it no longer trusts. Often it walks. The system worked. The regulatory path worked. The deal structure, as each party understood it, was never survivable.
Why scale stopped covering the gap
The model lived or died on economies of scale, and scale was exactly what the unforeseen and undisclosed costs ate into. Every challenge the opening narrative left out, the regulatory work that ran long, the operational hurdles nobody flagged, chipped away at the volume math meant to rescue the program. Those costs stay buried for a while but not forever. One more delay or overrun becomes the straw that breaks the camel’s back, and the price has to move. None of this traces back to technology. It traces back to a start with no honest accounting of the maturation curve, the regulatory timeline, or the true operating costs.
Plan the program before you fund it
The fix is real planning during development, not after. Name the known challenges across three fronts up front: regulatory, operational readiness, and scaling. Each front needs its own gating criteria, its own milestone deliverables, and its own contingency plan for the day it goes sideways. What happens if regulatory approval slips two quarters? What happens if an operational-readiness milestone fails outright? How do you recover, and what does recovery cost? Those answers belong in the plan before the program is funded, because every one of those questions gets asked eventually in real time, and that’s the worst moment to be inventing the answer.
Complexity widens every gap
The UAS decides how wide these gaps get. The more capable the platform, the longer its maturation curve, the harder its regulatory case, and the deeper the upfront loss someone carries before the model breaks even. Complexity stretches the distance between the price a buyer sees and the economics a program requires. Simple platforms forgive a thin plan. Complex ones do not.
What complex means here
These larger systems aren’t simply scaled-up versions of common Group 1 sUAS. Most are either repurposed military platforms or commercial systems built under heavy military and Department of Defense influence. They typically aren’t designed to be flown by the common operator, and they were never meant to be fully intuitive. In complexity and capability, they have almost nothing in common with the small commercial UAS most buyers picture. They’re demanding machines, capable in the right hands, carrying maintenance, procedural, and attention-to-detail requirements that exceed anything the commercial small-UAS market deals with today.
Decide whether you can carry it
Mitigation starts with understanding those complexities, not in engineering detail, but in scope and magnitude: how big this really is, and how far it is from what your operators already do. From there the decision is honest, even if it isn’t easy. Is your organization prepared to take on a program of this size and difficulty? You can carry it by contracting it out, or by building qualified people internally. Either way, the skills and qualifications these aircraft demand sit in a different category from the commercial small-UAS world, and they come at a different price point. Budgeting for them as though they were the same is how the gap opens in the first place.
Why this keeps happening
By this point it's tempting to close the file on both parties: shame on the provider for selling a model that couldn't hold, shame on the buyer for not catching it, and call the whole thing a pair of bad decisions. That reading is comfortable, and it's wrong. Decisions like these get made across the UAS industry constantly, by capable people on both sides.
Start with the provider. The pressure to move aircraft is relentless, and the honest version of economics rarely closes a deal. So, the optimistic version wins by default, the revenue math gets stretched to whatever keeps the program alive, and a bleak path to real profit gets reframed as a manageable one. The model only survives if the sale closes this week, and that pressure shapes the story long before anyone sits down to be candid.
The buyer isn't a passive mark here. These organizations need to move the innovation needle. They're drawn to the most convincing and defensible narrative on offer. Ironically, the most defensible-looking narrative often comes from the provider that has invested most in looking credible, which isn't the same as being sound. Polish and durability aren't the same thing, and the distance between them is where the failure modes sit.
Both of those narratives lean on a regulatory process that carries none of the consequence. The agency setting the timeline doesn't have to make payroll on Friday. The schedule risk, and the cost of every delay, falls entirely on the two parties who do, and neither one knew how to guardrail against that from the start.
None of this is exotic. It's become the default outcome of the incentives, which is why it repeats, and why the fix must start before any of it is set in motion.
The upside is real
Read all of this back and the caution can start to sound like a verdict: too hard, too costly, not worth attempting. That’s not necessarily true. The value proposition for larger, more complex UAS is real, and when a program is built right, with the right parties and an honest plan, the return compounds. Run correctly, the dividends can be enormous.
The catch is that the margin of error is close to zero. Programs like this don't fail gracefully. The mistakes that sink them, the unmapped costs, the unvetted provider, the misunderstood UAS, the plan that assumed the easy version, get made early, and they decide the outcome long before the trouble shows. The payoff is there. It's just unforgiving about how you reach it.
Buy the vitamins early
The most useful thing a new entrant can do is talk to people who have lived this and carry the scars. Those people will give you the harsh realities while you’re still deciding go or no-go. They’ll walk you through the true cost of maturation, the real shape of the regulatory timeline, and the operating economics at every stage of scale, so the budget you build survives contact with the program.
Tactien is in the business of vitamins. We’d rather guide a program through these realities at the start, when the cost of getting it right is small, than get called in later for pain pills. If you find yourself shopping for pain pills, the program has likely already fallen into the pattern above, and the pills are an added expense layered on top of what you’ve already lost, spent to rescue something that didn’t have to get sick. Vitamins at the beginning are cheaper, and far better for the program’s odds of survival, than strong medicine after the trouble has already set in.
