Software consulting for San Antonio's defense, finance, and health sectors

We have engineers living and working in San Antonio — not a sales rep with a PO box. That matters because defense, USAA-orbit financial services, and South Texas Medical Center work tends to require people who can be in the room on short notice. We can be at JBSA, the Tech Port, or the medical center for a working session inside a day, not a flight booking later.

We are SDVOSB-certified and operate a cleared personnel pipeline for engagements requiring Secret and above. Facility clearance and specific program access are scoped per engagement — we'll be direct about what we hold, what we can sponsor, and what would require a prime/sub arrangement. For 16th Air Force and JBSA-adjacent work, we typically partner under an existing prime when the program demands it.

Most discovery engagements run $25K-$60K fixed-bid over two to four weeks. Build engagements typically run $150K-$600K for a 3-6 month delivery with a senior pod of three to five engineers. Federal work priced under GSA or agency-specific vehicles varies. We give you a fixed number after discovery — not a T&M blank check that drifts for a year.

Yes. We've shipped systems under SOC 2, PCI-DSS, and GLBA constraints, including auth flows, transaction processing, and document workflows that touch regulated data. We don't pretend to be a compliance auditor — we build the engineering controls (encryption, audit logging, least-privilege IAM, evidence collection) that let your auditor sign off without a six-month remediation cycle.

Most of our work is modernization. Typical patterns: a 15-year-old .NET Framework app moving to .NET 8 on Azure, an Oracle Forms system getting a React front-end and a strangler-fig API layer, or a homegrown ETL pipeline being replaced incrementally. We don't recommend big-bang rewrites — they fail. We carve out modules, ship them to production, and retire the old system piece by piece.

We integrate Claude, GPT, or open-weight models into existing workflows — usually document processing, internal search via RAG over SharePoint or Confluence, support ticket triage in Zendesk or ServiceNow, or summarization inside Salesforce. We are skeptical of agentic demos that don't survive contact with production data. Every AI feature ships with eval harnesses, cost guardrails, and a fallback path when the model is wrong.

No. Knowledge transfer is part of the build, not an afterthought — your engineers pair on the code, the Terraform lives in your repo, and the runbooks are written for your on-call rotation. Most clients keep us on a month-to-month support contract for incident response and feature work, but it's cancelable with 30 days notice. We'd rather earn the renewal.

Yes. We've built and modernized systems for clinical operations, scheduling, and back-office workflows in HIPAA environments. We work in Epic and Cerner adjacencies — integrating ancillary systems via HL7 and FHIR rather than touching the EHR core. For research and population health work, we've built data pipelines that respect IRB constraints and de-identification requirements.

Two reasons. First, sit-in-the-room engineering: hard problems get solved faster when the engineer can walk into your office Tuesday morning instead of dialing in from three time zones away. Second, durable support: we're still here in year three. Fly-in-fly-out engagements tend to leave a system nobody on your team can maintain, and a phone number that goes to a different account manager every quarter.