When engineering leaders compare contractor engagement models, three terms get used loosely: onshore, nearshore, and offshore. Each one names a different geographic relationship between the developer and the buyer — but the imprecise way they're used in marketing copy obscures the dimensions that actually move the decision. This guide names what each term means in concrete terms, when each model fits, and why the engagement structure matters as much as the geography.
The three terms, defined
The cleanest way to define these terms is by time-zone overlap with the US business day, not by raw geography. The geographic shorthand is useful, but the functional question — "how many of our working hours overlap with the developer's working hours?" — is what shapes the day-to-day experience.
- Onshore. Developer is in the same country as the buyer. For a US engineering team, that means a US-based contractor. Highest cost, full time-zone overlap, simplest legal and tax pathway (1099, no cross-border complications).
- Nearshore. Developer is in a nearby country with substantial time-zone overlap. For a US buyer, that typically means Latin America — Mexico, Argentina, Brazil, Colombia, Costa Rica, Chile, Uruguay, and others. Moderate cost relative to US rates, 4–8 hours of overlap with the US business day, established cross-border contractor pathways.
- Offshore. Developer is in a distant time zone with limited overlap. For a US buyer, that usually means South or Southeast Asia (India, Philippines, Vietnam) or Eastern Europe (Poland, Ukraine, Romania, depending on the engagement). Lowest cost, 0–4 hours of overlap (mostly the early US morning or late US evening), more complex legal and compliance shape.
The terms are imprecise in practice. Some firms market Eastern European placements as "nearshore" to a US buyer, which stretches the geographic framing — the time-zone overlap is closer to offshore. Use the overlap-hours definition when you need to be precise.
The decision matrix
Four dimensions matter when comparing the three models. Costs in this table are expressed as a percentage of a US senior contractor's rate to keep the comparison portable across roles.
| Dimension | Onshore | Nearshore (LATAM) | Offshore |
|---|---|---|---|
| Cost (vs US senior) | 100% | 40–60% | 20–40% |
| US time-zone overlap | Full (8 hours) | 4–8 hours | 0–3 hours |
| Communication friction | Lowest | Low | Moderate to high |
| Legal / compliance | Domestic 1099 | Established cross-border | Complex (PE risk, treaty rates) |
| Project-management overhead | Lowest | Low | Higher (async handoff cycles) |
| Billing currency complexity | US dollars only | US dollars (well-routed by good platforms) | Often multi-currency |
These numbers are directional, not precise. Actual per-developer rates vary by role, stack, and seniority — the relative ratios are what's useful when sizing the trade-off, not the specific percentages.
When each model fits
When onshore fits
Onshore is the right answer in a small set of specific cases:
- Regulated workloads. HIPAA, FedRAMP, certain government contracts, and some financial-services regulations require US-only data residency or US-citizen access. If your compliance regime gates on this, onshore is the only option that clears the bar.
- Very short engagements. Under two to four weeks, the ramp time dominates the cost calculus. A nearshore or offshore developer might need a week to absorb your codebase before they're productive; a US contractor on a two-week sprint can sometimes start faster because the contracting friction is lower.
- Roles requiring physical co-location. Increasingly rare in software engineering, but exists for some embedded-systems or hardware-adjacent work where the developer needs to be in the office to interact with physical equipment.
- Procurement-driven preferences. Some buyers have political or vendor-list constraints that make US-based the only acceptable answer. That's a constraint, not a recommendation — but if it's your constraint, onshore is the answer.
For the typical US engineering scaling scenario — adding senior contractors to a software team running standard cloud infrastructure — the onshore cost premium is hard to justify when nearshore can deliver comparable seniority at 40–60% of the rate.
When nearshore fits
Nearshore is the default answer for most US engineering teams scaling with senior contractors:
- Multi-month engagements where time-zone overlap is felt every working day. If your team runs live standups, synchronous code review, or pair-programming sessions, a 4–8 hour overlap window is the difference between "we collaborate in real time" and "we ping each other across a 16-hour async gap."
- Senior contractor placements where your money goes further than offshore (the cost-per-quality ratio is favorable in LATAM) and you still get full overlap with the US business day.
- US-dollar billing simplicity. A good nearshore engagement bills you in US dollars and handles the cross-border payment to the developer's local currency on its side. You don't reconcile multi-currency invoices; you don't track exchange rates.
- Established cross-border contractor pathways. LATAM contractor engagement is a well-trodden path. The legal structure (Independent Contractor Agreement signed by the platform, 1099-equivalent local tax handling) is mature, not experimental.
The trade-off: you give up the absolute lowest cost (offshore wins on raw dollars) and you give up domestic-only data residency (regulated workloads can't use this path).
When offshore fits
Offshore is the right answer in a narrower set of cases than the volume of offshore-marketing-copy would suggest:
- Project-based work that can be handed off with a clean specification. If your team can write a precise spec, pass it off, and review the deliverable async two or three days later, an offshore developer can deliver against it. The model breaks down when the spec evolves during the build or when real-time clarification matters.
- Cost-driven engagements where the time-zone gap is acceptable because the work doesn't need real-time collaboration. Internal tools, backend batch jobs, ETL pipelines, and similar work often fits.
- Niche specialty depth concentrated in offshore markets. Certain mobile-game development, specific game-engine work, and some ML domains have deeper benches offshore than nearshore today.
- 24-hour development cycles. Global product teams running follow-the-sun handoffs — US team commits at end of day, offshore team picks up overnight, US team reviews next morning — can legitimately benefit from the time gap. This requires real org maturity to run well.
The pattern that doesn't fit offshore well: an engineering team that wants a senior contractor to integrate into the existing standup rhythm and act as a member of the team. The overlap math defeats it.
A decision tree (for skimmers)
If you want to short-circuit the full read:
Is the work regulated (HIPAA / FedRAMP / etc.)?
├─ Yes → Onshore only
└─ No → continue
Does your engineering rhythm depend on live collaboration —
standups, synchronous code review, pair programming?
├─ Yes → Nearshore (the overlap window is the point)
└─ No, we can run fully async with clean specs → continue
Is cost the dominant factor and you have the org maturity
to manage async handoff cycles?
├─ Yes → Offshore
└─ No → Nearshore is still your default
The engagement model matters as much as the geography
The "nearshore vs offshore vs onshore" framing captures one dimension of the decision — where the developer is. It misses an equally important dimension: how the developer is engaged.
Two engagements with developers in the same country can differ wildly:
- Traditional staff augmentation. Agency retains 40–50% margin between client bill rate and developer pay. Agency pays the developer on its own internal cycle (the agency floats). You reconcile timesheets weekly, in some cases manage retainer-vs-hours used math, and sign annual commitments.
- Direct contractor engagement. Published per-developer rate written into the contract at signing. One monthly invoice in your billing currency. Funding-gated payouts where the developer is paid only after your invoice settles. Month-to-month with a notice period — no annual commitment.
These are the same developer, the same geography, the same skill level — completely different operational shape on the buyer's side. The engagement-model decision is at least as load-bearing as the geography decision, and most marketing copy in the space conflates the two.
The contractor engagement model walks through what an "engagement" means at sourceBOLD specifically — MSA + SOW + Independent Contractor Agreement, no W-2, no benefits, no PM bundled in.
How sourceBOLD positions in this matrix
sourceBOLD is nearshore + contractor-engagement by design. We source senior developers across Latin America — Americas-only, no offshore — and structure the engagement as a month-to-month contractor relationship with a published rate, a single US-dollar monthly invoice, and a funding-gated payout state machine.
That's a deliberate scope choice. We don't try to be everything to every buyer:
- No onshore offering — if you need US-based developers, sourceBOLD isn't the right fit.
- No offshore offering — if your cost target is below 40% of a US senior rate, sourceBOLD's $-band won't reach it.
- No staff-augmentation framing — we don't bundle a PM, don't run dedicated-team engagements, and don't carry the ~50% traditional staff-aug margin.
Where we do fit: a US engineering team scaling with senior contractors who need to integrate into the daily standup rhythm, who care about developer take-home and billing predictability, and who want the contract terms visible before the discovery call.
For the engagement mechanics — the 4-gate vetting funnel, the funding-gate state transition, the recruiter-installment math — see The 4-gate vetting funnel, The funding gate, and The contractor engagement model. For pricing detail, What it costs carries the literal $-band that gets written into the MSA at signing.