The Art of CTO Headcount Forecasting tool projects future staffing needs accounting for revenue growth targets, target revenue per engineer, attrition, time-to-hire and ramp-up time. (Hiring pipeline conversion rates were removed from the model — see lib/headcount-forecasting/calc.ts — and replaced with an explicit hiring lag, so a requisition opened in one month lands time-to-hire months later.)
How many engineers will we need next year?
A month-by-month headcount forecast with attrition and ramp-up built in.
About 10 min · Calculator · Free
About this toolWhy it matters, common mistakes, FAQ
How Many Engineers Will You Actually Need?
Headcount plans are committed a year ahead and are the largest line in most engineering budgets. Ask for too few and you miss the roadmap; too many and you are the one explaining the burn in a downturn.
Forecasts extrapolate from current velocity and ignore that added people cost time before they add any. Ramp, attrition and the management layer a growing team needs are what make the naive number wrong.
Questions CTOs ask
- How do you forecast engineering headcount?
- Engineering headcount forecasting combines bottom-up demand (planned projects, maintenance burden, and on-call requirements) with top-down constraints (budget, revenue-per-engineer targets, and growth rate). You should account for attrition (typically 10-20% annually in tech), ramp-up time for new hires (3-6 months to full productivity), and time-to-hire, so a requisition is opened early enough that the person lands when the gap actually appears. This tool models exactly those inputs — it does not model recruiting funnel conversion rates.
- What is the ideal engineer-to-manager ratio?
- The widely accepted range is 5-8 engineers per engineering manager, with 6-7 being the sweet spot for most organizations. Smaller ratios (4-5) work well for junior teams or complex domains requiring heavy mentorship, while larger ratios (8-10) can work with senior, autonomous teams. Going below 4 creates unnecessary management overhead, and exceeding 10 typically means managers cannot provide adequate support.
- When should you hire your first engineering manager?
- Most startups should hire or promote their first engineering manager when the team reaches 6-8 engineers. At this size, the technical founder or lead can no longer effectively handle both people management and technical leadership without one suffering. Signs you have waited too long include declining 1:1 frequency, delayed performance reviews, unresolved team conflicts, and the tech lead becoming a bottleneck for all decisions.
Related Reading
Engineering Team Scaling Calculator Guide: Build a Hiring Plan That Matches Your Roadmap
Engineering team scaling calculator: how big should your engineering team actually be?
guidesArchitecture Calculator Guide: Capacity Planning and Infrastructure Sizing for Series A CTOs
Architecture Calculator Guide: system capacity planning calculator for infrastructure sizing
guidesEngineering ROI Calculator Guide: Justify Engineering Initiatives With Real Numbers
Engineering ROI calculator guide: justify engineering initiatives with real numbers