Your first hire: contractor or employee?

The moment your business has more work than you can do alone, you face the first-hire question — and most small owners frame it wrong. 'Contractor or employee' isn't a preference you pick to save money; it's a legal classification determined by how the working relationship actually operates. Get it right and hiring is straightforward. Get it wrong and you've built a payroll tax time bomb with your name on it.

The test: control, not labels

The IRS looks at three clusters of facts. Behavioral control: do you direct how, when, and where the work is done, or just the result? Financial control: does the worker have their own tools, expenses, other clients, and the ability to profit or lose? Relationship: is this open-ended and core to your business, or a defined project? A designer with five clients, her own software, and a project contract is a contractor. That same designer working 9-to-5 in your workflow, on your tools, for you alone, indefinitely — that's an employee, no matter what the contract calls her. States can be stricter still: California's ABC test and similar laws presume employee status unless the work is outside your usual course of business.

What each one actually costs

A contractor's rate is the whole cost — no payroll taxes, no benefits, no equipment (which is why contractor hourly rates are legitimately higher; they're covering their own taxes and overhead). An employee costs their wage plus roughly 10–15% before benefits: employer FICA (7.65%), federal and state unemployment insurance, workers' comp, plus payroll software ($40–60/month), and whatever benefits you offer.

When each genuinely fits

• Contractor: defined projects with clear deliverables, specialized skills you need occasionally (a bookkeeper, a web developer), fluctuating volume, or a trial collaboration before committing.
• Employee: ongoing work central to your business, work you need to direct and schedule, client-facing roles you must control the quality of, or anyone effectively working for you full-time.
• The honest middle path: many great first hires start as a contractor on a real project basis and convert to employee when the hours become steady and the direction becomes daily. That's legal — as long as each phase matches the actual working reality.
• Never the answer: hiring someone as a 'contractor' to do exactly what an employee would do, purely to skip payroll taxes.

The paperwork for each path

1. Contractor: collect a completed W-9 before the first payment, sign a simple independent contractor agreement (scope, rate, deliverables, IP ownership), pay by invoice, and file Form 1099-NEC by January 31 for anyone paid $600+ in the year.
2. Employee: get an EIN and register with your state's employment agencies, collect a W-4 and I-9, set up workers' comp insurance, run payroll through a service (Gusto, OnPay, ADP — they handle withholding, filings, and W-2s), and check state rules on pay frequency, sick leave, and required postings.
3. Either way: put the relationship in writing before work starts, and keep the file (W-9s, contracts, invoices, timesheets) — classification disputes are won and lost on documentation.

The bottom line

Let the actual relationship pick the classification: control and permanence mean employee, independence and projects mean contractor — the IRS and your state will see it that way regardless of the label. Then let utilization pick the economics: steady hours favor the employee's lower rate; lumpy needs favor the contractor's flexibility. The only unambiguously wrong answer is calling an employee a contractor to save 12% — that discount comes with interest.

The cost comparison at a glance

Read the last two rows together and the decision framework falls out: the employee is roughly $12,000 cheaper if the hours are genuinely steady, and roughly infinitely more expensive if the work evaporates for a quarter and you are still running payroll. Price your actual demand curve, not your hopeful one — then let the classification rules, not the cost math, make the final call.

Whichever path you choose, revisit the classification annually. Relationships drift: the project contractor who now works core hours in your workflow every week has quietly become an employee in the eyes of your state, and the audit exposure grows with every quarter the paperwork lags the reality. A ten-minute annual review against the control-and-permanence test is cheap; retroactive payroll taxes are not.