Case Study: PEO vs Direct Payroll — A 15-Person Company with Employees in 5 States

For a startup with employees spread across five states, the choice between direct state-by-state payroll registration and a professional employer organization is one of the most consequential operational decisions the CFO will make in any given year. The cost difference between the two approaches can exceed fifty thousand dollars annually, and the wrong choice can produce compliance gaps, hiring friction, and audit exposure that compound over time. This case study walks through the full cost stack for a 15-person company with employees in California, New York, Texas, Washington, and Massachusetts, and identifies the break-even point at which the PEO model becomes net cheaper than direct registration.

The scenario

TechFlow Inc. is a venture-backed software startup with 15 employees distributed across five states: 5 employees in California, 4 in New York, 3 in Texas, 2 in Washington, and 1 in Massachusetts. The company is headquartered in San Francisco, with a satellite office in New York City and remote employees in the other three states. Total annual payroll is $2.4 million, with salaries ranging from $120,000 for junior engineers to $300,000 for senior management. The company has a Section 125 cafeteria plan and offers health insurance through a small-group plan in California, with the same plan extended to out-of-state employees through a network with national coverage. The CFO is evaluating two options for 2026: registering directly in all five states for payroll, SUI, and workers compensation, or moving to a PEO such as Gusto, Rippling, TriNet, or Insperity.

The tax problem

The structural problem is that multi-state payroll requires registration in each state where an employee performs services, with separate employer identification numbers, separate SUI accounts, separate workers compensation policies, and separate quarterly and annual filings in each state. Each state has its own SUI wage base, new-employer rate, and reporting cadence, and each state requires periodic reconciliation between payroll tax deposits and filed returns. A 15-person company with five-state exposure can easily spend 80 to 120 hours per year on payroll tax administration alone, plus another 40 to 60 hours on HR compliance, benefits administration, and workers compensation management.

The PEO model collapses this complexity by becoming the employer of record in each state and aggregating the company's employees into the PEO's master payroll, benefits, and workers comp programs. The PEO charges an administrative fee that is typically 2 to 5 percent of gross payroll, plus a per-employee-per-month fee in some pricing models. For TechFlow's $2.4 million payroll, the PEO fee ranges from approximately $48,000 to $120,000 per year, depending on the level of service and whether benefits are included. The question is whether the bundled services—benefits, HR, compliance, workers comp, multi-state payroll—justify the premium over direct registration.

Step 1: Determine residency classification

For an employer-side analysis, residency classification means identifying where each employee is a resident for income tax purposes and where each employee performs services. TechFlow's 5 California employees are California residents performing services in California, generating California-source wages and California SUI wage liability. The 4 New York employees are New York residents performing services in New York, generating New York-source wages and New York SUI wage liability. The 3 Texas employees are Texas residents performing services in Texas, generating no state income tax liability but producing Texas SUI wage liability. The 2 Washington employees are Washington residents performing services in Washington, producing Washington SUI and Washington paid family and medical leave liability. The 1 Massachusetts employee is a Massachusetts resident producing Massachusetts-source wages and Massachusetts SUI liability.

The residency classification is straightforward because each employee both lives and works in the same state. There is no convenience-rule or reciprocity complexity at the employee level. The complexity is entirely on the employer side, where TechFlow must register, file, and remit in each of the five states.

Step 2: Identify which states have nexus

TechFlow has employer payroll tax nexus in California, New York, Texas, Washington, and Massachusetts because each state has at least one employee performing services in the state. The nexus threshold for employer payroll tax registration in each state is the presence of at least one employee performing services, regardless of whether the employee is full-time or part-time. California, New York, and Massachusetts also impose income tax withholding obligations on the employer, while Texas and Washington do not (Texas because it has no income tax; Washington because it has no income tax on wages). All five states impose SUI obligations on the employer.

Washington also imposes a separate paid family and medical leave (PFML) premium that is split between employer and employee contributions, currently totaling approximately 0.92 percent of wages with no wage cap for 2025. Massachusetts imposes a similar PFML premium of approximately 1.18 percent of wages, with an employer share of 0.52 percent and an employee share of 0.66 percent, applied to wages up to the Social Security wage base. These state-specific payroll taxes are additional costs beyond the SUI and must be accounted for in the comparison.

