Summary
Decision
Loading…
Org Structure by Function
Headcount by Function
Largest Function
—
Total Headcount (Dec)
📖 WHAT YOU'RE LOOKING AT
Each bar shows headcount stacked by function over 12 months. A steep upward slope = aggressive hiring. A flat line = stable headcount — watch whether demand keeps rising despite no new hires, because utilization will climb with it.
Opex by Function
Highest-Cost Function
—
Total Monthly Opex (Dec)
📖 WHAT YOU'RE LOOKING AT
Each bar is fully loaded monthly cost stacked by function — salary, benefits, payroll tax, bonus, and one-time hiring costs. Month spikes = new hires (equipment + recruiting + onboarding hit in one shot). A growing total bar means your cost base is expanding — verify revenue growth is keeping pace.
Fully Loaded Cost Structure
Capacity & Utilization
Utilization by Function
Highest Utilization
—
Avg Utilization (Dec)
📖 WHAT YOU'RE LOOKING AT
Each line tracks utilization % over 12 months per function (Demand ÷ Capacity). The dashed red line is the overload threshold — above this, a hire is justified. The orange line is the caution zone. Lines trending upward mean demand is outgrowing capacity and the hiring window is narrowing.
Current Capacity Status
Hiring Justification Logic
Hiring Strategy Comparison
Runway Impact
💡 So What — Runway Impact
- ›Every hire shortens runway. This chart shows exactly how many months you trade away under each hiring strategy — making the hire/delay tradeoff explicit and board-ready.
- ›Conservative hiring preserves 3–6 additional months of runway vs aggressive — enough time to close a funding round or reach a revenue milestone that reduces cash dependence.
- ›If runway gap between strategies exceeds 4 months: Default to conservative hiring plan and flag aggressive scenario as requiring a capital raise or revenue acceleration commitment.
- ›If runway < 12 months on either path: Pause all non-critical hires, model cash-neutral staffing (backfill only), and present funding options to the board within 30 days.
12-Month Hiring Plan
Derived from utilization and runway thresholds — no randomness