I’ve spent a loooong time in this market. I’ve watched companies buy the wrong product because a vendor used the wrong term. I’ve seen compliance teams inherit risk they didn’t know they were taking on. I’ve had advisors tell companies they needed an EOR when what they actually needed was global payroll - and the other way around.

The terminology problem is not minor. When you pick the wrong model, you either overpay, take on unexpected liability, or create a compliance gap that shows up later in a tax audit or an employment dispute.

So I wrote a paper about it. It’s live on SSRN now.

And the four models are not the same, and the differences matter.

With an EOR, the vendor becomes the legal employer of your worker in the foreign country. They handle payroll, taxes, benefits, and employment contracts. You direct the work. They own the legal relationship. You don’t need your own entity in that country.

A PEO is co-employment. The PEO shares the employer relationship with you - they handle HR administration, benefits, and compliance, but you typically need your own registered entity in the country first. Common in the US. Less common internationally.

Global Payroll is different at its core. You are the employer. You have the entity. You just need someone to run payroll across multiple countries without getting it wrong. No co-employment. No legal employer transfer. Just payroll execution.

COR - Contractor of Record - engages a contractor on your behalf. The worker is classified as an independent contractor, not an employee. The COR handles the contract and payments. The key risk is misclassification. If the worker should legally be an employee, calling them a contractor does not protect you.

The taxonomy in the paper is built around four questions. Who is the legal employer - is it the vendor, you, or shared? Do you need your own entity in the country? How portable is the model across different countries? And who carries the liability?

Run any of the four models through those four questions and the differences become clear. EOR answers all four differently from PEO. COR is different at its core from Global Payroll. The terms are not interchangeable because the answers are not interchangeable.

Why does this paper exist? There’s no formal definition of these terms anywhere. Vendors define them however suits their product. Regulators use different language. Even the academic literature on platform work and worker classification doesn’t map cleanly onto how these services are actually sold and used.

The ILO has a framework for employment relationships - who employs who, what obligations follow - but nobody had applied it systematically to these four categories. I drew on that framework, regulatory definitions across jurisdictions, academic literature on worker classification and platform work, and ten years of watching how these models get used and misused in practice.

The result is a taxonomy and a decision framework. The decision framework is at the end of the paper. If you’re trying to figure out which model fits your situation, start there.

What this paper is not: it’s conceptual. I’m not testing the taxonomy across every jurisdiction. That’s future research - and I say so explicitly. I’m also co-founder of an independent advisory platform in the global employment solutions market. That’s declared upfront. The paper doesn’t recommend any vendor. It’s not a sales tool. It’s an attempt to give the market a shared vocabulary that actually holds up.

Most people think this terminology confusion is just a minor communication issue. It’s not. It’s a structural problem in the market. And it costs companies real money.

If you advise companies on global hiring, this is the vocabulary your companies need you to have. If you’re buying one of these services, the decision framework alone is worth the read. If you work in global HR and you’ve ever sat in a meeting where three people used EOR to mean three different things, you’ll recognise every problem this paper is trying to solve.

The paper is 23 pages. Link here.

Nyepi is the Balinese Day of Silence. One day a year, the entire island stops. No cars. No flights. No internet. No leaving your home. Silence from 6am to 6am the following day - a full 24 hours where nothing moves and nothing happens.

The airport shuts down. Literally closes. The streets are empty and patrolled by local guards called Pecalang to make sure nobody breaks the rules. If you’re a tourist who didn’t plan for this, you’re stuck in your hotel with nothing to do. That’s the point.

My first year, I was not a tourist who had planned for this. I was an idiot who had completely forgotten it was happening. I had no food in the house. Zero. I think I had half a bag of rice and some soy sauce. What followed was less a spiritual day of reflection and more an involuntary 36-hour fast, because by the time Nyepi ended the following morning I’d already been running on fumes since the afternoon before. Nothing humbles you quite like sitting in silence contemplating your own existence while your stomach is aggressively reminding you that existence requires groceries.

So. Learn from me. Buy food.

The first time I actually experienced it properly - with, crucially, food in the house - I thought it would feel like a mild inconvenience. It didn’t. It felt strange in a way I wasn’t prepared for. The absence of noise is loud in its own way. You realize how much background stimulation you’ve normalized.

This year I used the time to read Start with Why by Simon Sinek. I’d had it on my list for months. Never made time for it because there was always something more urgent. There’s always something more urgent.

The book hit differently without any distractions competing for the same mental space. The central question Sinek asks is simple: why do you do what you do? Not how. Not what. Why. I’ve thought about this before. Most people in business have. But sitting with it for hours, with no notifications, no traffic outside, no background noise - it becomes a different question entirely.

I didn’t arrive at some dramatic revelation. That’s not how this works. What I noticed was that my usual mode is reaction. Something comes in, I respond. Something breaks, I fix it. There’s always a queue. And when there isn’t a queue, I manufacture one by checking things I don’t need to check.

Nyepi removes the queue. Completely. And you’re left with whatever’s actually underneath it.

Most people I know - genuinely smart, capable people - haven’t stopped moving in years. Not really stopped. Vacations have Wi-Fi. Weekends have side projects. Time off has email. The idea of an enforced 24-hour pause, with no way around it, sounds either terrifying or pointless to most of them.

That reaction is the problem.

The world has no natural stopping points anymore. There’s no mechanism that forces you to sit with your own thoughts. Every gap gets filled. You’re waiting for a flight - scroll. You finish a project - immediately open the next one. You wake up at 3am - check your phone. The default is always more input.

Nyepi is the only thing I’ve encountered that genuinely breaks the loop. Not because it’s spiritual, not because of the cultural significance - although both of those things are real - but because it’s mandatory. You can’t opt out. You can’t schedule it for a more convenient time. It happens on the same day every year and the whole island enforces it together.

That’s what makes it different from any personal productivity habit or silent retreat or digital detox weekend you might voluntarily choose. Voluntary stops are soft. You can always decide you really need to check one thing. Nyepi doesn’t give you that exit.

I’ve been in more strategy sessions, planning offsites, and quarterly reviews than I can count. Most of them produce slides. A day of forced silence where you can’t perform productivity or signal effort produces something else - actual thinking.

The real question is why no other country has something like this. A national day with nothing scheduled. No commerce, no traffic, no events. Just a pause baked into the calendar that everyone takes together whether they want to or not.

