ARR Per Employee

What is ARR per employee?

ARR per employee (also called revenue per employee, revenue per FTE, or workforce efficiency ratio) is total annual recurring revenue divided by the total number of full-time equivalent employees. It measures how efficiently the organization converts headcount into revenue. Operators and CFOs use it to benchmark hiring pace, evaluate organizational leverage, and forecast when the company will reach profitability.

This metric exposes a problem that EBITDA alone does not: whether the company is building a team that scales efficiently or one that requires linear headcount growth for every dollar of new revenue. A company growing ARR at 50% per year while growing headcount at 60% is becoming less efficient with every hire. ARR per employee makes that visible.

For venture-backed B2B SaaS, the benchmarks shift significantly by stage. Pre-product-market-fit companies may operate at $80-$120K per employee. Growth-stage companies ($10-$50M ARR) should target $150-$250K. Late-stage and public companies above $100M ARR typically reach $250-$400K. Companies preparing for IPO that fall below $200K face hard questions from institutional investors about margin trajectory.

ARR per employee differs from revenue per employee in one critical way. ARR per employee uses annualized recurring revenue, excluding one-time fees, services revenue, and non-recurring charges. Revenue per employee includes everything. For SaaS companies with material professional services revenue, the two numbers can diverge significantly.

Why ARR per employee matters for operators

Hiring is the largest expense at most SaaS companies. Payroll, benefits, and related costs consume 60-80% of operating budget at growth-stage companies. ARR per employee tells operators whether each additional hire is producing enough revenue to justify the cost — or whether the organization is adding complexity faster than it is adding value.

A company with $18M ARR and 110 employees runs at $164K per employee. If the leadership team plans to reach $30M ARR next year and maintains the same ratio, they will need 183 employees — 73 new hires. At a $150K average fully loaded cost per employee, that is $11M in incremental payroll. The question becomes: is there a path to $30M ARR with 140 employees instead of 183? If so, the company saves $6.5M in cash burn.

Tracking ARR per employee by department surfaces where leverage exists and where it does not. Engineering and product teams often drive the most ARR per head because their output (the product) scales without linear headcount. Sales and customer success teams typically show lower ARR per head because each rep carries a finite quota. The ratio by department guides where to invest next.

ARR per employee formula

ARR Per Employee = Total ARR / Total Full-Time Employees

Example:
- Total ARR: $14,200,000
- Total FTE count: 78

ARR Per Employee = $14,200,000 / 78 = $182,051

With contractors included (FTE-equivalent):
- Full-time employees: 78
- Contractors (converted to FTE): 12
- Total FTE-equivalent: 90

Adjusted ARR Per Employee = $14,200,000 / 90 = $157,778

What each component means:

• Total ARR: Annualized recurring revenue only. Exclude one-time implementation fees, professional services, and non-recurring revenue. Use the ARR figure as of the measurement date, not an average.
• Total full-time employees: All FTEs on payroll. The question of whether to include contractors depends on how material they are. If contractors represent more than 15% of the workforce, include them as FTE-equivalents for a more accurate picture.

ARR per employee benchmarks by company stage

How workforce efficiency varies across B2B SaaS stages. Figures reflect median ranges.

Sources: Meritech Capital SaaS Index 2025, Bessemer Cloud Index 2025, SaaStr Annual Benchmark Report 2025 (n=1,200 companies).

Common mistakes when measuring ARR per employee

1. Excluding contractors and outsourced teams

A company with 50 FTEs and 30 offshore contractors reporting $200K ARR per employee is overstating efficiency. The 30 contractors are doing work that would otherwise require employees. Include contractors as FTE-equivalents or report both figures side by side.

2. Using total revenue instead of ARR

Including professional services, one-time fees, and hardware revenue inflates the number and makes it incomparable to SaaS benchmarks. Use recurring revenue only. If services revenue is material (>15% of total), report it separately.

3. Measuring at a single point in time

ARR per employee is most useful as a trend line. A single snapshot can be misleading — the company may have just completed a hiring wave for growth that has not yet converted to revenue. Track the metric quarterly and compare the trajectory to the plan.

