Nearshore is almost always sold on price. Someone shows you a table comparing hourly rates, your rate sits in the middle, and the pitch is that you get most of the quality for less money.
That is the weakest reason to do it, and it is the reason most likely to go wrong. If rate is what you are optimizing, there is always somewhere cheaper, and you will find out why it was cheaper six months in.
Here is the argument we would actually make, and it has almost nothing to do with the rate.
Someone can stand on your floor
This is the whole thing, and it applies to industrial software more than to anything else.
A warehouse management system specification is wrong until somebody has watched a picker work a full shift. Not read a process document. Watched. You learn that the printer is on the wrong side of the aisle, that the third rack from the end is never scanned because the barcode is at knee height, and that the night shift has a workaround nobody wrote down.
A manufacturing execution system is wrong until somebody has seen which machine actually stops, and asked the operator why.
An inventory system is wrong until somebody has seen where scrap really goes, which is almost never where the process says.
None of that arrives in a requirements document. It arrives by being there. And whether being there is possible depends entirely on distance. From Ciudad Juarez, a visit to a plant in El Paso costs an afternoon and a bridge crossing. From twelve time zones away, it costs a trip that has to be justified, scheduled and budgeted, which means it happens once at the start, if at all.
So the requirements get written from a call. And the software gets built to match the document instead of the floor.
The working day is the same one
Ciudad Juarez runs on Mountain Time, the same clock as El Paso. When Mexico ended daylight saving in 2022, the border municipalities kept it aligned with the United States, so the hour does not drift twice a year either.
That sounds like a small thing until you count exchanges. With a vendor ten or twelve hours away, a question asked in the morning gets answered overnight, and the follow-up question goes back the next night. One round trip per day. A decision that needs four exchanges takes four days.
Same time zone means that decision takes twenty minutes. Over a project of a few months, the difference is not a few days. It is the difference between a team that is working on your problem and a team that is working on last night’s version of your problem.
Both languages, because your operation has both
On a maquiladora site, the plant floor speaks Spanish and the corporate office often speaks English. The reports go north, the terminals stay south.
A vendor who works in only one of those makes the other side’s users second class. Either the operator gets an interface in a language they half read, or the corporate reviewer gets a system they cannot audit without a translator.
We write in both because we work in both, every day. That is not a service line, it is where we live.
The border is in the data, not just on the map
If your material crosses, your software has to understand that.
A company operating under an IMMEX program has to be able to say where each temporarily imported unit is, or what it became. That is not a report; it is a way of modeling inventory, in layers that carry their customs origin, instead of balances that only carry quantities.
A vendor who has never heard the word pedimento will model it as balances, because that is what every other business needs. The gap shows up two years later, when someone asks for the detail and the only way to produce it is a spreadsheet maintained by hand.
We have implemented inventory control under that obligation. It is the clearest example of something you learn by working here and cannot learn from a specification.
The practical things
They are less interesting but they decide deals:
- A buyer in El Paso can drive to the office and be back for lunch. No visa, no flight.
- Contracts, invoicing and payment work across the border every day in this region. It is the most routine thing here.
- Overlap is not “a few hours of overlap”. It is the entire working day.
What nearshore does not fix
This is the part the rate tables leave out, and it matters more than any of the above.
Proximity does nothing if the vendor never visits. Fifteen minutes away and never on site is the same as twelve time zones away. Ask for the visit before you sign, and notice whether it was offered or you had to request it.
It does not fix an undefined scope. If nobody on your side has decided what a good part is, or who approves a quote, no vendor at any distance will fix that for you. We have written about that for shop floor systems and it holds for everything else.
It does not make a weak team strong. Nearshore is a geography, not a skill level. The questions that tell you about skill are the same anywhere.
It is not automatically cheap. If someone’s main argument is the rate, ask what they are leaving out. Usually it is the senior engineer.
Four questions worth asking any vendor near you
- Will you walk my floor before quoting? Not after. The quote that comes after a visit is a different document from the one that comes after a call.
- Who writes the code? Ask for names and ask whether those people will still be on it in month four. The common pattern is senior people in the meeting and juniors after the contract.
- What happens to the code and the cloud accounts if we part ways? Get the answer in writing before you need it. This is the question that separates a supplier from a hostage situation.
- What hours will we actually overlap? Have them write it down. If the answer involves someone staying up, it will stop happening by month three.
If you are weighing this for a project on either side of the border, we are happy to be measured against those four questions. There is a twenty-minute call for exactly that, and nothing gets quoted in it.