The Commercial-First Playbook Has Limits

The strategy is now well understood: build a product for the commercial market, achieve scale and cost advantages a defense-only company never could, then sell the same technology to government at a price the traditional supply base cannot match.

It has produced genuine winners, and it has become the default assumption for a large number of ventures that should not be using it.

Why it works when it works

The logic is sound in specific conditions.

Commercial markets are larger, so volume drives cost down. Commercial development is faster, so capability advances more quickly than a programme of record can. And a company with commercial revenue is not dependent on a budget cycle, which means it can afford to wait out a procurement timeline that would kill a pure-play defense startup.

Where the government need is genuinely a subset of a large commercial need — computing, connectivity, certain sensors and components, logistics software — this is simply a better way to build the company.

Where it quietly fails

When the requirement is actually different. Hardening, environmental extremes, resistance to jamming or interference, operation without connectivity. Commercial products are not built for these, and the modification is frequently a redesign rather than an adaptation.

When the volume is not there. The cost advantage depends on commercial scale. A company with modest commercial revenue claiming a cost advantage over incumbents has the story without the mechanism.

When nobody in the company knows how to sell to government. Commercial success does not transfer. The company arrives with a superior product, no relationship with a programme office, no understanding of the budget calendar, and an assumption that being better will be sufficient. It is not.

When the commercial business objects. Defense revenue brings compliance obligations, security requirements, and constraints on hiring and investment that the commercial side experiences as friction. This tension surfaces internally more often than founders expect.

The reverse path is underrated

Building for government first and commercialising later is treated as the inferior strategy. In some categories it is the correct one.

Government customers will fund development of capability that has no commercial market yet. They tolerate long timelines. And a company that has cleared the compliance and certification bar has an asset that commercial entrants will need years to replicate.

The risk is becoming a services business — profitable, stable, and permanently sized to the contracts in hand. That is a real outcome, not a failure, but it is a different company from the one most founders set out to build, and it should be chosen rather than drifted into.

Questions worth asking

Is the government version the same product, or a redesign?

Where does the claimed cost advantage actually come from — volume, or an assumption about volume?

Who on this team has closed government business, and when?

What does the commercial business give up to serve the government one?

If the government opportunity vanished, is this still a good company?

That last question is the most clarifying one in the category. A commercial-first company should be able to answer yes without hesitation. If the answer is no, it is a defense company with a commercial story attached, and it should be underwritten as one.

The read

Neither direction is inherently right. What matters is whether the company chose deliberately and structured accordingly.

The failures in this category are rarely strategic mistakes made once. They are a default assumption that was never examined, discovered in year three when the two halves of the business start pulling against each other.