Revenue per employee benchmarks for agencies, dev shops, and consulting firms. Learn the RPE formula and 5 operational levers to improve it.
Two agencies. Both doing $2 million a year. Same city. Same industry. Same types of clients.
Agency A has 20 people. Agency B has 9.
Agency A's revenue per employee: $100,000. Agency B's: $222,000.
Agency A is barely breaking even. Agency B is printing money. Same revenue. Completely different businesses. The difference isn't luck or talent. It's operations.
Revenue per employee (RPE) is the single metric that tells you the most about how well your business actually runs. Not revenue. Not headcount. Not even profit margin in isolation. RPE captures the full picture of operational efficiency in one number.
And most service business owners never look at it.
What Is Revenue Per Employee?
Revenue per employee is exactly what it sounds like: your total annual revenue divided by the number of people in your business.
Revenue Per Employee = Annual Revenue / Total Number of Employees
That's it. No complex formula. No advanced accounting. Just divide two numbers.
If your business does $1.5 million a year and you have 10 employees, your RPE is $150,000.
Should You Include Contractors?
Yes, with a caveat.
If you use contractors who work dedicated hours for your business (essentially acting as team members), count them. If you use a freelancer for 3 hours a month, don't.
The goal is to measure how much revenue your workforce generates. If someone is part of your workforce in practice, include them.
A common approach: count full-time equivalents (FTEs). A contractor who works 20 hours a week for you is 0.5 FTE. Add them as a half.
RPE (FTE-adjusted) = Annual Revenue / (Full-Time Employees + Contractor FTEs)
Why RPE Matters More Than Revenue or Headcount Alone
Revenue is a vanity metric. A $5 million agency with 50 employees is in worse shape than a $2 million agency with 8 people.
Headcount tells you nothing about efficiency. Hiring more people feels like growth, but if revenue doesn't scale proportionally, you're just adding cost.
RPE connects the two. It tells you:
- How efficiently you deliver value. Higher RPE means you're generating more output per person.
- Whether hiring is working. If RPE drops after hiring, you added bodies without adding proportional revenue.
- Your pricing power. Low RPE often signals underpricing, not overstaffing.
- Operational health. Process inefficiency, scope creep, and poor utilization all show up as low RPE.
- Scalability. A business with high RPE can scale without drowning in headcount costs.
Think of RPE as a blood pressure reading for your business. It doesn't tell you everything, but abnormal readings always point to something worth investigating.
Revenue Per Employee Benchmarks by Business Type
Here's where you stand relative to peers. These benchmarks are based on service businesses in the $1M-$10M revenue range.
Service Business RPE Benchmarks
| Business Type |
Low |
Average |
High |
| Marketing Agency |
$100K |
$150K |
$250K |
| Dev Shop |
$120K |
$200K |
$350K |
| Consulting Firm |
$150K |
$250K |
$400K |
| Accounting Firm |
$100K |
$175K |
$275K |
| Staffing Agency |
$80K |
$125K |
$200K |
A few things to notice.
Dev shops and consulting firms have the highest RPE ceilings. This makes sense. A senior developer or strategy consultant can generate enormous value per hour. The leverage is in expertise, not volume.
Staffing agencies have the lowest. Their model is inherently low-margin and people-heavy. Revenue per employee isn't the right optimization metric for staffing. Margin per placement matters more.
Marketing agencies have a wide range. The gap between $100K and $250K RPE in marketing agencies is almost entirely explained by operational maturity. Same service, wildly different efficiency.
What "Low" Means
If you're in the "Low" column, you're likely experiencing some combination of:
- Thin or negative margins
- Feeling busy but not profitable
- Trouble giving raises or investing in growth
- Owner working 60+ hour weeks to compensate
- Every new client feels like more stress, not more profit
What "High" Means
If you're in the "High" column, you've probably nailed:
- Value-based or premium pricing
- Tight processes with minimal waste
- Strong utilization rates across the team
- Technology that multiplies output
- The right people in the right roles
Where Should You Be?
If you're below average for your category, that's your first target. Get to average. Then aim for the 75th percentile.
Don't compare yourself to the wrong category. A marketing agency shouldn't benchmark against a consulting firm. The business models are fundamentally different.
The 5 Operational Factors That Drive RPE
RPE isn't one thing you fix. It's the output of five interconnected operational factors. Improve any one and RPE goes up. Improve all five and the gains compound.
1. Utilization Rates
Utilization is the percentage of your team's available time that goes toward revenue-generating work.
If your team is at 60% utilization, 40% of their time is consumed by internal meetings, admin, context switching, and other non-billable activity. That's 40% of your payroll generating zero revenue.
The math is brutal:
A 10-person team at $75K average salary costs you $750K/year in labor. At 60% utilization, only $450K of that labor is generating revenue. At 80% utilization, $600K is generating revenue.
That's a $150K swing from utilization alone. No new clients. No new hires. Just getting more billable work out of the hours you're already paying for.
Benchmark targets:
- Individual contributors: 75-85%
- Managers: 50-65%
- Directors: 30-40%
How to improve: Cut unnecessary meetings. Reduce context switching by batching work. Automate administrative tasks. Track time religiously. See our utilization rate benchmarks guide for the full breakdown.
2. Process Efficiency (How Fast You Deliver)
Two agencies both charge $10,000 for a website. Agency A delivers it in 80 hours. Agency B delivers it in 120 hours.
Agency A's effective rate: $125/hour. Agency B's effective rate: $83/hour.
Same deliverable. Same price. But Agency A can take on 50% more projects per year with the same team because they deliver faster.
Process efficiency multiplies RPE without raising prices or hiring.
The biggest process efficiency killers I see:
- No SOPs. Every project is done differently. No templates. No checklists. Every deliverable reinvented from scratch.
- Excessive revision cycles. Poor discovery and unclear scope lead to 3-4 rounds of revisions that should have been 1-2.
- Manual work that should be automated. Reporting, invoicing, client updates, data entry, project setup.
- Poor handoffs. Work sits in someone's inbox for 2 days waiting for review because there's no clear handoff process.
How to improve: Document your top 10 recurring workflows. Time them. Find the bottlenecks. Build templates. Automate the repetitive steps. A 20% improvement in delivery speed is a 20% improvement in RPE potential.
3. Pricing Model (Hourly vs. Value-Based)
This is the single biggest lever most service businesses ignore.
Hourly pricing caps your RPE. There are only so many hours in a year. If you charge $150/hour and your team has 1,800 billable hours per person per year, your theoretical RPE ceiling is $270,000 per person. In practice, utilization brings that down to $200K-$215K.
Value-based pricing removes the ceiling. If you charge $50,000 for an outcome that takes your team 200 hours to deliver, your effective rate is $250/hour. If you get faster and deliver it in 150 hours, your effective rate is $333/hour. You keep the upside of efficiency.
The RPE impact is dramatic:
| Pricing Model |
Effective Rate |
Billable Hours/Year |
RPE |
| Hourly at $150 |
$150 |
1,500 |
$225K |
| Fixed-fee at $250 effective |
$250 |
1,500 |
$375K |
| Value-based at $350 effective |
$350 |
1,500 |
$525K |
Same number of hours worked. Same team. But a 2x difference in RPE depending on how you price.
How to improve: Start with your most commoditized service. Package it as a fixed fee. Price it based on the value to the client, not your cost to deliver. Track your effective hourly rate on every project. Over time, shift your entire book toward value-based engagements.
For a deeper dive on pricing and its impact on your bottom line, see our margin improvement framework.
4. Tech Stack Leverage
Technology should multiply your team's output. If it doesn't, it's just cost.
High-leverage tech examples:
- A reporting tool that turns 4 hours of manual reporting per client per month into 15 minutes
- A project management system that eliminates status update meetings
- AI tools that reduce research and first-draft time by 50-70%
- Automation that handles client onboarding, invoicing, and follow-ups without human involvement
The multiplier effect:
If a $200/month tool saves each team member 5 hours per week, that's:
5 hours × $100 effective rate × 50 weeks = $25,000 per person per year in recovered capacity
For a 10-person team, that's $250,000 in additional revenue capacity from a $2,400/year investment. That's over 100x ROI.
But most businesses have the opposite problem. They're paying for 30+ tools and using 40% of the features. The tech stack creates complexity instead of leverage.
How to improve: Audit your tools quarterly. For each tool, ask: "Does this save more time than it costs to maintain?" Kill the ones that don't. Double down on the ones that do. Automate the workflows between your core tools.
5. Team Structure and Skill Mix
Your team's composition directly determines RPE. The wrong structure bleeds money. The right one prints it.
The leverage model:
High-RPE firms use a pyramid structure. A few senior people (expensive, high-value) oversee work done by mid-level and junior people (less expensive, trained to follow systems).
1 Senior Partner ($200K salary, generating $500K revenue)
2 Mid-Level Staff ($80K salary each, generating $200K revenue each)
3 Junior Staff ($55K salary each, generating $120K revenue each)
Total salaries: $525K
Total revenue: $1.26M
RPE: $210K per person
The flat model (common in small agencies):
Everyone is a senior generalist doing everything from strategy to execution.
6 Senior Generalists ($100K salary each, generating $180K revenue each)
Total salaries: $600K
Total revenue: $1.08M
RPE: $180K per person
More expensive team. Less revenue. Lower RPE. And the seniors are burned out because they're doing junior-level tasks.
How to improve: Look at your senior people's calendars. How much of their time goes to tasks that a well-trained junior person could handle? Every hour a $150K employee spends on $50K work is a $100K opportunity cost. Build the pyramid. Hire junior people. Create systems they can follow. Let your seniors do the high-value work that actually commands premium rates.
The Compounding Effect: What Happens When You Improve All Five
Here's where it gets exciting. These five factors don't add up. They multiply.
Let's start with a baseline agency:
Current state:
- 10 employees
- $1.5M revenue
- RPE: $150,000
Now let's improve each factor by a modest 15-20%:
| Factor |
Improvement |
RPE Impact |
| Utilization: 65% to 78% |
+20% |
$150K to $180K |
| Process efficiency: 20% faster delivery |
+15% |
$180K to $207K |
| Pricing: shift 30% of work to value-based |
+18% |
$207K to $244K |
| Tech leverage: automate 10 hrs/week/person |
+12% |
$244K to $273K |
| Team structure: add 2 juniors, promote 1 senior |
+10% |
$273K to $300K |
From $150K to $300K RPE. That's doubling your per-person revenue without doubling your team or your prices.
In dollar terms, the same 10-person team (now restructured to maybe 11-12 people with juniors) is generating $3M+ instead of $1.5M. With better margins because operational costs are lower per dollar of revenue.
Each improvement makes the others more effective. Better utilization means more hours to sell. Better processes mean those hours are more productive. Better pricing means each productive hour generates more revenue. Better tools accelerate everything. Better team structure puts the right people on the right tasks.
That's the compounding effect. And it's why RPE is such a powerful metric. It captures the compounding of all five factors in a single number.
The "Adding People Doesn't Add Revenue" Trap
This is the most common mistake I see in growing service businesses.
Revenue plateaus. The owner's response: "We need more people to handle the workload."
They hire. Revenue stays flat. Now margins are thinner. So they work harder. Still flat. So they hire someone to help with the extra work from the last hire. Revenue goes up 10% but costs went up 25%.
The trap looks like this:
| Quarter |
Team Size |
Revenue |
RPE |
| Q1 |
8 |
$400K |
$200K |
| Q2 |
10 |
$420K |
$168K |
| Q3 |
12 |
$460K |
$153K |
| Q4 |
13 |
$470K |
$145K |
Revenue grew 17.5% over the year. Team grew 62.5%. RPE declined 27.5%.
The owner feels like the business is growing. The bank account tells a different story.
Why does this happen?
The new hires aren't productive yet. Onboarding takes 3-6 months for most service businesses. During that time, they're consuming resources without generating proportional revenue.
Management overhead increases non-linearly. Going from 8 to 13 people doesn't add 62.5% more management work. It can easily double it. More 1-on-1s. More coordination. More communication overhead.
Process breaks at scale. What worked with 8 people (informal communication, tribal knowledge, the owner doing everything) stops working at 12-13. Without updated systems, everyone moves slower.
Sales didn't scale with capacity. You hired to handle more work, but you didn't invest in selling more work. Now you have expensive idle capacity.
The fix: Never hire to solve an efficiency problem. Fix the process first. If your 8-person team is maxed out but RPE is below average, the problem isn't headcount. It's how the 8 people are being used.
Only hire when:
- Your team's utilization is consistently at or above target (75-80% for most service businesses)
- You have a pipeline of work that justifies the hire
- Your systems can absorb a new person without degrading efficiency
- RPE is at or above your category average
Track RPE every time you make a hiring decision. If RPE drops after a hire and doesn't recover within 6 months, something is wrong.
How to Calculate Your RPE and What to Do With the Number
Step 1: Calculate Your Current RPE
Pull your last 12 months of revenue. Count your average headcount (including contractor FTEs) over that same period.
RPE = Last 12 Months Revenue / Average Headcount
Why 12 months? Quarterly RPE is too noisy. Seasonal fluctuations, project timing, and one-time revenue spikes can distort shorter periods. Trailing twelve months smooths it out.
Step 2: Compare to Benchmarks
Find your business type in the benchmark table above. Where do you fall?
- Below Low: You have a serious operational problem. This is urgent.
- Low to Average: There's significant room for improvement. Focus on the 5 factors.
- Average to High: You're running well. Fine-tune and look for the next gear.
- Above High: You're exceptional. Focus on sustaining it as you scale.
Step 3: Diagnose the Root Cause
If your RPE is below where you want it, run through this diagnostic:
Is utilization the problem?
- Track billable vs. total hours for 2 weeks
- If utilization is below 70% for ICs, start there
Is pricing the problem?
- Calculate your effective hourly rate on your last 10 projects
- If it's below your target, you're underpricing or over-delivering
Is process the problem?
- Look at project delivery times vs. estimates
- If you're consistently over-running, your processes are leaking time
Is your tech stack the problem?
- Audit how many manual hours your team spends on tasks that should be automated
- If it's more than 5 hours per person per week, your tools aren't pulling their weight
Is team structure the problem?
- Look at what your highest-paid people spend their time on
- If senior staff are doing junior-level tasks, your structure is wrong
Step 4: Set a Target and Track Monthly
Pick an RPE target. Make it specific and time-bound.
Example: "Increase RPE from $140K to $180K within 12 months."
Then break it down:
- Months 1-3: Fix utilization (target: +$15K RPE)
- Months 4-6: Improve processes (target: +$10K RPE)
- Months 7-9: Adjust pricing (target: +$10K RPE)
- Months 10-12: Optimize team structure and tech (target: +$5K RPE)
Track RPE monthly on a rolling 12-month basis. Report it alongside revenue and profit. Make it a core metric in your business dashboard.
Step 5: Use RPE to Make Better Decisions
Once you're tracking RPE, use it as a filter for every major decision:
- Hiring: "Will this hire maintain or improve our RPE within 6 months?"
- Pricing: "Does this engagement meet our RPE target, or is it pulling it down?"
- New services: "What's the projected RPE of this service line?"
- Client retention: "Is this client's RPE above or below our average?"
- Tool purchases: "Will this tool improve team output enough to move RPE?"
RPE gives you a single lens to evaluate decisions that otherwise feel like gut calls.
RPE by Growth Stage
Your RPE target should change as your business matures.
Early Stage ($0-$500K Revenue)
Expected RPE: $80K-$120K
RPE is naturally lower because the founder is doing everything. Sales, delivery, admin, hiring. That's fine. Focus on finding product-market fit and building repeatable processes.
Priority: Document your delivery process. Start tracking time. Build the operational foundation that will support higher RPE later.
Growth Stage ($500K-$2M Revenue)
Expected RPE: $120K-$180K
This is where RPE should start climbing. You've hired your first team members. Systems matter now.
Priority: Build SOPs. Implement project management. Start tracking utilization. Transition from founder-does-everything to team-delivers-consistently.
Scale Stage ($2M-$5M Revenue)
Expected RPE: $175K-$250K
At this stage, RPE separates the businesses that will scale from the ones that will stall. If your RPE is declining as you grow, you're building a job for yourself, not a business.
Priority: Optimize pricing. Invest in automation. Build the team pyramid. Hire a dedicated ops person if you haven't already.
Mature Stage ($5M+ Revenue)
Expected RPE: $200K-$350K+
High-performing service businesses at scale achieve RPE well above $200K. They've nailed pricing, processes, team structure, and technology.
Priority: Maintain RPE as you grow. Resist the temptation to over-hire. Invest in systems that scale. For a comprehensive playbook on scaling without losing efficiency, see our scaling operations playbook.
The RPE Dashboard
Here's what to track on a monthly basis:
| Metric |
Formula |
Target |
| Revenue Per Employee |
Revenue / Headcount |
Category benchmark |
| Effective Hourly Rate |
Project Revenue / Total Hours |
$150-$250+ |
| Utilization Rate |
Billable Hours / Available Hours |
70-80% (blended) |
| Revenue Per Billable Hour |
Revenue / Total Billable Hours |
Above your rate card |
| Cost Per Employee |
Total OpEx / Headcount |
Below RPE by 30%+ |
| RPE Trend |
Month-over-month change |
Stable or increasing |
When RPE and its supporting metrics are all trending in the right direction, your business is getting more efficient. When they diverge, something needs attention.
FAQ
What is a good revenue per employee for a service business?
For most service businesses, $150K-$200K is a solid benchmark. Marketing agencies should target $150K+, dev shops $200K+, and consulting firms $250K+. But "good" depends on your business type, pricing model, and growth stage. The benchmark tables in this article give you category-specific targets. If you're above average for your category, you're in good shape. If you're below the "Low" threshold, it's time to take action.
How do you calculate revenue per employee?
The formula is simple: divide your annual revenue by your total number of employees. For accuracy, include full-time equivalent (FTE) contractor headcount and use trailing 12-month revenue to smooth out seasonal variation. Example: $2M annual revenue with 12 FTEs gives you an RPE of $166,667.
Is revenue per employee the same as productivity?
Not exactly. RPE measures revenue efficiency, which is influenced by pricing, utilization, process efficiency, and team structure together. A team could be highly productive (working hard, shipping fast) but have low RPE because they're underpriced. Conversely, a team with high RPE might not be "busier" but they've optimized pricing and processes to generate more revenue per hour of effort. RPE is a better metric than productivity because it captures the financial outcome, not just the activity.
What causes revenue per employee to drop?
The most common causes are: hiring faster than revenue grows, declining utilization rates, pricing that doesn't keep up with costs, process inefficiency (especially during growth), and taking on low-value clients or projects. The "adding people doesn't add revenue" trap is particularly dangerous. If you hired 3 people last quarter and RPE dropped, the problem is almost certainly that you added capacity before fixing efficiency.
How can I improve revenue per employee without overworking my team?
Focus on the five operational levers: improve utilization by cutting non-billable overhead (not adding hours), streamline delivery processes so the same work takes less time, shift toward value-based pricing so you capture more revenue per engagement, leverage technology to automate repetitive tasks, and optimize team structure so expensive people do high-value work. None of these require working more hours. They require working smarter.
Should I compare my RPE to tech companies or FAANG?
No. Tech companies like Google ($1.5M+ RPE) and Apple ($2M+ RPE) operate fundamentally different business models. Software scales infinitely. Services don't. Comparing your agency's RPE to Google's is meaningless and demoralizing. Compare within your category and business model. A $200K RPE at a marketing agency is excellent. A $200K RPE at a software company would be a red flag.
Start Tracking RPE This Week
Here's your action plan:
Today: Pull your trailing 12-month revenue and current headcount. Calculate your RPE.
This week: Compare to benchmarks. Are you below average, average, or above? Be honest with yourself.
This month: Run through the five-factor diagnostic. Where's the biggest gap: utilization, process, pricing, tech, or team structure?
This quarter: Pick the biggest lever and focus on improving it by 15-20%. Track RPE monthly.
Most service businesses have 30-50% RPE improvement available without hiring a single new person. The gains are already inside your business, locked up in inefficient processes, poor pricing, and suboptimal team structure.
The businesses that track RPE make better decisions. They hire at the right time. They price with confidence. They scale without chaos.
If you need help diagnosing your RPE gap and building the operational systems to close it, that's exactly what we do.
Book a free strategy call and we'll walk through your numbers together.
Related Reading