Conversation
Highlights

Overwatch Imaging: Why the Message That Closes Investors Will Lose You the Enterprise Deal

Before venture capital discovered defense tech, Greg Davis had one option: get customers or get out. Within months of founding Overwatch Imaging, he was under contract and delivering product. No runway to burn while searching for fit. No pitch deck substituting for proof. Just software deployed on real aircraft, in real missions, where failure had real consequences.

That constraint shaped everything about how Overwatch sells today. The company runs a roughly 50/50 split between civil and defense revenue, carries both profitability and venture backing, and has built a go-to-market approach that cuts against nearly every instinct a venture-funded founder develops.

The central lesson: the message that excites an investor will actively destroy your credibility with the operator writing the check.

In a recent episode of BUILDERS, Greg unpacked the GTM decisions behind Overwatch Imaging’s growth — why he runs two completely separate messaging tracks, how he designed an adoption on-ramp for risk-averse government buyers, and what a decade of mission-critical deployments actually buys you in a sales cycle.

Two Audiences, Two Completely Different Conversations

Most enterprise startups run one narrative. They find a story that works — usually one that leads with technology capability and market size — and deploy it everywhere. It closes investors. It gets recycled for customers.

Greg watched competitors do exactly this and watched it fail with operators. His customers pushed back directly: “We don’t need it to be AI enabled, like we just want a workload reduction.”

The distinction matters more than it sounds. An investor hears “AI-enabled” and sees a platform, a moat, a category. An operator in a mission-critical environment gets skeptical. They’ve watched vendors relabel existing products with AI branding and deliver nothing new. They’re not evaluating technology — they’re evaluating whether this tool will reduce cognitive load under pressure without introducing new failure modes.

Greg’s response was to separate the tracks completely. “There’s a different message perhaps to investors than there is to users,” he said. “Mission critical users that we serve don’t really appreciate being treated like investors.”

This isn’t a messaging tweak. It’s a company-wide discipline. The investor conversation covers platform vision, autonomy at scale, the size of the opportunity. The customer conversation covers workload reduction, operational reliability, and mission outcomes. Letting those conversations bleed into each other costs deals.

The On-Ramp as a GTM Strategy

Overwatch sells into markets defined by long procurement cycles, risk aversion, and large installed bases of existing hardware. The standard enterprise pitch — replace your current solution with ours — is a structural non-starter.

Greg’s answer was to build a go-to-market model around the on-ramp rather than the replacement. Overwatch software runs on aircraft already in service. Customers don’t retire their fleets. They don’t change their operations. They add autonomy to what they already own.

“We don’t require users to kind of throw away their whole multi-trillion dollar fleet of existing assets,” Greg explained. “We allow users this on ramp that takes the existing fielded material solutions that are out there today and give them an easy path to bring autonomy to that existing hardware.”

The GTM insight here is about correctly diagnosing the adoption barrier. Greg found that his customers already wanted autonomy — they weren’t skeptical of the outcome, they were afraid of the transition. “Users know they need to adopt this technology and they’re just sort of afraid about the potential risks or how they step into that.” The on-ramp removes the barrier without removing the desire. That’s a different problem to solve than convincing someone they need the technology at all.

How to Build Trust When Trust Is the Product

In mission-critical government markets, trust is built through deployments that worked under pressure — not onboarding flows or NPS scores.

Overwatch has been running TRL9 real-world applications for nearly the entire lifespan of the company. Close to a decade of software deployed in situations where the stakes were life-and-death. That track record is not marketing. It is the sales asset.

“Building trust in autonomous systems is a long game,” Greg said. The practical implication: every deployment that works becomes a proof point that lowers risk perception for the next deal. The compounding only works if you don’t over-promise along the way.

Greg made under-promising a cultural operating principle, not a sales tactic. “We’ve under promised and we’re going to over deliver and the tech’s going to work.” He introduces this to every new employee. If the whole team owns the promise, it shows up consistently across every customer touchpoint — the sales call, the demo, the deployment, the support interaction. Trust doesn’t come from a single great pitch. It comes from a pattern that holds over years.

The Problem Signature Filter

Overwatch operates across wildland fire, maritime domain awareness, border security, law enforcement, and defense. That looks like a broad market strategy. It isn’t.

Greg uses a tight problem signature to qualify every market: time-critical, wide-area search for small objects. Every vertical Overwatch serves matches that description. The filter came before the market selection.

This is the operative lesson for founders expanding into adjacent markets. The question isn’t “is this market large enough?” It’s “does this market have the same problem architecture as the ones where we already have fit?” A precise problem definition travels across verticals in a way that a broad market thesis does not.

What Bootstrapping in a Capital-Scarce Market Actually Bought

When Greg started Overwatch, venture capital did not fund defense tech. Bootstrapping wasn’t a philosophy — it was the only path. He was under contract delivering product within months of founding, building through services-led entry that funded early product development.

That constraint produced something durable: a company with close to a decade of real-world proof before the defense tech funding wave arrived. When venture capital became available, Greg had deployment receipts that no pitch deck could replicate. The bootstrapped years weren’t a liability. They were the moat.

For founders entering risk-averse, long-cycle markets: early revenue discipline — even through services, even at lower margins — builds the deployment history that eventually closes enterprise deals. The track record is the product, and it can only be built one deployment at a time.