Second Sponsor

People in recovery need support at the moment they reach for it, not at the next meeting. Second Sponsor gives them a companion they can text or call that remembers their history, draws on the program's own material, and flags risk signals for follow-up. That has to work on a phone, at 3 a.m., under healthcare privacy rules.

CTO since 2025. Santiago owns the architecture and works hands-on across the mobile app, the API server, AI behavior, the voice agent, compliance, releases, and production operations.

• —Conversations contain protected health information, so storage, retrieval, and every AI provider in the loop have to sit inside a HIPAA boundary with a signed BAA.
• —Voice runs through a live speech model, so the call has to stay usable through real phone conditions and reconnect without losing the transcript.
• —Second Sponsor is one of several branded healthcare apps built from the same codebase, so improvements have to land in a form the other apps can pull in.

• 01Build from RagRecall, a template codebase the branded apps fork and keep merging from, so compliance, memory retrieval, and voice are solved once and shared through Git rather than re-implemented per app.
• 02Run the voice agent as its own deployable on LiveKit with Gemini Live inside a Google Cloud Assured Workloads HIPAA folder, and persist transcripts through durable workflows so a dropped call never loses the conversation.
• 03Give the assistant a memory layer and organization-level retrieval so replies come from the person's history and the program's material instead of a generic model.
• 04Keep the shape small enough to operate: five deployable apps, one Fastify server, fifteen shared packages, one shared HIPAA cloud project.

• —Second Sponsor v1.0 shipped in June 2025 and is live on the App Store and Google Play.
• —The same codebase and infrastructure run multiple branded healthcare applications.
• —Voice, chat, memory retrieval, and risk assessment are all in production, with releases cut through a production workflow Santiago set up.

• —A shipped, maintained product in a regulated category, with the voice and memory features that define it working on real devices.
• —A codebase that makes the second and third healthcare app cheaper to build than the first.