An operations lead ticking items on a printed checklist on a clipboard in a sunlit office, team softly out of focus

/Free tool · 10 minutes

Nearshore readiness checklist.

This nearshore readiness checklist tells you whether your company is ready to hand work to a team in Mexico or Latin America, before you spend weeks on vendor calls. Answer 21 questions, get a weighted score and a short list of the gaps to close first. It runs in your browser, and nothing you enter is sent to us.

The work

The work is written down well enough that a new hire could start without a call.

Process docs, ticket examples, a Loom walkthrough. If it lives in one person’s head, answer no. Weight 3/3

You know whether the work is repeatable (bought per ticket or output) or judgment-heavy (needs a dedicated team).

Tier-one support and bookkeeping are repeatable. Product engineering and brand design aren’t. Weight 2/3

The work will run for at least six months.

Short engagements rarely earn back the ramp-up time a new team needs. Weight 2/3

You’ve picked a first slice small enough to pilot in 30 to 60 days.

One queue, one product area or one channel, not the whole function. Weight 1/3

Ownership

One named person on your side owns the relationship, with time set aside for it every week.

Plan for several hours a week in the first two months. “The team will manage it” means no. Weight 3/3

Someone on your side can judge the quality of the output, not just whether it arrived on time.

A senior engineer reviewing code, a support lead listening to calls. Weight 2/3

Decision rights are clear: what the team can decide alone and what needs your sign-off.

Refund limits, merge rights, publishing approval. Weight 2/3

You’ve planned how the team will get context: product demos, customer calls, past decisions.

Teams that never meet your customers make worse calls on their behalf. Weight 1/3

Time zone and communication

You know how many hours of overlap you need each day, and for which roles.

Live support needs full coverage of your hours. A design team might need two. Weight 2/3

Your team already works asynchronously: written tickets, recorded decisions, shared docs.

If decisions happen in hallway chats, a remote team will always be a step behind. Weight 2/3

You know the English level each role needs, internal only or customer-facing.

Customer-facing roles need more than a team lead who speaks well on sales calls. Weight 1/3

Process and documentation

Runbooks, style guides or coding standards exist for the work you’re handing over.

They can be rough. They can’t be missing. Weight 2/3

Each deliverable has a definition of done and someone who accepts it.

Without one, “done” means whatever the last person to touch it thought. Weight 2/3

The work is tracked in a system the new team can use, not in email inboxes.

A help desk, a repo with issues, a CRM, a project board. Weight 2/3

Data, security and compliance

You know which systems and data the team will touch, and you can grant access per role.

Shared admin passwords mean no. Single sign-on with roles means yes. Weight 3/3

You’ve checked the data rules you’re bound by, such as HIPAA, PCI DSS or your own customers’ security terms.

Your enterprise customers’ contracts often restrict where their data can be handled. Weight 2/3

You’ll confirm the vendor employs its staff directly and is registered in Mexico’s REPSE registry.

Since the 2021 subcontracting reform, using an unregistered provider can make you share liability. Weight 2/3

Budget and success

You’ve defined two or three measurable outcomes for the first 90 days.

Resolution time, tickets closed, features shipped, cost per lead. Not “it feels better”. Weight 3/3

Your budget covers the full cost: the vendor’s rate plus your management time, tools and travel.

Buyers who budget only the rate tend to cut the management time first. Weight 2/3

You know what the work costs today, per unit of output, so you can compare.

Cost per ticket, per invoice processed, per sprint. Weight 1/3

You know the exit terms you want: notice period, knowledge transfer, and who owns the IP and documentation.

Agree them before you start, while both sides are optimistic. Weight 2/3

Saved in this browser only. Nothing is sent to us.

Why readiness matters more than vendor choice

Most failed outsourcing engagements we’ve been asked to rescue didn’t fail because the vendor was weak. They failed because the buyer handed over work nobody had written down, with nobody on their side who had time to manage it.

A strong vendor can’t fix that. They’ll ask good questions, but if the answers live in one person’s head, the team ramps slowly, quality drifts and the engagement gets blamed. The checklist puts those buyer-side gaps in front of you while they’re still cheap to fix.

