How to Decide: Hire or Contract?

Hire or contract is one of the decisions where "the math" gives the wrong answer on its own. The legal classification is the first gate — if a role doesn't pass it, the loaded-cost comparison is moot. This guide walks the three gates in order.

1. Classification: the IRS 20-factor test

Federal classification tests look at substance over form. Calling someone a contractor doesn't make them one. The IRS uses a common-law 20-factor test^[1], which the 2024 DOL final rule refined for FLSA purposes into a six-factor economic-reality test^[2].

Core factors that weigh toward employee classification:

• Control over work details. You dictate when, where, how, and with what tools the work is done.
• Economic dependence. The worker relies on you for a majority of their income over time.
• Integration into your operations. They sit on your team Slack, attend your meetings, use your project management tools, report to your managers.
• Duration. Ongoing, indefinite relationship rather than a defined project with an end.
• Provision of tools/equipment. You provide the laptop, software licences, and working environment.
• No profit/loss risk. Worker earns a steady rate regardless of project outcomes.

Factors that weigh toward contractor classification:

• Worker has other clients (not economically dependent).
• Worker sets their own hours and methods.
• Defined-scope engagements with clear start and end.
• Worker provides their own tools and equipment.
• Worker bears profit/loss risk — fixed-fee projects, their own overhead, opportunity to earn more through efficiency or less through delays.

If a role is mostly in column A, classifying the worker as a contractor is misclassification. Uncertain cases: file IRS Form SS-8 for a determination^[4], or err toward employee status to avoid back-tax liability.

2. The loaded-cost comparison

For roles that legitimately qualify for either classification, compare loaded costs:

• Employee: Base salary × 1.25–1.40 (loaded cost multiplier including payroll taxes, benefits, PTO)^[3]. For a $100k base: ~$130k annual loaded cost, delivering roughly 1,700 productive hours = $76/hour effective rate.
• Contractor: Hourly rate × actual hours. For $100/hour × 1,900 productive hours in equivalent full-time engagement = $190k annual.

At face value, the employee looks cheaper per hour. Three adjustments usually matter:

• Utilisation. Employees are paid whether they are fully utilised or not. If the actual need is 20 hours per week of specialized work, the full-time employee is over-provisioned. A contractor billing only 20 hours at $100 = $104k annual — below the employee loaded cost.
• Ramp time. Employees take 3–6 months to reach full productivity. Contractors with relevant experience are typically productive within 1–2 weeks. For short engagements, ramp time dominates the cost difference.
• Cessation cost. Contractor engagements end cleanly. Employees don't — severance, unemployment insurance experience rating, and the morale cost of involuntary exits all have financial implications.

3. Scope stability is the hidden deciding factor

Employees are efficient per-hour-of-work when the workload is steady. Contractors are efficient when the workload is spiky or uncertain.

The workload question:

• Will this role have enough work for 35–40 hours per week, every week, for the next 12+ months?
• Is the work steady enough that ramp-up time amortises over a long productive period?
• Is the skill set specialised enough that off-hours productivity can't be absorbed by training into adjacent work?

If yes to all three: employee is usually correct. If the work is uncertain, project-based, or the skill set is narrow enough that full-time work would not fill the role productively, contractor is usually correct.

Example. A company needs design work. They could hire a $95k designer full-time or contract a senior designer at $90/hour. If the work is steady at 35 hours/week: employee is ~$124k loaded for 1,700 hours = $73/hour; contractor is $90/hour × 1,820 hours = $164k. Employee wins by ~$40k/year. If the work averages 15 hours/week of specialist output with occasional spikes: contractor is $90/hour × 780 hours = $70k; the employee is still $124k but delivering only modest incremental value in the slack periods. Contractor wins by ~$54k.

4. A decision framework that works

Three questions, in order:

1. Does the role legitimately qualify for contractor classification? If no, the decision is made — it must be an employee or it must be restructured.
2. Is the workload steady at 35+ hours per week for 12+ months? If yes, default to employee. If no, default to contractor.
3. Is there a meaningful strategic reason to deviate? (Specialist scarcity, short runway, building a competitive capability that must be internalized, etc.)

Most roles should land clearly in one category. The ambiguous middle — part-time specialist work, trial periods before full-time conversion — is where most misclassification happens.

5. Common mistakes and misclassification risk

Misclassification is expensive when caught. The DOL and IRS can both assess back taxes, penalties, and interest; state-level enforcement adds another layer. A well-documented case can result in 50–150% of the total compensation paid over the engagement period in back-tax liability alone^[2].

Common mistakes that create exposure:

• Converting a laid-off employee immediately into a contractor doing the same work. High-risk pattern — IRS audits routinely catch this.
• Treating contractors like employees — requiring them at daily standups, assigning them to your internal tools, managing their hours. This erodes their legitimate contractor status.
• "1099 employees." There is no such category. A person is either a W-2 employee or a 1099 independent contractor; the term "1099 employee" has no legal meaning and usually means the classification is wrong.
• State-level variation. California, New York, Massachusetts, and others have ABC tests that are stricter than the federal tests. A contractor classification valid federally may fail state law^[5].

