What a first offshore hire really costs

Every company that considers hiring offshore builds the same spreadsheet. Local salary in one column, offshore rate in the other, difference at the bottom, and the difference looks enormous. Then they hire, and somewhere around month three the saving turns out to be smaller than the spreadsheet promised. Sometimes it turns out to be negative.

The spreadsheet was not wrong about the rate. It was missing about six other lines.

The lines nobody puts in the model

Here is the full cost structure of a remote hire, in the order the costs actually arrive:

1. Sourcing and vetting

Either you pay an agency, or you pay with your own time. A serious technical vetting process for one role is several hours of a senior person's attention across screening, a task and two conversations. If you skip it, you have not removed the cost, you have deferred it into the rework line below at a much worse exchange rate.

2. Contracting, payroll and compliance

Paying someone in another country is not a wire transfer. There is a contract that has to hold up in both jurisdictions, a payment rail that does not lose eight percent to intermediaries, and a compliance position on whether this person is a contractor or, in the eyes of their local law, an employee. Getting this wrong is not expensive until it is very expensive.

3. Onboarding, which is the big one

A local hire absorbs an enormous amount by proximity. They hear how people talk to customers, notice what gets escalated, and pick up standards by watching. A remote hire absorbs none of that unless someone deliberately constructs it. Budget real senior time here, concentrated in the first three weeks. This is the single line most companies leave out entirely, and it is the one that determines whether the hire works. The specific ways it goes wrong are the subject of how to build an offshore team without the quality drop.

4. Ongoing management overhead

Assume a few hours a week of a manager's time, more at the start. If your answer is that the hire will be self-directing from day one, you are describing a very senior person, and you should price them accordingly. Most of that overhead is ambiguity being resolved one round trip at a time, which is a writing problem before it is a management one: see job specs that survive a timezone gap.

5. Rework

The cost of output that has to be redone. This scales inversely with what you spent on lines one and three. A team that vets carefully and onboards properly runs a low rework rate. A team that hired the cheapest available option and sent them a Jira board runs a rework rate that can exceed the entire nominal saving.

6. Continuity risk

One person in one country with no backup is a single point of failure. When they are ill, the work stops. When they leave, the knowledge leaves with them. You either carry that risk or you pay to remove it, usually by hiring two rather than one.

How to actually compare

Put both options through the same model. Not offshore rate against local salary, but fully loaded cost per unit of accepted output against the same thing locally. Accepted output means work that shipped without a rewrite.

Do that honestly and two things happen. The offshore saving gets smaller than the naive spreadsheet claimed. And it remains substantial, because the local column has its own hidden lines that nobody counts either: recruiter fees, office cost per head, benefits loading, the same onboarding time, and the same management overhead.

The saving is real. It is just never the number in the first spreadsheet, and pretending otherwise is how companies talk themselves into a bad version of a good decision.

Where the money actually comes from

It is worth being precise about this, because the honest answer is more defensible than the marketing one.

The saving is not because the work is worth less. It is because salary tracks local cost of living and local labour market competition, not the value of the output. An engineer in Beirut and an engineer in Toronto solving the same problem produce the same value to the business. They are priced differently because rent, food and the number of employers competing for them differ by a factor of several.

That gap is a real arbitrage, and it is available to any company willing to build the operational muscle to use it. What it is not is a discount on quality. If you go in expecting to pay a third and get a third of the standard, you will arrange exactly that outcome.

The version I would actually recommend

If you are doing this for the first time, do not start with the most critical role you have, and do not start with one person. Start with a function where the output is clearly definable, hire two people rather than one, budget real senior time for the first month, and measure on accepted output rather than hours.

Get that working, then extend it. The companies that succeed at this almost never succeeded on their first single hire. They succeeded on their second attempt, after they stopped treating it as a procurement decision and started treating it as a hiring decision that happens to cross a border.