Dallas and Fort Worth are known for telecommunications, financial services, aviation and logistics, corporate headquarters and defense manufacturing, and together they are one of the largest air hubs of the country. These are industries of large organizations, with old systems and strict rules about change. This page goes through them one by one: what each tends to need from AI, which of my services covers it, and whether any of my published work comes from it.
Corporate headquarters
A headquarters has many departments that each want an assistant, and one security team that has to approve them all. What it needs is less a model than an order of work: one governed way for agents to reach corporate data, and a test that decides whether a change is allowed to ship. Enterprise AI is the service for that scale: data platforms, internal tools, agents and evaluation, starting from the process. The published work behind it is a set of evaluation gates for a multi-agent system that serves a higher-education group with 700,000+ students, and an MCP gateway that puts many tools behind a single entry. The first comes from education and the second is open source. Neither is a corporate headquarters, and both deal with its usual problem: many people, many systems, and a release that must not break what already works.
Telecommunications and financial services
A telecommunications company answers a very large number of questions about plans, bills and faults, and every answer has to come from the current catalog, not from what the model remembers. No case study on this site comes from telecommunications. What transfers is evaluation: scripted conversations with written expectations that run before each release, down to the check that the agent refused to invent a price. The services are AI agent development and LLM evaluation.
Financial services ask a different question: who did this, and on whose authority? No case study on this site comes from banking either. What transfers is the guide on agent auditability, which sets out what the record of an agent's action has to contain so that a reviewer can follow it long after the fact.
Aviation, logistics and defense manufacturing
An air hub runs on schedules, manifests and maintenance records, and they rarely live in one system. No case study on this site comes from aviation or freight. What transfers is data work published here: an analytics platform and a data warehouse, each fed from operational systems. An agent is only as good as the records it reads, so this usually comes first, and RAG and data platforms is the service that covers it.
Defense manufacturing is plant work under special rules. No case study on this site comes from defense. The plant side transfers from LeanManufacturing.mx, the platform of a lean manufacturing practice in Monterrey that works with food, metalworking and automotive plants: an open corpus, working tools, an assistant grounded in the corpus and an MCP server. The rules are yours. A defense program decides who may see its data and from which country, so ask your compliance team before you write to me.
One clock for two cities
Monterrey keeps the same hour all year. Dallas and Fort Worth are on that hour from early November to mid March, and one hour ahead of Monterrey from mid March to early November. The code lives in your repositories and your cloud accounts, and what is agreed on a call is written down afterwards.
Starting, and what is not on offer
Write to me with the role or the problem. I reply in writing with what I would build first and what I would need to see. I am open to senior roles and to contract engagements. What I cannot be is a local engineer in the metro, and this page does not pretend otherwise.