G&A Team Headcount

What it measures

Total count of full-time equivalent (FTE) and part-time personnel whose primary function is finance, accounting, legal, tax, human resources, facilities, information technology (core infrastructure and security, not product engineering), compliance, corporate governance, administrative support, and executive operations. Include employees, contractors, and outsourced partners on payroll or contracted spend. Exclude any employee whose primary output is revenue-generating (sales, customer success, product engineering, marketing) or cost-of-revenue delivery (customer support, onboarding services) — those are measured separately. Do not include finance business partners embedded in revenue teams if their primary output is supporting those teams' metrics and forecasts.

Why it matters

G&A headcount is your overhead burn — the people cost of running the company's corporate machinery, incurred whether revenue grows or not. Every G&A hire reduces operating margin and shortens runway, and unlike a salesperson or an engineer, a controller or HR generalist does not directly produce revenue or product. That is precisely why investors and operators watch it: the discipline of scaling revenue faster than G&A is what produces operating leverage and, eventually, profitability. Tracked against revenue and total headcount, G&A headcount tells you whether your back office is right-sized, whether you are quietly accumulating bureaucracy, and how much runway you can free up. Boards treat a controlled, slowly-declining G&A ratio as a proxy for management's financial discipline.

How to read it

G&A headcount is most useful as a ratio: G&A as a percentage of total headcount, and G&A spend as a percentage of revenue. Read G&A headcount alongside total headcount and revenue growth. If total headcount grows 30% but G&A headcount grows 50%, your company is over-staffing administrative functions and not balancing growth. If G&A stays flat while revenue grows 20%, you are leveraging existing infrastructure and building operating leverage. If G&A grows but revenue is flat, you are accumulating overhead without payoff. Seasonal patterns (H1 tax planning and audit prep, H2 bonus and benefits administration) and one-time project loads (IPO, acquisition, restructure) can spike G&A temporarily — account for these in trend analysis. Do not overreact to a single month; look at rolling three-month or trailing-twelve-month averages to see underlying trajectory.

What good looks like

Watch-outs

• Including revenue-supporting functions in G&A. A Finance Business Partner working full-time on sales margin analysis, a Legal person focused on customer contracts, or an HR person managing the sales commission plan are supporting revenue functions, not corporate overhead. Misclassifying them inflates G&A and distorts overhead metrics; assign them to the revenue or customer-facing team they support.
• Ignoring outsourced and contract labor. If you use a fractional CFO, an outside accounting firm, contract legal counsel, or a Shared Services Center, the cost appears in vendor spend, not W2 payroll. Either convert outsourced provider costs to FTE equivalents (annual spend ÷ market rate) or track them separately; excluding them makes G&A headcount look lean and hides true administrative cost.
• Forgetting to adjust for business model shifts. An early-stage SaaS company might have 1 Finance person per $1M ARR; a mature enterprise SaaS might have 1 per $20M ARR. Do not benchmark a scale-up's G&A ratio to an early-stage company or vice versa. Track the trend in your own company — is the ratio compressing as you grow? If not, you have overhead bloat.
• Double-counting shared infrastructure. If a Systems Administrator manages both IT infrastructure (G&A) and product development systems, assign them entirely to the role consuming >50% of their time, or split as fractional FTE. Do not count them in both G&A and Engineering, or your overhead metrics will overstate true corporate-only cost.

Worked example