4. Comparing across vastly different business models

A PLG company with 40 employees and $20M ARR ($500K per employee) is not necessarily "better" than an enterprise company with 200 employees and $60M ARR ($300K per employee). Business model, ACV, and go-to-market motion all affect what "good" looks like. Compare within your segment.

5. Optimizing the metric by underinvesting in headcount

Cutting hiring to improve ARR per employee is a vanity move if it stalls growth. The metric should reflect efficiency, not austerity. A company at $300K per employee that is growing at 15% is less healthy than one at $180K per employee growing at 80%.

How Fairview tracks ARR per employee automatically

Fairview's Margin Intelligence layer pulls ARR data from your billing system (Stripe, HubSpot, Salesforce) and maps it against headcount data from your HR or finance tools. ARR per employee is calculated at the company level and by department, updated as headcount and revenue change.

The Operating Dashboard shows the trend line alongside burn multiple and Rule of 40 metrics, giving operators a single view of capital efficiency. When the ratio declines for two consecutive quarters, the Next-Best Action Engine surfaces the departments where headcount growth is outpacing revenue contribution.

→ See how Margin Intelligence works

ARR per employee vs revenue per employee

Both measure workforce productivity. They differ in what counts as revenue.

ARR per employee is the SaaS-specific metric. Revenue per employee is the general business metric. If recurring revenue is above 85% of total revenue, the two numbers will be close. If services or one-time revenue is significant, use both and explain the gap.

FAQ

What is ARR per employee in simple terms?

ARR per employee is how much recurring revenue the company generates for each person on the team. Divide total ARR by headcount. A company with $15M ARR and 80 employees has $187K ARR per employee. It shows whether the team is growing efficiently or whether each new hire adds more cost than revenue capacity.

What is a good ARR per employee for B2B SaaS?

For growth-stage B2B SaaS ($5-50M ARR), $180-$250K is strong. Top-quartile public SaaS companies exceed $300K (Meritech Capital, 2025). Below $130K at the growth stage suggests the company is overstaffed relative to revenue. Early-stage companies naturally run lower because they are building ahead of revenue.

How do you calculate ARR per employee?

Divide total annual recurring revenue by the number of full-time employees. For example, $14.2M ARR divided by 78 employees = $182K per employee. Use recurring revenue only — exclude services and one-time fees. If contractors are a significant portion of the workforce, include them as FTE-equivalents.

What is the difference between ARR per employee and revenue per employee?

ARR per employee counts only recurring subscription revenue. Revenue per employee includes all revenue: subscriptions, professional services, one-time fees, and non-recurring charges. For pure SaaS companies, the numbers are close. For hybrid models with material services revenue, revenue per employee will be higher and less comparable to SaaS benchmarks.

How often should you track ARR per employee?

Quarterly. ARR per employee is a strategic metric — it changes slowly unless the company has a major hiring wave or revenue event. Monthly tracking adds noise without insight. Quarterly measurements aligned with board reporting provide the right cadence for spotting trends and adjusting hiring plans.

How do you improve ARR per employee?

Three paths: grow revenue faster than headcount (invest in product-led channels that scale without proportional hiring), improve sales productivity so each rep generates more ARR, or audit non-revenue roles for consolidation. The most sustainable approach is building product features that reduce the need for manual support, implementation, and success headcount.

Related terms

• ARR — Annual recurring revenue, the numerator in the ARR per employee calculation
• EBITDA — Earnings before interest, taxes, depreciation, and amortization, the profitability metric ARR per employee feeds into
• Burn Multiple — Net burn divided by net new ARR, measuring how efficiently the company converts cash into growth
• Rule of 40 — Growth rate plus profit margin, the combined efficiency benchmark where ARR per employee is a key input
• Magic Number — Measures sales efficiency specifically, showing how much ARR each dollar of sales and marketing spend generates

Fairview is an operating intelligence platform that tracks ARR per employee alongside burn multiple, EBITDA, and Rule of 40. Start your free trial →

Siddharth Gangal is the founder of Fairview. He built departmental efficiency tracking into the platform after watching operators make hiring decisions based on headcount plans disconnected from revenue math.