If you run two or more entities — separate LLCs, subsidiaries, or distinct business units spread across states — projecting the ROI of a PEO arrangement gets complicated fast. The math that works cleanly for a single-entity, single-state company falls apart when you’re dealing with different headcounts per entity, varying state tax and compliance obligations, separate workers’ comp profiles, and potentially different pricing tiers from the same provider.
Most PEO providers will hand you a generic savings estimate. That number is almost always wrong for multi-entity buyers. It doesn’t account for the structural complexity underneath, and in many cases, it obscures which entities are actually driving the savings and which ones are quietly dragging the arrangement into negative ROI territory.
This guide walks you through building your own projection, entity by entity, so you can see where a PEO actually saves money, where it doesn’t, and where the hidden costs live. You won’t need a finance degree. You will need your actual cost data. No made-up benchmarks, no industry averages standing in for your real numbers.
The goal isn’t to arrive at a single blended figure. It’s to build a structured, honest view of the economics across your entire entity structure — so the decision you make is based on your reality, not a sales deck.
Step 1: Map Every Entity’s Current HR Cost Baseline
Start here, and don’t skip it. The most common mistake multi-entity buyers make is aggregating costs before they’ve understood them at the entity level. That shortcut will cost you later.
List each entity separately. For each one, document the following cost categories:
Payroll burden: This includes employer payroll taxes — federal and state unemployment insurance, Social Security, Medicare — broken out per entity. State unemployment insurance (SUI) rates vary significantly by state and by your entity’s claims history. A California entity and a Texas entity will have materially different SUI profiles even if they’re the same size. Understanding multi-state payroll compliance is essential when mapping these differences.
Benefits spend: Health, dental, vision, and any voluntary benefits. If entities are on separate group plans, capture premiums and employer contributions per entity. If they share a plan, allocate costs proportionally by headcount but flag this as an approximation.
Workers’ comp premiums: This is where multi-entity complexity really shows up. Different entities often have different class codes, different loss histories, and different state rate tables. A manufacturing entity and a professional services entity will have completely different premium structures. Don’t blend these. For a deeper look at unifying coverage, see our guide on workers’ comp multi-entity consolidation.
Compliance costs: Outside counsel fees, compliance consultant retainers, penalties paid in prior years, and any state-specific filing costs. If you’ve hired someone specifically to manage multi-state compliance, allocate their time across entities as accurately as you can.
HR staff and admin overhead: Estimate the hours your HR team spends on each entity’s payroll processing, benefits administration, onboarding, and regulatory filings. Assign a dollar value to that time. It’s real cost even if it doesn’t show up on a single invoice.
Soft costs that people miss: Time spent managing separate payroll runs, reconciling benefits across different carriers, handling multi-state tax filings, coordinating open enrollment for employees in different states. These costs are diffuse and easy to undercount, but they add up across entities.
Why does entity-level granularity matter this much? A 50-person entity in California has a fundamentally different cost profile than a 15-person entity in Texas. California carries higher SUI rates, mandatory state disability insurance, paid family leave contributions, and significantly more compliance complexity. Aggregating both entities into a single baseline hides where the real savings opportunity lives — and where it doesn’t.
By the time you finish this step, you should have a cost baseline document for each entity that covers payroll taxes, benefits, workers’ comp, compliance, and admin overhead. That’s your starting point for everything that follows.
Step 2: Separate What a PEO Actually Changes From What It Doesn’t
Not every cost category shifts when you move to a PEO. Some get cheaper, some stay roughly flat, and some may actually increase — particularly in multi-entity setups where complexity is higher. Getting this wrong inflates your projection with savings that won’t materialize.
For each entity, go through your cost baseline and mark every line item as either PEO-affected or PEO-neutral. Here’s how to think about the common categories:
Health insurance premiums: PEO-affected. PEOs pool employees across their entire client base to negotiate group rates, which can produce meaningful savings for smaller entities that couldn’t access competitive rates on their own. The degree of savings depends on your current plan, your employee demographics, and the PEO’s carrier relationships. Don’t assume savings — get actual quotes and compare them to your current premiums per entity.
Workers’ comp premiums: PEO-affected for most entities. Under a PEO’s master workers’ comp policy, your entity’s loss history may be partially absorbed into the larger pool. This can help entities with poor claims histories. It can also mean entities with excellent loss histories subsidize others in the pool. Understanding how to track workers’ comp accounting through your PEO is critical for verifying these numbers per entity.
Payroll processing fees: PEO-affected. If you’re currently paying a third-party processor per entity, those fees typically get replaced by the PEO’s service. Whether this is cheaper depends on your current setup.
Compliance monitoring: Partially PEO-affected. A PEO can absorb some compliance monitoring functions, particularly around federal employment law and payroll tax filings. But entity-specific state compliance obligations — particularly in states with complex employment law like California, New York, or Illinois — often still require dedicated legal counsel. Don’t assume a PEO eliminates your state compliance legal spend entirely.
Technology and HRIS licensing: Often PEO-neutral or worse. Many businesses keep existing systems running alongside the PEO platform during transition and sometimes permanently. If you’re paying for an HRIS that doesn’t fully integrate with the PEO, you may be paying for both. This is a real and frequently underestimated cost. Our guide on using a PEO alongside your internal HR department covers how to manage this overlap effectively.
Management time during transition: Temporarily PEO-negative. Onboarding multiple entities to a PEO simultaneously creates operational strain. Benefits enrollment windows may not align across entities. Payroll cutover dates create overlap periods where you’re effectively paying twice. Factor this into your year-one cost model.
The discipline here is being honest about which savings are real and which are theoretical. A PEO sales team will often present a savings estimate that assumes every cost category improves. Your job is to pressure-test each line item against your actual entity structure.
Step 3: Model PEO Pricing Across Your Entity Structure
This is where multi-entity buyers frequently get surprised. PEO pricing is rarely as straightforward as a single per-employee-per-month rate applied uniformly across all your entities.
The first thing to understand is that most PEOs price based on two primary models: percentage-of-payroll or flat per-employee-per-month (PEPM). The model matters a lot for multi-entity buyers because the impact isn’t uniform across entities with different wage levels and headcounts. For a broader framework on modeling these costs, our PEO savings projection model guide walks through the mechanics in detail.
Percentage-of-payroll pricing: If a PEO charges, say, 3% of gross payroll, your higher-wage entities pay proportionally more. A professional services entity with $150,000 average salaries will carry a much heavier PEO fee than a retail entity with $40,000 average salaries, even if they have the same headcount. For high-wage entities, this model can quietly destroy ROI even when the lower-wage entities look profitable.
Flat PEPM pricing: This model charges the same amount per employee regardless of salary. It’s more predictable, but it can disadvantage entities with low headcount and complex compliance needs. A 10-person entity in California with high compliance overhead pays the same per-head rate as a 10-person entity in a low-complexity state — but the California entity’s compliance costs are significantly higher, meaning the flat rate covers less of the actual cost burden.
When you request pricing from PEO providers, ask for entity-level breakdowns explicitly. Don’t accept a single master quote that blends all your entities together. If a provider won’t give you entity-level pricing, that’s a transparency problem worth taking seriously. Comparing providers side by side is essential — our top PEO providers comparison can help you benchmark what competitive pricing looks like.
Watch for minimum headcount thresholds. Many PEOs charge a minimum fee per entity, regardless of how few employees that entity has. If you have a 5-person entity and the PEO charges a minimum equivalent to 15 employees, the ROI for that entity is likely negative before you’ve run a single calculation. This is one of the most common ways multi-entity buyers overpay.
Also clarify how the PEO handles entities in different states. Some providers are stronger in certain states and weaker in others. If a provider doesn’t have deep infrastructure in one of your entity’s states, their compliance support may be thinner and their pricing may be less competitive in that market.
Get pricing in writing at the entity level before you model anything. Work with what’s real, not what’s estimated.
Step 4: Calculate Net Savings (or Net Cost) Per Entity
Now you have what you need to run the actual numbers. For each entity, build a simple side-by-side comparison: current annual cost versus projected annual cost under the PEO. Do this line by line, not as a lump sum.
The structure looks like this for each entity:
1. Current annual cost (from your Step 1 baseline): payroll burden, benefits, workers’ comp, compliance, HR admin overhead, payroll processing fees.
2. Projected annual PEO cost: the PEO’s fee for that entity plus any costs that remain outside the PEO arrangement (retained legal counsel, technology costs, etc.).
3. Net annual impact: subtract projected PEO cost from current cost. Positive number means savings. Negative number means the PEO costs more for that entity.
Don’t stop at the steady-state comparison. Year one has additional costs that often don’t make it into projections. Our detailed PEO ROI and cost-benefit analysis guide covers the full range of cost categories you should be capturing.
Transition costs to include: Onboarding fees charged by the PEO, IT and system integration costs, HR staff time diverted to onboarding (this is real labor cost), overlap periods where you’re paying both old payroll infrastructure and the new PEO setup, and benefits enrollment costs if employees are switching plans mid-year.
For multi-entity buyers, these transition costs multiply. If you’re onboarding four entities simultaneously, you’re managing four parallel transitions with potentially different payroll cutover dates, different benefits enrollment timelines, and different compliance requirements in each state. The operational strain is real and the cost is real.
Flag entities where the PEO arrangement is ROI-negative. This is not a failure of the analysis — it’s the point of the analysis. It’s very common for one or two entities in a multi-entity portfolio to be net negative under a PEO while others are clearly positive. Knowing this before you sign is what gives you negotiating leverage or the option to exclude certain entities from the arrangement.
One more thing on risk reduction: some PEO sales conversations lean heavily on compliance risk reduction as a justification when the direct cost savings are thin. Risk reduction is real and worth valuing. But be honest about what it’s actually worth in dollars for each entity. An entity with minimal compliance exposure in a straightforward state shouldn’t be assigned the same risk reduction value as a California entity with active employment litigation risk. Our guide on cost accounting methods for internal HR vs PEO can help you quantify these comparisons more precisely.
Step 5: Stress-Test the Projection With Real Scenarios
A projection based on a single set of assumptions is a guess dressed up as analysis. Before you make a decision, run your entity-level numbers through at least three scenarios.
Best case: All entities see their projected savings. Benefits premiums come in as quoted. Workers’ comp rates hold. Headcounts stay stable. Transition costs come in on budget. This is your ceiling — useful for understanding the upside, but not what you should plan around.
Base case: Two or three entities underperform the projection. Maybe benefits rates are better than current but not as good as quoted. Maybe one entity’s workers’ comp situation doesn’t improve as much as expected. Transition costs run 20% over estimate. This is the scenario you should use for your primary decision-making.
Worst case: Headcount drops at one entity, pushing it below the PEO’s minimum threshold and triggering higher per-employee fees. A state changes its regulatory requirements mid-contract, adding compliance costs you didn’t anticipate. You sell or close one entity and the PEO contract has early termination penalties. Benefits rates increase significantly in year two. This scenario tells you your downside exposure. If the worst case materializes and you need to exit, understanding the process for leaving a PEO should be part of your contingency planning.
Multi-entity buyers face specific risks that single-entity buyers don’t. What happens to your blended pricing if one entity closes? If headcount drops below minimums at your smallest location? If you acquire a new entity mid-contract — does the PEO pricing adjust, and how? These aren’t hypothetical edge cases. They’re predictable events for growing or restructuring businesses.
Model year two and year three explicitly. Most PEO contracts allow annual repricing on benefits and workers’ comp. Your year-one ROI may look solid, but if benefits rates increase and workers’ comp rates adjust at renewal, the picture can shift materially. A projection that only covers year one is incomplete for a multi-year contract commitment.
Also test the partial PEO scenario. Would your overall ROI improve if you placed only your higher-complexity, higher-headcount entities on the PEO and kept smaller or lower-complexity entities on their current arrangements? This is a genuinely underexplored option. PEO sales teams rarely bring it up, but it’s worth modeling. For some multi-entity buyers, a selective PEO strategy produces better economics than an all-in approach.
Step 6: Build a Decision Framework That Goes Beyond the Spreadsheet
The ROI projection gives you a number. The decision is bigger than the number.
Once you have entity-level financial projections stress-tested across scenarios, use them to drive a structured conversation about operational tradeoffs — not just to confirm or deny a single savings figure.
For each entity, work through these questions honestly:
Does the savings justify the loss of control? A PEO co-employs your workforce. That means certain HR decisions go through the PEO’s processes and policies. Understanding how a PEO works at a structural level helps you evaluate what control you’re actually giving up. For some entities — particularly those with specialized HR practices or sensitive employee relations situations — this tradeoff matters more than the cost math.
Is the compliance risk reduction meaningful for this specific entity? A 10-person entity in a low-complexity state with straightforward employment practices probably isn’t carrying much compliance risk to begin with. The risk reduction argument is much stronger for a 60-person California entity in a regulated industry. Weight it accordingly.
Does the PEO’s service model actually fit this entity’s operational needs? Some PEOs are built for professional services firms. Others specialize in industries with high workers’ comp complexity. If a PEO’s core competency doesn’t match one of your entities, the service quality may be lower even if the pricing looks acceptable. Our guide on evaluating and selecting a certified PEO provides a structured framework for assessing provider fit.
A simple entity-by-entity scorecard can help. Rate each entity on financial ROI, operational fit, risk reduction value, and strategic alignment. Weight these factors based on what matters most to your business right now. An entity you’re planning to sell in 18 months should be weighted differently than a core entity you’re scaling.
Know when to walk away. If the projection shows marginal savings spread thin across entities with significant transition risk and a multi-year contract commitment, the economics may not justify the complexity. A PEO is not the right answer for every multi-entity structure, and a projection that’s honest about that is more valuable than one engineered to justify a predetermined conclusion.
Putting It All Together
A multi-entity ROI projection isn’t a single spreadsheet — it’s a structured comparison that treats each entity as its own decision. The businesses that get burned by PEO arrangements are usually the ones who accepted one blended number and assumed it applied evenly across everything they owned.
Before you finalize any decision, run through this checklist:
1. Every entity has its own cost baseline documented, including payroll burden, benefits, workers’ comp, compliance, and admin overhead.
2. You’ve separated PEO-affected costs from PEO-neutral ones for each entity — no inflated projections from savings that won’t materialize.
3. You have entity-level pricing from providers, not just a master blended quote.
4. You’ve calculated net impact per entity including year-one transition costs.
5. You’ve run at least three scenarios — best case, base case, and worst case — including year-two rate adjustments.
6. You’ve evaluated operational fit and risk reduction alongside the financial numbers, and you’ve tested whether a partial PEO approach might outperform an all-in commitment.
If any of those boxes aren’t checked, the projection isn’t finished yet.
When you’re ready to compare providers with the kind of entity-level detail this analysis requires, you need real pricing data — not ballpark estimates. Don’t auto-renew. Make an informed, confident decision. PEO Metrics provides unbiased, side-by-side provider comparisons with actual pricing breakdowns, so you can evaluate your options against the numbers you’ve built here — not the numbers a sales team wants you to see.
