🧞‍♂️ New to Exponential Scale? Each week, I provide tools, tips, and tricks for tiny teams with big ambitions that want to scale big. For more: Exponential Scale Podcast | Scalebrate | Scalebrate Hub

Founding Supporters: Support the following people and companies because they supported us from the beginning: DataEI | Dr. Bob Schatz | .Tech Domains | Fairman Studios | Jean-Philippe Martin | RocketSmart AI | UMBC

Latest Podcasts: What You Missed

Revenue-Per-Person Metrics: The True Scaling Indicator

You hire your first employee. Revenue goes up. You hire another. Revenue goes up again.

So you keep hiring. Five people. Then ten. Then fifteen.

But one day, you look at your P&L and realize: you're making the same profit as when you had five people. You've tripled headcount, but you haven't tripled results.

What went wrong?

You optimized for growth, not leverage. You measured headcount, not productivity. You built a bigger team—but not a more efficient one.

The companies that scale smart don't ask, "How many people do we have?" They ask, "How much revenue does each person generate?"

That's Revenue Per Person (RPP). And it's the most underrated scaling metric.

The $2M Company with a $200K Problem

Let me tell you about Marcus, founder of a 12-person software consulting firm.

Marcus's business was growing. Year one: $800K revenue, 4 people. Year two: $1.5M revenue, 8 people. Year three: $2M revenue, 12 people.

On the surface, that looked great. Revenue was up 150% over three years.

But Marcus felt stuck. He was working harder than ever. Payroll was ballooning. And profit margins were shrinking.

So Marcus did the math:

Revenue Per Person (RPP):

  • Year 1: $800K ÷ 4 = $200K per person

  • Year 2: $1.5M ÷ 8 = $187K per person

  • Year 3: $2M ÷ 12 = $167K per person

Revenue was growing. But efficiency was declining.

Each new hire was generating less revenue than the last. Marcus was scaling up, but he wasn't scaling smart.

Think of it like adding more engines to a plane. More engines = more power, right?

Not if each new engine adds weight, complexity, and drag. At some point, you're burning more fuel than you're gaining in speed.

Marcus had hit that point. He was hiring to solve problems—but each hire created new overhead, communication costs, and management burden.

He needed to flip the equation: instead of adding people to grow revenue, he needed to grow revenue per person.

Marcus set a new goal: increase RPP from $167K to $250K within 12 months—without cutting headcount.

Here's what happened:

12 months later:

  • Revenue: $3M (up 50%)

  • Headcount: 12 (same)

  • RPP: $250K per person (up 50%)

Profit margins doubled. Marcus worked less. The team was more focused.

How? He didn't hire faster. He scaled smarter.

What Is Revenue Per Person (RPP)?

Revenue Per Person = Total Revenue ÷ Total Headcount

It's the simplest, most revealing metric for operational efficiency.

High RPP = Leverage. Your team is productive, processes are efficient, and you're not over-hiring.

Low RPP = Bloat. You're paying people to do work that doesn't directly drive revenue.

Why RPP matters for microteams:

  • Every hire is expensive. Salary + benefits + taxes + overhead = 1.4x salary. A $60K hire actually costs you $84K.

  • Coordination costs scale non-linearly. Two people = 1 connection. Five people = 10 connections. Ten people = 45 connections. More people = exponentially more communication overhead.

  • Not all work drives revenue. Admin, internal meetings, "process improvement" tasks—these can consume 30-50% of a team's time if you're not careful.

RPP forces you to ask: "Is this person generating more value than they cost?"

Why This Matters for Microteams

Big companies can afford inefficiency. Google, Microsoft, Facebook—they have RPP in the $1M-2M range because they're printing money.

Microteams? Your RPP might be $100K-300K. And that's fine—as long as it's going up, not down.

Here's why tracking RPP is critical:

  • It reveals productivity trends. If RPP is declining as you grow, you're scaling inefficiently.

  • It prevents premature hiring. Before adding headcount, ask: "Could we hit this revenue target by improving RPP instead?"

  • It highlights automation opportunities. If one person is doing $500K in revenue, what are they doing that others aren't? Can you replicate it?

  • It keeps you lean. The goal isn't to build a big company—it's to build a profitable one.

The best microteams have RPP 2x-3x higher than their competitors. They're not working harder—they're working with more leverage.

The RPP Optimization Framework

Here's how to measure, track, and improve your Revenue Per Person.

Step 1: Calculate Your Current RPP

Formula:

RPP = Annual Revenue ÷ Full-Time Headcount

Example:

  • Annual revenue: $1.5M

  • Headcount: 8 people

  • RPP = $1.5M ÷ 8 = $187.5K per person

Count as headcount:

  • Full-time employees

  • Founders actively working in the business

  • Full-time contractors

Don't count:

  • Part-time contractors (prorate them: 20 hrs/week = 0.5 FTE)

  • One-off freelancers

Step 2: Benchmark Against Your Industry