I’m not talking about a public holiday where you go shopping or visit family. I mean a day where the default is stillness, not activity. Where the systems around you slow down too.

Every year I come out of Nyepi noticing things I hadn’t noticed before. What’s been bothering me that I’ve been too busy to name. What I’ve been doing out of habit versus intention. What actually matters when there’s nothing else competing for the answer.

Seven years in, I still think it’s one of the strangest and most underrated things about living here.

Also, I now have a dedicated Nyepi shelf in my pantry that I restock every year. Hard lessons stay learned.

That’s exactly why it’s dangerous.

And this is the part that catches people off guard - misclassification risk doesn’t build like a leak you can hear. It builds like debt you can’t see. Every month that passes, every Slack message directing their schedule, every company tool you hand them, every deadline you set - that’s evidence stacking up in a file nobody’s reviewing yet.

Until someone does.

The most common thing I hear is some version of: “We’ve been doing this for two years and nothing’s happened.” I get it. Two years of nothing feels like proof. It’s not. It’s just a longer fuse.

The real question is what happens when it blows. And that varies wildly by country - more than most people realize.

Germany is one of the stricter environments. If a German tax authority decides your contractor is actually an employee, you’re looking at backdated social security contributions for both sides - yours and theirs. The employer portion alone can run 20%+ of total compensation. For two years. Retroactively. Plus penalties on top. Germany also has a concept called “Scheinselbstständigkeit” - fake self-employment - and they take it seriously. The criteria they use aren’t just about contracts. They look at how the work actually happened.

Argentina is a different kind of problem. Employment law there is heavily weighted toward workers. If someone is reclassified as an employee, the company can be on the hook for statutory severance, unpaid benefits, and contributions going back to day one. Argentina also has high inflation, which means the peso values shift but the liability calculates based on what was owed at the time. The math gets ugly fast.

South Africa has its own version. Labor courts there have increasingly sided with workers claiming employee status even when contracts said otherwise. The key test isn’t the contract language - it’s the economic reality of the relationship. Did they work exclusively for you? Did you control how the work was done? Those answers matter more than what the agreement says.

This is the part people miss. Most founders and HR leads assume that having a contract calling someone a contractor is the protection. It’s not. Every country with meaningful enforcement uses a substance-over-form test. They look at the actual relationship, not the document.

I wrote an article on this on Employ Borderless, I’ll attach the link here: https://employborderless.com/eor/vs-cor/

The silence is what compounds it. Unlike a bad hire or a missed deadline, misclassification has no obvious signal while it’s happening. The contractor doesn’t know to flag it. Your finance team isn’t tracking the exposure. Legal isn’t involved because nothing has gone wrong yet. By the time someone raises a hand, you’re often looking at years of accumulated liability.

From what I’ve seen, the companies that get hit hardest are the ones who grew fast. They hired a few contractors across a few countries, it worked operationally, they added more, nobody paused to ask whether the classification still held. Then they try to raise a round, or get acquired, and due diligence surfaces it. Or a contractor leaves unhappy and files a complaint. Or a local authority runs an audit.

The other thing worth knowing: the person you hired often has no idea this is coming either. Reclassification doesn’t just hit the company. In some countries, the worker suddenly has tax obligations they weren’t planning for. Benefits they were supposed to receive but didn’t. It creates a mess on both sides.

I’ve spent a decade watching companies handle global hiring. The contractor question comes up constantly, and the answer is almost always the same: it works until it doesn’t, and the gap between those two states is invisible.

Two years of nothing is not a green light. It’s just two years.

The thing is, EOR is a great product for the right stage. It’s a terrible product if you’ve aged out of it and don’t realize it.

The basic EOR fee structure is pretty consistent across the market. You’re paying somewhere between $500 and $1,500 per employee per month on top of actual salary and benefits. Call it $800 as a working average for a mid-market provider in a Western European or APAC market. Some charge a percentage of salary instead - usually 15 to 25 percent - which gets painful fast if you’re hiring senior people.

Now run the other side of the equation. Setting up a local legal entity costs real money. Registered address, local accountant, payroll software, HR administration, legal fees to incorporate, annual compliance filings. Depending on the country, you’re looking at $15,000 to $40,000 to get set up properly, then $2,000 to $6,000 per month to run it. Germany and the Netherlands are on the higher end. Simpler markets come in lower.

So the math isn’t complicated. If you’re paying $800 per head per month on EOR, and your entity costs $4,000 a month to operate, you break even at five employees in that market. Above five, the entity is cheaper. Every month you wait past that point, you’re leaving money on the table.

The real question is why so few companies actually hit that trigger. A few reasons.

One, the upfront entity cost feels big even when the ongoing savings are obvious. $30,000 to incorporate and get compliant feels like a lot. The fact that you’ll recover it in under a year with six employees doesn’t land the same way emotionally.

Two, entity management is operational work that nobody owns. EOR is clean - one invoice, one vendor, their problem. Running your own entity means hiring or contracting a local payroll person, managing relationships with local accountants, and staying on top of regulatory changes. That’s real overhead.

Three, companies cluster their hires without realizing it. You don’t cross five employees in Germany all at once. You get to two, stay there for a year, add another, plateau again. The math technically tips in your favor but nobody notices because nobody’s watching it.

Here’s what I’ve seen over and over. Companies hit eight or ten employees in a market and they’re still on EOR because the original decision was never revisited. The person who set it up is gone, or they’re busy, or it just never came up in a quarterly review. They’re paying $8,000 to $10,000 a month when an entity would cost them $4,000 to run. That’s $50,000 to $70,000 a year in pure overhead waste.

Market density matters too. If your hires are spread across five countries with two people each, EOR makes sense indefinitely. Managing five separate entities for ten total employees would be a compliance nightmare that costs more than it saves. The breakeven calculation only tips toward entity when you have concentration - five or more people in a single market.

The other variable people ignore is employee seniority. A $200,000 base salary on a percentage-based EOR fee is $30,000 to $50,000 per year in fees alone. One senior hire in the wrong fee structure and the entity math shifts dramatically. I’ve seen single hires where the entity would have paid for itself in 18 months just from eliminating the fee on that one person.

There’s also a hidden cost to EOR that doesn’t show up in the fee line. You don’t control the employment relationship fully. Some providers restrict what benefits you can offer. Contract terms are standardized. If you want to do something non-standard - equity plans, unusual leave policies, custom bonus structures - you’re either fighting the provider or paying extra for customization. Your own entity gives you that flexibility without negotiating it every time.

