Texas AI Developer for Automation and Custom Software
I am a Texas AI developer serving Houston, Dallas, Austin, San Antonio, Fort Worth, and the rest of the state — AI automation, OpenAI integrations, custom AI tools, and self-hosted LLM systems for Texas businesses. 25 years in computer science, B.S. Computer Science from the University of Houston, U.S. Army veteran, single-principal delivery. Houston-anchored, statewide remote, in-person discovery available in the Houston metro.
Texas as an AI development market
Texas is four AI-buyer profiles layered on top of each other. Houston is energy operators digitizing field operations, healthcare networks automating intake and triage, and Microsoft-shop enterprises looking for AI inside Azure-anchored stacks. Dallas / Fort Worth is financial services AI (fraud detection, document automation, compliance summarization), aerospace and defense (controlled environments where self-hosted is the only option), and large healthcare networks. Austin is AI-native SaaS startups, federal-research-adjacent shops, and the open-weights / Hugging Face contributor community. San Antonio is military-adjacent contracting, USAA-adjacent financial services, and large healthcare systems with compliance postures that rule out third-party APIs.
Texas businesses are unusually well-positioned for AI work right now. The state's no-income-tax posture attracts the kind of capex that funds custom AI builds. The Texas energy sector has billions of dollars of legacy operational software ripe for AI automation. The Texas Medical Center is the largest medical complex in the world; the volume of healthcare automation opportunity is enormous. The two-largest US military bases (Fort Hood / Cavazos and JBSA) anchor a defense-adjacent contracting surface where self-hosted AI is table stakes. The right AI engagement in Texas is shaped by which of these four profiles the buyer fits.
What I build for Texas businesses
- AI automation for business workflows. CRM automation, document processing, internal AI tools, customer-service triage. See the AI automation developer page for the broader services.
- OpenAI and Anthropic integrations. SaaS-API-based AI for buyers whose compliance posture allows third-party providers.
- Self-hosted LLM systems. Llama, Mistral, custom fine-tunes deployed on the buyer's hardware for healthcare, energy, financial services, and defense-adjacent compliance postures.
- Custom AI tools. Internal dashboards, RAG-backed knowledge systems, AI-assisted operator surfaces — built for the buyer's specific workflow, not a generic SaaS product.
- AI engineering for SaaS products. The AI features inside the SaaS that differentiate it — built with eval harnesses, monitoring, and the operating discipline the production system actually needs.
The Texas city pages
- Houston AI Developer — energy, healthcare, Microsoft-shop enterprises. In-person discovery available.
- Dallas AI Developer — financial services and Microsoft-shop enterprises.
- Austin PHP Developer — Austin SaaS engagements where AI is a feature inside the product.
- San Antonio Laravel Developer — healthcare and military-adjacent buyers (Laravel-shaped applications with AI features inside).
Texas-specific signals
B.S. Computer Science from the University of Houston. U.S. Army veteran with Texas-anchored service history (Fort Sill, Fort Bliss, Fort Carson — the artillery branch). Houston metro home base. Texas-resident, Texas-bank-anchored business operations. The procurement-friction reduction from a Texas-based AI vendor is meaningful for state-government, public-university, and Texas-anchored corporate buyers.
Are you available statewide, or only in Houston?
Statewide remote with Houston as the home base for in-person discovery. Austin and College Station are reachable by car within a few hours notice. Dallas, Fort Worth, San Antonio, and El Paso are remote-only for most engagements; flying in for kickoff meetings is possible for engagements that justify it.
Can you build self-hosted AI for compliance-sensitive Texas industries?
Yes — this is one of the more common Texas engagement shapes. Healthcare networks, energy operators, financial-services firms, and defense-adjacent contractors all have compliance postures that rule out third-party AI APIs. Self-hosted deployment via Ollama, vLLM, or llama.cpp running on the buyer's hardware is the right answer for those engagements.
Do you work with Texas state-government or public-university buyers?
Subcontract-shaped engagements through a prime contractor are workable. I am not currently registered as a direct prime with the State of Texas or the UT system; if your buyer requires that I will refer to a network contact rather than pursue the registration mid-engagement.
Will my data be sent to OpenAI?
Only if you want it to be. Most Texas engagements offer a choice: OpenAI / Anthropic when the workflow is non-sensitive and the SaaS providers fit your compliance posture; self-hosted Llama / Mistral when the data must stay inside your network. I will say honestly which one your specific workflow needs.
What is your hourly rate?
Bespoke, scoped per engagement, written into SOW before contract. Texas AI engagements are typically priced per-phase rather than hourly: eval harness; first working model; production deploy; monitoring.
Scope This Engagement
Single principal, plan first, working code on every checkpoint.
Start a Conversation