Arizona does not change its clocks, and Monterrey does not either. That gives Phoenix a fixed distance from me: one hour behind, in January and in July alike. The city is known for semiconductors, for aerospace and defense, for healthcare, for the back-office operations of financial services, and for construction and real estate. For each one, this page gives the usual need, the service that covers it and the published work that carries over.
One hour behind, in every season
No one has to remember when the difference changes, because it never does. Phoenix is one hour behind Monterrey all year. A standing call on Tuesday stays where it is in March and in November. Between calls the work is visible in your repository: branches, tests, and written notes on what changed and why.
Semiconductor plants and their suppliers
A chip plant and the companies that supply it live by procedure: process notes, maintenance logs, supplier qualifications, shift handovers. People there want the right paragraph quickly, and they want to trust it. No case study on this site comes from semiconductors. The nearest published work serves plants of other kinds: the platform of a lean manufacturing practice in Monterrey that works with food, metalworking and automotive plants. It has an open corpus, an assistant that answers from it and an MCP server. The matching service is RAG and data platforms.
Aerospace and defense
The question in these companies is traceability: which revision, who approved it, what a system did with it. No case study on this site comes from aerospace or from government, the customer behind most defense work. What transfers is a way of building in which nothing an agent does goes unrecorded. The guide on agent auditability spells it out.
Healthcare
Health systems, clinics and insurers want AI that reads and routes: referrals, schedules, authorizations, messages. The services are enterprise AI and AI agent development. What the site can show at that scale is from higher education, not from healthcare. It is a multi-agent system for a group with 700,000+ students that answers questions, books appointments and hands people to the right human team. The case study covers the evaluation gates that decide what ships.
Back-office work for financial services
A back office is a queue. A request comes in by email, someone reads it, looks up a record in a core system and writes an answer much like the last one. A system can draft that answer with the record attached, and a person approves it. The service is email automation with AI. No case study on this site comes from banking. What transfers is governed, logged access to company data through an MCP gateway, and tests that stop a bad release.
Construction and real estate
Contractors, suppliers and developers sell by bid and by quote, and they lose days between the request and the number. The published work that fits is about quoting: agents that do the repeated work around every quote, inside a deal-tracking system used by small and medium companies in Latin America. The service is custom AI tools when the estimate itself is the problem, and AI sales development when the problem is finding the next project.
First step and limit
Email the role or the process. I send back a written plan: the first thing to build, the access needed, the things I will not promise. The limit is that I am in Monterrey. If a badge and a desk are part of the job, hire locally.