Conservative, Base, Aggressive: Modeling Three Hiring Cadences

A hiring plan is not a spreadsheet of names and start dates. It is a bet on how fast you can spend money before revenue or the next round catches up. Modeling three hiring cadences — conservative, base, and aggressive — side by side is how you turn that bet into a runway decision the board can actually argue about, because each cadence produces its own net burn curve and its own month where the cash either turns positive or runs out.

The mistake most finance teams make is treating headcount as a single number to defend. The CEO wants to hire; the CFO wants to conserve; the meeting becomes a negotiation over a scalar. Three cadences reframe the question. You are no longer defending 5 hires against 8. You are comparing three runway outcomes and letting the board choose which risk they want to own.

What each cadence actually contains

Start with concrete plans, not adjectives. "Aggressive" means nothing until it has hires attached to months.

Conservative: 2 net new hires in H2, both in go-to-market, spread across Q3 and Q4. No engineering adds. This is the plan you run if the next round slips two quarters.

Base: 5 net new hires, weighted toward the functions already carrying pipeline — say two AEs, an SDR, a customer success hire, and one backfill. This is the plan the board approved at the last raise.

Aggressive: 8 net new hires including 2 engineers in Q3. The engineers are the expensive part, not because of salary but because fully loaded cost — benefits, payroll tax, equipment, software seats — runs 1.25 to 1.4x base for technical roles.

Each cadence needs the same three outputs so they're comparable: monthly net burn, runway in months, and the month you hit break-even or hit zero cash. Anything less and you're comparing plans on different axes.

Building the three burn curves

The mechanics are identical across cadences; only the timing and headcount differ. If you've already built forward burn from your headcount line by line, you have the engine. Each new hire adds their loaded monthly cost from their start month forward, layered on top of committed spend.

The number that matters is net burn, not gross. Net burn is cash out minus cash in — and cash in moves with the go-to-market hires. An AE who starts in July doesn't produce bookings until a ramp lands, typically 3 to 5 months out per Bessemer's benchmarks on sales productivity. The aggressive cadence spends earlier and harder but also pulls revenue forward, which is exactly why you can't judge cadences on burn alone.

Runway is cash on hand divided by net burn, recomputed each month because net burn changes every month a hire lands. The SaaS Capital research on efficient growth is blunt about the tolerance here: below roughly 12 months of runway, the aggressive cadence stops being a growth bet and becomes a financing bet.

The break-even month is the headline

For each cadence, find the month where net burn crosses zero — or, if it never does inside the model window, the month cash reaches zero. That single figure is what the board remembers.

The conservative plan might break even in month 19 with 14 months of runway to spare. The base plan pushes break-even to month 16 but drops minimum runway to 9 months. The aggressive plan reaches break-even in month 13 — if the engineers ship the feature that unlocks the pipeline the AEs are hired to close, and if that whole chain lands on schedule. Now the board is choosing between certainty and slope, which is the conversation you actually want.

Where the hand-built version breaks

Most teams build these three cadences once, in a deck, before a board meeting. Then the meeting ends and the model dies. This is the failure mode worth naming.

The problem is that actuals move underneath the model. You built the aggressive cadence assuming the Q3 engineers start in July. One slips to September. A sales hire you modeled at $140K loaded comes in at $165K. Bookings land 20% under the ramp you assumed. By the time the next board meeting arrives, all three cadences are anchored to numbers that have already changed — and rebuilding them by hand means re-keying actuals from your accounting system, re-checking every start date, and re-deriving three break-even months against a cash balance that moved.

This is the core argument of headcount planning that protects runway rather than just recording hires: the plan has to stay live. A cadence comparison that recalculates net burn and break-even every time actuals close is a capital-allocation instrument. One frozen in a slide is a memory. The distinction shows up most sharply in the visibility gap — the lag between what your bank balance actually is and what your model still assumes it is.

The tooling that closes that gap doesn't need to be exotic. It needs to pull actuals — payroll, spend, bookings — and rerun the three cadences without a human re-keying anything. Whether that's a purpose-built platform, a well-disciplined operations workflow, or a tightly wired Runway or Mosaic instance matters less than the property itself: the scenarios have to move when the numbers move.

See how live actuals change a cadence comparison between board meetings. →

The three-cadence model earns its keep in the room, when a director asks what happens to runway if you take the aggressive plan and the engineers slip a quarter — and you can answer with a recomputed break-even month instead of a promise to circle back. That answer is only possible if the model was still connected to the numbers when the question got asked.