Most nearshore hiring decisions get made on a spreadsheet with one column in it: cost. Pick the country with the lowest number, open the req, and find out four months later that the rep writes flawless follow-up email and cannot hold a discovery call with a CRO who talks fast.
The cost delta is real — we typically see 30–40% against a comparable US hire. It is also the least useful thing to choose a country on, because it lands in roughly the same range everywhere in Latin America. Two variables actually separate a nearshore revenue team that works from one that quietly stalls, and almost nobody benchmarks either one.
Cost is the reason to look at nearshore. It is almost never the reason a nearshore hire works or doesn’t.
Start with the US number your comp gets measured against
Before you can judge a nearshore band, you need the domestic one it is being compared to — by you, by the candidate, and by every competing offer they are holding.
The Bridge Group’s research, drawn from 351 B2B companies, puts the median US SDR at $80K OTE — $55K base and $25K variable, a 68:32 split. The striking part is that the figure has been unchanged since 2022. Four years of flat US sales development comp is the backdrop to every nearshore business case written since.
The same research puts median ramp at 3.0 months, the lowest since 2010, against median tenure of 1.9 years. That arithmetic does not improve when you move the seat south. Roughly a seventh of every SDR hire is spent getting to productive regardless of geography, and nearshore does nothing to compress it. If your model assumes cheaper also means faster, rebuild the model.
One more number worth holding: 60% of reps hit quota in that dataset — the lowest on record. A nearshore team does not fix a quota problem. It changes what the same problem costs you.
And the arbitrage is narrowing. Deel’s 2026 Global Hiring Report, built on more than one million worker contracts across 37,000+ companies in 150+ countries, records Latin American roles among the fastest-repricing anywhere — financial analysts in the region saw compensation climb 195%. Lock your band now and revisit it annually. Do not build a three-year plan on today’s spread.
English proficiency is the variable nobody benchmarks
Every nearshore vendor on earth says its candidates have “excellent English.” Nobody publishes the base rate they are drawing from. The EF English Proficiency Index does — it scores national adult populations using the EF SET, and the 2025 edition draws on more than 2.2 million test takers who sat the test in 2024.
| Country | EF EPI 2025 score | Global rank | Band |
|---|---|---|---|
| Argentina | 575 | #26 | High |
| Uruguay | 542 | #34 | Moderate |
| Chile | 517 | #54 | Moderate |
| Costa Rica | 516 | #55 | Moderate |
| Brazil | 482 | #75 | Low |
| Colombia | 480 | #76 | Low |
| Mexico | 440 | #103 | Very Low |
The global average is 488. Bands run Very High (600+), High (550–599), Moderate (500–549), Low (450–499) and Very Low (below 450) — the scale is published in EF’s methodology, and Argentina’s country page shows it took the region’s top spot at 575, up 13 points year over year.
Read the table honestly, in both directions.
The gap between the top and the bottom of that list is 135 points and 77 global places. Mexico — the country most US companies default to on proximity alone — has the weakest measured English in the region and sits in the Very Low band. Argentina, the strongest, would rank ahead of several Western European markets.
Now the caveat, because it matters: EF EPI measures a self-selected slice of the adult population, not the technology sector. A SaaS AE in Mexico City is not the Mexican national average, any more than a US engineer is the US average. What the index actually tells you is the base rate your search is filtering against. In Argentina you are picking from a deep pool. In Mexico you are looking for a much thinner top slice — the hire is entirely possible, but the sourcing work, and the number of people you screen per offer, is not the same job.
So set the bar as a demonstration, never as a self-rating. Nobody has ever put “conversational” on their own résumé. Run a live, unscripted call — an objection-handling role-play or a mock discovery — and listen for how the candidate performs under interruption, not how they perform reading.
Time zones and English pull in opposite directions
This is the part that surprises people, and it is the reason the country decision is genuinely a decision rather than a lookup.
| Hub | UTC offset | vs US Eastern (EDT) | vs US Pacific (PDT) |
|---|---|---|---|
| Buenos Aires | −3 | +1 | +4 |
| Montevideo | −3 | +1 | +4 |
| São Paulo | −3 | +1 | +4 |
| Santiago | −4 (−3 Sep–Apr) | 0 to +1 | +3 to +4 |
| Bogotá | −5 | −1 | +2 |
| Lima | −5 | −1 | +2 |
| Mexico City | −6 | −2 | +1 |
| San José | −6 | −2 | +1 |
For an East Coast team, the Southern Cone is close to perfect. A Buenos Aires rep starts an hour ahead of New York and overlaps the entire working day — and Argentina also happens to top the English table. That combination is why it is the strongest default for East Coast GTM hiring.
Flip the headquarters to San Francisco and the same choice inverts. Four hours ahead means your Argentina rep signs off around 2pm Pacific, which removes them from exactly the afternoon call block a West Coast SDR team lives in. The countries that fit a Pacific schedule — Mexico and Costa Rica at UTC−6, one hour ahead of Pacific — are the same ones sitting lowest on the English index.
There is no country that wins both columns for a West Coast company. What you do instead is choose which constraint you are willing to solve with process:
- Solve the time zone. Hire in Argentina or Uruguay, take the English depth, and shift the role’s day earlier — a 7am-to-4pm local schedule buys back most of the Pacific afternoon.
- Solve the English. Hire in Mexico or Costa Rica, keep the clean overlap, and accept that your screen-to-offer ratio will be materially higher. Budget the extra sourcing rather than lowering the bar.
Pick one deliberately. Teams that pick neither end up hiring whoever answered first.
Which GTM roles travel well — and which don’t
Nearshore is a fit question by role, not a blanket policy.
Travel well. Anything structured, remote-native and measurable on output. SDR and BDR seats are the clearest case — the work is process-driven and the scoreboard is unambiguous. Revenue and marketing operations travels well for the same reason, as does GTM engineering, where the work product is systems and the review is asynchronous. SMB and mid-market customer success generally works. So does most technical and data work.
Travel poorly. Enterprise AEs, where a meaningful share of what you are buying is a US network, in-person executive access and the ability to be in a room in Chicago on Thursday. First sales leaders, for the same reason plus the culture-setting problem. Field marketing, obviously. Any role whose value comes from relationships that were built in a specific US market — those do not relocate, and no amount of cost saving replaces them.
The honest test: if the role’s output can be reviewed without being in the room, it travels. If the role’s value is being in the room, it doesn’t.
Decide the employment model before you source, not after
Three structures, and the choice is yours to make before the first conversation:
- Contractor agreement. Fastest, cheapest, and still the most common structure across the region. The costs are real, though — misclassification exposure, no clean equity path, and weaker retention, because a contractor who gets a full-employment offer elsewhere usually takes it.
- Employer of record. The EOR employs the person locally and handles payroll, benefits and compliance for a per-head monthly fee on top of salary. It is the right default for roles you intend to keep for years, and it removes the classification question entirely.
- Your own entity. Only worth the overhead once you have a real cluster in one country — the setup, accounting and ongoing compliance cost does not amortize across three people.
The reason to decide early is not legal, it’s competitive. Strong candidates ask about the structure on the first call, because they have been burned by a contractor arrangement that ended abruptly. “We haven’t worked that out yet” is an answer that loses you the exact people you opened the search for.
Running the search
Sourcing is rarely the bottleneck. Nearshore searches stall on decisions that should have been made before the req opened, so make them first.
- Set the band against the US number, not the local one. You are competing with every other US company hiring in that market, and they are all working from the same $80K OTE reference point.
- Define the English bar as a task. A live objection-handling role-play, scored the same way for every candidate. Not a self-rating, not a written assessment.
- Choose the constraint you are solving — time zone or English depth — and let that pick the country, rather than picking the country and discovering the constraint later.
- Lock the employment model so your recruiter can answer it in the first screen.
- Move fast. Median tenure is 1.9 years and ramp is 3.0 months; every week of process is taken directly out of the productive window you are paying for.
That is also how we run it. We source outbound into the region against a defined English bar and a decided structure, and we come back with a pre-interviewed shortlist in days, not weeks — because the candidates worth hiring in Buenos Aires and Bogotá are fielding the same three US offers everyone else is.
