Startup economics: model your runway before you hire

Meta description: Model burn rate, hiring curves, and ARR growth to decide if engineer #3 accelerates your startup or burns your last 6 months of runway. Model it first.

---

TL;DR

The decision to hire engineer #3 is not a culture call or a gut-feel move — it is a math decision. Model burn rate, ARR growth rate, and the hiring curve’s impact on both before signing an offer letter. Startups that skip this model routinely discover that a well-intentioned hire compressed their runway below the threshold needed to close the next round.

---

The problem with “We need more engineers”

Most teams get early hiring wrong the same way: they treat headcount as a proxy for velocity. It is not. In financial models I have reviewed across 20+ seed-stage teams, the correlation between engineers hired and features shipped is weak in the first 90 days — and sometimes negative.

The variables that actually matter:

• Burn multiple: how much do you burn for every dollar of new ARR added?
• Time-to-productivity: how long until a new hire ships net-positive value?
• ARR growth rate: is revenue compounding fast enough to justify the additional burn?

---

Building the model

Runway (months)  = Cash in Bank / Net Monthly Burn
Net Monthly Burn = Total OpEx − MRR
Total OpEx       = Salaries + Infrastructure + Other Fixed Costs

The hire/defer decision becomes a direct comparison of scenarios. The table below uses these explicit assumptions: $700K starting cash; $40K/mo current net burn; $15K/mo all-in new hire cost; 3-month ramp with zero revenue contribution; $7K/mo net burn reduction post-ramp as the hire drives incremental MRR; starting MRR $20K/mo growing at 3%/mo organically, accelerating to 6%/mo once the hire is fully productive.

Scenario	Month 6 Cash	Month 12 ARR	Runway at Month 12
Hire Eng #3 now	$391K	$444K	2.1 months
Defer to Month 6	$460K	$373K	3.1 months
No hire	$460K	$342K	5.5 months

Hiring now produces $71K more ARR at month 12, but compresses runway to 2.1 months — almost no margin to close the next round. Deferring six months costs you roughly $71K in ARR and leaves you with a meaningfully stronger position going into a fundraise. Which trade-off is better depends entirely on your timeline.

---

The burn multiple as a north star

Operate as if the next check is not coming.

Burn Multiple = Net Burn / Net New ARR

Burn Multiple	Signal
< 1x	Elite efficiency
1x – 1.5x	Healthy
1.5x – 2x	Acceptable — watch closely
> 2x	Danger zone

If hiring engineer #3 pushes your burn multiple above 2x for more than two consecutive quarters, you are buying ARR with borrowed time.

---

Modeling the hiring curve

The hiring curve is nonlinear. A new engineer does not contribute at Day 1. Model it as a step function with linear interpolation during the ramp window:

def arr_contribution(month, hire_month, ramp_months=3, monthly_arr_uplift=5000):
    if month < hire_month:
        return 0
    months_since_hire = month - hire_month
    if months_since_hire < ramp_months:
        return monthly_arr_uplift * (months_since_hire / ramp_months)
    return monthly_arr_uplift

This model uses linear interpolation across the ramp window — a conservative, auditable default. In practice, contribution often follows an S-curve (slow start, acceleration, plateau), but linear interpolation is a sound baseline for spreadsheet modeling because it avoids overstating early contribution. The logic maps directly to a simple spreadsheet: one column per month, a conditional formula on months since hire date. The ramp assumption is the most sensitive input — stress-test it at 60, 90, and 120 days.

Overestimating a new hire’s ARR contribution is one of the most common errors I see in early-stage financial models. Linear interpolation over 90 days is closer to reality than a cliff step at Day 1.

---

When to hire anyway

There are legitimate reasons to hire despite the math:

1. A critical path blocker exists — if a missing skill is the sole barrier to closing a design partner, the hire pays for itself.
2. Your existing engineers are at capacity — attrition is more expensive than a new hire; do not conflate the two costs.
3. You have a signed term sheet — hire into capital, not ahead of it.

Outside these conditions, extend runway.

---

Three actionable takeaways

1. Build the two-scenario model before every hire. Run “hire now” vs. “defer N months” with honest ramp assumptions and reconcile every figure against your stated inputs. If the runway delta at month 12 exceeds one month, the case for waiting is strong.

2. Track burn multiple quarterly, not annually. A spike above 2x for one quarter is a warning. Two consecutive quarters is a crisis. Build this into your board deck from the start.

3. Treat your hiring curve as a step function, not a straight line. Ninety days is the minimum for an early-stage engineer to ship net-positive value. Model it with linear interpolation during ramp — do not let optimism substitute for arithmetic.

---

Tags: startup, saas, product-engineering, mvp, architecture