I used to assume HR complexity followed headcount.
Ten people should be simple.
Fifty should be harder.
A hundred should be much harder.
Then I started looking at how different businesses actually operate.
A company with 100 people working similar jobs in one location can sometimes have a more predictable workforce structure than a 30-person business spread across several states, using different schedules, roles, and employment arrangements.
That’s when headcount stopped being my favorite measure of HR complexity.
Thirty People Doesn’t Always Mean a Small HR Problem
Consider two businesses.
Company A
100 people.
One location.
Similar roles.
Relatively stable workforce.
One management structure.
Company B
30 people.
Four states.
Remote and on-site positions.
Different job types.
Seasonal hiring.
Several managers.
Frequent workforce changes.
Which company creates more unusual HR situations?
It isn’t automatically Company A.
Company B may have fewer people but many more variables.
Geography Multiplies Questions
Adding another state doesn’t simply add another address to the company directory.
Where people work can affect employment-related requirements and administrative responsibilities.
That means a distributed company has to think geographically.
A procedure that works perfectly for one group may need another review before leadership assumes it applies everywhere.
For a small business, that can create surprising complexity very quickly.
Different Roles Create Different Situations
A 30-person business might include:
- Office staff
- Field teams
- Supervisors
- Salespeople
- Remote workers
- Part-time roles
- Seasonal positions
Now the company isn’t managing one repeatable workforce pattern.
It’s managing several.
Each additional variation creates another place where managers need clear guidance.
Remote Work Changed the Math
Remote hiring makes this especially interesting.
A company can remain physically tiny while its workforce becomes geographically complicated.
Leadership might still sit in one office with six desks.
Meanwhile, employees work from multiple jurisdictions.
From the outside, it looks like a small company.
Administratively, it may no longer behave like one.
Turnover Matters More Than the Snapshot
Headcount tells me how many people are here today.
It doesn’t tell me how much workforce activity happened during the year.
A stable 100-person company might replace relatively few people.
A 30-person seasonal business could repeatedly bring people in and out.
That creates much more administrative movement than the number “30” suggests.
I started thinking about workforce velocity, not just workforce size.
Growth Rate Matters Too
A business with 30 people today may have had 12 people six months ago.
That’s a completely different situation from a company that has remained at roughly 30 people for ten years.
Fast growth creates:
- New managers
- New responsibilities
- New procedures
- More questions
- More exceptions
- More opportunities for inconsistency
The organization is changing while everyone is still trying to run it.
Manager Count Can Add Complexity
Suppose 30 employees report to one experienced leadership team.
Now compare that with 30 employees divided among six managers.
The second structure creates more management handoffs.
Each manager needs to understand where their authority begins and ends.
Without a consistent framework, six managers can create six different interpretations of the same workforce issue.
Seasonal Businesses Have Their Own Rhythm
A business might look simple during its quiet period.
Then peak season arrives.
Hiring increases.
Schedules change.
More managers become involved.
The workforce expands rapidly and later contracts.
The HR infrastructure has to support the busy version of the company, not just the calm version visible in February.
Industry Can Matter More Than Size
Different businesses face different workforce realities.
A professional office with 40 long-tenured employees isn’t administratively identical to a 40-person company with field operations, physical workplace risks, seasonal changes, and several locations.
That’s why I don’t think a business should evaluate HR needs using headcount alone.
The operating model matters.
Exceptions Are a Better Warning Sign
One thing I watch for is how often leadership says:
“Normally we do X, but in this case…”
Every company has exceptions.
But when exceptions become routine, administration gets harder.
Five unusual cases among 30 people can create more work than 100 people following one predictable process.
This Changes How I Think About Internal HR Staffing
If I only look at headcount, I might say:
“We’re too small to need much HR infrastructure.”
But that’s the wrong question.
I should be asking:
“How complicated is our workforce to administer?”
A relatively small company can still need significant HR knowledge and support.
That doesn’t automatically mean building a large internal department.
It means recognizing the actual complexity instead of dismissing it because the company hasn’t reached an arbitrary size.
Where Trion Solutions Enters the Picture
This is one reason the PEO model can be relevant beyond simply “large” businesses.
A company may have modest headcount while dealing with a complicated workforce structure.
Working with a PEO such as Trion Solutions can give the organization external HR support across areas that would otherwise require additional internal knowledge and administrative capacity.
The business can then evaluate its needs based on operational reality rather than waiting until it reaches some imagined employee threshold.
I Use a Different Complexity Checklist Now
Instead of asking only:
How many people do we have?
I also ask:
✅ How many locations do we operate?
✅ Where do our people work?
✅ How different are their roles?
✅ How quickly are we growing?
✅ How much turnover do we experience?
✅ Do we hire seasonally?
✅ How many managers make workforce decisions?
✅ How often do unusual cases appear?
✅ How much time does leadership spend resolving HR administration questions?
Those answers tell me much more than headcount alone.
A Small Company Can Still Have a Big Infrastructure Problem
That’s the idea I wish I’d understood earlier.
“Small business” describes size.
It doesn’t necessarily describe simplicity.
A 30-person organization can be spread across locations, growing rapidly, hiring frequently, operating with several management layers, and dealing with a wide variety of workforce situations.
Meanwhile, another business with three times the headcount may have a remarkably predictable structure.
So I no longer ask whether a company is “big enough” to think seriously about HR infrastructure.
I ask whether its workforce has become complicated enough that informal administration is starting to become a liability.
Those are two very different thresholds.