An Executive Playbook for Deciding What to Outsource, What to Keep In-House, and How to Build HR Infrastructure That Scales
There is a stage of business growth when HR stops being a collection of administrative tasks and starts becoming infrastructure.
Payroll has to run accurately. Benefits need administration. New hires need onboarding. Employee records have to remain organized. Managers need HR support. Employment taxes, workers’ compensation, unemployment, wage-and-hour requirements, and other compliance responsibilities continue whether the company has five employees or 150.
The strategic question for a CEO is therefore not simply whether the company “needs HR.” Every employer already has HR responsibilities.
The better question is: What HR operating model makes sense at our current size—and when should that model change?
For many small and midsize businesses, a Professional Employer Organization (PEO) can provide payroll, benefits, HR, workers’ compensation, and compliance infrastructure without requiring the company to build every specialty internally. As headcount and organizational complexity increase, however, there can eventually be a business case for bringing more of those functions in-house.
There is no universal employee count at which that switch should happen. The decision should be based on workload, complexity, cost, internal expertise, risk, and how much control the organization wants over its HR infrastructure.
That is the framework behind two recent conversations with Denali HR President Josh Henderson.
The Executive Decision Map
Before getting into the details, founders can think about the decision in four operating stages.
| Business Stage | HR Question Leadership Should Be Asking |
| Early employer | How do we build compliant payroll and HR processes without hiring an entire department? |
| Growing workforce | How do we support managers, benefits, payroll, compliance, and employees consistently? |
| Increasing complexity | Is outsourcing still more efficient than building specialized internal capabilities? |
| Mature HR operation | Which functions should remain outsourced, and which now justify dedicated internal specialists? |
Notice what is missing from that table: a magic headcount.
Josh mentions roughly 100–200 employees as a range where some businesses may begin to justify internal HR capacity. That is his practical experience, not a statutory threshold or universal industry rule. A 60-person company operating in several states may have considerably more HR complexity than a 150-person company operating from one location with a stable workforce.
Headcount matters.
Complexity matters more.
When Does a Company Outgrow a PEO?
Josh’s first video addresses the other side of the PEO conversation: a PEO does not necessarily have to be the permanent HR model for every company.
As a business becomes larger, leadership may eventually have enough ongoing HR work to justify dedicated internal employees. Josh points out, however, that the first internal HR hire creates its own challenge. One person may suddenly be expected to understand payroll, benefits, compliance, employee relations, recruiting, and onboarding.
That is an unusually broad job.
For some organizations, the economics may become more compelling when the company can support multiple HR specialists rather than asking one generalist to replace an entire outsourced HR infrastructure.
▶️ Watch Josh explain when growing companies may begin considering the move from a PEO to internal HR.
This creates a more useful question than “How many employees do we need before hiring HR?”
Leadership should ask: Do we have enough sustained HR workload—and enough need for specialized internal expertise—to justify rebuilding these functions ourselves?
PART I: Understand What You Are Actually Replacing
Moving away from a PEO is not simply hiring an HR manager.
A PEO relationship can involve multiple employer functions. NAPEO says PEOs provide services including payroll, benefits, workers’ compensation, regulatory-compliance assistance, and other HR services. Its 2026 industry data says PEOs serve more than 230,000 small and midsize businesses employing more than 4.5 million people.
That means the correct comparison is rarely:
PEO fee vs. HR employee salary.
A better comparison is: PEO-supported infrastructure vs. the full internal cost and capability required to reproduce the functions the company currently uses.
An employer moving HR in-house may need to account for some combination of payroll technology, payroll administration, employment-tax processes, benefits administration, HR information systems, employee relations expertise, recruiting, onboarding, workers’ compensation administration, compliance support, employee records, handbook/policy management, manager support, and outside professional services.
The exact list depends on the PEO agreement.
That is why the first step in a PEO exit analysis should be a function inventory, not a job posting.
What Does a PEO Actually Take Off the Owner’s Plate?
Josh’s second video approaches the decision from the founder’s side.
Business owners generally want to spend their time on customers, operations, strategy, products, hiring the right people, and growth. Payroll administration, benefits enrollment, employment paperwork, tax administration, and regulatory processes still have to happen—but they are rarely the reason someone started the company.
A PEO creates a co-employment relationship in which specified employer responsibilities are allocated between the business and PEO.
The key word is specified.
Utah law says the professional employer agreement governs the co-employment relationship and allocates employer rights and obligations between the parties. The statute requires the agreement to address responsibilities including employee compensation, payroll-related taxes, unemployment contributions, certain benefits responsibilities, and workers’ compensation. Utah law also expressly preserves the client’s right to hire, discipline, and terminate covered employees.
▶️ Watch Josh explain what business owners can delegate through a PEO relationship—and what they continue controlling.
The practical value is not that the founder stops being an employer.
It is that the founder no longer has to personally build and administer every employer function.
PART II: The PEO/Owner Responsibility Matrix
This is where founders need more precision than the usual “PEO handles HR” explanation.
Under Utah’s Professional Employer Organization Licensing Act, responsibilities are allocated through the professional employer agreement and applicable law. The PEO must pay compensation to covered employees and withhold, collect, report, and remit specified payroll-related taxes and unemployment contributions. Benefits and workers’ compensation responsibilities also depend on the agreement and statutory framework. The client retains important operating responsibilities, including rights concerning hiring, discipline, termination, and—unless otherwise expressly provided—direction, supervision, training, and control of employees’ work.
| Business Function | What Leadership Should Understand |
| Business strategy | Remains with the business |
| Hiring decisions | Client retains hiring rights under Utah’s PEO framework |
| Compensation decisions | Business determines its workforce/compensation strategy; agreement governs administration |
| Day-to-day work | Generally remains under client direction/control unless otherwise expressly provided |
| Payroll processing | Commonly administered through the PEO relationship |
| Payroll-related taxes | Specific PEO obligations are established under Utah law/agreement; federal treatment depends on arrangement |
| Benefits | PEO may administer/provide benefits according to the agreement and plan structure |
| HR guidance | Common PEO service; scope depends on provider/agreement |
| Employee relations | Management remains involved; PEO HR professionals may advise/support |
| Workers’ compensation | Responsibility must be addressed in the professional employer agreement |
| Compliance | Shared/allocation-dependent rather than a blanket transfer of every legal obligation |
That final row is important.
A PEO is not a legal invisibility cloak for the business.
PART III: PEO, Payroll Provider, and CPEO Are Not the Same Thing
This distinction is especially important for CEOs evaluating providers.
The IRS explains that an ordinary payroll service provider may calculate payroll, prepare tax returns, produce W-2s, and make federal tax deposits, while the employer generally remains liable for its employment-tax obligations.
A Certified Professional Employer Organization (CPEO) has a different federal tax framework. The IRS says a CPEO is generally solely liable for paying specified federal employment taxes, filing returns, and making deposits regarding remuneration it pays to qualifying worksite employees under a CPEO contract, although the rules contain important exceptions and circumstances where both parties may have liability.
CPEO certification is voluntary. To maintain IRS certification, CPEOs must meet requirements involving tax compliance, bonding, audited financial statements, quarterly attestations, and other standards.
For founders, the due-diligence question should therefore be more sophisticated than:
“Do you handle payroll taxes?”
Ask what legal arrangement the provider uses, whether it is an IRS-certified CPEO, what responsibilities the contract assigns to each party, and which employer obligations remain with the client.
PART IV: What Does a Utah Business Still Need to Get Right?
A PEO relationship does not make employment law disappear. It creates infrastructure around responsibilities that would otherwise need to be administered internally.
For example, Utah generally requires employers to withhold Utah income tax for wages paid for work performed in Utah, and Utah withholding calculations use the employee’s federal W-4 and Utah withholding tables. Utah employers also generally must provide workers’ compensation coverage, subject to statutory exceptions.
The PEO structure can help administer applicable processes, but management still needs accurate information flowing into that system. If a company hires someone and never tells the PEO, changes an employee’s compensation without communicating it, allows unrecorded hours, ignores HR guidance, or makes an employment decision outside established procedures, the existence of a PEO does not automatically correct the underlying management problem.
Think of the relationship as an operating system.
The infrastructure can be excellent, but the company still has to use it correctly.
PART V: The Remote-Team Stress Test
A remote workforce is one of the clearest ways to see whether a company’s HR infrastructure is mature enough.
A Utah company can hire an employee who performs all of their work in another state. That can introduce additional questions involving payroll withholding, unemployment insurance, workers’ compensation, wage-and-hour requirements, leave laws, pay notices, new-hire reporting, and other jurisdiction-specific obligations.
Even basic timekeeping becomes important. The U.S. Department of Labor says employers must pay employees for all hours worked that they know or have reason to believe were performed, including qualifying work performed remotely, and its telework guidance discusses employers’ obligation to exercise reasonable diligence in tracking compensable hours.
This is where a scalable HR model earns its value. A growing remote employer needs a repeatable process for identifying work location, onboarding correctly, establishing payroll/tax setup, administering applicable policies, recording time, managing benefits, maintaining employee records, and recognizing when state-specific HR review is necessary.
Whether those functions sit inside the company or with a PEO is a strategic choice.
Someone still has to own them.
PART VI: The Build-vs.-Buy HR Test
Instead of choosing based on headcount alone, leadership can score the organization across six operating questions.
1. Workload
How many hours of recurring work now exist across payroll, benefits, onboarding, employee relations, compliance, recruiting, reporting, and HR administration?
2. Specialization
Does the company need one HR generalist—or expertise across payroll, benefits, employee relations, compliance, recruiting, and HR technology?
3. Geographic Complexity
Are employees working in one state or ten? A distributed workforce can make a relatively small organization operationally complex.
4. Technology
What systems would the company need to purchase, integrate, secure, administer, and maintain if functions moved in-house?
5. Cost
Compare the full cost of the PEO with the fully loaded cost of the replacement model, not simply one employee’s salary.
6. Strategic Control
Which HR capabilities would genuinely become better if they sat internally? Employee experience? Recruiting? Leadership development? Workforce planning? Culture? Compensation strategy?
This framework prevents companies from insourcing simply because they reached an arbitrary employee count.
PART VII: Three HR Operating Models—Not Two
The decision does not have to be PEO or internal HR.
Growing businesses typically have three strategic models available.
| Model | Best Operational Fit |
| PEO-led infrastructure | Company wants broad outsourced payroll/HR/benefits/compliance infrastructure and access to HR expertise |
| Hybrid model | Company has internal HR leadership but continues outsourcing selected administrative/specialized functions |
| Primarily in-house HR | Scale and complexity justify dedicated internal payroll, benefits, employee relations, recruiting, compliance, and HR systems capability |
The hybrid stage is particularly important because it solves the problem Josh identifies in Video 1.
A growing company may hire an internal HR leader because it needs someone embedded in the organization who understands its people, culture, managers, and business strategy. That does not automatically mean the same person should personally process payroll, administer benefits, monitor every compliance requirement, manage workers’ compensation, recruit every role, and handle every employee-relations issue.
An internal HR leader and external HR infrastructure can coexist.
PART VIII: What the 2026 Data Says About Outsourcing
This decision is happening while small and midsize employers are under significant workforce pressure.
NAPEO’s 2026 survey of 500 U.S. business decision-makers found that 67% identified hiring as a major challenge and 62% identified employee retention as a major challenge. The survey also found that 61% outsourced health insurance, 56% outsourced payroll, and 50% outsourced retirement benefits, with businesses citing time savings and focus on core growth among their reasons for outsourcing.
There is also industry-sponsored evidence associating PEO use with business outcomes. NAPEO-commissioned 2024 research by McBassi & Company reported that PEO clients had more than twice the growth rate, 12% lower employee turnover, and were 50% less likely to go out of business than comparable non-PEO businesses during the period studied. Those findings are associations from NAPEO-sponsored research and should not be interpreted as proof that PEO use alone caused those outcomes.
For CEOs, the useful takeaway is not that outsourcing is always better.
It is that outsourcing core employer administration is already a mainstream operating decision—not merely a temporary workaround for very small companies.
PART IX: The PEO Exit Readiness Audit
Before bringing HR functions in-house, leadership should be able to answer the following questions.
People: Who owns payroll? Who administers benefits? Who handles employee relations? Who manages onboarding? Who tracks compliance changes? Who owns workers’ compensation? Who handles payroll-tax administration?
Systems: Which HRIS, payroll, timekeeping, benefits, applicant-tracking, document-management, and reporting systems will replace the existing infrastructure? How will those systems exchange data?
Processes: Are onboarding, terminations, pay changes, leave, performance documentation, complaints, benefits changes, remote hiring, and payroll approvals documented as repeatable workflows?
Compliance: Who monitors federal requirements? Who monitors Utah requirements? Who identifies obligations when a remote employee works in another state?
Continuity: What happens if the only internal HR/payroll employee takes vacation, resigns, becomes ill, or makes an error?
That final question is often overlooked.
Replacing a PEO team with one HR employee can create key-person risk rather than eliminate outsourcing risk.
PART X: Denali HR’s View—Build the HR Model Your Business Needs Now
Josh’s two videos are really describing the same business principle from opposite directions.
A PEO makes sense when a company needs HR infrastructure, expertise, payroll administration, benefits support, and compliance processes but does not want—or cannot yet justify—building every capability internally.
As the organization becomes larger and more sophisticated, that calculation can change. There may eventually be enough recurring workload and strategic value to justify internal HR specialists. The right transition point is not determined by an internet headcount rule. It comes when leadership can demonstrate that the internal model will provide the capability the organization needs at a cost and level of operational resilience that make sense.
At Denali HR, the objective is not to convince a business that it should outsource HR forever.
It is to help the company have the right HR structure for the stage it is actually in.
That can mean payroll administration, benefits, HR support, risk management, compliance processes, employee documentation, and PEO services today—and a different operating model as the organization matures.
Good HR infrastructure should support growth.
It should not become something the company outgrows without a plan.
CEO PLAYBOOK: The Decision in One Page
Before choosing PEO, hybrid, or in-house HR, leadership should be able to document five things:
Current-state cost: What are we actually spending on the existing model?
Replacement cost: What will people, software, benefits administration, payroll infrastructure, outside expertise, and compliance support cost internally?
Capability gap: Which expertise would we gain or lose by changing models?
Risk ownership: Who will own each payroll, benefits, HR, workers’ compensation, tax, employee-relations, and compliance process?
Growth plan: Will this model still work if headcount, states, locations, or organizational complexity increase over the next 24–36 months?
If leadership cannot answer those questions, the company probably is not ready to make the decision based on price alone.
Final Decision
The question is not: “At what employee count should we leave a PEO?”
There is no universal answer.
The stronger executive question is: “At what point can we build an internal HR operation that is more effective, resilient, and appropriate for our business than the infrastructure we currently outsource?”
For some companies, that point comes relatively early. Others may use a PEO or hybrid model much longer. A company with a highly distributed workforce may value external compliance and payroll infrastructure even after hiring internal HR leadership.
What matters is understanding exactly what is being outsourced, what remains with management, what would have to be rebuilt internally, and how the decision supports the next stage of growth.
Do not graduate from a PEO because the company reached an arbitrary number. Graduate when the business case—and the HR infrastructure—are ready.
Planning Your Next HR Operating Model?
Denali HR helps growing businesses evaluate and manage payroll, benefits, HR administration, employee relations, risk management, compliance processes, and PEO services.
For Utah founders deciding whether to outsource HR, build an internal team, or create a hybrid model, the first step should be understanding what the business actually needs—not simply counting employees.
Call: +1 801 480 0002
Talk with Denali HR
About the Author
This article was reviewed by Josh Henderson, Founder of Denali HR.
Denali HR provides payroll services, employee benefits administration, human resources support, risk management, and PEO services for small and midsize businesses.
Sources & Additional Reading
Utah Legislature — Professional Employer Organization Licensing Act — Utah’s statutory framework for PEO co-employment and allocation of client/PEO responsibilities.
IRS — CPEO Customers: What You Need to Know — Federal employment-tax treatment for customers of IRS-certified PEOs.
IRS — Publication 15 (2026) — Current federal employer tax guidance, including payroll outsourcing and CPEO arrangements.
Utah State Tax Commission — Employer Withholding — Utah employer withholding requirements.
Utah Labor Commission — Employers’ Guide to Workers’ Compensation — Utah workers’ compensation requirements for employers.
U.S. Department of Labor — Telework Hours Guidance — Federal guidance concerning compensable work and tracking remote employees’ working time.
NAPEO — 2026 Small and Mid-Sized Business Survey — Current survey data on HR outsourcing, hiring, retention, and business pressures.
NAPEO — PEO Industry Research & Data — Current PEO industry research and market data.
