Nearshore Software Partner in Mexico: What to Check First

A good nearshore partner in Mexico works your hours, talks to your team without a go-between, and ships software you can maintain after the engagement ends. A poor fit costs you months. Most of what separates the two can be checked before you sign, usually in one or two calls. Here's what we'd look at if we were in your seat.

Time zones: simpler than they used to be

Mexico dropped daylight saving time in 2022. Under its time zone law, published October 28, 2022, most of the country, including Mexico City, Guadalajara, Monterrey and Morelia, is in the Central zone at UTC−6 all year. Only some municipalities along the northern border still change their clocks.

Here's how central Mexico lines up with you, as long as US clocks keep changing:

• US Central (Chicago, Dallas): the same time in winter; one hour behind you during daylight time.
• US Eastern and Toronto: one hour behind you in winter, two during daylight time.
• US Pacific: two hours ahead of you in winter, one during daylight time.
• Vancouver: British Columbia moved to permanent Pacific time at UTC−7, and clocks there don't fall back on November 1, 2026. Central Mexico now stays one hour ahead of Vancouver all year.

Either way, you share a full workday. Ask your partner to put in writing the hours they'll be reachable in your time zone, and which holidays they observe; Mexico's calendar isn't the same as yours.

We work between Morelia and Vancouver ourselves, which is part of why we pay attention to this.

Language: test it on the first call

Ask to meet the people who'll actually be in your standups, not only the person selling. Spoken English matters, but written English matters just as much: tickets, pull request descriptions, documentation, and the email that explains why a deadline moved. Ask for a sample of each from a past project, with client details removed.

Our founder, Memo Sánchez, spent more than 15 years in Vancouver on English-speaking teams at companies like Hitachi (Wenco), Unity Technologies, Sage and Central 1 Credit Union before founding Izalith. Most of our working habits come from there.

How progress gets reported

Status slides are easy to dress up; working software isn't. Look for:

• Demos on a fixed cadence of something you can click, every week or two.
• Access to the real work: the repository, the issue tracker and preview links, not a weekly summary of them.
• A written log of decisions: what was done, what was decided and why. We keep one per project; it's what lets anyone pick up the work weeks later.
• One named person you call when something breaks, and a clear idea of how fast they'll answer.

IP and contracts

Settle ownership on paper and in practice.

• On paper: an explicit assignment of intellectual property to your company. Mexico's federal copyright law gives the economic rights in a commissioned work to the party that commissioned it unless agreed otherwise, but it also says the contract terms must be clear and precise, and that doubts are resolved in the author's favor (articles 83 and 83 bis). Don't rely on defaults across two legal systems: spell it out, and let your lawyer choose the governing law.
• In practice: the code lives in a repository under your organization from day one. Cloud accounts, domains, app store listings and any WhatsApp Business account are in your company's name. If the relationship ends, nothing should need to be "transferred."
• Also ask: Do they subcontract? Which open-source licenses are in the code? How is confidential data handled?

Invoicing and payments

Ask early, because your accounts payable team will be the first to notice.

• A Mexican company bills with a CFDI, Mexico's electronic invoice, which is validated by an authorized certification provider and reported to the tax authority (SAT). You receive it as XML and PDF files.
• Some partners bill from a US or Canadian entity instead. Either can work. What matters is knowing which entity signs the contract, which one invoices, in what currency, and who pays the wire fees.
• Ask your accounting team which documents they need from a foreign vendor before the first payment, and send that list during contracting, not after the first invoice.

We can quote in MXN or USD.

Testing and what "done" means

"We test everything" means nothing until you see it. Ask:

• Which automated tests run before every deploy, and can I see a recent run?
• What does "done" include: code, tests, documentation, deploy steps, credentials handed over?
• Who checks the work on real devices and screen sizes?

For reference, our own website has 40 end-to-end tests, including checks at five screen widths, with JavaScript turned off and with reduced motion, and a new version only ships when they pass. Client projects carry their own test suites; you'll find examples in our portfolio.

Start with something small

Before a six-month commitment, run a paid pilot with a real deliverable: an internal tool, one integration, or an audit of an existing system. If you're not sure what to pick, what to automate first and custom ERP or spreadsheet can help you choose. A few weeks is enough to learn what you need to know:

• Did they ask good questions before writing code?
• Did they raise risks early, or did you find out at the demo?
• Is the code in your repository, and could another team pick it up?
• Did the written updates match what you saw?

If the pilot goes well, scale up. If it doesn't, you've lost little and learned what to ask the next partner.

We've built for the Canadian market from Mexico before: ClaimNorth, a platform for locating unclaimed property in Canada, and the bilingual site for πNORTH, a Canadian digital engineering consultancy.

If you're weighing your options

If you're comparing partners in Mexico, we're glad to have a straight conversation about your project, including whether we're the right fit. See how we work on Consulting, read about forward-deployed engineering, or get in touch.