The breakeven isn’t one number. It’s a function of headcount, market, salary levels, and how much you value operational control. But the rough answer for most markets is five to eight employees. Below that, EOR wins on simplicity and cost. Above that, you’re probably overpaying and the only reason nobody knows is that nobody checked.

The salary is almost never the number that surprises you. It’s everything sitting on top of it. Employer social security contributions. Mandatory pension. Statutory leave that you’re legally obligated to fund. Severance exposure that kicks in the moment someone signs a contract. That’s the real cost of hiring internationally, and almost nobody calculates it upfront.

I’ve been pulling data from the OECD to actually map this out across 50 countries. Employer social security rates alone range from under 10% in some countries to over 30% in others. France is the extreme case - total employment costs there run 40-45% above base salary. You hire someone at €60,000 and you’re spending closer to €85,000. That gap is not a rounding error.

Most people think the variance between countries is manageable. It isn’t. The spread between the cheapest and most expensive countries to employ someone is enormous, and it’s not always the countries you’d guess. Some high-salary markets have surprisingly low employer burdens. Some cheaper salary markets hit you hard on contributions.

The dataset I’m building covers employer social security rates, statutory leave entitlements, mandatory pension contributions, and severance exposure - the four things that actually move the number. Not the salary. The stuff wrapped around the salary.

The goal is a simple visualisation tool. You enter a country and a base salary. You get a breakdown of what you’re actually spending. No estimates, no ranges pulled from a consulting deck - OECD data, structured into something you can actually use before you make a hire.

Target date is March 31st, 2026. Still a ways out, but the data work takes time to do properly.

Why does this matter for how companies actually make decisions? Because I keep seeing the same pattern. A company wants to hire in a new country. They look at local salary benchmarks, pick a number that feels competitive, and assume that’s the budget line. Then the invoices start coming in and nothing adds up. The employer burden was never factored in.

This isn’t a niche problem. It affects every company hiring across borders - startups making their first international hire, larger companies growing a regional team, anyone trying to compare the true cost of headcount in Berlin versus Bogotá versus Bangkok.

And it connects directly to why Employer of Record services exist. An EOR doesn’t just handle payroll. It absorbs the local cost structure - registrations, contributions, compliance, all of it. When a company uses an EOR, they’re mainly outsourcing the navigation of exactly this complexity. But you still need to understand the underlying costs, because the EOR fee is built on top of them.

The data is also useful for comparing EOR quotes. If you don’t know what employer social security should cost in a given country, you can’t tell whether a quote is fair or padded.

I’m still adding countries to the dataset. If there’s a market you’re actively hiring in or considering, drop it in the comments. I’ll prioritize based on what’s actually useful to people working through this right now.

Companies pick EOR providers for the wrong reasons. They read a comparison article, pick the one with the most polished landing page, and sign a contract. Then six months later they’re frustrated, overpaying, or stuck in a structure that doesn’t fit what they actually need.

So here’s how I actually think through it.

First question: how many people are you planning to hire in this country over the next 12 months?

This one matters more than people realize. If the answer is one to five, EOR almost always makes sense. You’re not big enough to justify the cost and complexity of your own entity. The math doesn’t work. Setting up a legal entity in most countries costs anywhere from $5,000 to $30,000 in legal and admin fees alone, and that’s before you think about ongoing compliance, local accounting, and HR overhead.

But if the answer is fifteen or more, the calculation flips. At that scale, your EOR fees start to look like rent you’re paying on someone else’s building. You’re funding their entire operation when you could be building your own. Not always - there are exceptions - but the number fifteen is roughly where I start asking harder questions.

Second question: do you actually need a local entity, or do you just need to employ someone?

And here’s what most people miss. These are two completely different problems. And people mix them up constantly.

An EOR solves the employment problem. You can hire someone in a country where you have no legal presence. They get a proper employment contract, local benefits, compliant payroll. Done. The EOR is the legal employer on paper, you’re running the work.

What an EOR doesn’t solve is the business reason for being in that country. If you need to sign local contracts, hold a local banking license, bid on government work, or operate as a recognized local company - that’s an entity problem. EOR won’t fix it.

From what I’ve seen, most companies hiring their first employee abroad don’t actually need an entity. They need a person. They’ve conflated the two because someone told them “you need to set up locally” without asking why.

If the real reason is “we want someone on the ground who can do the work” - EOR handles that cleanly. If the reason is “we need to be a registered business in that market” - different conversation entirely.

Third question: how fast do you need this person to start?

This one cuts through a lot of indecision.

Setting up your own entity takes three to six months in most countries. Sometimes longer. There’s registration, tax IDs, local bank accounts, HR policies, payroll setup. It’s not complicated, but it’s slow. Bureaucracy moves at its own pace.

An EOR can get someone employed in two to four weeks. Sometimes faster. The systems are already in place. You’re plugging into something that exists.

If you have a hire who’s sitting on a competing offer and needs an answer in two weeks - entity setup isn’t a real option. Even if the long-term math eventually favors an entity, the short-term reality doesn’t.

I’ve talked to enough companies to know that urgency often drives the EOR decision more than anything else. Someone found a great candidate, they need to move, and they don’t have six months to wait on legal setup. EOR wins by default.

What I find interesting is how rarely these three questions get asked before someone starts Googling “top-rated EOR provider.” People jump straight to vendor comparison when they haven’t figured out what they actually need yet.

The provider question is the last question. Not the first.

First one: “Must be available during HQ business hours.”

You’ve hired someone to work nights. That’s it. That’s what you’re saying. If your HQ is in San Francisco and your hire is in Warsaw, you’re asking them to start their day at 5pm. That’s not a timezone overlap. That’s a night shift. Call it what it is or fix it before you post.

Next: “Competitive salary.”

This phrase is useless everywhere. For international hires it’s actually harmful. A competitive salary in Lagos and a competitive salary in Zurich are not the same number. Not even close. When you leave the number out, international candidates either assume the worst and don’t apply, or they apply, get to the offer stage, and everyone wastes weeks. Put a range. It’s not that complicated.

“We’re like a family here.”

I know this one feels warm. It’s meant to signal culture. But what it actually signals to experienced remote workers is this: this company runs on vibes and proximity, not documentation. Remote teams run on written processes, async communication, and clear expectations. Family culture usually means the opposite of that. It means hallway conversations, gut decisions, and you needing to be physically present to actually matter.

