"Onshore, nearshore or offshore?" arrives at board level as one question, but it is really three: what this location puts at risk, what it costs once everything is on the table, and who inside the business is accountable if it goes wrong. Answer only the first, usually by way of the cheapest quoted rate, and the other two surface later, on a worse timeline than any business case predicted.
Oliver has watched that shortcut get taken across 25 years running and advising contact centre operations, and it produces close to the same result each time: a rate that looks disciplined in the business case, and a location that turns out wrong in practice. That mismatch is usually discovered only once reversing it is expensive.
What follows skips the standard description of what onshore, nearshore and offshore mean. It sets out a working way to choose between them: the trade-offs that decide it, the cost lines a headline rate leaves out, where the decision most often goes wrong, the questions worth asking before you sign, and what a leadership team should do with all of this in the next quarter.
Onshore, nearshore, offshore: a trade-off, not a tier list
Onshore, nearshore and offshore are not quality tiers, and treating them as one is the first mistake in most business cases. Each is a different trade-off between cost, time zone alignment and cultural fit; none of them is inherently the right or wrong answer for a given operation.
Onshore keeps work inside your own market: the closest cultural and regulatory alignment, and the highest cost band of the three. Nearshore moves into neighbouring regions and closer time zones. It gives up a little of that alignment for materially better economics. Offshore reaches into deeper talent pools further afield, with the strongest economics of the three. That advantage is real on the invoice and in practice, but only once the process, training and management around it are built properly.
None of that is a ranking. It resolves only once you weigh a specific process against the seven factors below. Whichever option arrived first in a sales pitch has no bearing on that. The locations page sets out the honest strengths and limits of each region site by site, rather than a single verdict for onshore, nearshore or offshore as a whole.
The seven factors that decide it
Seven factors do most of the real work in this decision, and most conversations stall after the first two. Whatever preference had already formed by then gets treated as settled, and the rest never get a fair hearing. Working through all seven in order is what keeps a location decision defensible if a customer, a board or an auditor ever asks why it was made.
Time zones and hours of coverage
If the work is real time (voice, live chat, anything a customer expects answered now), time zone coverage becomes a hard constraint on the shortlist. A retention team covering evening calls in one market from a location eight hours ahead is running its best people through the small hours of their own night, and quality drifts as a direct result. Asynchronous work (back-office processing, email queues, case administration) tolerates a wider gap far better, which is exactly why the channel matters as much as the geography.
Language and cultural alignment
Fluent English is not the same as fluent customer. An agent can be grammatically flawless and still miss the sarcasm in a frustrated complaint, the regional idiom in a policy question, or the tone a specific market expects on a service call. Cultural alignment matters most in high-emotion, high-nuance interactions (complaints, sales objections, sensitive account issues) and matters far less in scripted, transactional exchanges. That is a genuine reason the same operation can justify more than one location at once.
How complex the work is
Simple, scripted, closely supervised work (password resets, order status, appointment booking) travels well almost anywhere. Work that needs judgement (technical diagnosis, complex billing disputes, anything where the agent has to hold context and reason through an answer rather than follow a script) needs a different calibre of hire and a tighter management model, wherever it sits. Complexity should drive the location decision. It is worth testing that per process rather than assuming one answer covers the whole operation.
Scale, now and in twelve months
Ten agents and two hundred agents are different decisions, even for the same process. A location with a shallow talent pool can handle a small pilot well and then strain badly at the hiring pace growth demands: recruitment slows, the bar comes down to fill roles, and the team that looked strong at launch looks thin a year in. Scale belongs inside the decision from day one. Ask any shortlisted location directly how quickly it can double a team without quality falling.
Budget, honestly costed
The quoted hourly rate is the start of the number, not the end of it. Training, technology, telecom, recruitment and the management layer that keeps quality on track all sit on top of it, and they vary by location as much as the headline rate does. A lower rate that comes with a thinner management structure or higher attrition can cost more within six months than a higher rate that holds. The next section sets out what belongs in that comparison.
Data protection and compliance
What the work involves (payment details, health information, regulated financial data) narrows the realistic list of locations before cost or language ever enter the conversation. This is worth settling early with whoever owns compliance in your organisation, rather than discovering a location is unworkable after a shortlist and a business case have already been built around it.
Whether anyone can get there
Relationships in this work are still built in person: sitting on the floor, meeting the management team, listening to calls live rather than reading a summary of them. A short, direct flight supports that kind of visit-as-routine relationship, and a leader who visits twice a year catches drift a monthly report never will. A location that needs two connections and a visa application gets visited rarely, and a partnership that is rarely visited is harder to keep honest.
What the headline rate leaves out
A rate comparison is the easiest exercise in the whole process, which is exactly why so many location decisions stop there. It is also the least complete number in the business case, because the hourly or per-seat rate is one line in a P&L that has several others sitting underneath it, largely invisible until the first full quarter of invoices arrives.
The categories worth putting on the same page as the headline rate, location by location, before any comparison is treated as final:
- Training investment, how much time and cost it takes to get a new hire productive on your specific process, which varies with a location's baseline skill level and English proficiency.
- Technology and integration, what it costs to connect a new location into your CRM, telephony and reporting stack, and whether the location's infrastructure already supports it or needs building.
- Telecom and connectivity, carrier costs, redundancy and resilience, which vary meaningfully by region and matter more for voice-heavy work than back-office processing.
- Recruitment and ramp, the ongoing cost of hiring against a location's attrition rate, beyond the one-off cost of staffing the launch team.
- Management and oversight, the layer of supervision, quality calibration and coaching that keeps performance on the brief, whether that sits with the partner, with you, or split between the two.
None of these are optional extras. They are the real cost of the location, and a proposal that does not itemise them separately is asking you to trust that they are already priced in fairly. That is a reasonable thing to ask a provider to demonstrate rather than assume.
Where the decision goes wrong
It is rarely the region itself that causes a bad location decision. The process behind it is usually the real cause, and the same handful of patterns show up in almost every one Oliver has been asked to unpick after the fact.
Choosing on hourly rate alone
Rate is the easiest number to compare, so it is where most shortlists start, and where too many of them end. A rate comparison alone says nothing about the management layer behind it, the training investment, or the attrition rate that will quietly erode quality within a few months. The saving on paper and the saving in year one are frequently different numbers, and the gap is rarely in the buyer's favour.
Assuming every centre does everything
Not every partner in every location can do everything well. A centre that runs a strong high-volume customer service operation may never have built a specialist technical support desk, and a site strong in collections may have no track record in complex retention conversations. Capability gets matched to the specific work during selection, drawing on a global network of 43 contact centre partners across the Caribbean, North America, the United Kingdom, South Africa and international markets. The match is based on what a specific site has built and delivered, ahead of its general reputation.
Letting procurement run the process alone
A request for proposal, an RFP, built entirely around price and contractual protection, with no input from anyone who has run a floor, tends to attract responses that answer exactly that brief. It says nothing about whether the work will get done well. Whoever ends up owning the relationship day to day should have a seat in scoring the shortlist. Being briefed on the outcome after the decision is made is too late to shape it.
Underestimating the management overhead
An outsourced team, wherever it sits, is not something you sign and then leave alone. Quality calibration, regular performance reviews, coaching and a genuine channel for the partner to escalate problems all still need to happen, typically with a heavier hand than they would with a team down the corridor. Leadership teams that treat go-live as the finish line are usually the ones surprised, months later, at how far performance has drifted from the brief.
Questions worth asking before you sign
Most of the disappointment that surfaces months into an outsourcing relationship could have been avoided with direct questions asked before signing, well before the first quarterly review goes badly. None of the following are hostile. A provider worth working with will have straightforward answers, usually because they have been asked before.
- How quickly can the team scale up, and what happens to quality while it does?
- What sits outside the headline rate: technology, reporting, management time, telecom?
- What is the attrition rate on comparable accounts, and how is a leaver replaced without a service dip?
- Who manages quality day to day, and how often do they escalate to us versus resolve it themselves?
- What access do we get to listen to calls, review work or visit the floor directly, and how often?
- If a process needs to move to a different location later, what does that transition involve?
Vague or evasive answers to two or three of these predict how the relationship will go better than anything in the pitch deck. It is worth putting a version of the same questions to your own organisation before the shortlist is built: who owns this relationship once it is live, what does good look like in the first few months, and who has the authority to say a location is not working and act on it. A provider can answer every question well and the engagement can still fail if nobody inside the business owns the answers to those three.
Running it as a blended decision
The location decision does not sit on its own. It belongs inside a proper solution design, built once discovery has established the volumes, hours, languages, complexity and budget the operation needs. The how it works page sets out that full route from a first conversation through to a live team. Location is one decision made inside that process, settled after discovery has already shaped the rest of the design.
Many operations end up blending models rather than picking one location for everything they run. Sensitive escalations and complex retention work get kept close, in a nearshore or onshore location; high-volume transactional work moves offshore, where the economics do the most good. There is no rule that says one business needs one location, and forcing every process onto the same site because it is administratively simpler is its own quiet source of underperformance.
None of this assumes outsourcing is the right move for every process either. Some work holds up better kept in-house regardless of which location would otherwise suit it, and that is a separate question worth answering honestly before this one. Where it is the right move, someone senior enough to reallocate budget or pause a launch needs to own the decision and the relationship afterwards, rather than leaving it to a committee or whoever happened to run the tender.
What to do this quarter
If a location decision is live somewhere in the business right now, a short set of actions this quarter does more good than another round of vendor pitches.
- Write down, per process, whether it is real time or asynchronous and how much judgement it genuinely requires. That alone rules out several locations before cost is even discussed.
- Build an honest total cost model for every location under consideration, using the categories above, before comparing a single hourly rate.
- Name the person who will own the relationship after go-live, and give them a seat in the decision now, while it can still be shaped.
- Put the data protection and compliance question to whoever owns it in your organisation before a shortlist goes any further.
- If nobody is confident which of the seven factors matters most for your operation, treat that as useful information rather than a gap to hide. It is a reasonable point to bring in independent input, through contact centre consulting, instead of guessing now and correcting later.
None of this needs to happen in one meeting, and it rarely does. What it needs is a clear order, with one person accountable for it from the first conversation through to the team going live. That accountability is worth raising as a direct conversation before any shortlist is finalised.
Frequently asked questions
Is offshore always the cheapest option?
Offshore usually wins on headline rate. Total cost is a different question: training, technology, telecom and management overhead all sit on top of the rate and vary by location, so a full comparison needs to include them before offshore can fairly be called cheaper.
Can we run one process onshore and another offshore?
Yes, and many operations do exactly that. There is no requirement to standardise the whole operation on one location class. The decision can, and often should, be made process by process.
How much does time zone difference matter?
It depends almost entirely on whether the work is real time or not. A live voice or chat queue needs genuine coverage of the hours your customers contact you; back-office and email work can sit further out of time zone without the same strain.
About the author
Oliver Catt is the founder of The Cattalyst. He has spent 25 years inside contact centres, customer service, sales and training operations, and now helps organisations develop their leaders and build outsourced teams through a global partner network.
Start a conversation with Oliver
