How Remote-First SaaS Companies Should Manage Benefits for Employees in Multiple States
Hiring one employee in a new state is a compliance event. Most remote-first SaaS founders learn this after it's already happened — when payroll flags a missing state tax registration or a new hire discovers their health plan has no in-network doctors near them. This post maps what actually happens operationally when you have employees in multiple states, and what to do about it.
Before You Start — What You Need in Place
Two prerequisites before adding any new state:
- A payroll platform with multi-state support. Gusto, Rippling, and Justworks all handle multi-state payroll registration. What varies is how much of the compliance work they do for you versus flag to you. Rippling handles state tax registration automatically in most states. Gusto requires you to initiate registrations yourself. Justworks (PEO model) covers compliance under their EIN.
- A clear map of where your employees actually work. Not where they're from — where they work. A hire who moves from Denver to Dallas mid-year is a Colorado-to-Texas compliance handoff. Your HRIS needs to reflect current work location, not original hire location.
Step 1: Register for Payroll Taxes in Each New State
Every state with an employee requires an employer to register for state income tax withholding and unemployment insurance (SUTA). Some states also require separate local tax registrations (Ohio and Pennsylvania are the most common examples).
What this involves:
- Apply for a state employer identification number with the state's department of revenue
- Register for state unemployment insurance with the state's labor department
- Register for any local taxes if the employee's city requires them
Timeline: most state registrations take 2–4 weeks. Some states (California, New York) have online registration that resolves faster. Do this before the employee's first paycheck — state withholding errors require amended payroll filings to fix.
The tool that automates this: Middesk or AbstractOps for direct companies; PEOs handle it under their own EIN. Expect $200–500/month for compliance tooling if you're going direct and have employees in 8+ states.
Step 2: Set Up Workers' Compensation in Each New State
Workers' compensation is state-regulated. Each state requires either a workers' comp policy from a state-approved carrier or registration with the state's workers' comp fund (some states have monopolistic funds — Ohio, Washington, Wyoming, and North Dakota don't allow private carriers).
For remote employees, the workers' comp policy must cover the employee's home state, not your company's home state. A California workers' comp policy does not cover a Texas employee.
If you're on a PEO, workers' comp is bundled into their model — this is one of the genuine administrative advantages of a PEO at the 25–75 employee stage. Going direct means maintaining separate workers' comp coverage or policy endorsements for each state.
Step 3: Understand State-Specific Benefit Mandates
This is where founders who assume benefits are federal get surprised.
Several states layer requirements on top of federal law:
California requires employers to maintain any benefit plan they offer in California in compliance with state-specific rules, including California's own disability insurance (SDI) and paid family leave (PFL) withholding. Expense reimbursement is also legally mandated under California Labor Code §2802 — which means your $50/month internet reimbursement isn't a perk in California; it's a legal obligation.
New York has its own short-term disability and paid family leave program with mandatory employer participation. New York City adds additional paid sick leave requirements.
New Jersey has mandatory state-run temporary disability insurance (TDI) and family leave insurance (FLI) programs.
Washington has a mandatory paid family and medical leave (PFML) program with state-run premiums.
Massachusetts has its own paid family and medical leave program (PFML) with employer contribution requirements above a certain size.
None of these are optional and none are handled by federal group benefit plans. Your broker or PEO should flag these as you add employees in each state — but verify it, because state-specific mandates are where benefits administration falls apart for founders who assume their platform handles everything.
Step 4: Fix Your Health Plan for Multi-State Coverage
This is the most common operational failure for distributed teams: the group health plan doesn't cover employees outside the carrier's primary market.
Why it happens: Group health carriers build networks state by state. A California-based HMO (Kaiser, for example) is explicitly in-network-only and covers nothing outside Kaiser's California service area. Even national PPO carriers (Anthem, United) have materially thinner networks in states where they don't have large market share.
What it looks like in practice: You sign a group PPO with Blue Shield of California. Your Austin, Texas engineer searches for an in-network primary care doctor and finds three options in their zip code, none accepting new patients.
The plan-type implications:
| Plan type | Multi-state suitability |
|---|---|
| HMO (including Kaiser) | Worst — in-network-only, state-specific networks |
| PPO (regional carrier) | Problematic — thin networks outside carrier's home state |
| PPO (national carrier: Anthem, United) | Better — but still varies by state market share |
| HDHP + HSA (national carrier) | Same as PPO — carrier network determines quality |
| ICHRA | Best — each employee buys in their own state's market |
The ICHRA solution: With an Individual Coverage HRA, you set a monthly allowance by geography class, and employees buy ACA marketplace plans in their own state. There is no carrier network gap because each employee's plan is issued by a carrier active in their state. A New York employee buys a New York plan. A Texas employee buys a Texas plan.
You set allowances by geography to account for cost-of-living differences. High-cost states (California, New York, Massachusetts) get higher monthly allowances. Lower-cost states get lower allowances. This is legal under IRS ICHRA class rules and prevents your coastal employees from being systematically under-covered.
ICHRA also satisfies the ACA employer mandate if you're over 50 FTEs — the allowance just needs to meet the affordability threshold (employee share of the lowest-cost silver plan cannot exceed 9.02% of household income in 2025). For a deeper look at how companies at this stage are structuring coverage, the Sequoia 2026 Benefits Benchmark has useful context on ICHRA adoption trends.
Step 5: Track the 50-FTE Threshold Across All States
The ACA employer mandate — which requires offering minimum-value, affordable health coverage to at least 95% of full-time employees or paying penalties — is calculated on total company headcount, not per-state headcount.
Your FTE count includes:
- Every full-time employee (30+ hours/week) in every state
- Part-time hours aggregated monthly (total part-time hours ÷ 120 = FTE equivalent)
- Seasonal workers, depending on duration
The penalty for non-compliance once you cross 50 FTEs: approximately $2,900/year per full-time employee (minus the first 30) if you don't offer coverage and an employee gets a marketplace subsidy.
For remote-first companies that hire continuously in multiple states, this threshold can arrive faster than the finance calendar anticipates. Start counting FTEs quarterly twelve months before you expect to cross 50.
Common Mistakes Founders Make
Assuming the PEO handles state compliance automatically. PEOs handle compliance under their EIN, which is a real advantage — but "handles" doesn't mean "tells you when something new is required." As you add states, verify that your PEO has registered in that state and that workers' comp is in place before the employee's first day.
Using one group health plan for a team in 8 states. The network gap problem is predictable and well-documented. A 2024 operator survey of 143 SaaS founders found that companies with distributed teams consistently regretted starting with a group PPO over an ICHRA. Nava Benefits has a useful primer on how to evaluate plan types for multi-state teams.
Leaving a PEO mid-year when you're in multiple states. PEO exit in the middle of a year causes Social Security and state tax withholding to restart as if employees changed employers. In multiple states simultaneously, this creates a payroll cleanup problem that takes six weeks to resolve. Always exit a PEO at January 1.
Not modeling state compliance costs before hiring in a new state. The cost of adding a state isn't just the employee's salary. Payroll registration ($200–500 one-time per state), workers' comp policy amendment, potential benefit mandate contributions (New York PFL, Washington PFML, California SDI), and platform compliance tooling all add up. For a single hire in a new state, the first-year administrative overhead often runs $2,000–4,000.
Multi-State Benefits Is a Finance Problem, Not Just an HR Problem
The operational complexity of a distributed team — state registrations, workers' comp policies, mandate compliance, ICHRA class design, ACA FTE tracking — lands on whoever is running finance and ops at your company. Most founders don't have the bandwidth to track all of it, and most HR platforms don't flag what they're missing.
This is exactly the kind of work Bridges handles for vertical SaaS companies as a fractional finance team. We map your state footprint, identify compliance gaps, model the cost of getting compliant, and help you choose the right benefits structure for where your team actually is — not where it was when you last thought about this. Talk to us before you add your next state.