Then there’s “occasional travel required.”

Fine. Travel happens. But occasional means nothing. Is it once a year for a team offsite? Is it quarterly? Is it every time there’s a client meeting? I’ve seen people take remote jobs, relocate their lives, and then discover occasional meant six weeks a year in a country they didn’t plan on visiting. Define it or don’t include it.

The fifth one is the one that annoys me most: “Must be legally eligible to work in [country].”

This line makes sense if you’re hiring for an in-office role. It makes zero sense on a fully remote job post.

Think about what work authorization requirements actually exist for - physical employment relationships. If you’re in the US and you hire someone to sit in your office, yes, they need to be authorized to work in the US. That’s how it works.

But if the job is fully remote and you’re open to hiring internationally, this requirement is self-imposed and optional. An Employer of Record handles exactly this. The EOR becomes the legal employer in the candidate’s country. You manage the work. They handle compliance, payroll, and local employment law. Your candidate doesn’t need to be eligible to work in your country because they’re not working in your country.

That one line - probably added by legal years ago and never revisited - is quietly eliminating candidates who are perfectly hireable. Strong engineers. Experienced operators. People who would do the job well. Gone before you even see their resume.

The math doesn’t work. You post a remote role. You say you’re open to global applicants. Then you require work authorization for a country the person will never physically work in. You’ve contradicted yourself and most candidates won’t bother to ask why.

The pattern I keep noticing is that remote job posts are written by people who’ve never worked remotely, based on templates written for office jobs, reviewed by legal teams focused on domestic hiring. Nobody stops to ask whether the requirements still make sense for the role.

Some of these five things are just sloppy writing. A couple of them are genuinely losing you candidates. The last one is doing both.

We celebrated. Good dinner, with her family, not as romantic as I was planning to (still hear that until today), but it was a nice night.

Saturday morning I woke up, made coffee, and opened my laptop.

Not because I was anxious. Not because something was on fire. Not because I couldn’t switch off. I opened it because I wanted to.

I’ve been trying to explain this for years and most people don’t buy it. The assumption is that if you’re working on a weekend - especially a weekend like that one - something is wrong. You’re avoiding something. You’re addicted to productivity. You don’t know how to rest.

Maybe that’s true for some people. It’s not true for me.

The thing is. A few years ago I was in Bali. Someone at a co-working space told me I should close the laptop and go relax. I told them that working in the morning is how I relax. They looked at me like I’d said something deeply broken.

But I meant it. Sitting with coffee, reading something interesting, poking at a problem I’ve been thinking about - that’s not the opposite of rest for me. That’s part of what rest looks like.

My fiancée knows this. She’s always known it. She didn’t say yes to a version of me that was going to wake up on a Saturday and go for a long run and journal and be fully off-grid until Monday. That guy doesn’t exist. She said yes to the guy who would be on the couch with coffee and a laptop by 6am, probably happy about it.

That matters. Because I think the conversation around work and rest has gotten weirdly binary. Either you’re burned out and grinding, or you’ve achieved some enlightened state of disconnection. There’s not much space for a third option: you just actually like what you’re building.

The real question is why, not how much.

If someone’s working on a Saturday because they’re scared of falling behind, that’s worth looking at. If they’re doing it because their inbox gives them anxiety and staying busy keeps that quiet, same thing. Those are real problems.

But if someone opens their laptop because they’re genuinely interested in what they’re working on? That’s just... a person with work they care about. Not a cautionary tale.

I’ve been in global hiring for a bunch of years now. I’ve tested more EOR providers than I care to count. And the weird part is - I find it interesting. Not performing-interesting for a newsletter. Actually interesting. The plumbing of how people get paid across borders, how compliance breaks down in weird edge cases, how companies get this wrong in the same ways over and over. I like thinking about it.

So Saturday morning after getting engaged, I opened my laptop and read something about payroll compliance in Southeast Asia, build some new features for our platforms, took some notes. It was a good morning.

Then I closed it and we went to brunch.

I’m not writing this to be contrarian or to make a point about hustle culture. I genuinely don’t care how other people structure their weekends. But I do think there’s a version of the rest-and-recovery conversation that accidentally makes people feel guilty for enjoying their work. Like if you’re not forcing yourself to step away, you must not understand what’s good for you.

Some of us are just wired differently. Building things is one of the good parts of life for me - not the thing I do between the good parts.

She knows that. She said yes anyway.

Good outcome.

Most companies overthink their first international hire. They see all these acronyms - EOR, PEO, contractor of record - and assume it’s rocket science.

It’s not.

Here’s what actually happens. You want to hire someone in Germany but you don’t have a German entity. You have two main options.

Option one: hire them as a contractor through a contractor of record service. This is faster and cheaper upfront. Takes maybe a week to set up. The person stays an independent contractor legally.

Option two: hire them as a full employee through an Employer of Record. This takes longer, costs more, but gives you and the worker full employment protections.

From what I’ve seen over the past years, most companies follow the same pattern. They start with contractor of record for their first hire. Test the waters. See if the person works out.

Once they’re confident about the hire - usually after 3-6 months - they convert to EOR. Now the person becomes a proper employee with benefits, vacation days, and job security.

I made a short YouTube video for whoever is interested.

The Employer of Record becomes the legal employer in that country. They handle payroll, taxes, compliance, benefits. You manage the day-to-day work. Think of it like outsourcing HR and legal stuff to someone who already has the setup in place.

The contractor route works fine short-term. But it gets messy if the person starts acting like an employee. Working set hours, using company equipment, taking direction like staff. Tax authorities don’t like when contractors look too much like employees.

That’s why the progression makes sense. Start as contractor to test the relationship. Move to EOR when you want them as permanent team members.

The whole industry has gotten better at making this simple. Most providers now offer both contractor and EOR services. You can start with one and switch to the other without changing platforms.

I’ve tested over 50 different providers. The mechanics are mainly the same everywhere. You fill out forms, provide documents, they handle the legal setup. The differences are in speed, cost, and how much hand-holding you get.

What trips people up is thinking they need to understand all the employment laws in each country. You don’t. That’s literally what you’re paying the EOR to handle.

The real decision is timing. Contractors work for short-term projects or when you’re unsure about the hire. EOR makes sense when you want someone as a permanent team member.

