The moment it breaks is when an HR coordinator onboards a new hire in a state where the company has never had an employee before, opens their payroll system, and has no idea what local jurisdictions to withhold for, what forms the employee needs to complete, or whether the company is now required to register in that state. Users said 'tax solutions for remote employees is not intuitive' and 'the process to update, change, terminate or create new local tax withholdings is difficult to understand, leading to potential errors.'

The reason this gap persists is structural: payroll software vendors cover the calculation engine but have no incentive to build out detailed, state-by-state onboarding guidance — that would mean maintaining a live database of local tax rules that changes constantly and supporting it when it's wrong. It's expensive to maintain and creates liability. So they leave it to the employer to figure out, or to a support team that is notoriously slow.

What HR teams actually need when onboarding a remote hire isn't just a withholding field — it's a checklist: which jurisdictions apply based on the employee's home address, what registration the company needs to complete before the first paycheck, what employee-facing forms need to be signed, and what the common mistakes are for that specific state. Nobody surfaces this at the point of hire.

This is a recurring business problem because companies hire remote employees continuously, and every new state is a new unknown. A missed local registration generates a penalty; a wrong withholding generates an amended W-2 and an angry employee. The need doesn't go away — it compounds as remote workforces grow.

What to build

Build a lookup tool where an HR coordinator enters a new hire's home address and the company's existing registered states, and gets back a step-by-step checklist: which tax jurisdictions apply, what employer registrations are required before payroll runs, what employee forms need to be completed, and what the common filing errors are for that locality.

Where to start

Launch with coverage for the 15 states that generate the most remote-worker tax complexity (California, New York, Ohio, Pennsylvania, New Jersey, Illinois, Texas, and others with active local tax regimes) and charge only for those — don't try to cover all 50 states before you have paying customers.

The hard part

Keeping the underlying jurisdiction and registration requirement data accurate across all 50 states and thousands of local taxing authorities — stale data means bad advice, which is worse than no advice, so the data maintenance cost is high from day one.

How it makes money

Per-lookup pricing for small teams (e.g., $15 per new hire tax profile generated) with a flat monthly subscription for teams hiring more than 10 remote employees per month.

See the evidence. The complaints behind this idea, the products they came from, and similar ideas in Core HR.

More ideas in Core HR