Well… That Depends.
This is one of the questions I get asked All. The. Time.
“How many team members should I have based on my number of customers?”
“How many team members should I have based on policy count?”
“How many team members should I have based on premium?”
And my answer is always the same.
Well… that depends.
I know.
That’s probably not the neat, simple answer people want.
But it’s the truth.
Because I will never tell someone they should have X number of team members based solely on customer count, policy count, or premium.
Why?
Because there are too many variables.
It Depends on More Than Numbers
Numbers alone do not tell the full story.
What really matters is the environment your team is operating in.
It depends on:
All those things matter. Because not all books of business are created equal.
Not All Customers Create the Same Demand
This is a huge piece people overlook.
Two agencies can have the exact same number of customers and require completely different staffing levels.
Why?
Because their customer demand looks completely different.
Are your customers:
Those things matter.
A book with constant walk-ins, frequent service requests, and highly hands-on customers creates very different demands than a book filled with customers who prefer self-service and digital communication.
Same number of customers.
Very different workload.
The Bigger Question: Are You Efficient?
This is the real question.
Not how many customers do you have.
Not how many policies do you have.
The question is:
How efficiently does your agency operate?
That’s what really determines capacity.
Some agencies are drowning with smaller books of business.
Others are thriving with much larger books.
Why?
Efficiency.
Or lack of it.
Are Your Team Members Doing Real Work…or Duplicate Work?
This is where systems and processes matter.
If your team is bogged down by:
You will need more people.
Not necessarily because demand is higher.
Because inefficiency is higher.
And inefficiency is expensive.
Very expensive.
It costs time.
It costs energy.
It costs capacity.
More People Doesn’t Always Solve the Problem
This is where agencies get stuck.
Things feel chaotic.
The team feels overwhelmed.
Leadership assumes:
“We need more people.”
Maybe.
But maybe not.
Sometimes the problem isn’t staffing.
Sometimes the problem is inefficiency.
Adding more people to broken systems rarely fixes the real issue.
It usually just creates more complexity.
More handoffs.
More communication breakdowns.
More confusion.
Efficient Agencies Create Capacity
Someone might look at one book of business and assume they are understaffed based on their team size.
From the outside, they may think:
“There’s no way that team can support that many customers.”
But from the inside?
I may look at it and think something completely different.
I may think:
“This team has capacity.”
They have time to sell.
Time to serve well.
Time to build relationships.
Time to focus on meaningful work.
Why?
Because they aren’t drowning in unnecessary work.
They aren’t buried in duplicate tasks or inefficient processes.
That changes everything.
Are You Training Customers to Be Efficient?
This is another big one.
Are we training our customers to do business efficiently?
That matters.
A lot.
Are we teaching them:
Are we leveraging technology to improve the customer experience?
Because we should be.
Not to avoid helping people.
To create better experiences.
Technology, automation, and customer education create capacity.
They allow customers to handle simple things quickly.
They allow teams to spend more time where they add the most value.
That means more time for:
That’s where great agencies win.
The Real Question Isn’t “How Many People Do I Need?”
The real question is:
How efficiently does my business operate?
Because if you are not leveraging:
You are going to need more people.
Not because the workload demands it.
Because inefficiency demands it.
And that’s a very different problem.
So if you ask me:
“How many team members should I have?”
My answer will probably always be the same.
It depends.
Are you efficient?
Or are you not?
That’s the question worth answering first.