How the score works

Each question carries a weight from 1 to 3. A 3 is a gap that, in our experience, sinks engagements on its own: no named owner, no written scope, no plan for data access. A 1 is worth fixing but rarely fatal.

Yes scores the full weight, partly scores half and no scores zero. Your result is the share of available points you earned, so you can stop halfway and still see a meaningful number. The gap list ranks your no and partly answers by weight, so the first item is the one most likely to hurt you.

The weights are our judgment from delivery work, not an industry benchmark. If a question doesn’t apply to you, answer yes and move on.

What to do with each result

Ready to pilot (80% and above): pick the smallest slice of real work that would prove the model, and run it for 30 to 60 days with two or three agreed measures. Our buyer’s guide covers what to ask vendors at this stage.

Ready with gaps (55% to 79%): you can start vendor conversations, but close the top gaps first or write them into the pilot plan. A good vendor will help with documentation and onboarding. They can’t give you an internal owner.

Not ready yet (under 55%): spend two to four weeks on the gap list before you talk to anyone. Writing down the work and naming an owner usually moves the score more than anything else.

The compliance question buyers skip

Mexico’s 2021 labor reform restricted subcontracting of personnel. Providers of specialized services must now be registered in the REPSE registry run by the Ministry of Labor (STPS), and companies that use unregistered providers can share liability for their workers.

That’s why the checklist asks whether you’ll confirm how your vendor employs its staff. Ask for the REPSE registration and check it yourself. It takes five minutes and it’s the cheapest due diligence you’ll do.

Source: STPS: REPSE registry

Three things to settle before day one

The checklist scores the conditions for success. A few decisions sit just outside it, and they shape the first month. Settle them before the team starts.

Onboarding: decide who runs the first two weeks, and have accounts, access and a recorded walkthrough ready on day one. People who spend their first week waiting for logins start the engagement behind.

Working style: agree how feedback is given, how often you meet and when someone from your side will visit in person. A team that only hears from you when something goes wrong learns to stay quiet.

Growth: decide what would make you add people or a second team, and who signs that off. Without it, scaling happens by accident after a busy month, and quality slips.

Frequently asked questions

What is a nearshore readiness checklist?

It’s a self-assessment you run before hiring a nearshore team. It checks the things on your side that decide whether the engagement works: written scope, a named owner, time zone overlap, documentation, data access, compliance and a budget that covers your own management time.

Is my data sent anywhere?

No. The checklist runs in your browser and saves answers in your browser’s local storage so you can come back to them. Nothing is sent to OTRO. Clearing your browser data or pressing start over removes it.

What score do I need before hiring a nearshore team?

We suggest 80% or above before a full engagement, and 55% or above before a small pilot. Those thresholds are our judgment, not a standard. More important than the number is that no weight-3 question is answered no.

Does this apply to offshore teams too?

Mostly, yes. Scope, ownership, documentation, security and budget questions apply to any external team. The time zone questions matter more offshore, because overlap with the US is usually a few hours at most, so async habits carry more of the load.

Is a readiness check the same as vetting a nearshore vendor?

No. Readiness is about your side: scope, ownership, access and budget. Vetting is about theirs: how they hire and test people, how they employ them, who owns the work product and what their clients say. Do the readiness check first, because no vendor can supply a missing internal owner. Then take the vetting questions to your shortlist.

What drives the cost of a nearshore team?

The role, seniority, language level and hours of coverage you need. As a rule, onshore costs more than nearshore, and nearshore costs more than offshore. For most buyers the bigger swing is on their own side: management time, onboarding and the weeks before the team reaches full output. That’s why the checklist asks for a budget that covers more than the vendor’s rate.

How long does it take?

About ten minutes. If a question takes longer than a minute to answer, that’s usually a sign the honest answer is partly.

Can I share the results with my team?

Yes. Copy the results as text, or print the page and save it as a PDF. Both include your score, your answer to every question and the ranked gap list.

Want a second opinion on your gaps?

Send us your score and the top three gaps. We’ll tell you honestly whether you’re ready, even if the answer is not yet.

Talk to us