There’s a moment almost every founder recognizes, usually somewhere around month six or seven of running an actual business instead of just imagining one. You need help. Real, consistent, specific help — someone to handle customer calls, write code, run the warehouse floor three days a week. You can’t afford a full-time hire with payroll taxes and benefits and all the machinery that comes with it. So you do what everyone around you seems to be doing: you call the person a contractor, send them a 1099 at the end of the year, and tell yourself you’ve handled it.
I’ve watched this play out dozens of times, and I’ve watched it go wrong in ways that make the original payroll savings look laughably small. A design agency in Austin brought on a “freelance” project manager who worked forty hours a week, used a company email address, attended every internal meeting, and was told explicitly which tools she had to use and how to structure her day. The founder genuinely believed the 1099 classification was correct because there was no benefits package and because she’d signed an independent contractor agreement. When a state labor audit arrived two years later, none of that mattered. The back taxes, penalties, and interest came to just over $34,000. The project manager hadn’t even complained — the state found the arrangement through a routine audit of the company’s filings.
That story isn’t unusual. What’s unusual is founders hearing it before they make the same call themselves.
The Test Isn’t What You Call the Relationship — It’s What the Relationship Actually Is
The core confusion around worker classification is that founders treat it as a paperwork decision. They believe that if both parties sign a contract calling the arrangement independent contracting, and if the worker invoices instead of receiving a paycheck, then the classification is settled. It isn’t. The IRS, the Department of Labor, and every state agency with jurisdiction over employment taxes look past the label and examine the substance of the working relationship. The contract is relevant but it is not determinative.
The IRS uses a framework built around three broad categories: behavioral control, financial control, and the type of relationship. Behavioral control asks whether the company controls how the work is done, not just what the final output looks like. If you’re telling someone when to show up, which software to use, and how to structure their workflow, you are exercising behavioral control consistent with an employment relationship. Financial control examines whether the worker has a real opportunity for profit or loss independent of your business — a true independent contractor typically has multiple clients, sets their own rates, and bears their own business expenses. The type of relationship category looks at things like written contracts, benefits, permanency, and whether the work is integral to the company’s core business. You can read the full IRS guidance on this at irs.gov, and it’s worth doing so before you make your next hiring decision.
California adds an additional layer that has caught many out-of-state companies off guard. Under AB5, which codified the ABC test into law, a worker is presumed to be an employee unless the hiring entity can demonstrate all three of the following: the worker is free from the company’s control, the worker performs work outside the usual course of the company’s business, and the worker is customarily engaged in an independently established trade or occupation. That third prong — the independently established trade — is where a lot of arrangements collapse. If your “contractor” doesn’t have other clients, doesn’t have a business entity of their own, and has never operated independently in this field before working with you, California will almost certainly call them an employee regardless of what your contract says.
The 1099 vs W-2 distinction matters enormously in dollar terms. As an employer, when you hire a W-2 employee you pay the employer’s share of Social Security and Medicare taxes — 7.65 percent of wages up to the applicable ceilings — along with federal and state unemployment taxes, and you handle withholding. When you hire a genuine independent contractor, none of that applies. The contractor handles their own self-employment taxes, and your administrative burden is minimal. The savings are real. But so is the liability when the classification is wrong: you can owe the employee’s share of taxes that were never withheld, the employer’s share, penalties, and in some states, civil damages if the worker files a complaint.
What I find most striking, having watched this from the outside and occasionally from uncomfortably close up, is how rarely founders apply any structured analysis before making the call. They look at the situation and use a shorthand: “She’s only here part-time” or “He has another client” or “We agreed on a project basis.” None of those facts, individually, is conclusive. A part-time worker can absolutely be an employee. Having one other client doesn’t establish genuine independence. Project-based work is done by both employees and contractors. The question is always the totality of the relationship, and the honest answer is that many arrangements founders label as contractor relationships would not survive serious scrutiny.
Practical Steps Before You Classify Anyone
The most useful thing I can offer here is a set of concrete questions to ask before you issue that first 1099. Not a checklist in the bureaucratic sense, but a genuine interrogation of what the relationship actually looks like on the ground.
First: does this person work exclusively or near-exclusively for you? If someone is devoting forty or more hours a week to your business and has no other meaningful clients, the economic reality of that relationship looks like employment regardless of the paperwork. Second: do you control the method, not just the result? There’s an important distinction between saying “I need this feature built by Friday” and saying “I need you to build this feature in Python, using this framework, following our internal coding standards, during these hours.” The former is directing output. The latter is directing work, which is the hallmark of an employment relationship. Third: is the work integral to what your company actually does? A software company that hires someone to clean the office twice a week has a genuinely different arrangement than one that hires a software developer to build its core product. The developer is doing the thing the company exists to do. Courts and agencies notice that.
Fourth — and this one founders consistently underestimate — how permanent does the arrangement feel in practice? If you’ve had the same “contractor” for two years with no defined end date and no genuine project scope, what you have is an ongoing employment relationship with unusual tax treatment. The IRS looks at permanency as a significant indicator. The Department of Labor’s economic reality test, used in federal wage and hour cases, places enormous weight on whether the worker is economically dependent on a single company.
If you go through those questions honestly and find yourself in gray territory — which is genuinely where many arrangements live — there are legitimate tools for getting a formal answer. You can file an IRS Form SS-8, which asks the agency to determine the status of a worker for federal employment tax purposes. This is not a fast process and it does put the relationship under official scrutiny, but it provides a defensible answer. You can also consult a labor attorney in your state before the relationship begins rather than after a dispute arises. An hour of legal fees upfront is almost always cheaper than the alternative.
The Department of Labor publishes its own guidance on worker misclassification and the economic reality test, and it’s genuinely readable — not the impenetrable bureaucratic prose you might expect. If you’re classifying workers right now, it’s worth an afternoon to understand how the agency that can fine you is actually thinking about the question.
One thing I want to push back on gently is the idea that this is primarily a risk management issue — something you think about because of audits and penalties. It is that, but it’s also a business clarity issue. When you’re vague about whether someone is a contractor or an employee, you’re usually also vague about what you actually need from them, how long you need it, and what success looks like. The misclassification is often a symptom of a deeper fuzziness about the role itself. Getting the classification right forces you to think clearly about the work, the relationship, and the commitment you’re actually making — and that clarity tends to produce better outcomes for everyone involved, including the worker who deserves to know where they stand.
The founder in Austin eventually rebuilt her team with proper employment classifications, a cleaner understanding of what each role actually required, and payroll software that made the administrative side manageable. She told me the $34,000 penalty was the most expensive lesson she’d paid for, but also, in a strange way, one of the more clarifying ones. She stopped thinking of worker classification as an accounting choice and started thinking of it as a reflection of what kind of company she was actually building. That reframe, she said, changed how she hired for everything that came after.
