GymRevenue — SaaS Architecture & Engineering Leadership

Gym operators often rely on separate systems for leads, memberships, payments, communications, reporting, and day-to-day staff tasks. GymRevenue set out to bring core operations into one modular platform, with shared data across gym teams and locations. It was a substantial funded product effort, but the full platform was not completed or commercially launched before funding ended in December 2024.

During funded development, the team implemented CRM and lead/member records, recurring billing, email/SMS campaigns and drip sequences, configurable email templates, real-time reporting and dashboards, multi-location operations, staff calendars and tasks, and barcode check-in. The product vision extended further: POS, forecasting, leaderboards, and HR/payroll were not built; event-triggered workflows, web CMS, and white-label mobile work remained partial.

After the original architect departed, I assumed architectural ownership and, as Director of Engineering, led a 17-person engineering organization through three leads and a Principal Engineer. We extended an existing Laravel/PHP system with Spatie Event Sourcing, event-derived read projections and reactors, Lighthouse GraphQL, and MySQL. Tenant and per-location boundaries shaped the design; hosting used Laravel Vapor on AWS.

I introduced documented engineering standards, structured onboarding and mentorship, code-review gates, automated testing, CI/CD quality gates, and more predictable planning and release practices. Over approximately one year, sprint velocity increased by about 50%, and automated test coverage rose from effectively 0% to roughly 70%. These improvements strengthened delivery foundations, but the overall product remained unfinished when funding ended.