operations

The Misclassification Trap: When Your "Contractors" Are Actually Employees

A friend of mine runs a 15-person startup in Austin. Last year he got a letter from the Texas Workforce Commission.

James Heaney
James Heaney
CTO & Co-founder
|
January 30, 2026·7 min read
The Misclassification Trap: When Your "Contractors" Are Actually Employees

A friend of mine runs a 15-person startup in Austin. Last year he got a letter from the Texas Workforce Commission. Turns out three of his "contractors" — people who'd been working with him for over a year, on his schedule, using his tools — were reclassified as employees. He owed $47,000 in back payroll taxes, unemployment insurance, and penalties.

He's not dumb. He just didn't know the rules.

Most founders don't. You find someone good, you call them a contractor because it's easier, and you move on. No benefits to manage, no payroll tax to withhold, no workers' comp. Until someone files for unemployment, or the IRS decides to take a closer look.

What misclassification actually means

Worker misclassification is when you treat someone as an independent contractor but the actual working relationship looks like employment. It doesn't matter what your contract says. It doesn't matter if both parties agreed to the arrangement. The IRS and the Department of Labor look at the reality of how the work gets done.

If you control when they work, how they work, and provide the tools they work with — that person is probably an employee in the eyes of the law, regardless of what you put on paper.

The IRS test (it's not as complicated as you think)

The IRS uses a three-category test to determine worker classification:

Behavioral control. Do you dictate how the work gets done? If you set specific hours, require them to follow your processes, or supervise their day-to-day tasks, that points to employment. A true contractor decides their own methods and schedule.

Financial control. Do you control the business side of the relationship? Contractors typically invest in their own equipment, can work for multiple clients, and have the opportunity for profit or loss. If someone works exclusively for you and you provide everything they need, that looks like employment.

Relationship type. Is there a written contract? Are there benefits? Is the work a core part of your business? A contractor you hired to redesign your website is clearly doing project-based work. A "contractor" who's been writing your core product code for 18 months is harder to defend.

No single factor decides it. The IRS looks at the whole picture.

The ABC test (some states use this instead)

About 30 states use a stricter standard called the ABC test. Under this test, a worker is presumed to be an employee unless the hiring entity proves all three conditions:

A — Absence of control. The worker is free from the company's control and direction in performing the work.

B — Business difference. The work is outside the usual course of the company's business.

C — Custom of trade. The worker has an independently established trade, occupation, or business.

That middle one trips people up. If you run a software company and you hire a "contractor" to write software, condition B is hard to meet. The work is your core business.

California, New Jersey, Massachusetts, and Illinois all use versions of the ABC test. If your contractors are in those states, you should know this.

Why startups get this wrong

Three common patterns I see:

The "we call everyone a contractor" approach. Some companies classify everyone as a contractor by default because it's cheaper and simpler. No payroll taxes, no benefits, no employment paperwork. This works until it doesn't.

The long-term contractor who's really an employee. Someone starts as a contractor for a 3-month project. The project extends. Then extends again. A year later, they're working 40 hours a week on your core product, attending your standups, and using your Slack. They're an employee in everything but name.

The "they said they wanted to be a contractor" defense. The worker's preference doesn't matter. If the working relationship looks like employment, it's employment. Both parties agreeing to contractor status doesn't change the legal analysis.

What happens when you get caught

The consequences are real:

Back taxes and penalties. You'll owe the employer's share of FICA taxes (7.65%) for every misclassified worker, going back up to three years. The IRS can add penalties of 1.5% of wages for income tax failures plus 20% of the employee FICA share you should have withheld. Those numbers add up fast with even a handful of workers.

State penalties. States often pursue misclassification independently. California's EDD, for example, can assess penalties up to $25,000 per violation plus back unemployment insurance premiums.

Worker lawsuits. Misclassified workers can sue for unpaid overtime, benefits, and expense reimbursement. Class action lawsuits from groups of misclassified workers have cost companies millions. Uber, Lyft, and FedEx all faced these.

Audit triggers. One misclassification finding often leads to audits across your entire workforce. If you misclassified one person, they'll check everyone.

How to stay on the right side

Here's what actually works:

Start with the work, not the label. Before you hire someone, think about what the relationship will actually look like. Will they set their own hours? Work for other clients? Use their own tools? If yes, contractor status is defensible. If no, hire them as an employee or restructure the engagement.

Keep engagements project-based. Contractors should work on defined projects with clear deliverables and end dates. "Build this feature by March" is a contractor engagement. "Maintain our product indefinitely" starts to look like employment.

Don't control the how. Give contractors the outcome you want, not step-by-step instructions. They should choose their own tools, methods, and schedule. The moment you start requiring 9-to-5 hours and attendance at daily standups, you're creating an employment relationship.

Document everything. Have a written contractor agreement that reflects the actual relationship. Include the scope of work, payment terms, and a clear statement that the contractor controls the manner and means of performing the work. But remember: the document has to match reality.

Pay them like contractors. Contractors should invoice you. They should be paid for completed work, not on a salary schedule. Using a payment system built for contractors (not payroll software) helps maintain the distinction.

This is partly why we built Grade. When you pay contractors through Grade, the workflow reinforces the correct relationship. Contractors set up their own payment method. They get paid for delivered work, not on a payroll cycle. There's a clear paper trail showing a contractor-style engagement. It's not a silver bullet — you still need the underlying relationship to be legitimate — but the payment infrastructure matters.

Review your contractors annually. At least once a year, look at every contractor relationship and ask: does this still look like contracting? If someone has been working full-time on your core product for a year, it might be time to convert them to employment or restructure the engagement.

The conversion conversation

Sometimes the right answer is to make someone an employee. That's not a failure. If the relationship has evolved into employment, formalizing it protects both of you.

The conversation doesn't have to be awkward. Most contractors in this situation already know they're functioning as employees. Many would welcome the stability of employment — benefits, paid time off, unemployment insurance protections.

The cost of employment (benefits, payroll taxes, workers' comp) is real but predictable. The cost of misclassification is unpredictable and usually worse.

What actually matters

Contractor misclassification isn't some obscure compliance issue. The DOL recovered over $274 million in back wages in fiscal year 2024, and misclassification was one of the top enforcement priorities. State agencies are getting more aggressive too.

If you're a startup with 5+ contractors, spend an hour reviewing your classifications. Look at each relationship honestly. Are they really contractors, or are they employees you're calling contractors because it's convenient?

The IRS doesn't care about your intentions. They care about the reality.

Get the classification right from the start, pay your contractors like contractors, and you'll never have to open a letter from the IRS and wonder how much it's going to cost you.

#contractors#taxes#compliance#hiring#startups
James Heaney
James Heaney
CTO & Co-founder

Building Grade to make paying contractors effortless.

LinkedIn

Ready to scale your contractor payouts?

With just their email, you can track results, send payouts, and automate tax forms.

Try Grade Free →