Most companies I talk to wish they’d started sooner. They spend months researching and planning when they could have had someone working in a few weeks.

The pattern I keep seeing is this: companies that move fast on their first international hire end up building better global teams. They learn by doing instead of planning.

From a practical standpoint, the contractor-to-EOR path gives you flexibility. Low commitment initially, full employment relationship later. Most providers make the transition smooth.

The costs aren’t as scary as people think either. Contractor services usually run 5-10% of salary. EOR services are typically 15-25%. Yes, it’s an expense, but it’s predictable and includes everything.

I spent years overcomplicating this before I realized the basic mechanics are straightforward. You want to hire internationally, you need local compliance, these services provide that foundation.

The industry has matured enough that the main providers handle the complex stuff reliably. Your job is picking the right one for your specific situation, not becoming an expert in German employment law.

Here’s the thing though. I don’t use tools like OpenClaw for my actual business operations. I’m still skeptical about the security implications. Handing over access to my sales data or client information feels too risky right now.

So instead, I started building custom agents with Claude. Way more control over what data gets shared and how it’s processed.

I’m surprised by the output quality. I’m using Claude Sonnet 4.5 for most routine tasks and switching to Opus when I need deeper analysis. Created separate agents for revenue forecasting and SEO content optimization. Each one handles specific workflows without crossing into sensitive territory.

The real question is why more people aren’t doing this. You don’t need a computer science degree to start. Tools like Cursor and Claude make it accessible. You just need to get familiar with how prompt engineering works.

Two reasons this matters right now. One, it simplifies your daily work output immediately. Two, we’re entering a phase where this becomes table stakes for staying competitive. Better to experiment now than scramble to catch up later.

Most people think building AI agents requires complex coding. It doesn’t. The core thinking process is straightforward logic chains. If this condition exists, then execute that action. Basic workflow automation.

I keep seeing the same pattern in my network. Business owners wait until they absolutely have to learn these tools. By then, competitors who started experimenting early have already figured out what works for their industry.

From what I’ve experienced, the learning curve isn’t as steep as people assume. You just need to start somewhere. Pick one repetitive process you handle weekly. Doesn’t need to generate revenue immediately. Doesn’t need to be perfectly optimized.

Here’s what actually worked for me. I started with my content creation process. Built an agent that takes my rough notes from client calls and structures them into case study drafts. Nothing groundbreaking, but it saves me about two hours per week.

Then I built another one for competitor research. Feeds it a company name and gets back a formatted analysis of their pricing, positioning, and recent updates. Again, not rocket science, but it handles the tedious research phase I used to dread.

The breakthrough moment was realizing these agents don’t need to be sophisticated. They just need to handle the boring parts consistently. My revenue forecasting agent simply takes monthly data and runs it through scenarios I’ve used for years. But now it happens in minutes instead of hours.

What surprised me most was how quickly I started thinking in terms of agent workflows. Instead of doing tasks myself, I began asking: “Could an agent handle this routine part while I focus on the strategic decisions?”

The security angle matters though. I’m not feeding these agents sensitive client data or financial details I wouldn’t want logged somewhere. But for content creation, research, and data formatting? The risk-reward ratio makes sense.

My approach has been to start small and specific. Don’t try to build an agent that handles everything. Build one that does a single task really well. Then expand from there.

For example, my SEO agent only handles keyword research and content outline creation. Doesn’t write full articles or make publishing decisions. Just handles the groundwork so I can focus on the strategic content choices.

The short version is this: start experimenting now while the stakes are low. Think of one process you do every week that follows the same basic steps. Try building an agent for just that piece. See what happens.

What actually works is hands-on experimentation. Not reading case studies or waiting for industry best practices to emerge. Just building something basic and iterating based on what you learn.

The tools are accessible now. The use cases are becoming clearer. The main barrier is just getting started with something simple and seeing where it leads.

Ten years building companies and I still force myself through business books. Most are garbage anyway. Same recycled advice wrapped in different stories.

Then I picked up The Machine by Stijn Bronzwaer. It’s about how Booking.com started. Finally found a book I couldn’t put down. (first book I read in Dutch since ages too)

Here’s the thing. Reading about a business that mirrors your own changes everything. Suddenly the struggles make sense. The growth hacks feel familiar. The mistakes hit different when you’ve made them too.

Booking’s origin story starts with Geert-Jan Bruinsma in his Amsterdam apartment in 1996. He was pissed off trying to book hotels over the phone. Language barriers. Busy signals. Hotels hanging up on foreigners.

So he built Bookings.nl (later Booking.nl). The premium domain Booking.com was owned by someone else and would cost serious money to acquire.

The real breakthrough came from their obsession with SEO. While competitors were still figuring out Google, Booking went all-in on massive landing page generation. They’d create dedicated pages for every city, every type of accommodation, every search combination they could think of.

Deep internal linking. Scaled content architecture. They understood early that Google rewarded sites that could answer every possible travel query.

Similar playbook to what we run in the EOR space. Dedicated pages for different countries make sense because employment law is genuinely different everywhere. The content has to be tailored anyway.

But here’s what the book actually reveals about their obsession with testing. They didn’t just test button colors. They tested everything. The shade of blue on their logo. Whether to show prices in ascending or descending order. Whether hotel photos should be landscape or portrait.

Koen Riedijk, their head of user experience, would run hundreds of A/B tests simultaneously. Most changes moved conversion rates by tiny fractions. But those fractions added up to millions in revenue.

The book describes countless experiments with button colors, text copy, page layouts. Some moved the needle significantly. Others barely registered. But they kept testing because at their scale, even 0.1% improvements were worth millions.

They also had zero shame about copying competitors. The book describes how they’d monitor competitor sites daily. New feature launches? Copied within weeks. Better search filters? Implemented faster.

Competitive intelligence was built into their DNA. They’d analyze every successful booking site, travel agency, even airline websites for ideas worth stealing.

The growth was brutal. Constant pressure to expand into new markets before competitors could establish themselves. They’d hire country managers and figure out regulations as they went.

Booking nearly died in 2000. The dot-com crash hit right as they were gaining traction. Funding dried up. Staff got slashed from 150 to 25 people. Survival mode kicked in hard.

They survived by being scrappier than competitors. While Expedia held strategy meetings about European expansion, Booking was already live in multiple countries. While others hired consultants, Booking hired locals and figured it out.

