Switchboard
The shared messaging layer behind all of the above — WhatsApp and SMS with multi-provider failover.
The calls that shaped it
Build it once, use it five times
OTP, templates and opt-out handling are needed by every product above. Switchboard is the shared Go service that does it, so none of them re-implement messaging.
Provider failover by design
Twilio, Telnyx, Infobip and Plivo behind one interface. When a provider degrades in a region, traffic moves without a deploy.
Compliance as a shared concern
Opt-out handling and template management live in one place, which is the only way to keep five products consistently compliant.
What this proves about how I lead
Switchboard is the platform-team instinct: identify the capability every product needs, extract it, and own reliability centrally. As a CTO, deciding what becomes a shared service — and what stays local — is one of the highest-leverage calls I make.
Every product under Atrix was built with the same operating model I bring to a team: a written architecture decision before the first commit, a thin vertical slice in production within the first weeks, AI-assisted delivery for the volume work, and human judgment reserved for the decisions that compound — data model, security boundary, provider choice. The hire-me page lays out how that translates into a 90-day plan for your company.
Want to talk through the architecture?
I'm happy to walk a hiring panel or a founder through any of these systems in detail — or ask my AI twin first.