Hiring6

The Compliance Mistake We Almost Made Hiring Our First International Employee

We almost classified our first international hire as a contractor to save time and money. Here's what caught the mistake, and what it would have cost us.

We had a contractor agreement drafted and ready to send to our first hire outside the US. It would have saved us a month and a few thousand dollars in setup fees. It also would have been wrong, and we didn't catch it until two days before we sent it.

The hire that almost went out as a contractor

We'd found a strong engineer in a country where we had no legal presence. Opening an entity there made no sense for one person. An employer of record felt slow and expensive for a role we needed filled that month. So our first instinct, like a lot of founders' first instinct, was to just hire her as a contractor. Send a services agreement, pay an invoice, move on.

The agreement was drafted. Her start date was set. Then our ops lead, who'd been through this once before at a previous company, asked one question that stopped the whole thing: would this look like a full-time employee to a regulator, or an actual independent contractor with other clients and control over her own schedule?

We didn't like the answer. She'd be working our hours, using our tools, reporting to our engineering manager, attending our daily standup, and working exclusively for us with no other clients. On paper we were calling her a contractor. In practice, we were describing an employee.

What misclassification actually costs, once regulators look

Most founders assume the risk of misclassifying a contractor is a slap on the wrist if you get caught. It isn't. Regulators outside the US, and the IRS domestically, don't look at what your contract calls someone. They look at the reality of the working relationship: fixed hours, exclusivity, control over how the work gets done, integration into your internal team structure. If those boxes get checked, the label on the contract stops mattering.

The exposure isn't hypothetical. Misclassification findings routinely trigger back taxes, unpaid social contributions, retroactive benefits, and penalties, and in some jurisdictions those penalties compound per employee, per month of the violation. In the US alone, unintentional misclassification can mean paying a percentage of unpaid wages plus interest, on top of the employer's own share of Social Security and Medicare the company never withheld. If it's found to be intentional, the per-worker penalty and back-wage exposure both go up sharply. Outside the US, notice periods, mandatory severance, and social contribution back-pay vary so much by country that assuming your home country's rules travel with you is one of the most expensive habits in global hiring.

We ran the numbers on what a finding would have cost us for one misclassified hire, factoring back contributions and penalties into our runway. It wasn't close to what we'd have saved by skipping an EOR for a month. It wasn't in the same order of magnitude.

Why we didn't just open an entity instead

Once we ruled out the contractor route, the obvious next question was whether to just open a foreign entity and hire her directly. We priced it out. A foreign subsidiary typically runs $15,000 to $80,000 to set up depending on the country, before you count the ongoing cost of local payroll administration, tax filings, and a registered agent. For one hire, that math doesn't work. The generally accepted crossover point, where opening an entity starts to make more sense than paying an EOR's per-employee fee, is somewhere around 15 to 20 employees in that country. We had one.

What we did instead, and how fast it actually moved

We signed with an employer of record instead. The part that surprised us was the timeline: we'd assumed switching from a contractor agreement to an EOR-based employment contract this late would cost us two to three weeks. It cost us four business days, most of which was the EOR's own local compliance review, not paperwork on our end. She started on the date we'd originally planned. The only thing that changed was the structure underneath the offer, not the offer itself.

The EOR handled local payroll, the employment contract in the local language and under local law, statutory benefits, and the tax withholding we had no ability to do correctly ourselves. We paid a per-employee monthly fee for it. That fee, spread over a year, was a fraction of what one misclassification finding would have cost us, and nowhere close to what standing up our own entity would have cost for a single employee.

The one question that would have saved us the scare

If we'd asked one question before drafting the contractor agreement instead of two days before sending it, we'd have skipped the whole scare: does this role look, in practice, like a full-time employee, regardless of what we call it on paper? Fixed hours, exclusivity, integration into internal team processes, and control over how the work gets done are the four things regulators actually check. If two or more of those are true, the contractor label won't hold up, no matter how carefully the agreement is worded.

We ask that question first now, before any international hire gets a contract of any kind. It takes five minutes and it's the cheapest compliance check we've ever run.

Frequently asked questions

How do I know if my international hire should be a contractor or an employee? Look at four things: fixed hours, exclusivity to your company, integration into your internal team and processes, and how much control you exercise over how the work gets done. If two or more apply, regulators will typically treat the role as employment regardless of the contract's label.

What does misclassifying an international employee actually cost? It varies by country, but typically includes back taxes, unpaid social contributions, retroactive statutory benefits, and penalties that can compound per worker and per month of violation. It is almost always more expensive than the EOR fee you were trying to avoid.

At what headcount does opening a foreign entity make more sense than using an EOR? Generally around 15 to 20 employees in a single country, once the entity's setup cost (commonly $15,000 to $80,000) and ongoing compliance overhead get spread across enough people to beat cumulative EOR fees.

How long does it take to switch a hire from a contractor agreement to an EOR employment contract? In our case, four business days, most of it the provider's own local compliance review. It's usually faster than founders expect, especially compared to standing up a foreign entity from scratch.

Is it worth using an EOR for just one international hire? Yes, for almost any founder below the 15-to-20-employee-per-country threshold. The monthly per-employee fee is small compared to either the cost of a misclassification finding or the cost of setting up and maintaining your own foreign entity for a single person.

Read enough.
Ready to grow?

19 spots in the cohort. Applications open now.