Counting Warheads, Not Burn Rates: Why Defense Tech Board Metrics Need a Complete Overhaul

Most defense tech board decks look like they were built by someone who read a YC template and added the word 'government' to the customer column. Monthly recurring revenue. Net revenue retention. Customer acquisition cost. These numbers are not wrong, exactly. They are just measuring the wrong things, and in this sector, the gap between the metric and the underlying reality can cost you years.

Photo by Aseem Borkar on Pexels.

The SaaS-era board metric set was designed for a specific kind of business: one where customers churn monthly, where sales cycles are weeks long, and where the product ships as software over a wire. Defense tech businesses rarely work that way. A company that wins a $40M Other Transaction Authority contract isn't seeing that revenue for 18 months. A hardware program that hits technical readiness level 6 just made a massive advance, even if the P&L shows nothing. None of that shows up in a standard ARR slide.

So what should defense tech boards actually be tracking?

Contract Vehicle Diversification

Government customer concentration is a known risk, but boards often treat it as a binary: do you have more than one customer? The real question is how many distinct contract vehicles your revenue sits on. A company with $20M across three SBIRs has fragile revenue. A company with $20M split between a DIU Prototype OTA, a direct Army contract, and a small Air Force SBIR Phase II has something that looks more like a real portfolio. Vehicle-level diversification tells you far more about program survival risk than customer count alone.

Technical Readiness Level Velocity

TRL movement is a leading indicator that almost no board deck includes. If a hardware company entered the year at TRL 4 and is now at TRL 6, that's a significant funding and transition milestone cleared, even if zero revenue has been recognized. VCs who ignore TRL progression and only watch cash burn are essentially flying blind on the most capital-intensive part of the business. Track TRL by major subsystem, not just the headline number. The weakest subsystem is always the one that causes program slippage.

Program of Record Proximity

This is the defense tech equivalent of pipeline stage. How close is each customer engagement to a Program of Record inclusion or a LRIP decision? Boards should see a simple map of where each government engagement sits in the acquisition lifecycle, updated every quarter. Here's a rough version of what that can look like:

graph TD
    A[SBIR / BAA Award] --> B(OTA Prototype)
    B --> C{Transition Decision}
    C --> D[Program of Record Inclusion]
    C --> E[/Effort Abandoned/]
    D --> F((LRIP / Full Rate Production))

Most companies stall at the transition decision node and never tell their boards clearly. The diagram forces the conversation.

Clearance Capacity Utilization

If your portfolio company has a Facility Clearance, that clearance has a capacity ceiling based on the number of cleared personnel and the level of classified work authorized. A company running at 90% of cleared-personnel capacity with three classified contract bids in the pipeline has a hiring bottleneck that will directly constrain revenue growth over the next 12 months. Boards should see this number. Almost none do.

ITAR and Export License Pipeline

For dual-use companies pursuing international sales, the export authorization queue is a revenue timing risk that rarely gets a dedicated board slide. Directorate of Defense Trade Controls processing times have stretched considerably in recent years. If you have $8M of international ARR dependent on DSP-5 licenses sitting in review, your Q3 revenue forecast has a serious asterisk. Track the number of pending applications, their submission dates, and the expected decision windows. That slide saves a lot of awkward quarterly calls.

None of this means abandoning standard financial metrics. Cash runway still matters. Gross margin still matters. The point is that financial metrics alone tell an incomplete story for businesses operating inside the defense acquisition system, where the distance between technical achievement and revenue recognition can span multiple fiscal years.

Boards that only look backward at recognized revenue will consistently misread the health of their defense tech companies. The companies worth backing are the ones generating observable progress across the acquisition lifecycle, not just the ones whose bank account timing happened to align with the quarterly report.

Measure what the business is actually doing. The money follows later.