What is nearshore vs offshore? A glossary for US buyers

How to use this glossary for Latin American hiring

Use these definitions to turn a proposal into clear decisions. Start with where the person works, then identify who employs them and who directs their work. A nearshore label answers only the location question.

For example, you may want a developer who joins planning meetings and takes tasks from your engineering lead. That is a different purchase from asking an outside team to deliver a finished application. Both can involve nearshore software development, but the scope and management duties differ.

Read the proposal beside the statement of work. Circle terms such as "dedicated," "managed" and "all-in." Ask the provider to explain each one through daily work or a line on the invoice. If your team and the provider use different meanings, resolve that before signing.

Use the same questions when considering Opus. This site is an Opus-owned reference; recommendations are editorial.

Start with the terms closest to your decision. If you already have a candidate, read the entries on employment models and cost. If you need someone to own a project, focus on delivery scope and acceptance. If your team needs help during its workday, check overlap before reviewing a shortlist.

Give the resulting notes to the hiring manager and the person who approves the agreement. They should be able to describe the same arrangement without relying on a sales label.

Compare hiring models with Opus.

What do the terms mean for your hiring decision?

The glossary separates geography from the service you buy. Apply the definitions below when reviewing proposals, setting a budget or preparing a role for approval.

Separate location from responsibility

"Nearshore" describes proximity to the buyer. "Offshore" commonly describes a more distant location. Neither term assigns responsibility for the work. An offshore developer can report to your engineering manager, while a nearshore project team can have its own delivery lead.

Write down who sets daily priorities. For staff augmentation, that may be your engineering manager. For a managed project, ask the provider to name its delivery lead and explain which decisions still require your approval.

Then name the employer or contracting party. Do not infer that answer from the company sending the invoice. Have the agreement spell out who signs with the worker and who handles payroll questions.

A useful test is to describe an ordinary workday. Who assigns the next task? Who reviews it? Who handles an absence? If the answers remain vague, the proposal needs more detail. Repeat the test for a missed deadline so everyone understands who must respond.

Check overlap against actual calendars

Time zone overlap means both teams are working and available at the same time. Record the worker's city, normal schedule and the meetings they must attend. "US hours" needs a named US time zone and a start and finish time.

Mexico City is UTC-6 and does not observe daylight saving time. Tijuana follows seasonal clock changes. A proposal that says only "Mexico time" needs a city or time zone identifier. These schedules are recorded in the IANA North America time zone rules.

Bogotá is UTC-5 throughout the year. Buenos Aires and São Paulo are UTC-3 without seasonal clock changes. These locations do not all share the same hours with a US team. Their schedules appear in the IANA South America time zone rules.

Ask the candidate to confirm availability against your calendar in both winter and summer. Include recurring meetings and release windows. Agree on the expected response outside shared hours, too. A shared afternoon does not establish overnight support.

Decide whether you need a person or a deliverable

Staff augmentation adds people to a team you manage. If your engineering lead owns the backlog, assess the candidate and your ability to support them. Name the person who reviews code and helps the hire learn the system.

Project outsourcing places a defined piece of work with an outside company. If you are buying a finished feature or application, define acceptance before discussing the delivery date. State what must work, how your team will test it and who fixes defects.

A managed service needs its own boundary. Ask which ongoing tasks the provider owns and what falls back to your team. For a support service, for example, define which requests it handles and how it escalates problems.

Keep those models distinct during price comparisons. An hourly quote for a developer and a fixed quote for a project cover different commitments. Compare the responsibilities included in each, then decide whether the price fits what you need.

Clarify what recruiting and employment support cover

A recruiting agency finds and presents candidates. An employer of record is the legal employer in the arrangement. Those definitions answer different questions, so confirm whether a proposal includes both candidate search and ongoing employment support.

Ask who conducts interviews and who makes the final hiring decision. Then ask who signs the employment agreement, handles pay questions and administers leave. Put a named contact beside each duty so a new hire knows where to go.

"Direct hire" also needs a clear meaning in a cross-border proposal. Name the entity that will employ the person. If the proposal instead uses an independent contractor agreement, have the planned working relationship reviewed before choosing that route.

Give the reviewer the actual work plan, including supervision and expected hours. A contract label alone is too little information for that review. Resolve the arrangement before asking the candidate to sign.