The regulatory battles were constant. Germany tried to ban their business model entirely. France required them to register as a travel agency. Italy demanded they pay tourist taxes for customers.

They fought these battles market by market. Sometimes they won in court. Sometimes they just paid the fines and kept operating. The book shows how they’d rather ask forgiveness than permission.

The Priceline acquisition in 2005 was wild too. Priceline was struggling in the US. Their stock was under $7. But they saw Booking’s European growth and bought them for $133 million.

Within five years, Booking was generating more revenue than Priceline’s entire US operation. The subsidiary became bigger than the parent company.

Reading about their expansion into Asia felt like déjà vu. Cultural misunderstandings everywhere. They assumed European hotel booking behavior would translate globally. It didn’t.

In Japan, hotels wanted fax confirmations for every booking. In China, customers expected to pay cash on arrival. In India, dealing with massive overbooking was standard practice because hotels assumed many reservations wouldn’t show.

Their technology kept breaking in unexpected ways. Systems that handled Amsterdam’s internet infrastructure couldn’t cope with Bangkok’s spotty connections. Mobile sites that worked perfectly in London were unusable on older phones common in Southeast Asia.

But they kept adapting. Built separate mobile sites for different connection speeds. Created country-specific payment methods. Hired local staff who actually understood the markets.

The best part of the book? Brutal honesty about their mistakes. Like when they tried to expand into flights to compete with Expedia. Burned through millions. Never gained traction. Eventually shut it down.

Or their restaurant booking venture. Seemed logical. Hotels and restaurants both take reservations. But the business models were completely different. Another expensive lesson.

The book admits most of their early success was timing. The internet was becoming mainstream exactly when people wanted alternatives to travel agents. Mobile adoption happened right as they were scaling globally.

Most business books pretend success was inevitable. That every decision was genius. This one shows the chaos. The near misses. The stupid mistakes that somehow worked out.

Like how they discovered their review system almost by accident. Hotels kept complaining about bad reviews, so Booking started verifying that reviewers actually stayed at the property. Turns out verified reviews converted way better than anonymous ones.

Or how their “free cancellation” policy started as a desperate attempt to differentiate from Expedia. Hotels hated it. Booking’s finance team hated it. But customers loved it, and it became their biggest competitive advantage.

The book also reveals how they built their company culture around data and testing. New employees had to understand statistics. Marketing campaigns needed testing plans before approval. Even office decisions got measured for impact.

That obsession with measurement extended everywhere. They tracked customer service response times by individual agent. They measured how long people spent on each page. They tested email signatures, page load speeds, checkout flows.

Reading about a business that mirrors your own changes everything. Their struggles with international expansion. Regulatory uncertainty. Scaling customer service across time zones. Competition from better-funded rivals.

Every challenge felt familiar. Every breakthrough made me think about our own growth strategies.

That’s why I actually enjoyed reading for once. It wasn’t some consultant’s framework divorced from reality. It was real people figuring it out as they went. Making mistakes. Learning from them. Building something massive through iteration rather than inspiration.

The chaos wasn’t sanitized into clean lessons. The victories weren’t inevitable. The failures weren’t glossed over with wisdom.

It was just honest about how messy building something actually is. How many experiments fail. How much depends on timing and luck and being willing to try stupid things that might work.

Funny how finding the right story changes everything. Maybe I don’t hate reading. Maybe I just hate boring books written by people who’ve never actually built anything.

Here’s the link to the book on Amazon: https://www.amazon.com/Machine-How-Booking-com-Took-World-ebook/dp/B0BW8YY5QG - not affiliated, just actually worth reading.

It’s 7am in Nusa Dua. My fiancé is still sleeping. I’m downstairs at the hotel restaurant with my laptop, building new comparison features for my platforms.

Guy at the next table starts talking. “You shouldn’t work on weekends. You need to relax.”

I told him I don’t feel relaxed when I’m not working. He said that didn’t make sense.

Here’s the thing. Relaxation isn’t universal.

For him, relaxation means zero work. Phone off. Mind empty. That works for him.

For me, relaxation means working on stuff I choose. No meetings. No calls. Just me and code at 7am with terrible hotel coffee.

The real question is why we think everyone should relax the same way.

Most people think weekends mean complete separation from work. That if you’re typing on a laptop, you’re stressed. That productivity and peace can’t coexist.

I’ve tested this. Forced weekends off. Felt anxious the entire time. Kept thinking about features I wanted to build. Problems I wanted to solve.

So I stopped forcing it.

Now I work Saturday mornings because I want to. Not because I have to. Big difference.

I’m not checking emails or taking calls. I’m building stuff that matters to me. In a place I chose. At a time I chose.

That’s my version of relaxation.

The guy finished his breakfast and left. Probably thinks I’m some stressed workaholic who can’t disconnect.

Maybe I am. Or maybe I just know what actually works for me.

Point is, there’s no right way to spend your Saturday morning. Some people need complete disconnection. Others need creative flow.

Both are fine.

Just don’t assume your version of relaxation is the only valid one.

I posted about EOR pricing complexity last week. Within minutes, I had five comments about “great insights” and “thanks for sharing” and “this really resonates.” All from real people with real jobs who apparently couldn’t spare ten seconds to form an actual thought.

The AI comment problem isn’t just obvious bot accounts. It’s professionals using AI to generate responses because engaging authentically takes too much time. The result is a platform where everyone sounds like they’re reading from the same customer service script.

X has the opposite problem but somehow ends up in the same place. Instead of bland corporate speak, you get AI-generated hot takes designed to maximize engagement. Every thread about remote work gets flooded with generic contrarian responses that hit all the algorithmic triggers but contribute nothing.

I spent years building my network on these platforms. Now I scroll through comments sections that feel like talking to a chatbot that’s really committed to the bit.

The worst part is how it’s changing real human behavior. People are starting to write like the AI comments because that’s what gets engagement. We’re all copying the robots that are copying us.

I keep seeing the same phrases everywhere. “This is spot on.” “Couldn’t agree more.” “Great perspective.” These used to be genuine reactions. Now they’re the default response when you want to engage but don’t want to think. It’s hard to actually figure out when someone is genuine or not.

The platforms know this is happening. They have to. But AI engagement still counts as engagement for their metrics. A meaningless comment drives the algorithm just as well as a thoughtful one.

