Payroll for Startups: What to Set Up Before Your First Hire
Most founders don’t think about payroll until they’ve already made an offer. That’s normal — hiring is exciting, and taxes are not. But the gap between “we hired someone” and “we can legally pay them” is smaller than it feels, and skipping a step in that gap is what turns into a letter from a state agency six months later.
The four things that have to exist before you run payroll
None of these are optional, and none of them are things payroll software can invent for you — they have to be set up once, in this rough order:
1. An EIN (Employer Identification Number)
This is the federal tax ID for your business. If you’ve already incorporated, you likely have one. If not, it’s a same-day application on the IRS website — but it has to exist before anything else on this list.
2. A state unemployment insurance (SUTA) account
Every state runs its own unemployment insurance program, and every employer has to register — usually within 20-30 days of the first hire. Your SUTA rate is state-specific and often starts at a new-employer default rate until you build a claims history.
3. A decided pay schedule
Weekly, biweekly, semi-monthly, or monthly — some states set minimums on how often you’re allowed to pay. Decide this before the offer letter goes out, not after, because it affects the number your new hire sees in it.
4. A completed W-4 and I-9 for the new hire
The W-4 tells you how much federal income tax to withhold. The I-9 confirms your new hire is authorized to work in the U.S. Both should be completed before day one, not during the first pay cycle.
Why “I’ll just figure out taxes later” doesn’t work here
Payroll tax isn’t one thing — it’s several separate obligations that layer on top of each other every time you run payroll: federal income tax withholding, Social Security and Medicare (FICA), federal unemployment (FUTA), and state-level taxes that vary by where your employee lives and works. Calculating this by hand for one employee is manageable. Getting it wrong on the first run, and having to correct it retroactively, is not.
| Task | Handled by payroll software |
|---|---|
| Calculating federal/state/local tax on each run | Yes |
| Withholding the correct amount from each paycheck | Yes |
| Depositing what’s withheld with the IRS/state on time | Yes, with GOAT |
| Filing your quarterly and year-end tax returns (941s, W-2s) | Stays with your accountant — GOAT hands them the data |
That last row matters more than it sounds. A lot of first-time employers assume “payroll software” means every tax obligation disappears into a black box. In practice, the software handles the calculation, withholding, and on-time deposits — the part that happens every single pay period — while your accountant still handles the periodic returns, using the data the software hands them. You’re not choosing between software and an accountant. You’re using both for what each is actually good at.
Setting the pay rate — and what happens when it’s not one flat number
Startups rarely pay everyone the same way. A technical co-founder might be salaried, an early contractor might be hourly, and a part-time advisor might be paid a flat stipend. Good payroll software should let you run all three in the same pay cycle without exporting anyone to a separate spreadsheet.
What this looks like in practice
Once the four setup items above are in place, running payroll itself takes a few minutes per cycle — not because the underlying tax math got simpler, but because it’s been done once, correctly, and now just repeats. That’s the actual difference between “payroll is scary” and “payroll is a Tuesday task.”
What to do if you’re hiring across state lines from day one
A lot of early-stage teams hire remotely without thinking of it as a multi-state payroll decision — but that’s exactly what it is. If your first hire lives in a different state than where your business is registered, you need a state unemployment (SUTA) registration and, in most cases, a withholding setup in their state, not yours. This is easy to miss because nothing about the hiring process flags it as a payroll issue — it just looks like hiring the best candidate, wherever they happen to live. The fix is simple once you know to look for it: confirm the employee’s actual work state before the first payroll run, not after.
A note on timing your first payroll around cash flow
Startups tend to be careful about cash flow everywhere except payroll, where the date often gets set by convenience rather than by when money will actually be in the account. Since taxes are withheld and deposited on every run regardless of your own cash position, it’s worth choosing a pay schedule that lines up with when revenue or funding actually lands — not just what feels administratively simple. This is a decision worth making once, deliberately, rather than defaulting to whatever the first payroll tool suggests.
Frequently asked questions
Do I need an accountant to run payroll for my first hire?
You don’t need one to run the payroll itself — the software calculates, withholds, and deposits taxes for you. Most founders still keep an accountant for the periodic tax filings (quarterly and year-end returns), since that’s a separate obligation from running the actual pay cycle.
How soon after hiring do I need a state unemployment account?
Most states require registration within 20-30 days of your first hire’s start date, though the exact window varies. Registering before you run your first payroll avoids having to backfill it under a deadline.
Can I run payroll for one employee and add more later without switching systems?
Yes — the setup steps above (EIN, SUTA account, pay schedule) apply the same way whether you have one employee or ten. Adding a second hire later doesn’t require redoing any of it.
