Operating consultancy for defence tech

The operating challenge in defence tech is the dual mandate. Mission and market do not optimise for the same thing.

Most operating advice imported from consumer tech or enterprise SaaS assumes one customer, one buying motion, one cadence you can tune the whole company around. Defence tech doesn't get that luxury. You are building for a warfighter who needs the thing to work in conditions nobody can fully simulate, and you are building a company that needs revenue, headcount runway, and a cap table that survives to the next round. Those two things pull in different directions more often than founders admit before they've lived it.

Two customers, two definitions of "done"

A programme office measures success in mission assurance: does the capability perform under the worst conditions, is it auditable, does it survive an after-action review. A venture board measures success in ARR, logo count, and time to the next raise. Both are legitimate. Neither will wait for the other.

I've watched founders try to run one cadence across both and burn out their best engineers doing it. The programme side wants a six-month integration cycle with a formal test range booked eight weeks out. The product side wants a shipped feature by Friday because a demo is riding on it. Force those into the same sprint calendar and you get a team that's permanently behind on both fronts, because the sprint was designed for neither.

The fix isn't heroics. It's structural: stand up two cadences, not one. A programme cadence tracks the customer's world: test windows, security accreditation gates, the milestones written into the contract. A product cadence tracks the team's world: the weekly build-measure-learn loop that keeps the commercial product improving in the gaps the programme cadence leaves open. The two cadences share a roadmap but not a calendar. When people ask why the same company seems to move glacially on one workstream and fast on another, that's usually the answer: two clocks running on purpose.

Compliance is the lane you drive in

Founders coming from commercial SaaS treat ITAR, CMMC, or a security clearance requirement as friction to be minimised. Wrong framing. Compliance in defence tech is the lane the venture is permitted to drive in. Nobody let you into the market without it. Trying to build outside the lane doesn't get you to market faster, it gets you disqualified before the contract's even scored.

This changes what "good operations" looks like. A commercial ops leader optimises for removing steps. A defence tech ops leader optimises for making the required steps repeatable and boring, so they stop being the bottleneck. The audit trail, the classification handling, the export control review: build these into the default workflow once, properly, and they become a competitive moat rather than a tax. Competitors who treat compliance as an afterthought get stuck re-litigating it on every deal. You've already paid that cost once and it's compounding in your favour.

A carpenter doesn't argue with wood. They read it first. The grain here runs classified, slow, and procedural on the mission side. Fighting that grain wastes motion. Reading it, and building the operating system to run with it, is the actual job.

The procurement clock does not run on venture time

This is the mismatch nobody warns founders about early enough. A Series A term sheet assumes a growth curve measured in quarters. A defence procurement cycle, especially anything routed through a formal acquisition process, is measured in years: requirements definition, a competitive down-select, testing, a production decision, then actual fielding. Even fast-track pathways designed to compress this still run on a different clock than an investor update.

Founders who don't plan for this burn cash waiting for a contract that was always going to land eighteen months later than the pitch deck implied. The ones who survive treat the procurement clock as a known constant, not a variable to be wished away, and they build a commercial or dual-use revenue line that doesn't depend on it to keep the lights on while the primary contract works its way through the system. Call it reading the timeline correctly instead of forecasting off hope.

Operators are the ones who make this bridge work in practice, which is why the hire matters more here than almost anywhere else in the operating stack.

Hire the translator, not just the operator

The single highest-leverage hire in a defence tech operating team is someone who has actually sat inside the customer organisation: a former programme manager, a former contracting officer, someone who has been on the other side of the requirements document. Not for their network, though that helps. For the translation.

Translation is most of the work. Engineering teams write in capability language. Programme offices evaluate in requirements language. Investors think in market language. A translator who has lived in the customer's world can take a technical capability and phrase it as a line item against an actual requirement, catch the compliance gap before it becomes a stop-work order, and tell the product team which "nice to have" is actually a "will not be scored" in disguise.

Without that person, every proposal, every demo, every review becomes a guessing game about what the customer actually meant. With that person, the guessing stops, because someone in the room has already been the customer.

Building the operating system that holds both

None of this resolves into a single tidy process. That's the point. An operating consultancy for defence tech isn't selling founders a way to make the dual mandate disappear. It's building the scaffolding that lets both mandates run at once without either one silently starving the other: two cadences that share a roadmap, a compliance function treated as infrastructure rather than overhead, a realistic model of procurement time sitting next to the commercial growth model, and at least one person in the building who has genuinely been on the customer's side of the table.

Get that scaffolding right and the dual mandate becomes the actual shape of the business rather than a contradiction to manage around.