What’s funny is how bad most AI comments still are. They’re getting better at sounding human, but they’re terrible at actually understanding context. I’ve seen AI responses confidently agreeing with posts they clearly didn’t comprehend.

The signal-to-noise ratio was already rough on professional networks. Now we’re drowning in generated content that looks like engagement but feels like screaming into the void.

I’m not sure there’s a way back from this. Once everyone realizes they can automate their professional presence, why wouldn’t they? Authentic engagement was already competing with busy schedules and notification fatigue. Now it’s competing with robots that never sleep.

Maybe this is just what networking looks like now. Algorithmic small talk and AI-generated agreement. But it feels like we’re losing something important in the translation.

I’ve looked at maybe 50 pricing pages building comparison platforms over the years. The pattern is always the same. Big number up top, asterisk, fine print about select countries only.

The Philippines costs $199. Germany costs $800. Guess which one they advertise.

Look, I get why they do this. Put $800 on your homepage and people bounce before you can explain why German payroll compliance costs more than a Netflix subscription. Put $199 and you get them on a sales call where you can walk through the actual complexity.

But it’s still annoying as hell when you’re trying to help companies budget for global hiring. Every conversation starts with sticker shock because someone saw that starting price and assumed it applied to their expensive European markets.

P.S. I recorded a quick video on the costs of EOR services if you might be interested:

The sales teams always have the same script too. “Well, Germany has more complex labor laws, so there’s additional compliance work, plus statutory benefits are higher, and the payroll processing requires specialized knowledge.” All true. Also completely predictable if you’ve done this before.

What kills me is that the actual pricing isn’t even that shocking once you understand what you’re buying. $800 a month to handle German employment law, payroll, benefits, and compliance isn’t insane. It’s just not $199.

I spent years thinking there had to be cheaper options because the advertised prices looked so reasonable.

Some providers have started being more upfront about regional pricing. Not many, but a few. It’s refreshing when you see actual numbers instead of marketing theater.

The funny thing is that the bait-and-switch probably works. People book calls, sales teams explain the value, deals get closed. But it makes the whole industry feel less trustworthy than it needs to be.

Most companies shopping for EOR services aren’t idiots. They know hiring someone in Germany costs more than hiring someone in the Philippines. They just want to know what it actually costs without playing twenty questions with a sales rep.

The pricing opacity made sense when EOR was a niche service and every deal was custom. Now that it’s becoming commoditized, the “call for pricing” approach feels outdated.

I keep waiting for someone to just publish real pricing for major markets upfront. Would probably convert better than the current approach, but what do I know. I’m just the guy comparing all these providers while everyone else is optimizing their lead gen funnels.

I hate WordPress.

Okay, that’s not entirely fair. WordPress is great for blogs. It’s great for simple websites. It’s great for a lot of things.

But it’s terrible when you’re trying to maintain information about 180+ countries and 50+ EOR providers that changes every single week.

You know what’s fun? Manually updating pricing tables across 30 different pages because RemoFirst changed their fees in Brazil. You know what’s even more fun? Realizing you missed updating 5 of those pages and now you’re giving people outdated information that could cost them thousands of dollars.

So this weekend, I did what any sane person would do: I threw it all away and built something new.

The problem was simple

People come to Employ Borderless to make decisions about global hiring. They need to know: Which EOR provider should I use? What does it cost to hire someone in Vietnam? What are the compliance requirements in Germany?

And that information changes constantly. Providers update pricing. Countries change labor laws. New players enter the market.

With WordPress, every update was manual work. Copy. Paste. Format. Repeat 47 times. Hope you didn’t miss anything. Hope you didn’t break something.

I wasn’t giving people the best information. I was giving them the most recently updated information I had time to manually change.

That’s not good enough.

What I built instead

A completely custom solution that treats country data and provider data like what it actually is: structured information that needs to be updated systematically, not 50 different blog posts.

Now I can:

• Update provider pricing once and have it flow everywhere it needs to

• Build automations that flag when information is outdated

• Add comparison tools that actually help people make decisions

• Ship new features without wrestling with page builders and plugins

The whole point is this: I don’t want people to browse information about global hiring. I want them to make a decision and move on with their lives.

What’s next

I’m building a bunch of stuff I couldn’t do before:

• Real-time provider comparisons based on your specific use case

• Automated updates when providers change their pricing or features

• Better filtering so you see only what’s relevant to your situation

• A dark mode because apparently that’s what the kids want

But honestly, the best part is this: I can now make sure that when a CEO is trying to figure out how to hire their first remote employee, they get the right information, not just the information I had time to manually update last week.

That’s what this whole thing is about. Making decisions easier. Getting people the answers they need. Solving the problem and getting out of the way.

WordPress couldn’t do that. So I built something that can.

Now back to building.

So working with companies on their global hiring through Employ Borderless, I kept running into the same situation.

A company would reach out asking about EOR providers. We’d start talking, and then they’d mention they already have an entity in the country they’re hiring in.

They don’t need an EOR. They just need payroll.

But here’s the thing. Figuring out which global payroll provider to use is just as confusing as choosing an EOR. Maybe more confusing, because the information is even more scattered.

So we built Payroll Overview.

What Payroll Overview is

It’s an independent research site for global payroll services. Same approach as EOR Overview. Unbiased reviews, comparisons, and guides. No provider pays for rankings. We just help you find what actually fits.

You can check it out at payrolloverview.com.

What I’m working on right now

Honestly, we’re still in the early stages of building out the data.

Global payroll is complicated. Every country has different rules, different tax structures, different compliance requirements. And most of the information online is either outdated, incomplete, or written by providers trying to sell you something.

So I’m doing the boring work. Talking directly with payroll providers to get accurate pricing and coverage data. Digging through government sources to understand the actual regulations in each country. Researching average salaries, tax brackets, and employer contributions by region. Documenting what actually matters when you’re choosing a provider.

It’s a big operation. There are a lot of countries, and the details matter.

But I think it’s worth doing properly. If we can get all the right information into one platform, we can actually help companies make informed decisions. Not just “here are 10 payroll providers, good luck.” But real insights on which provider makes sense for your specific situation.

Scaling in APAC? Different answer than scaling in LATAM. Need integrations with your existing HRIS? That narrows it down. Budget constraints? We can show you the trade-offs.

That’s the goal.

The fun part

What’s kind of funny is that I made the intro video for Payroll Overview with just a few prompts using Remotion and Claude Code. Like, a few prompts and I had a really nice video ready to go.

