Veteran-owned software consulting, based in San Antonio.
SDVOSB-certified. Engineers who live here, work in your time zone, and understand the JBSA, USAA, and South Texas Medical Center orbit you operate in.
San Antonio buyers keep getting sold national playbooks that don't fit SATX.
We hear the same story across the I-10 corridor: a coastal firm wins the work, flies in a partner for kickoff, then hands the engagement to a rotating offshore bench three time zones away. Standups happen at 6am. Deploys land on Friday afternoons. The team has never set foot in JBSA, has no idea what a USAA-spinout codebase looks like, and treats HIPAA and CMMC like a checkbox. By month four the program is behind, the scope has drifted, and your internal team is rewriting their work after hours.
- ▸ Offshore teams that disappear at 4pm CT and miss the window where production actually breaks
- ▸ Generalist consultants who confuse FedRAMP Moderate with HIPAA and write SOWs that conflate the two
- ▸ Glossy AI demos that never integrate with the Salesforce, Zendesk, or mainframe system actually running the business
- ▸ Modernization plans that propose a full rewrite when the real fix is strangling three batch jobs over six months
How we run engagements out of San Antonio
- STEP-01
On-site discovery in SATX
We meet at your office near the Quarry, Port SA, or off Loop 1604. Two engineers, one week, reading code and watching workflows. We leave with a written assessment, not a slide deck.
- STEP-02
Scope to a 6-12 week first slice
We carve out a first deliverable that ships to production inside a quarter. Fixed scope, named engineers, weekly demos. If it can't ship in 12 weeks, the scope is wrong and we resize it.
- STEP-03
Build with cleared-eligible staff when needed
For DoD or AFCYBER-adjacent work, we staff U.S. persons and clearance-eligible engineers. Source stays in your GitHub or GitLab tenant. We work inside your IL4/IL5 boundary, not ours.
- STEP-04
Hand off with documentation that survives
Runbooks, ADRs, and Loom walkthroughs go into your repo. Your team pairs with ours for the last two sprints. We exit when your engineers are running the system without us on the standup.
# Typical SATX engagement profile
engagement:
location: San Antonio, TX
onsite_cadence: 1-2 days/week within Loop 1604
timezone: America/Chicago
team:
- role: Tech Lead
seniority: 10+ yrs
clearance_eligible: true
- role: Senior Engineer
seniority: 7+ yrs
clearance_eligible: true
- role: Senior Engineer
seniority: 7+ yrs
contract_vehicles:
- SDVOSB sole-source (FAR 19.1406, up to $5M)
- Prime subcontract
- Commercial MSA
compliance_posture:
- CMMC L2 alignment
- FedRAMP Moderate (via AWS GovCloud / Azure Gov)
- HIPAA for SA medical center work
first_deliverable_window: 6-12 weeks
source_control: customer-owned tenant
Shape of a typical San Antonio engagement — staffing, vehicles, and compliance posture.
Field FAQ.
→ Are you actually based in San Antonio, or is this a satellite listing?
We are based here. Our engineers live in San Antonio and the surrounding area — Stone Oak, Alamo Heights, Schertz, Boerne. We meet in person at your office, at coffee shops on Broadway, or at Geekdom downtown. We are not a coastal firm with a forwarding address. When we say we'll be on-site Tuesday, we drive there.
→ Do you hold an active SDVOSB certification, and can you take sole-source awards?
Yes. We are certified through the SBA Veteran Small Business Certification (VetCert) program, which is the current authority since the 2023 transfer from VA CVE. Under FAR 19.1406, contracting officers can award us SDVOSB sole-source contracts up to $5M for services. We can also prime or sub on set-aside competitions and most GWACs through teaming arrangements.
→ Can you support work tied to JBSA, 16th Air Force, or AFCYBER?
We staff U.S. persons and clearance-eligible engineers for DoD-adjacent work, and we have people who have held clearances. For classified work itself, we operate as a subcontractor under a cleared prime with the appropriate facility clearance — that is the honest answer. For unclassified development, modernization, and AI integration supporting JBSA missions, we can contract directly.
→ What kind of work do you typically do for San Antonio financial and healthcare clients?
On the financial side — heavily shaped by the USAA ecosystem and its spinouts — we do legacy modernization (mainframe-adjacent batch jobs to event-driven services), API platforms, and AI integration into servicing workflows. On the healthcare side, around the South Texas Medical Center, we work on HIPAA-aligned applications, EHR integrations via FHIR/HL7, and prior-auth automation. No invented case studies — ask us for references during scoping.
→ How does same-time-zone work actually matter in practice?
Central time means your 9am standup is our 9am standup. No 6am calls to sync with offshore. When a production issue hits at 3pm, an engineer is reachable, awake, and can be on-site within an hour for clients inside Loop 1604. Code review turnaround is hours, not next-day. It sounds small until you've spent a year waiting overnight for a one-line fix.
→ What does AI integration look like for a San Antonio enterprise — not a demo?
Real work, not chatbots. We integrate Claude or GPT into existing systems: Salesforce Service Cloud for case summarization, Zendesk for triage, internal knowledge bases via RAG against SharePoint or Confluence, and document extraction pipelines for claims and contracts. We deploy through Azure OpenAI or AWS Bedrock when data residency or FedRAMP matters. We measure deflection and handle-time, not vibes.
→ Can you augment our existing engineering team instead of taking over a project?
Yes, and it's often the better move. We embed senior engineers — typically 7-15 years of experience — directly into your squads on your tooling (GitHub, Jira, Slack). They attend your standups, write code in your repos, and follow your review process. Engagements run 3-12 months. We do not send junior bodies to bill hours. If we don't have the right person, we say so.
→ What contract vehicles do you work under for federal customers?
We prime SDVOSB set-asides and sole-sources directly. For larger awards, we sub under primes on vehicles like SeaPort-NxG, GSA MAS IT, CIO-SP3 SB, and Alliant 2 SB through teaming agreements. We also work commercial MSAs for USAA-ecosystem and medical center clients. Tell us the vehicle and the office, and we'll be straight about whether we can support it directly or need a teaming partner.
→ How do you price engagements?
Three models. Fixed-price for well-scoped first slices (6-12 weeks, defined deliverable). Time-and-materials with a not-to-exceed for discovery and exploratory modernization. Monthly retainer for staff augmentation, billed per named engineer. Federal work follows the contract type the CO awards — FFP, T&M, or LH. We publish blended rate ranges during scoping. No surprise change orders for things we should have caught upfront.
Continue recon.
Services overview
Custom development, AI integration, modernization, and senior staff augmentation.
REL-02Who we are
Veteran-owned, SDVOSB-certified, and the engineers behind the work.
REL-03Engagement packages
Fixed-scope first slices and retainer shapes we run most often.
REL-04Start a conversation
Tell us the system, the deadline, and the constraint. We'll respond.
Talk to engineers who live in San Antonio, not a national sales desk.
Talk to a VooStack operator. We respond within one business day.