Most M&A integration models get HR wrong. Not because the people building them are careless, but because HR cost structures are genuinely complicated — and PEO arrangements are a category that most deal teams have never modeled before.
Here’s the specific problem: when either the acquiring company, the target, or both are running their workforce through a Professional Employer Organization, you’re not dealing with a standard HR budget line. You’re dealing with co-employment contracts, bundled insurance pools, workers’ comp master policies, and compliance infrastructure that doesn’t translate neatly into a traditional G&A synergy calculation. Apply generic assumptions and your savings projections will be wrong — sometimes significantly wrong.
This article is a practical walkthrough for business owners and finance leads who need to build a real PEO M&A integration cost savings model during a deal. Not a theoretical one. Not one that looks good in a deck and falls apart six months post-close. One that actually holds up when you’re sitting across from a CFO asking why the HR synergies aren’t materializing.
This is a leaf-level topic. If you need background on how PEOs work or general M&A workforce integration principles, those fundamentals are worth reviewing separately before diving in here. What follows assumes you already have that foundation and need to go deeper on the cost modeling itself.
Why Standard Integration Models Miss the PEO Layer
In a typical M&A cost synergy model, HR expenses get rolled into G&A and treated as a relatively straightforward reduction target. Cut duplicate headcount, consolidate systems, eliminate redundant vendor contracts. The math feels clean.
PEO arrangements break that logic immediately.
When a company uses a PEO, its HR costs aren’t organized the way a traditional HR budget is. There’s no separate line for “health insurance premiums” because those premiums flow through the PEO’s master policy. There’s no standalone workers’ comp budget because that’s pooled through the PEO’s experience modification rate. Payroll taxes, compliance filings, and HR administration are bundled into a per-employee-per-month fee structure that obscures the true cost of each component.
This means that when you’re building integration synergies, you can’t just look at the target’s income statement and extract an HR cost number. The real costs are embedded in the PEO fee schedule, the benefits contribution structure, and the underlying insurance policies — none of which show up cleanly in standard financial statements. Understanding the full PEO pricing and cost structure is essential before you can decompose these bundled expenses into modelable line items.
The co-employment structure adds another layer of complexity. Savings in a PEO context aren’t just about eliminating duplicate positions. They involve renegotiating master health plans based on the combined employee census, restructuring workers’ comp pools that now reflect a different risk profile, and potentially consolidating compliance infrastructure across multiple states. These are not headcount-driven savings. They’re contract and structure-driven savings, and they behave very differently.
Timing is also a real constraint that generic models ignore. PEO contracts typically run on annual cycles with 30 to 90 day termination notice requirements, and many include early termination fees. Benefits plans lock in at open enrollment. This means the savings you project don’t start flowing on Day 1 of close — they’re gated behind contract cycles and renewal windows that can push realization out by six to eighteen months depending on where you are in the calendar when the deal closes.
The practical implication: PEO-related integration savings need their own isolated model, with its own timeline, its own inputs, and its own set of assumptions. Lumping them into a generic G&A reduction target is how you end up with projections that never materialize.
The Five Cost Buckets That Drive PEO Integration Savings
Building a credible PEO integration savings model starts with understanding where the savings actually come from — and where they don’t. There are five core buckets, and each one behaves differently.
Benefits Plan Consolidation and Rate Arbitrage: This is typically the largest potential savings area, and the hardest to model accurately. When two companies merge, there’s an opportunity to consolidate onto a single health plan and negotiate rates based on the combined employee census. Larger pools can mean better rates — a dynamic explored in depth when you look at PEO insurance pooling savings estimation. But this only works if the combined workforce’s claims experience is favorable. Merging a high-utilization workforce into a low-claims pool can raise rates for everyone. You need actual census data and ideally claims history from both entities before you can make any credible projection here.
Workers’ Comp Experience Mod and Premium Pooling: PEOs carry workers’ comp through master policies with their own experience modification rates. When entities merge, the combined workforce changes the risk profile. If the target’s workforce is in lower-risk job classifications, consolidation can improve the combined mod and reduce premiums. If the target operates in industries with higher injury rates, the opposite happens. This bucket can produce negative savings — meaning costs go up — and that outcome needs to be modeled explicitly using a sound workers’ comp cost allocation model, not ignored.
Payroll Administration and Tax Filing Redundancy: This is the most predictable bucket. Two companies running separate payroll systems, separate tax filings, and separate HR administration create genuine duplication. Consolidating onto a single PEO relationship or a single payroll platform eliminates that redundancy. The savings here are real and relatively straightforward to quantify once you have the current cost per employee for each entity.
Compliance and Legal Exposure Reduction: PEOs carry significant compliance infrastructure — employment law updates, state registration maintenance, HR policy management, and shared liability for certain employment practices. When two entities are running separate PEO arrangements or one is running standalone HR, there’s often duplicated compliance overhead. Consolidation can reduce that overhead, though the savings are harder to quantify and often show up as risk reduction rather than direct cost reduction.
PEO Admin Fee Elimination or Renegotiation: PEO administrative fees are typically charged on a per-employee-per-month basis or as a percentage of payroll. Combined headcount gives you negotiating leverage. If the acquiring company is already in a PEO relationship, bringing the target’s employees onto that same contract increases the headcount base, which can justify renegotiating the per-employee rate downward. Alternatively, if the deal creates enough scale to move away from a PEO entirely and build internal HR infrastructure, the admin fee elimination becomes a direct savings line. This bucket is the most predictable of the five once you have the current fee schedules.
The honest note here: not all five buckets produce savings in every deal. Workers’ comp and benefits consolidation in particular can move in either direction depending on workforce composition. A model that only shows upside across all five buckets isn’t a model — it’s a wish list.
Building the Model: Inputs, Assumptions, and Where to Stress-Test
A PEO integration savings model is only as good as the data feeding it. Before you can build anything credible, you need specific inputs from both entities.
On the PEO contract side, you need current fee schedules for both companies, broken down by component where possible. Per-employee-per-month admin fees, benefits contribution splits between employer and employee, workers’ comp premium rates and current experience mod factors, and payroll processing costs. If either entity is not currently using a PEO, you need their equivalent standalone costs for each category — a process that mirrors building an enterprise HR cost baseline before evaluating providers.
On the workforce side, you need employee census data: headcount by state, job classification, benefits enrollment status, and tenure. This feeds both the benefits underwriting projections and the workers’ comp risk assessment. Without accurate census data, benefits savings projections are essentially guesses.
Once you have the inputs, the model needs three distinct time horizons, and this is where most integration models fail by only showing one.
Day 1 savings are what you can capture immediately at close. These are typically limited to eliminating truly redundant vendor contracts and administrative overhead that doesn’t require contract renegotiation. For PEO arrangements, Day 1 savings are usually small because the contracts are still in place.
Year 1 savings reflect what you can capture after the first full contract renewal cycle and open enrollment period. This is where benefits consolidation and PEO fee renegotiation typically become available. Year 1 is the most operationally realistic savings horizon for most PEO-related line items.
Run-rate savings represent steady state after full integration — the ongoing annual benefit once everything is consolidated. This is the number that typically shows up in deal decks, and it’s the most optimistic view. Presenting only run-rate savings to deal stakeholders without showing the timeline to get there is misleading and sets up post-close disappointment.
Stress-testing matters more here than in most synergy categories. Ask what happens if employee attrition post-merger runs higher than projected — because PEO fee savings tied to combined headcount leverage disappear if headcount drops. Ask what happens if the PEO won’t renegotiate rates on the combined entity and requires full re-underwriting. A structured PEO scenario analysis financial model helps you map these contingencies explicitly. Ask what happens if state-specific requirements prevent consolidation in certain jurisdictions. Each of these scenarios should have a modeled outcome, not just a footnote.
The most useful version of this model shows a range — conservative, base, and upside — with explicit assumptions attached to each line item. That’s what survives contact with reality post-close.
Where These Models Break Down After the Deal Closes
The gap between projected PEO integration savings and realized savings is often significant. Here’s where the breakdowns happen most consistently.
The most common failure is assuming both workforces can be moved onto a single PEO contract immediately after close. In practice, PEO providers often require new underwriting for the combined entity. The resulting rates may not match what was projected during diligence — particularly if the combined workforce has different claims history, job classification mix, or geographic distribution than the PEO’s existing book of business. Running a PEO cost variance analysis against your original projections helps identify where the numbers diverged and why.
Regulatory complexity is underestimated in multi-state deals. Workers’ compensation is the most common trap. Ohio, North Dakota, Washington, and Wyoming operate monopolistic state workers’ comp funds — meaning PEOs cannot provide workers’ comp coverage in those states. If the target has operations there, the workers’ comp consolidation savings you modeled simply don’t exist for that portion of the workforce. This isn’t a minor footnote; it can materially affect the model if those states represent a significant employee concentration.
PEO registration requirements also vary by state. Some states require PEOs to register and maintain separate licensure. If the acquiring company’s PEO isn’t registered in states where the target operates, you’re either waiting on registration approvals or you’re running parallel arrangements longer than planned — both of which delay savings realization.
The third failure mode is cultural and operational, and it’s the one finance teams are least prepared for. The target’s employees may be on a PEO-administered benefits plan they genuinely value — better health coverage, a retirement match structure, or supplemental benefits that the acquirer’s plan doesn’t offer. Forcing migration to the acquirer’s plan creates retention risk, particularly among the employees you most want to keep. The savings projection assumed a clean headcount transfer. The reality is that some percentage of key employees leave, and the cost of replacing them erodes or eliminates the projected benefit.
None of these failure modes are unavoidable. But they’re only manageable if you’ve modeled them before close, not discovered them after.
When PEO Cost Modeling Actually Changes the Deal
Most of the time, PEO integration savings are a secondary line item in a larger synergy picture. But there are specific scenarios where getting this model right materially affects deal structure or valuation.
The clearest upside scenario: a target company that has never explored PEO and is paying well above market for standalone HR administration, benefits, and workers’ comp. This is more common than you’d expect, particularly in companies that grew quickly without ever revisiting their HR infrastructure. Comparing those standalone costs against PEO alternatives — essentially a rigorous PEO vs internal HR cost modeling exercise — often reveals the magnitude of the opportunity. If the acquirer already has a mature PEO relationship with favorable rates, onboarding the target’s workforce can generate meaningful savings that weren’t available to the target independently. That’s a real synergy — not a theoretical one — and it should be reflected in the deal math.
The opposite scenario is less intuitive but equally important. Sometimes the target’s PEO arrangement is genuinely better than what the acquirer has. Better health plan rates because of favorable claims history. Better workers’ comp rates because of a clean safety record. Better admin fee economics because of a longer relationship with the PEO. Forcing that workforce onto the acquirer’s infrastructure destroys a cost advantage that was embedded in the target’s operating model. Understanding how to properly adjust for PEO relationships in M&A valuation ensures this hidden value isn’t overlooked or destroyed during integration planning.
How you present these findings to deal stakeholders matters. The temptation is to show the best-case number. Resist it. Use ranges, not point estimates. Separate confirmed savings — things you can commit to based on existing contract terms — from contingent savings that depend on PEO cooperation, regulatory approvals, or employee acceptance. Tie each line item to a specific integration milestone with a realistic date. A savings model that shows $X in Year 1 with clear dependencies attached is far more credible, and far more useful, than a single run-rate number with no timeline.
Deal teams that do this work properly sometimes find that PEO-related savings are larger than expected, which can support a higher purchase price. More often, they find that projected savings were overstated, which is equally valuable — it’s better to know before you close than after.
Building a Model Worth Trusting
A PEO M&A integration cost savings model isn’t a spreadsheet exercise you do once and file away. It’s a decision tool. It should influence how you structure the deal, how you sequence the integration, and how you set expectations with investors and leadership about when HR synergies actually show up in the financials.
The model is only as good as the underlying data. PEO contract details, current fee schedules, benefits contribution structures, workers’ comp mod rates, and employee census data need to come out of due diligence — not estimated after the fact. That means PEO arrangements should be on the diligence checklist early, not treated as an HR detail to sort out post-close.
If you’re going into a deal and you don’t have a clear picture of what either entity’s PEO relationship actually costs on a per-employee basis, you’re modeling blind. The same applies if you’re evaluating whether to consolidate onto a single PEO or renegotiate an existing arrangement post-close — without accurate market comparisons, you don’t know if the rates you’re being offered are actually good.
That’s where having unbiased, data-driven PEO comparisons becomes genuinely useful — not as a procurement exercise, but as a modeling input. Knowing what comparable arrangements cost in the market gives you a realistic anchor for your savings projections and helps you push back when a PEO comes back with post-merger rates that don’t reflect the leverage your combined headcount should create.
The goal is a model that holds up. One where the savings you project are savings you can actually capture, on a timeline you can actually defend. That’s what separates a useful integration model from one that creates problems six months after close.
