Serious Engineering
for Companies That Can’t Afford to Rebuild.
Nexa Devs is a US-incorporated software development and engineering partnership with delivery teams across Latin America. We build, modernize, and maintain the internal systems mid-market companies depend on, and we’ve been doing it long enough that some of our first clients are still our clients today.
Why This Company Exists
The problem Nexa Devs was built to solve is not a technical problem. It's a structural one.
Most software vendors are organized around projects. They scope a piece of work, build it, hand it off, and move on to the next client. The code goes out the door. The documentation doesn't. The institutional knowledge of how the system was built, why certain decisions were made, and what breaks under specific conditions. All of that stays with the people who built it.
The client ends up with working software and zero real ownership of it.
We built Nexa Devs around a different model. Every engagement transfers complete documentation to the client from day one. Every engagement includes a post-launch SLA that defines exactly what we're accountable for after delivery. And we use AI across our full development process, not to replace engineering judgment, but to move faster while documenting more thoroughly.
The result: clients who own their systems, understand them, and aren't dependent on us to keep them running. The ones who want us to stay do so because the relationship is working, not because they have no other option.
Who Runs This, and Why It Matters
Vivian Aguilar
"I co-founded my first technology company in 1999 and ran it for nearly twenty years. Twenty-five years of watching the same problem repeat: knowledge that walks out with the team, code only the vendor understands, clients who can't touch their own systems. That is why I built Nexa Devs the way I did."
Before Nexa Devs, Vivian co-founded Viaro Networks in 1999 and ran it as Senior IT Project Manager for nearly twenty years. That history matters: she didn't start Nexa Devs because she was a good engineer looking for independence. She's a serial founder who has built and operated technology companies across different markets, team structures, and economic cycles, directly accountable for client outcomes the entire time.
She holds two MBAs from Universidad Francisco Marroquín (Finance and Marketing) and has completed advanced programs at MIT Sloan (AI for Business Strategy) and MIT (Digital Transformation). In 2018, while already running Nexa Devs, she went back to UC Berkeley Extension to study full stack web development. A CEO voluntarily relearning to build things from scratch mid-career is a specific kind of signal: she is not a founder who drifted away from the technical side as the company grew.
From 2019 to 2024 she served as Network Director for Women Who Code Guatemala, a US-founded international nonprofit with chapters across six continents, and has continued that community work since 2024 as Network Director for Aurora STEAM Guatemala.
B.Sc. Management Information Systems, UFM
MBA (Finance + Marketing), UFM
UC Berkeley Extension: Full Stack Web Development (2018–2019)
MIT Sloan: AI for Business Strategy + MIT: Digital Transformation
Network Director: Women Who Code Guatemala (2019–2024) → Aurora STEAM Guatemala (2024–present)
Why Latin America, and Why It Matters to You
We're US-incorporated with engineering delivery teams across Latin America. That's not a cost-reduction strategy. It's a structural advantage for mid-market US companies.
Time Zones That Actually Overlap
Our engineers work in EST, CST, and PST-adjacent time zones. Morning standups work. Afternoon reviews work. You're not waiting 12 hours for a response to a question asked at 2pm.
Cultural Alignment That Reduces Friction
Latin American engineering culture has significant overlap with US business norms: communication style, professional expectations, and how client relationships are structured. 87% of US companies working with LATAM nearshore teams report high satisfaction, versus 53% for offshore alternatives.
IP Protection That's Unambiguous
We're a US-incorporated company. All work is performed under US contract law with work-for-hire agreements. You own the code from the moment it's written. There's no ambiguity at the end of the project about who owns what.
Access to Serious Engineering Talent
Latin America has produced over 2 million trained technology professionals with deep skills in AI, cloud, and modern engineering. We know where that talent is because we're embedded in it, through our team, our network, and Vivian's work with Women Who Code Guatemala.
What We've Learned After Building Systems for 25+ Years
Documentation Isn't a Deliverable. It's a Standard.
The most common reason software projects fail long-term isn't bad code. It's knowledge that lives in people's heads and not in files. We produce documentation continuously throughout every engagement, not assembled in the last sprint. If you needed to hire a new engineering team tomorrow, you'd have everything they'd need to be productive in two weeks.
Post-Launch Accountability Shouldn't Be Optional.
Every engagement we take includes a defined post-launch SLA: response times, scope commitments, and escalation paths. Not because clients ask for it. Because a vendor who builds something and walks away wasn't really accountable for what they built.
AI Speeds Up the Work. Engineers Make the Decisions.
We use Claude Code and MCP integrations across our full development process. Architecture decisions, code reviews, and client communication are made by engineers, not by AI. We use AI to handle mechanical work faster. We use engineering judgment to decide what to build and how. Every AI-generated output is reviewed by a senior engineer before it ships.
The Clients Who Stay Longest Are the Ones Who Needed This Once.
Our longest relationships, including 10+ years with UCLA's David Geffen School of Medicine and 8+ years with TSB and United Way, started as single projects. They continued because the work was done right, the documentation was transferred, and when things needed to evolve, we were already embedded enough to help without starting over.
Where We Have the Most Experience
We've built production systems in environments where reliability, compliance, and documentation standards are non-negotiable.
EMR systems, lab management platforms, psychological assessment tools, clinical operations software, built to audit standards and designed for clinical and administrative users who aren't engineers.
Research platforms, faculty portals, learning management systems, and finance systems, including a 10+ year partnership with UCLA's David Geffen School of Medicine.
Donation processing infrastructure, fundraising platforms, and payment systems, including an 8+ year partnership supporting FrontStream's platform for hundreds of nonprofit clients.
MVNO carrier operations, analytics infrastructure, and operational support systems, including an 8+ year partnership with TSB.
We're not industry-exclusive. But if your system runs in a regulated environment or carries significant operational risk, we've been there.
Talk to the Team
30 minutes. You describe what you're dealing with: the system, the team, the history. We tell you whether we're the right fit and what we'd do first.
No prepared pitch. No proposal emailed beforehand. A real conversation about your actual situation.