Step 3: Determine withholding scenario

The withholding scenario for TechFlow's employees is straightforward resident withholding in each employee's state of residence. There is no reciprocity or convenience-rule complexity at the employee level. The employer withholds California state income tax from the California employees' wages, New York state and New York City income tax from the New York employees' wages, no state income tax from the Texas and Washington employees' wages, and Massachusetts state income tax from the Massachusetts employee's wages. The withholding is computed using each state's withholding tables or percentage-of-wages method, based on the employee's Form W-4 and state withholding allowance certificates.

The withholding configuration is the same whether TechFlow uses direct registration or a PEO. The difference is in who operates the withholding: under direct registration, TechFlow's payroll software computes and remits the withholding under TechFlow's state employer identification numbers; under a PEO, the PEO computes and remits the withholding under the PEO's state employer identification numbers, and the W-2 reports the PEO as the employer. From the employee's perspective, the paycheck and the year-end tax forms look substantially the same, with the principal difference being the employer identification number on the W-2.

Step 4: Calculate federal tax

The federal payroll tax burden is the same under both options. TechFlow pays employer FICA of 7.65 percent on each employee's wages up to the Social Security wage base, totaling approximately $170,940 in employer FICA on $2.4 million of payroll (assuming most employees are below the Social Security wage base; the exact figure varies with wage distribution). Federal unemployment tax (FUTA) is 6.0 percent on the first $7,000 of each employee's wages, less a credit of up to 5.4 percent for state unemployment tax paid, producing an effective FUTA rate of 0.6 percent on $7,000 per employee. For 15 employees, the FUTA liability is approximately 15 × $7,000 × 0.6 percent = $630, before any credit reductions for states with outstanding federal UI loans.

For 2025, no states are subject to FUTA credit reduction, so the full 5.4 percent credit applies and the effective FUTA rate is 0.6 percent. The employer FICA and FUTA are identical under direct registration and under a PEO; they are statutory obligations that follow the wages regardless of who operates the payroll. The federal tax calculation is therefore not a differentiating factor between the two options, but it is part of the total payroll cost stack that the CFO must budget for in either scenario.

Step 5: Calculate each state's tax

The state SUI liability is computed using each state's new-employer rate and wage base. For California, the 2025 new-employer SUI rate is 3.4 percent under California Unemployment Insurance Code §977(a), applied to the first $7,000 of each employee's wages. TechFlow's California SUI liability is 5 employees × $7,000 × 3.4 percent = $1,190. California also imposes an Employment Training Tax of 0.1 percent on the same wage base, adding $35. For New York, the 2025 new-employer SUI rate is 4.1 percent (variable by industry and experience, but 4.1 percent is the standard new-employer rate), applied to the first $12,000 of each employee's wages. TechFlow's New York SUI liability is 4 employees × $12,000 × 4.1 percent = $1,968.

For Texas, the 2025 new-employer SUI rate is 2.7 percent (the standard new-employer rate for positive-rated industries), applied to the first $9,000 of each employee's wages. TechFlow's Texas SUI liability is 3 employees × $9,000 × 2.7 percent = $729. For Washington, the 2025 SUI rate for new employers in the software industry is approximately 2.7 percent (rates vary by industry classification and the new-employer rate is set annually), applied to an unusually high wage base of $68,500 for 2025. TechFlow's Washington SUI liability is 2 employees × $68,500 × 2.7 percent = $3,699, which rounds to approximately $3,716 with the exact 2.71 percent rate. Washington also imposes the PFML premium of approximately 0.92 percent on all wages with no cap, adding 2 employees × average wage × 0.92 percent, which for $200,000 average Washington wages is approximately $3,680.

For Massachusetts, the 2025 new-employer SUI rate is 2.4 percent (the standard new-employer rate under Massachusetts G.L. c. 151A), applied to the first $15,000 of each employee's wages. TechFlow's Massachusetts SUI liability is 1 employee × $15,000 × 2.4 percent = $360. Massachusetts also imposes the PFML premium of approximately 1.18 percent on wages up to the Social Security wage base, with the employer share of 0.52 percent producing an additional cost of approximately $1,040 for a $200,000 employee. The total state SUI liability across all five states is $1,190 + $1,968 + $729 + $3,716 + $360 = $7,963. Adding the state-specific PFML contributions in Washington and Massachusetts adds approximately $4,720, bringing the total state-side payroll tax to approximately $12,683.