It’s wild what you can do now. We’re living in this AI era where you can just build stuff. Have an idea in the morning, ship something by the afternoon. I’m having a lot of fun with it honestly. Building cool companies has never been more accessible.

Why I’m sharing this now

I’ve been documenting my building journey publicly, so it felt right to share this.

Payroll Overview is live, but it’s early. The database will grow. The tools will improve. If you’re running global payroll or thinking about it, I’d love to hear what information would actually be useful to you.

And if you know of good government sources for payroll regulations in specific countries, send them my way. Always looking for better data.

More updates as we build.

Robbin

You found the perfect candidate. They’re skilled, motivated, and ready to start.

One problem. They live in another country.

Now what?

If you’re like most founders, you start googling. EOR. PEO. Entity setup. Contractor agreements. Permanent establishment risk. Tax implications.

Three hours later you have 47 browser tabs open and a headache.

Let me save you some time.

You probably need an EOR

EOR stands for Employer of Record. It’s a company that legally employs your international hire on your behalf. They handle payroll, taxes, benefits, and compliance. You handle the actual work.

Think of it like this: on paper, the EOR is the employer. In practice, your new hire works for you, reports to you, and feels like part of your team.

Why not just hire them as a contractor?

You can. Many companies do. But there’s risk.

If someone works full time for you, uses your tools, follows your schedule, and only works for your company, most countries consider that an employee. Not a contractor.

Misclassifying an employee as a contractor can lead to fines, back taxes, and legal trouble. The rules vary by country but the pattern is the same. If it looks like employment, it probably is.

An EOR removes that risk entirely.

What about setting up your own entity?

You could open a legal entity in the country where your hire lives. Register with local authorities. Set up payroll. Handle compliance yourself.

This makes sense if you’re hiring a whole team in one location. It doesn’t make sense for one or two people. The cost and admin overhead will eat you alive.

Rule of thumb: under five employees in one country, use an EOR. Five or more, start thinking about your own entity.

How to pick an EOR?

This is where most people overcomplicate things.

They spend weeks comparing features. Reading reviews. Building spreadsheets. Talking to sales reps who all say the same things.

For your first international hire, only three things matter:

Does the provider cover the country you need? Not all EORs operate everywhere. Some have direct entities, some use partners. Check the specific country, not just the total count.

Is the pricing clear and within budget? EOR pricing ranges from around $199 to $699 per employee per month. Some charge setup fees. Some have hidden costs. Get the full number before you commit.

Can they onboard in your timeline? Some EORs take a week. Some take a month. If your candidate is waiting, speed matters.

That’s it. The fancy dashboards, the AI features, the integrations with tools you don’t use yet. That stuff matters when you have 50 international employees. Not when you have one.

The actual process

Once you pick an EOR, the process looks something like this:

You sign an agreement with the EOR. They send an employment contract to your new hire. Your hire signs and submits their documents. The EOR registers them with local authorities. Payroll gets set up. Your hire starts working.

Most of this happens in the background. Your main job is providing the job details, salary, and start date. The EOR handles the rest.

Timeline varies. Some countries are fast. Some have bureaucratic delays. Ask your EOR for a realistic estimate for the specific country.

What it costs

EOR pricing is usually per employee per month. The range is wide.

Budget options start around $199 per month. Mid-range providers charge $400 to $500. Premium providers with owned entities everywhere go up to $699 or more.

There’s often a correlation between price and coverage. Cheaper providers may use partner networks. More expensive ones may have their own legal entities. Both can work fine. It depends on your priorities.

Some providers also charge for contractors, usually $25 to $50 per month. Some charge setup fees. Some have minimum commitments. Read the fine print.

If you want to compare pricing across providers, I built a database at EOR Overview with exact numbers and country coverage.

Common mistakes

Overthinking the first hire. You don’t need the perfect provider. You need one that works for this specific country and this specific role. You can always switch later.

Ignoring the candidate experience. Your new hire is signing a contract with a company they’ve never heard of. Make sure the EOR communicates clearly and professionally. A clunky onboarding reflects on you.

Forgetting about offboarding. Ending employment in some countries is complicated. Notice periods, severance rules, and termination procedures vary wildly. Ask about this before you need it.

Not budgeting for the real cost. The EOR fee is just one part. You also pay the employee’s salary, benefits, taxes, and sometimes additional local contributions. Get a full cost breakdown.

Start simple

Your first international hire doesn’t need to be complicated.

Find a candidate. Pick an EOR that covers their country. Sign up. Let them handle the paperwork.

You can optimize later. You can switch providers if something doesn’t work. You can build spreadsheets and comparison matrices when you have ten international employees.

For now, just get started!

The best companies I’ve seen treat their first international hire as an experiment. They learn the process, figure out what matters to them, and build from there.

You don’t need to get it perfect. You just need to get it done.

If you’re stuck choosing a provider, I help companies figure this out at Employ Borderless. Happy to point you in the right direction.

Every time I needed to hire someone abroad, I’d spend weeks researching.

Which EOR should I use? Is Deel worth $599/month? What about Remote? Oyster? There are dozens of these companies now. And every website I found was either outdated, a sales pitch, or both.

I’d Google (yes back then we still used Google instead of ChatGPT) “best EOR” and get listicles that were clearly paid placements. I’d ask in founder communities and get ten different answers. I’d talk to sales reps who obviously just wanted to close me.

It was exhausting.

I’ve been in international hiring for over a decade. I started Internship Abroad years ago, helping people find placements overseas. I’ve worked as a freelancer across borders. I’ve dealt with the compliance headaches, the payroll confusion, the “we don’t support that country” emails.

I know this space. And I still couldn’t find straight answers.

So in 2024, my co-founder Paul and I started Employ Borderless.

The idea was simple: build what we wished existed. An independent advisory platform that actually helps companies find the right EOR, PEO, or payroll provider. No paid rankings. No sponsored “top 10” lists. Just honest recommendations based on what the company actually needs.

We also run EOR Overview, where we publish reviews, comparisons, and guides. Same principle: useful information without the sales pitch.

We’re based in Singapore. Small team. No outside funding. Just building something we think should exist.

If you’re trying to figure out how to hire internationally, I’ll be writing about what I’ve learned. The stuff that actually matters, not the marketing fluff.

Thanks for reading.

Robbin