Happy Software
(2018 – 2025)
Happy Software (renamed from LemonScale in 2023) is a product development agency. Clients came in needing more than a website — they needed systems that could run part of their business: bookings that don't double-sell, catalogs a non-technical team can update, mobile apps that don't crash mid-checkout.
My role: Senior Software Engineer, later leading the Reacttiv initiative. I scoped the business problem behind each request, architected the system, and shipped it to production.
Stack: React, React Native, Next.js, Node.js/Nest.js, PHP (Laravel), PostgreSQL, AWS, DigitalOcean.
What I was accountable for
- Turning client requirements into shipped, production systems — not just interfaces.
- Architecture and performance: high-traffic apps built on Next.js/Nest.js, consistently scoring 95+ on Lighthouse, which measurably improved client retention (~20%).
- Mentoring junior engineers and setting technical direction for the team.
- Direct communication with product owners and stakeholders — translating between business goals and engineering trade-offs.
Selected systems I shipped
Camino Real — hotel group mobile app
Problem: the group's booking app ran on PhoneGap + PHP and crashed often enough to hurt guest experience and bookings.
What I built: migrated the app to React Native with a Laravel backend, coordinating the transition with stakeholders and other teams.
Outcome: crash rate down 40%, with a smoother booking flow for guests.
Lala / Lala Plenia — brand websites
lala.com.mx · lalaplenia.com.mx
Problem: the marketing team needed to publish and update content without waiting on engineering for every change.
What I built: both sites on OctoberCMS, with ongoing maintenance and support.
Outcome: content the team can update on its own, with the sites staying stable across releases.
Maestros Parrilleros
Problem: an existing OctoberCMS site needed to grow past its original scope.
What I built: extended the platform's functionality and kept it running.
Outcome: the site kept pace with the business without a rebuild.
Freightliner Mexico
Problem: a corporate site needed a CMS a non-technical team could manage, on modern infrastructure.
What I built: Keystone.js + Next.js, with ongoing maintenance and support.
Outcome: a fast, maintainable site the client's team updates independently.
Red Clelac
Problem: members of the client's business cluster had no shared way to find and connect with their peers.
What I built: a directory and networking platform on Laravel + React, working directly with stakeholders to define scope.
Outcome: a live platform members use to find each other.