Efficiency and Operations Metrics
Runaway growth is fine only until the runway runs out
Ops metrics run the company: burn, runway, gross margin, headcount efficiency and capacity. They show whether growth is turning into operating health or into a beautiful, costly fire.
What you will learn
- Compute burn, runway and gross margin
- Track headcount and per-employee efficiency
- Read operational ratios to spot trouble early
What is this?
Efficiency and operations metrics describe how the company converts investment into margin. Burn is net cash spent per month; runway is how many months the treasury survives at that burn. Gross margin separates product economics from overhead. Headcount metrics (revenue per employee, cost per head) and capacity metrics (on-time delivery, cycle time) track the engine itself.
Why do you need it?
- Cash is the constraint every startup meets; burn/runway make it visible.
- Rising revenue with falling gross margin is a slower, sneakier failure.
- Per-employee revenue drops usually precede layoffs; measuring it early is humane.
- Operations metrics pair analytics with the actual running of the business.
Mental model
A mountain fuel gauge
Operational metrics
Your vehicle shows fuel remaining (cash), consumption per hour (burn) and estimated hours left (runway). A beautiful view (revenue growth) does not refill the tank (margin does).
How it works
- Burn = recurring net cash outflow per month (opex minus operating income impact).
- Runway = cash on hand / monthly burn.
- Gross margin = (net revenue - cost of goods sold) / net revenue.
- Revenue per employee = net revenue / average headcount.
- Cycle time and on-time measures track deliverable throughput for ops teams.
From cash to runway.
Examples
Runway and margin snapshot
WITH monthly AS ( SELECT month, SUM(net_cash_flow) AS burn, gross_margin, average_headcount FROM ops_fct GROUP BY 1)SELECT month, burn, SUM(burn) OVER (ORDER BY month ROWS BETWEEN 2 PRECEDING AND CURRENT ROW)/3 AS burn_3m, gross_margin, revenue / average_headcount AS rev_per_headFROM monthly;The query smooths burn over a trailing three months, keeps gross margin adjacent, and computes revenue per head โ the three knobs operations reads together.
In production
- A board dashboard shows burn, runway and gross margin as the three 'tripwire' cards every month.
- An ops leader tracks revenue per employee quarterly to justify hiring or flag softness.
- A SaaS exec reads net cash vs net margin trend to see the pivot from funding to self-sufficiency.
Best practices
- Report burn net of one-time items with a footnote.
- Keep runway per month but look at trailing three months for trend.
- Reconcile headcount metrics to the payroll period, not the project plan.
- Review gross margin by segment to find the margin-diluting offer.
Common mistakes
- Measuring burn gross (ignoring income), overstating the danger.
- Quoting runoff based on one volatile month.
- Calculating revenue per employee against contractors unevenly.
- Reading margin on bookings instead of recognized revenue.
Common issues
Runway looks fine but bank balance swings wildlyBurn averaged over a lumpy month
Use a 3-month average burn and flag one-time items.
Gross margin drops without a price changeCOGS reclassification or new channel costs
Reconcile COGS line items and re-baseline the margin definition.
Revenue per employee falling while hiring continuesFront-loaded hiring vs recognition timing
Present the metric on a trailing basis and separately show time-to-value of hires.
Debugging tips
- Reconcile any headline number back to the cash statement or P&L.
- Slice gross margin by segment to find the diluting lines.
- Compare runway under two burn scenarios before believing one.
- Audit headcount against the payroll export each quarter.
Interview checkpoint
Quick quiz
Which metric tells you how many months the treasury lasts at current burn?
Gross margin should be measured on recognized revenue, not bookings.