Nearshore vs. offshore vs. outsourcing: only one of these is a business model

Buyers use "nearshore," "offshore," and "outsourcing" interchangeably. Most vendors let them, because the confusion sells.

Here's what the confusion costs: a CTO prices nearshore, signs outsourcing, and eight months later tells the next vendor "we tried nearshore once." The geography never got a fair trial. The model failed, and the map took the blame.

So this post does the unglamorous thing and defines the terms. Two of these words describe where a team sits. One describes how a vendor treats it. Keeping those axes separate is the difference between buying the thing you evaluated and buying the thing the fine print actually describes.

Nearshore describes where

Nearshore means the team works from a country whose clock matches yours. Not "overlaps by two hours if someone stays late." Matches.

For a US company, that means Latin America. Costa Rica runs on Central Standard Time year-round. Colombia runs on Eastern Standard Time year-round. No daylight-saving drift, no split-shift heroics. Your 10am standup is their 10am standup, in January and in July.

That's what nearshore actually means, and it's all it means. The word says nothing about whether the team is senior or junior, dedicated or pooled, in your Slack or hidden behind an account manager. A nearshore team can be excellent or terrible. The word only tells you they're awake when you are.

At SMASH, nearshore means Costa Rica and Colombia. That's where our customer experience and business support teams sit, exclusively, and where most of our engineering sits too. Engineering adds a third country, Pakistan, and we're deliberate about what that word does: Pakistan is not nearshore to the US, and we never market it as if it were. It's the second-hemisphere extension of our engineering delivery, the part of the team that's building while Costa Rica and Colombia sleep. Different word, different job. A vendor who blurs that line for you will blur others.

Offshore also describes where. Just farther.

Offshore is the opposite time-zone bet: the team works while you sleep. For a US buyer, that's South Asia, Eastern Europe, Southeast Asia.

A 10-to-12-hour gap isn't a detail. It's an operating system. Every question waits overnight. Every ambiguity becomes a written spec, because the person who could answer it in thirty seconds is asleep. Work turns into a relay race: package the context, pass the baton, hope nothing drops between hemispheres. Teams that do this well build real handoff discipline, with documentation habits most co-located teams never develop.

Here's the honest part most nearshore staffing content skips: offshore is not a slur. It's a constraint. Well-specified, low-ambiguity work can genuinely fit it, and a second hemisphere can extend the build day rather than fragment it (that's the job our Pakistan engineers do by design, not by accident). What doesn't fit is embedded product work, where the day is made of thirty-second questions. Pay the overnight tax on each of them and the sprint quietly stretches.

The failure mode isn't the engineers. Offshore hubs are full of excellent ones. The failure mode is pretending the constraint isn't there: buying a team twelve hours away and running it like it sits down the hall.

Outsourcing describes how

Now the word that doesn't belong in the same list. Outsourcing is not a geography. It's a commercial model, and you can identify it from the invoice without ever asking where anyone sits:

• You buy capacity, not people. Seats, agents, ticket volume, blocks of hours drawn from a shared pool.
• Billing follows units of output. Per ticket, per call, per hour. The vendor's margin improves when your work gets less of their people's attention.
• The vendor owns the relationship. You talk to an account manager. The people doing the work rotate underneath, and their names never reach your org chart.
• Detachment is the design, not a defect. Rotation keeps the vendor's utilization high. Continuity is your problem to absorb.

Notice that nothing in that list mentions a country. You can buy outsourcing from a building across the street; a shared-pool agency in your own city is still outsourcing. And you can run the exact opposite model from another country: a dedicated, named, embedded team is not outsourcing, no matter which flag flies outside the office.

The conflation is the trap

Where and how are independent axes. That gives you four combinations, and naming them explains most of the horror stories in this category:

1. Offshore geography, outsourcing model. The classic ticket farm. Twelve-hour gap, rotating strangers, per-unit billing. This combination built the category's reputation, and it's what most buyers picture when they hear any of the three words.
2. Offshore geography, embedded model. Real, and sometimes right. A dedicated team that's deliberately async, doing well-specified work while you sleep. It costs documentation discipline and buys a longer build day.
3. Nearshore geography, outsourcing model. The trap quadrant. Time zone right, model wrong. The standup happens live, but the faces rotate. You paid nearshore rates for outsourcing mechanics. This is where "we tried nearshore once" stories actually come from.
4. Nearshore geography, embedded model. Your clock and your culture. Named people in your Slack, your sprint planning, your review cycle. The word for this isn't outsourcing at all. It's a team.

Where SMASH sits, in checkable terms

Quadrant four: nearshore geography without the outsourcing model. Not outsourcing. An extension of your team. Since that's the same sentence every competitor uses, here's what it means on paper:

• Named people, not pools. If Diego is your backend lead, Diego is your backend lead next year. Outsourcing bills capacity; we bill specific humans, and the invoice line items show it.
• We're the employer of record. Payroll, local labor compliance, equipment, performance reviews, a real career path. You get the person; we carry the employer stack.
• Engagements start small and grow because they work. The typical arc is one senior engineer on a high-value problem first. Most clients who start with one role reach eight people within 12 months.
• Monthly contracts, documented exit. No lock-in clauses calibrated to trap you. The model has to hold up on its own.

The cost difference is real (roughly 40-60% lower fully-loaded than an equivalent US senior, a number we've published before), but it's the byproduct, not the product. Leaders who choose this model for the discount alone tend to recreate the outsourcing mechanics that burned them. The ones who stay for years choose it for continuity: same people, same product, same clock. Different location. Same team.

Three questions that expose the model

Vocabulary is cheap, so don't audit the vendor's words. Audit the mechanics. Three questions, in any order:

1. Who employs this person? Payroll, benefits, equipment, reviews. If the answer starts with "well, technically," you're in a marketplace, not a team.
2. What exactly is on the invoice? Named humans, or units of capacity? This one question separates embedded from outsourced faster than any pitch deck.
3. If I ask for the same person in twelve months, what does the contract say? Silence here means rotation is the plan.

We keep our own answers public on the FAQ page, because a vendor who makes you extract this information on a sales call has already told you something.

If you're evaluating nearshore and want to be sure you're not accidentally pricing outsourcing, book a 30-minute call. We'll map the four quadrants against your actual roadmap, and if a different model fits your work better, we'll say so.