Team Architect · Engineering & the teams that do it
I build the first one so the second is configuration, not code.
Carlos “Mumo” Muñiz. Fifteen years split between building software and building the teams that build it — and the same method underneath both.
0 lines
of new code for the five identity providers that came after the first. Configuration, not a rebuild.
− → 99
client NPS, from negative, in six months as COO of a ~70-person consultancy. eNPS 10 → 95 alongside it.
months → weeks
time to market on the work a multi-agent development workflow touched — in production, not a demo.
Selected work
Identity at scale, without rebuilding it every timeMigrated identity from Devise sessions to Auth0 JWT with RBAC — 60K+ users in daily use across 5+ federated providers, each one after the first a configuration rather than code.Multi-agent AI workflows in production, not a demoDesigned a multi-agent SDLC (Claude/Codex/Gemini, Challenger/Risk roles) that cut time to market from months to weeks.From negative NPS to 99Negative NPS to 99, eNPS 10 to 95, utilization 80% to ~99% — all in six months, then walked when the company stopped valuing the approach that got there.All five case studies →Recent writing
The Goal Is Reducing UncertaintyWhat good MCP tool design has in common with reducing uncertainty for the humans on a team.Not a Hiring Problem. A Context Problem. Again.AI isn't destroying the job market. It's exposing a context problem that was already there.If AI Makes Us Faster, What Should We Do With the Time?Every AI conversation turns into a productivity conversation. That's the wrong question.
Currently at Bravo. Open to the right conversation.