Table of Contents
101
4 min
03.09.2026
Hiring ahead of the contract: how payroll burns your runway in defence tech
.avif){kind=icon}
Oleksandr Solovei
CEO & Co-founder Finmap
«We were all but promised a big contract, so we hired eight engineers ahead of it to be ready. The contract slipped by half a year. And the salaries had to be paid every month — and they ate the runway we'd built over years. Hiring on a promise turned out to be the most expensive mistake.»
This is a painful but typical story in defence tech. The temptation to scale the team for a future contract is understandable: you want to be ready, not lose momentum, not turn a customer down. But salaries are the biggest fixed burn, and they start at once, while the promised revenue comes later or not at all.
Why payroll is the most dangerous cost
Unlike components, which you can choose not to buy, salaries must be paid every month regardless of whether the contract arrived. Every new engineer is not a one-off but a recurring cost added to the burn right after hiring. In defence tech, where inflows are uneven and depend on tranches and acceptances, a large team hired ahead turns a temporary revenue delay into an existential risk.
How hiring shortens runway
Let's count. A company has $240,000 in the accounts and a team giving a burn of $30,000 a month — that's 8 months of runway. Now it hires eight more engineers for a promised contract.
| State | Burn / mo | Runway |
|---|---|---|
| 10 engineers (before) | $30,000 | 8 months |
| 18 engineers (after) | $54,000 | ≈4.4 months |
| Contract slips 6 months | $54,000 | cash to zero sooner |
Hiring ahead nearly halved the runway — from 8 months to 4.4. If the promised contract arrives on time, the bet pays off. If it slips by half a year — which in defence tech is the rule rather than the exception — the company ends up in a cash gap with a large team and no revenue to fund it.
The key rule: hire for committed, not promised
The difference between «the contract is all but signed» and «the contract is signed, the advance is in the account» is the difference between a managed and a fatal risk. A healthy rule: tie team size to committed revenue and available runway, not to deals that are «about to close». Hire when there's an advance, a signed contract, or runway that survives the team even if revenue is delayed. A customer's promise is not money in the account.
«You can skip buying components. You can't skip paying salaries. That's why hiring ahead is the riskiest bet in a production business: it turns a temporary revenue delay into a permanent cost.»
What it looks like in real life
You hear the problem in typical phrases. «Let's hire now so we're ready when they sign.» «The contract's about to close, we need to scale.» «The team grew, but the revenue to fund it hasn't arrived yet.» «We thought it'd be on time, and it slipped — and now the runway is melting.» Each line is about hiring on a promise, not on money in the account.
How to keep it under control
To avoid this trap you need to see how each hire affects burn and runway. In Finmap you track salaries as part of fixed costs, see the total burn and how many months the account survives — and you can play out a scenario: what happens to runway if you hire more people and revenue is delayed. The decision to scale the team is made on numbers, not on optimism about a contract.
Related — counting runway between tranches and tracking R&D cost by direction.
A few tips
- Tie team size to committed revenue and runway, not to promised contracts.
- Before each hire, count how it shortens runway — the salary is permanent, the revenue for it may not come.
- Hire after an advance or a signed contract, not «to be ready» for a deal that's «about to close».
- Keep a runway buffer that survives the team even with a few months' revenue delay.
- Distinguish «all but signed» from «money in the account»: only the second justifies hiring.
The ambition to scale for a future contract is understandable, but salaries don't wait for a promise. Hiring ahead turns a temporary revenue delay into a permanent cost that eats runway. The moment you see each hire's impact on runway, scaling the team becomes a calculation, not a bet that the contract will be signed on time.
Money Doesn't Disappear. You Just Don't See It.
Try Finmap free for 14 days and see how each hire affects your burn and runway — before salaries eat the reserve you built over years.
Share valuable content — become a source of insights
Frequently asked questions
Why can't I hire for a future contract?
You can, but only when runway survives the team even with a revenue delay. The risk is that salaries are permanent while the contract can slip. Hiring for committed revenue or an advance is safe; for a promise it isn't.
Why is hiring more dangerous than buying components?
Components are a one-off cost you can postpone. A salary is permanent, due every month regardless of revenue. So each hire raises the burn forever, while a purchase can simply not be made.
How do I calculate a hire's impact on runway?
Add the new salary to the monthly burn and divide cash in the accounts by the new burn. The difference between old and new runway is the hire's cost in time. If it's critical, better postpone the hire until revenue is committed.
What runway buffer should I keep in defence tech?
Given tranche and contract delays, a comfortable benchmark is 9–12 months. Hiring while dropping runway below 6 is risky, because a single revenue slip can take the company to zero.
Any questions left?
We are ready to answer them.
Finmap support
