There's a version of the board conversation that goes badly: the CTO presents a headcount plan, the CFO asks about fully-loaded costs, the CTO doesn't have the number, and the conversation derails into a finance lesson that damages credibility.
There's a version that goes well: the CTO presents a structured headcount model with fully-loaded costs, benchmarked salaries, scenario analysis, and a clear link between headcount investment and business outcomes. Budget gets approved.
This is a guide to the second version.
What is your board actually evaluating in an engineering cost presentation?
When a board reviews an engineering cost presentation, they're asking four questions — whether they say them out loud or not:
- Are you allocating capital efficiently? Are your people costs in line with market benchmarks?
- Is the plan grounded in reality? Are the cost numbers defensible?
- Can you connect spend to value? What does this investment in engineering actually produce?
- Are you managing risk? Are there concentration risks or key-person dependencies?
Every element of a strong engineering cost presentation is designed to answer these questions before they're asked.
What should an engineering cost board presentation include?
Slide 1: Current Team Snapshot
Start with a clear picture of where you are today:
- Total engineering headcount by function
- Current fully-loaded team cost (annualised)
- Average cost per engineer
- Salary benchmark position (above/below/at market)
Slide 2: The Headcount Plan
Present planned hires as a structured table, not a narrative:
- Role, level, and function
- Planned start quarter
- Base salary and fully-loaded cost per hire
- In-year cost vs annualised run rate (these are different numbers — show both)
- Cumulative team cost at end of plan period
Separate growth hires from backfill hires.
Slide 3: Benchmark Comparison
Show how your compensation sits relative to market data. A simple chart showing your team's salaries against 25th/50th/75th percentile benchmarks by role demonstrates analytical rigour and helps the board trust your numbers.
Slide 4: The ROI Case
This is the most important slide — and the one most CTOs skip.
For each significant hiring tranche, answer:
- What will this team build? Specific product capabilities or technical initiatives
- What business outcome does this enable? Revenue unlocked, cost reduced, churn reduced
- What is the cost of not doing it? Delayed roadmap, technical debt, competitor advantage
Be quantitative where you can. "Hiring two platform engineers at £130k fully-loaded will reduce infrastructure cost by an estimated £80k/year and unblock three product teams" is a stronger argument than "we need to invest in platform."
Slide 5: Scenarios
Present two to three scenarios at different investment levels:
- Base case: The plan you're recommending
- Conservative case: Fewer hires, prioritised to the highest-ROI roles
- Accelerated case: More aggressive hiring if funding or growth permits
This gives the board a structured way to give you direction rather than a binary yes/no.
Slide 6: Efficiency Metrics
Boards at sophisticated companies increasingly track:
- Revenue per engineer: Total ARR ÷ engineering headcount
- Engineering cost as % of revenue: For early-stage, 40–60% is common; target 15–25% at scale
- Infrastructure cost as % of revenue: Efficient companies run 5–15%
What questions does a board ask a CTO about engineering costs?
"What's the fully-loaded cost, not just base salary?" Have the full breakdown ready: base + NIC + pension + benefits + tooling + recruiting + overhead.
"What happens if we slow the hiring plan by a quarter?" Model this explicitly. Show the impact on capacity and roadmap timing.
"How does our compensation compare to market?" Have benchmark data by role and level, sourced from a credible dataset.
"What are we getting for the platform/infrastructure spend?" Have specific metrics: uptime improvement, deployment frequency, cost reduction.
What are the most common CTO presentation mistakes?
Leading with headcount, not outcomes: "We need 8 engineers" is a harder sell than "these 8 hires deliver £X of roadmap and reduce £Y of risk."
Presenting base salary as the cost: Finance will remodel with on-costs. Getting caught presenting incomplete numbers damages credibility significantly.
No scenario analysis: A single plan with no alternatives looks inflexible.
Vague timelines: "We plan to hire in H2" is less useful than "Q3 hire, 12-week lead time, £132k fully-loaded run rate from Q4."
No benchmark context: Salary numbers without market context are uninterpretable.
How does a CTO become a credible financial partner to the board?
The best CTOs treat the board relationship as a partnership, not a pitch. That means coming to every headcount conversation with the same analytical rigour the CFO brings to their financial model.
The payoff is a board that trusts you with budget, gives you more latitude on decisions, and treats you as a peer in strategic conversation rather than a function to be managed.
How TeamCalc Helps You Prepare
TeamCalc generates the numbers you need for exactly this type of presentation. Model your current team and planned hires, get fully-loaded costs with employer contributions calculated automatically, compare against salary benchmarks, and export a PDF or CSV that drops straight into your board pack.