In the typical case, the defensible choice is the one that matches the substance of the relationship. If the decision feels like it's bending the rules for cost reasons, it probably is — and the back-tax exposure is rarely worth the cashflow savings.

6. Contractor-to-employee transitions

A common pattern: hire as a contractor initially to assess fit, transition to employee after 3–6 months. Done well, this works. Done poorly, it creates classification risk.

To do it well:

• Set a defined trial period upfront. Written agreement stating the arrangement is project-based with a specific deliverable, not ongoing work.
• Preserve contractor-substance behaviours during the trial. Let them set their hours, use their own equipment, work outside your daily management cadence.
• Pay project fees or defined deliverables, not hourly. Reduces the weight of "economic dependence" and "hourly management" factors in classification tests.
• Convert cleanly at offer time. W-2 onboarding, full benefits, revised compensation that reflects the different loaded-cost economics.

Common mistake: "contract-to-hire" as a euphemism for "employee with delayed benefits." If the person is working 40 hours/week at your office using your tools and reporting to your manager, they are an employee — regardless of what the contract says.

7. International hiring considerations

For remote-first companies, the hire-vs-contract question gets more complex internationally. Key decisions:

• Local entity. If you plan to hire 5+ employees in a country, establishing a local entity is usually the lowest long-term cost. Setup: $5–25k and 2–6 months. Ongoing compliance costs $10–40k/year.
• Employer of Record (EOR). For 1–5 employees in a country, using an EOR (Deel, Remote, Oyster, similar) avoids the entity setup cost. EOR fees typically add 10–15% to loaded cost. Fast to set up — usually 1–2 weeks.
• International contractors. Paying international contractors is simpler administratively but carries classification risk in countries with strict labour laws (UK, Germany, France have particularly aggressive enforcement). Some jurisdictions won't recognise a contractor arrangement that looks like employment regardless of what the contract says.

Before hiring internationally, consult local tax and employment counsel. The up-front legal review is significantly cheaper than the backend costs of misclassification in most jurisdictions. As US federal enforcement of classification rules has tightened under the 2024 DOL final rule^[2], expecting similar or stricter enforcement globally is the safer planning assumption.

8. Numeric worked example — 30-hour role across three structures

A bootstrapped SaaS needs a senior designer for ~30 hours/week of product and marketing design. The workload is predictable but doesn't fill a full-time role. Compare three structures at 1,560 productive hours/year.

Structure          Annual cost     Effective $/hour   Notes
─────────────────────────────────────────────────────────────────────────
FT employee        $115k base × 1.3 = $149.5k loaded
                   / 1,700 productive hr × (30/40) utilised =  ~$117/hr
                   Risk: 10 hr/wk slack paid for

Part-time W-2      $86k (pro-rated) × 1.25 = $107.5k loaded / 1,560 = $69/hr
                   Works if role genuinely qualifies at this cadence

Contractor         $95/hr × 1,560 = $148.2k                    $95/hr
                   No benefit load, clean termination
                   Must pass IRS 20-factor + DOL 2024 test[1,2]

Part-time W-2 is the cheapest per productive hour and eliminates misclassification risk. FT W-2 at 75% utilisation is the most expensive per actual hour delivered and burns $40k/year on unused capacity. Contractor sits between the two on pure cost but creates the classification question: 30 regular hours per week on your tools, attending your team meetings, under your day-to-day direction is probably employee-substance under the 2024 DOL final rule^[2]. If the work genuinely is defined-scope with worker autonomy, contractor is defensible; if it's "employee with a 1099," it isn't.

9. Failure modes worth naming

• Ex-employee re-engaged as 1099 doing the same work. The highest-risk misclassification pattern — IRS audits routinely flag this because it's a paper record of identical scope under a different classification. If an ex-employee must continue, structure genuinely different scope (defined project, external tools, client-facing autonomy) or accept W-2 continuation.
• State-level ABC tests ignored. California's ABC test, codified in AB-5 and its successors, is materially stricter than the federal tests^[5]. A role that passes IRS scrutiny federally can fail CA state review. For contractors in CA, MA, NJ, and IL particularly, run the state-level test explicitly.
• EOR relationship treated as "same as contractor." Employer-of-Record services (Deel, Remote, Oyster) add 10–15% to loaded cost but convert the worker to an employee of the EOR, not your company. Don't price them against the contractor's rate; price them against the W-2 loaded cost — the economics usually still favour EOR over setting up a local entity for fewer than 5 hires per country.

As of 2026-Q2, the DOL 2024 final rule has been in effect for over a year and enforcement data shows increased audit activity on misclassification across the professional-services segment^[2]. Plans benchmarked against pre-2023 classification norms systematically under-price legal exposure.