Step 6: Calculate credits

The credits analysis in this case is the credit TechFlow receives against federal FUTA for state unemployment tax paid. Under IRC §3302, employers that pay state unemployment tax on time receive a credit of up to 5.4 percent against the 6.0 percent FUTA rate, reducing the effective FUTA rate to 0.6 percent. Because TechFlow pays SUI in all five states, the full FUTA credit is available, and the effective FUTA rate is 0.6 percent. If TechFlow were in a FUTA credit-reduction state, the effective FUTA rate would be higher, but no states are in credit reduction status for 2025.

The PEO model does not change the FUTA credit outcome, because the PEO pays SUI on the same wages and the credit flows through to the PEO as the employer of record. The credit mechanism is therefore not a differentiating factor between the two options. The credit analysis matters primarily to confirm that direct registration does not lose any FUTA credit by virtue of being late or deficient in any state, which would be a real risk if the company self-administered without dedicated payroll staff.

Step 7: Total tax burden

The total payroll tax burden for TechFlow under direct registration is approximately $170,940 (employer FICA) + $630 (FUTA) + $7,963 (state SUI) + $4,720 (Washington and Massachusetts PFML) = $184,253. This figure is the statutory payroll tax cost, which is identical under direct registration and under a PEO. The differentiation between the two options is in the administrative cost layer that sits on top of the statutory payroll tax.

Under direct registration, the administrative cost layer includes the payroll software subscription, the workers compensation insurance premium, the HR administration time, and the cost of registering and maintaining accounts in each state. Under a PEO, the administrative cost layer is the PEO's bundled fee, which typically includes payroll software, workers compensation, HR administration, multi-state registration, benefits administration, and compliance support. The next sections quantify each option's administrative cost layer.

Step 8: Compare to alternative scenarios

Under Option A (direct registration), the administrative cost stack is as follows. State registration fees total approximately $1,200 across the five states, ranging from $0 in some states to $500 in others; this is a one-time cost amortized over the period of registration. The payroll software subscription (using Gusto or Rippling in employer-of-record mode rather than PEO mode) costs approximately $40 to $80 per employee per month, producing an annual cost of $7,200 to $14,400 per year for 15 employees. Workers compensation insurance for a low-risk software classification at approximately 0.20 per $100 of payroll produces an annual premium of approximately $4,800 on $2.4 million of payroll. HR administration time, assuming a fractional HR generalist or outsourced HR consultant at 15 to 25 hours per month at $125 per hour, costs approximately $22,500 to $37,500 per year.

The total Option A administrative cost is approximately $1,200 (registration, one-time) + $10,800 (payroll software, midpoint) + $4,800 (workers comp) + $30,000 (HR, midpoint) = $46,800 in the first year, dropping to approximately $45,600 in subsequent years after the registration is amortized. Adding the statutory payroll tax of $184,253 produces a total cost of approximately $231,053 in the first year under Option A. This is consistent with the typical range of $25,000 to $40,000 in incremental administrative cost beyond the statutory payroll tax, depending on the level of HR support and the payroll software pricing.

Under Option B (PEO), the administrative cost stack is the PEO's bundled fee. PEO pricing for a 15-employee software company typically ranges from $1,500 to $3,000 per employee per year for the administrative fee alone, plus the cost of health insurance and other benefits passed through at the PEO's negotiated rates. The administrative fee is approximately $22,500 to $45,000 per year for 15 employees, which is comparable to or slightly higher than Option A's administrative cost. The full PEO fee including benefits administration, however, ranges from $4,800 to $8,000 per employee per year, producing a total of $72,000 to $120,000 per year on 15 employees, consistent with the 3 to 5 percent of payroll benchmark.

The key comparison is in the benefits layer. Under Option A, TechFlow's small-group health insurance for 15 employees at approximately $9,000 per enrollee per year, with the employer covering 70 percent, costs approximately $94,500 in employer premium contributions. Under Option B, the PEO's master health plan at large-group rates of approximately $7,200 per enrollee, with the same 70 percent employer share, costs approximately $75,600. The PEO saves approximately $18,900 per year in health insurance premiums, which partially offsets the higher administrative fee. The net comparison is therefore approximately $46,800 (Option A admin) + $94,500 (Option A benefits) = $141,300 in total administrative and benefits cost for Option A, versus approximately $72,000 to $120,000 for Option B (which includes both administration and benefits). Option B is cheaper when the company needs competitive health benefits, by approximately $21,000 to $69,000 per year. Option A is cheaper when the company does not need competitive benefits, by approximately $25,000 to $48,000 per year.