Industry RPP benchmarks (rough averages):

  • SaaS companies: $150K-400K (higher if product-led growth)

  • Agencies / consulting: $100K-250K

  • E-commerce: $200K-500K (low labor, high automation)

  • Professional services: $150K-300K

  • Content / media: $100K-200K

Your goal: Be in the top quartile for your industry.

If your RPP is below average, you're either under-pricing, over-hiring, or under-leveraging.

Step 3: Identify RPP Killers

Common reasons RPP declines:

1. Hiring for busy work instead of revenue work

  • Admin, coordination, "process improvement" roles that don't directly generate revenue

2. Poor delegation

  • High-value people doing low-value tasks (founder answering support emails instead of closing deals)

3. No automation

  • Humans doing work that software could handle

4. Overhead creep

  • Too many internal meetings, reports, check-ins

5. Low pricing

  • Undercharging clients = more work for same revenue

Audit your team: Who's directly generating revenue? Who's supporting revenue generation? Who's doing neither?

Step 4: Set an RPP Target

Goal: Increase RPP by 20-30% year-over-year.

How:

Option 1: Grow revenue faster than headcount

  • Automate, systematize, delegate to AI/contractors

  • Raise prices

  • Upsell existing clients

Option 2: Keep revenue flat, reduce headcount

  • Fire low performers

  • Automate roles

  • Outsource non-core work

Option 3: Grow revenue, freeze hiring

  • This is Marcus's approach: grow 50%, same team size

Most microteams should aim for Option 3.

Step 5: Track RPP Quarterly

Set up a simple dashboard:

Quarter

Revenue

Headcount

RPP

Change

Q1 2026

$400K

8

$50K

Q2 2026

$450K

8

$56.25K

+12.5%

Q3 2026

$500K

9

$55.5K

-1.3%

Red flag: RPP declining quarter-over-quarter.
Green flag: RPP increasing while headcount stays flat or grows slowly.

Step 6: Increase RPP Through Leverage

Five ways to boost RPP without hiring:

1. Automate low-value work

  • Use AI for customer support, data entry, reporting

  • Example: One person handling 500 tickets/month instead of 200

2. Raise prices

  • 10% price increase = 10% RPP increase (if you don't lose clients)

3. Fire low-performing clients

  • Drop the bottom 10% of clients by revenue

  • Reallocate time to high-value clients

4. Delegate down

  • Founders should do $500/hr work, not $50/hr work

  • Hire a $25/hr VA to handle admin

5. Productize your service

  • Turn custom work into repeatable packages

  • Example: Custom consulting → templated workshops

Step 7: Use RPP to Guide Hiring Decisions

Before making a hire, ask:

1. Will this hire increase RPP?

  • If yes → hire them

  • If no → find another way

2. Can we hit the same goal by improving RPP instead of adding headcount?

  • Example: Instead of hiring a second salesperson, can we improve the first one's close rate from 20% to 30%?

3. What's the breakeven RPP for this hire?

  • Example: Hiring a $60K person (true cost = $84K). They need to generate at least $84K in new revenue to maintain RPP.

Rule: Only hire when you've maxed out leverage from your current team.

The RPP Ceiling and How to Break It

At some point, RPP will plateau. You can't keep squeezing more revenue out of the same people forever.

When you hit the ceiling:

1. Shift to higher-value work

  • Stop doing $10K projects, start doing $50K projects

  • Same effort, 5x revenue

2. Build leverage into your business model

  • SaaS scales better than consulting

  • Courses scale better than 1:1 coaching

  • Licensing scales better than custom dev

3. Hire for multiplication, not addition

  • Hire people who enable others to be more productive (great manager, systems builder)

  • Not just "another pair of hands"

Today's 10-Minute Action Plan

You don't need to overhaul your entire team today. Just calculate your RPP and set a target.

Here's what to do in the next 10 minutes:

  1. Pull your revenue from last month (or last quarter, or last year)

  2. Count your headcount (full-time people only)

  3. Calculate RPP — Revenue ÷ Headcount

  4. Compare to industry benchmarks — are you above or below average?

  5. Set a goal — increase RPP by 20% in the next 12 months

That's it. One number, one goal, 10 minutes.

Next quarter, measure again. If RPP is going up, you're scaling smart. If it's going down, you're scaling inefficiently—time to automate, delegate, or cut.

A Final Thought

Revenue is a vanity metric. Profit is a sanity metric. But RPP is a scaling metric.

It tells you whether you're building a lean, efficient machine—or a bloated, inefficient one.

Most founders celebrate hitting $1M, $2M, $5M in revenue. But they don't ask: how many people did it take to get there?

The best microteams don't just grow revenue. They grow revenue per person.

Because the goal isn't to build a big team.

The goal is to build a high-leverage team.

Refer Folks, Get Free Access

That’s it for this issue.

Think Big. Stay Lean. Scale Smarter.

— Scalebrate

Recommended for you