You found a brilliant engineer in Bogotá or Karachi. Then your lawyer asked three questions you could not answer: who legally employs this person, who owns the code they write, and what happens if a tax authority decides your contractor was really an employee all along.
That is where most cross border hiring plans stall. The choice between EOR vs staff augmentation vs a direct contractor agreement is not a procurement detail. It decides who carries the misclassification risk, who holds the IP assignment, and whether your next round of due diligence turns into a fire drill.
This guide breaks down all three models: what they actually cost, what they protect you from, and which one fits a Series A or Series B team that needs engineers shipping now, not in six months.
Why the Contractor vs EOR Question Got Harder in 2026
US worker classification rules are moving again. On February 26, 2026 the Department of Labor proposed a rule to rescind the 2024 independent contractor test and restore an economic reality analysis built around two core factors: the nature and degree of control over the work, and the worker’s opportunity for profit or loss based on initiative or investment. The public comment period closed on April 28, 2026.
Meanwhile the IRS has not moved at all. It still applies common law rules across three categories: behavioral control, financial control, and the type of relationship. The IRS is blunt that there is no magic number of factors. You have to weigh the entire relationship and document how you reached your conclusion.
Read those two together and one thing jumps out. If you tell a foreign contractor when to log on, hand them your tooling, put them in your daily standup, give them a company email address, and keep them for 18 months, you do not have a contractor. You have an employee holding a contractor invoice. That gap is exactly what auditors, acquirers, and unhappy workers pull on.
The good news: you have three legitimate ways to close it, and only one of them requires you to open a legal entity in another country.
The Three Models, Explained in Plain English
1. Direct contractor
You sign a contract directly with an individual abroad. They invoice you monthly. You pay by wire or through a contractor payment platform.
It is the cheapest and fastest option on paper. It is also the one that puts every ounce of classification risk, IP risk, and permanent establishment risk on your company. Nobody stands between you and a bad outcome. Contractor payment platforms publish rates starting around $29 to $49 per contractor per month (publicly reported figures; confirm current terms with the vendor), and those tools handle invoicing and document collection. They do not, in the base tier, absorb your legal exposure.
2. Employer of Record (EOR)
An EOR is a company that already has a legal entity in the country where your engineer lives. The EOR employs the person formally, runs local payroll, withholds local taxes, provides statutory benefits, and invoices you. You direct the work day to day.
This is the strongest compliance posture available without opening your own entity. It is also the most expensive per head and the slowest to start, because real employment onboarding takes time. Major providers publish EOR pricing starting around $599 to $699 per employee per month on top of the salary itself (publicly reported; confirm current pricing directly with each vendor). One provider also publishes a contractor of record tier at $325 per contractor per month and another offers a contractor tier at $99 per month that adds indemnity coverage up to $100,000 per contractor.
3. Staff augmentation
A staffing partner employs or formally engages the engineer under its own entity and contracts with you for their time. You get one commercial agreement, one invoice, one hourly rate, and a vendor who is contractually on the hook. If you have never used the model, our primer on what staff augmentation is covers the mechanics, and our breakdown of staff augmentation vs outsourcing explains why it is not the same thing as handing a project to an agency.
The key difference from an EOR: an EOR is a compliance utility, you still have to source, vet, and interview the person yourself. A staff augmentation partner finds the engineer too. That distinction matters more than the price gap, because sourcing is usually the bottleneck, not paperwork.
EOR vs Staff Augmentation vs Contractor: The Comparison Table
| Factor | Direct contractor | Employer of Record | Staff augmentation |
|---|---|---|---|
| Who legally employs the engineer | Nobody, they are self employed | The EOR’s local entity | The staffing partner’s entity |
| Who carries misclassification risk | You | The EOR, contractually | The staffing partner, contractually |
| Who finds the engineer | You | You | The partner |
| Typical cost structure | Rate plus roughly $29 to $49 per month platform fee | Salary plus benefits plus roughly $599 to $699 per month | One blended hourly rate (Divogue: $30 to $35 all in) |
| Time from decision to first day | Days | Two to six weeks | Candidates in about 48 hours |
| IP assignment path | Direct in your contract, enforceability varies by country | Through the EOR employment agreement, then assigned to you | Through the vendor agreement, backed by the vendor entity |
| Local entity required | No | No | No |
| Exit | Per contract, usually fast | Local statutory notice and severance apply | Per master service agreement, usually 2 to 4 weeks |
| Best for | Short, genuinely project scoped work | A specific person you already found and want long term | Filling a role fast with vetted talent |
Cost figures for third party platforms are publicly reported list prices and change often. Confirm current terms directly with each vendor before you budget.
Who Actually Owns the IP, and Why Most Founders Get This Wrong
Here is the part that bites during acquisition diligence. In the US, a work made for hire doctrine covers employees. It does not automatically cover contractors, and it definitely does not travel cleanly across borders. Several countries give the creator moral rights or statutory ownership that a one page US contract does not override.
Three rules will save you most of the pain:
- Get a present tense assignment, not a promise.
“Contractor hereby assigns” survives. “Contractor agrees to assign” creates a future obligation you may have to chase someone across a border to enforce. - Make the agreement governed by law you can actually use.
A contract governed by a jurisdiction where you will never realistically litigate is decoration. This is one of the quiet advantages of working through a vendor entity: your counterparty is a company with US contractual exposure, not an individual 8,000 miles away. - Assign the tools, not just the deliverable.
Prompts, eval harnesses, fine tuning datasets, and agent scaffolding are where AI work lives now. If your assignment clause only names “software,” go widen it.
Our deeper guide on offshore development security and protecting your IP walks through the access controls and contract language that hold up under scrutiny.
What Misclassification Actually Costs You
The IRS is direct about the consequences: an employer who treats an employee as an independent contractor without a reasonable basis can be held liable for employment taxes for that worker, including the Social Security and Medicare amounts that should have been withheld. Workers, for their part, can file Form 8919 to claim the uncollected share, which is often how the agency learns about the arrangement in the first place.
Add the practical costs on top of the tax bill:
- Diligence delay.
Acquirers and Series B leads will ask for your contractor roster and your IP assignments. A messy answer costs weeks and sometimes price. - Permanent establishment exposure.
A long running, fully directed worker abroad can, in some jurisdictions, create a taxable presence for your company in that country. - Back pay and benefits claims.
Local labor law sets floors for notice, severance, and paid leave, and those claims follow the relationship, not the invoice header.
None of this means hiring abroad is dangerous. It means the structure is not optional. Our look at the true cost of hiring a US AI engineer shows why teams keep looking offshore anyway, and the real offshore rates by region are the reason the math works.
How to Choose: A Decision Guide by Situation
You need a defined deliverable in under 90 days from a specialist you already know.
Direct contractor is fine. Genuinely scope it, keep control light, set an end date, and use a present tense IP assignment.
You have already identified one specific senior person abroad and want them for years.
EOR wins. You are paying for local employment compliance and benefits that keep a great hire happy and legally clean. The monthly fee is trivial against a senior salary.
You need two to five engineers, you have not found them yet, and the roadmap slips every week you wait.
Staff augmentation. The sourcing is the constraint, and an EOR does not solve sourcing. This is the situation most Series A and Series B teams are actually in.
You are testing whether a role works at all before committing headcount.
Staff augmentation with a trial period. Divogue runs a two week risk free trial with no upfront cost precisely so the first bet is cheap. If you are comparing vendors, our seven point checklist for choosing a staff augmentation company is a good filter.
You will have 20 or more people in one country within two years.
Start modeling your own entity. At that scale the per head fees on any intermediary stop making sense.
Where Staff Augmentation Is the Wrong Answer
Being honest about this is more useful than pretending otherwise, so here are the cases where we tell people to go elsewhere.
You want equity to be the retention mechanism.
Contractors and augmented engineers do not get your option pool. If your entire hiring pitch is early equity in something huge, an EOR arrangement or a direct hire is the right structure and we are not.
The role is inherently a US presence role.
Federal contracts with citizenship requirements, on site hardware work, customer facing field engineering, or anything under ITAR. No amount of timezone overlap fixes that. Our guide to hiring software engineers by state is the better starting point there.
You need one narrow specialist for three weeks.
A marketplace or a well scoped direct contract is cheaper and faster than onboarding a vendor relationship. Staff augmentation earns its keep over months, not weeks.
Your engineering org has no onboarding process.
An augmented engineer with no owner, no first ticket, and no code review path will underperform, and it will not be their fault. If you cannot name who they report to on day one, fix that before you hire anyone from anywhere.
An EOR genuinely beats us in one clear case.
When you have already found the person, you want them permanently, and you want them to feel like a full employee with local benefits and statutory protections. That is what an EOR is built for, and it is a better fit than any hourly vendor arrangement.
Key Takeaways
- Direct contractor is cheapest and fastest, and it leaves every classification, IP, and permanent establishment risk with you.
- An EOR employs the person legally in their country and absorbs compliance risk, but it does not source, vet, or interview anyone for you.
- Staff augmentation solves sourcing and compliance in one contract, which is why it fits teams that have a roadmap gap rather than a named candidate.
- The IRS weighs behavioral control, financial control, and the type of relationship. Day to day direction of a long term worker is the single biggest red flag.
- Use present tense IP assignment language and extend it to prompts, evals, and datasets, not just source code.
- Published third party pricing ranges from roughly $29 per month for basic contractor payments to roughly $599 to $699 per month for EOR. Confirm current terms with the vendor.
- At roughly 20 people in one country, building your own entity starts to beat paying per head fees.
Frequently Asked Questions
What is the difference between an EOR and staff augmentation?
An EOR is a compliance layer: it legally employs a person you already found and handles local payroll, tax, and benefits. Staff augmentation includes that legal layer but also sources, vets, and presents the engineer. If your bottleneck is paperwork, use an EOR. If your bottleneck is finding qualified people, use staff augmentation.
Is it legal to hire an engineer abroad as an independent contractor?
Yes, when the relationship is genuinely independent. It becomes a problem when you control how and when the work is done, the engagement runs indefinitely, and the person works only for you. The IRS common law test looks at the whole relationship, so document your reasoning and revisit it as the engagement changes. This is general information, not legal advice, so run your specific setup past employment counsel.
How much does an Employer of Record cost?
Major providers publish rates starting around $599 to $699 per employee per month on top of the salary and statutory benefits, with lower tiers for contractor management. These are publicly reported list prices that change, so confirm current terms with the vendor before budgeting.
Who owns the code an offshore engineer writes?
Whoever the contract says owns it, provided the assignment is enforceable in the engineer’s jurisdiction. Work made for hire does not automatically cover contractors or travel cleanly across borders, so use a present tense assignment clause, pick a workable governing law, and make sure it covers prompts, datasets, and tooling alongside source code.
Does staff augmentation work across time zones?
It depends entirely on where the engineers are. Divogue places engineers from LATAM and APAC with full US timezone overlap built into the arrangement, which is the difference between same day code review and a 14 hour round trip on every question. Our comparisons of nearshore development in LATAM and hiring AI engineers in APAC go deeper on the tradeoffs.
The Bottom Line
The contractor versus EOR versus staff augmentation decision is really a question about what is scarce for you right now. If compliance certainty is scarce, buy an EOR. If a specific short deliverable is all you need, a well scoped contractor agreement is fine. If qualified engineers are what is scarce, and for most Series A and Series B teams in 2026 they are, then the model that also solves sourcing is the one worth paying for.
What you should not do is default to direct contractor because it is the path of least resistance today. That decision is cheap for twelve months and expensive exactly once, usually in the middle of a diligence process when you have no time to fix it. If you are still weighing geographies, our roundup of the best countries to hire remote software developers pairs well with this one.
Hire Engineers Abroad Without the Compliance Headache
Divogue places pre vetted, AI fluent engineers from LATAM and APAC with US tech teams at $30 to $35 per hour all in. Our entity holds the employment relationship and the IP assignment, so you get one contract and one invoice instead of a classification problem. Candidates in about 48 hours, full US timezone overlap, a two week risk free trial, and no upfront cost.
Book a 15 minute call to talk through your roles, or reach us through the contact page and we will send profiles this week.