Step 9: Strategy recommendations

The break-even analysis points to a clear strategic recommendation. If TechFlow intends to offer competitive health benefits to attract and retain talent in the venture-backed software market, the PEO model is net cheaper by approximately $20,000 to $70,000 per year, depending on the PEO pricing and the small-group market rates in California and New York. The PEO also reduces operational complexity, eliminates multi-state registration maintenance, and provides access to HR expertise that a 15-person company could not afford to hire directly. For a venture-backed startup expecting to scale to 30 or 50 employees within 18 to 24 months, the PEO model is the standard choice for these reasons.

If TechFlow does not intend to offer competitive benefits—because, for example, the founders are bootstrapping or the employees are mostly covered by spouses' plans—direct registration is cheaper by approximately $25,000 to $48,000 per year. The direct-registration model also provides more control over payroll timing, more flexibility in compensation structures (such as equity grants or bonus pools), and a cleaner separation between employment and the PEO's master policies. For a small company with a stable headcount and no near-term hiring plans, direct registration is a reasonable choice.

A hybrid strategy is also available: use a PEO for the first 18 to 24 months while scaling, then transition to direct registration once the headcount exceeds 30 to 50 employees and the company can support its own HR function. The transition costs approximately $15,000 to $25,000 in one-time conversion expenses, including state SUI account transfers, year-to-date wage data migration, and employee re-onboarding. The transition should be planned 60 to 90 days in advance, and the timing should align with the start of a calendar quarter to simplify wage reporting.

A fourth strategy is to use an employer of record (EOR) service for individual remote employees in states where the company does not have a critical mass. An EOR is similar to a PEO but typically operates on a per-employee-per-month fee of $500 to $800 and is used for one or two employees in a state rather than for the entire workforce. For TechFlow, using an EOR for the single Massachusetts employee and direct registration in the other four states may produce a lower total cost than a full PEO, depending on the EOR's pricing and the company's appetite for managing four-state direct registration.

Common mistakes to avoid

The most common mistake is underestimating the cost of multi-state SUI compliance. The Washington SUI wage base of $68,500 is more than nine times the California wage base of $7,000, and a single Washington employee can produce more SUI liability than five California employees. Treating SUI as a uniform percentage of wages across states produces material budget errors. A second mistake is failing to register in a state where a remote employee works, on the assumption that one employee does not trigger registration. Every state with an income tax or SUI program requires employer registration from the first employee in the state, and failure to register exposes the employer to back withholding, interest, and penalties.

A third mistake is selecting a PEO without auditing the bundled services. Some PEOs charge an all-in fee that includes competitive benefits, while others charge a lower administrative fee and pass through benefits at full cost. The comparison should be on an all-in basis including benefits, workers comp, and any ancillary fees. A fourth mistake is failing to plan the PEO-to-direct-registration transition, which can produce W-2 errors, SUI wage-base tracking gaps, and compliance friction at year-end. A fifth mistake is treating the PEO decision as permanent; the optimal model changes as the company grows, and the right answer at 15 employees may be wrong at 50 employees.

What to do next

TechFlow's CFO should solicit detailed pricing from at least three PEOs (such as TriNet, Insperity, and Rippling PEO) and at least two direct-registration payroll providers (such as Gusto and Rippling core payroll), with itemized quotes for administration, benefits, and workers comp. The CFO should run the break-even analysis using the company's actual benefits enrollment assumptions, not the PEO's marketing benchmarks, and should model the cost under three scenarios: 15 employees with benefits, 25 employees with benefits, and 50 employees with benefits. The CFO should also consult an employment law attorney to review the PEO co-employment agreement for indemnification, joint-employer liability, and termination provisions before signing. Finally, the CFO should run our multi-state withholding calculator and SUI reference tool to validate the state-by-state tax assumptions, and should consult a licensed payroll tax professional before executing the chosen arrangement.