Define what a dedicated team includes

"Dedicated" can describe a group assigned to your account, but the contract should explain the allocation. Ask whether each named person works exclusively on your tasks and whether that commitment covers the full working week.

Check which roles are shared across accounts. If a delivery lead or specialist supports several clients, agree on their availability and how your team requests their time. Ask what happens when two clients need them at once.

For an offshore development center, extend the questions to the operation itself. Establish who controls staffing and infrastructure. Ask where documentation lives and who holds administrator access to the systems used for your work.

Plan for changes to the team. Specify whether substitutions need approval, how the incoming person receives context and who pays for handover time. A list of names at the start does not settle those later decisions.

Compare fully loaded cost on the same basis

"Fully loaded" is intended to include costs beyond base pay. Request an itemized definition before using that figure in a budget. The worker's salary and your total invoice are different amounts.

Ask each provider to put included services beside its charges. Have it identify separate costs for equipment, employment administration or ending the arrangement. Confirm whether paid leave changes the invoice and how absences affect delivery commitments.

Use the same role and period when comparing quotes. Check whether the proposal assumes a fixed work schedule or bills for hours used. If a monthly charge can change, ask what triggers the change and how much notice you receive.

Currency belongs in the agreement as well. Specify the invoice currency, payment schedule and who bears exchange-rate changes. Ask finance to review the payment terms before approval, especially when the worker's pay and your invoice use different currencies.

Write a statement of work you can test

A statement of work should turn the sales discussion into obligations that someone can check. For a staffing arrangement, include the role, agreed allocation and management duties. For a project, describe the deliverable and the conditions for accepting it.

Avoid accepting "production-ready" as the entire test. State which workflows must function, who runs the tests and where defects are recorded. Decide who can approve the work on your side.

Add a process for scope changes. If a new requirement appears after work begins, identify who estimates the extra effort and who can approve the charge. Keep that approval separate from a casual request in a team chat.

For a service-level agreement, define the measurement clock. A promise to respond needs a start event, covered hours and a definition of response. An acknowledgment and a resolved problem are different outcomes. Specify which one the commitment covers.

Make asynchronous work usable

Asynchronous work lets people continue without waiting for everyone to be online. It still needs an agreed place for decisions and enough context for the next person to act.

For a handoff, record what changed and what remains blocked. Link the relevant task or code review, then name the person who should pick it up. If a decision is needed, state the options and the deadline.

Reserve shared hours for work that needs discussion. A design disagreement may need a call, while a routine status update can live in the task record. Decide which problems justify an urgent message outside the usual overlap.

Test the process during onboarding. Ask a new teammate to continue a small task from its written notes. Their questions will show which assumptions your existing team has left undocumented.

Define hiring milestones before promising a start date

Time to hire measures an interval between recruiting milestones. Ask where the clock starts and where it stops. A shortlist date, an accepted offer and a first working day are separate events.

Work backward from the date you need someone contributing. Reserve time for your interviews and approvals. Tell the provider who decides and which evidence that person needs.

A fast shortlist cannot resolve an unsigned agreement or an unavailable interviewer. Put interview slots on the calendar and agree on how quickly your team will give feedback.

Treat onboarding as its own task. Name the person who arranges equipment and access, and prepare suitable work for the first week. Ask the candidate to confirm their start date before tying it to a release or customer commitment.

Read replacement terms and plan the exit

A replacement guarantee is a promise governed by its terms. Ask what triggers a new search, which exclusions apply and whether charges continue while the position is vacant. Confirm whether replacement support includes the same role or permits a revised search.

Keep that promise separate from your handover plan. Decide who documents current work and transfers access when someone leaves. Maintain that record during the engagement so the team can use it without relying on the departing person.

Review the end of the commercial agreement too. Ask about notice, final charges and the return or deletion of company data. Confirm how your team receives the work it needs to continue.

Before approving a proposal, explain the arrangement in plain words: where the person works, who employs them, who manages them, and what you pay. Add the agreed schedule and exit terms. Put unresolved answers into the agreement before work starts.

Compare hiring models with Opus.

<!-- Not saved: the workspace is read-only. Page rendering was not checked. -->