Part of the guide: Nearshore Software Development: A Field Guide
A note on this archive: an earlier version of this site was lost in a migration, with no surviving backup. This piece is a good-faith recreation of our writing from this period, not a recovered original; its date reflects the period it represents. See about this archive.
For twenty years, "outsource your development" mostly meant one thing: send the work as far away and as cheaply as you could, and accept the catch that came with it — a team twelve hours out of phase, where the question you asked at 5 p.m. got answered while you slept. That was the offshore bargain. You traded daylight for a lower rate.
I think that bargain is ending, and what's replacing it is better. The next chapter of outsourced engineering isn't farther away. It's closer to home — across the Americas, inside your own working hours.
The hidden cost of the offshore bargain
The rate was always the part everyone looked at. The clock was the part that quietly cost more.
We made this case years ago: when a developer's day doesn't overlap yours, a one-sentence clarification can take a full day to resolve, and those lost days compound until the cheapest hourly rate produces a project that's late and over budget anyway. None of that is a knock on the talent — excellent engineers are everywhere on earth. It's a knock on the schedule. Distance in miles you can design around. A twelve-hour gap you cannot.
What the pandemic settled
For a long time you could argue that distributed work was a compromise. After 2020, that argument was over.
Every company became a distributed team overnight, and the ones that thrived discovered what a handful of people had been saying for years: the obstacle was never the distance. It was whether you had the discipline to work well across it — to write things down, to trust people, to measure work by what ships rather than who's visible. Once a whole industry learned that muscle, "where does this developer sit?" stopped being a yes-or-no question about your office and became an open question about the entire map. We wrote, when that shift happened, that the talent map had been redrawn. This is what comes after.
Why the Americas
If location is open and overlap is what actually matters, the answer nearly draws itself: senior developers across the Americas, working in or near your time zone.
It's the combination that's hard to beat. You get the real-time collaboration of a teammate down the hall — the same-day review, the standup that actually happens, the "got a sec?" answered in a minute instead of tomorrow — without insisting everyone live in San Francisco. The developer isn't a vendor you brief and then wait on overnight. They're in the room, virtually, while the room is still awake.
And to be plain about how the economics should work: the advantage comes from cutting the overhead of engaging talent across a border, not from squeezing the people doing the work. We pay developers well — because, as the founders of this company argued long before I arrived, paying poorly only buys you turnover, and the client foots the bill for that in the end. Same-daylight, senior, and still a better deal than the local market. That's the whole idea.
Why now
Timing is the other half of it. The last two years rewired how companies think about where their people work, and the scramble for senior engineers hasn't eased — holding onto good ones may have gotten harder still. Teams are rebuilding how they engage talent from the ground up, and "cheapest, anywhere" has stopped impressing anyone. They want people who are genuinely good and genuinely reachable.
That's the bet I said we'd make when I stepped in: not the far edge of the map for the lowest rate, but the part of it that shares your daylight. Offshore taught everyone that talent is global. Nearshore is the correction — global talent you can actually work alongside.
The Americas are where that lands. We intend to be the ones who do it best.