Fitness Business Management Platform
Contributed across a full-suite fitness business management SaaS platform serving studios, gyms, and multi-location operators with scheduling, billing, CRM, member experience, and reporting.
Problem
The platform serves a wide range of fitness operators, from single-location startups to large franchises, each with different operational needs. It has to support scheduling, billing, lead management, member experience, staff workflows, and reporting in a consistent way across customers with different configurations. Delivering new capabilities without disrupting existing operators at scale is a constant engineering challenge.
Approach
I contributed across the breadth of the platform rather than a single vertical. That meant working on scheduling flows, billing and payment paths, CRM and lead management, member-facing experiences, and internal reporting depending on what the product needed. Working across domains gave me a wide view of how the system held together and where the real dependencies and constraints were, which informed how I approached both feature work and systemic improvements.
Architecture
The platform is a multi-tenant SaaS with a web frontend and a .NET backend, structured to serve many operator configurations through shared infrastructure. Supporting that breadth requires careful data isolation, configuration-driven behavior, and well-defined service boundaries so product changes in one area do not break unrelated workflows for other customers. Reporting and analytics run across a data layer that has to stay consistent despite high write volume from concurrent operator activity.
Tradeoffs
Breadth at a SaaS company means balancing feature velocity against operational stability across many concurrent customers. A change to billing or scheduling logic can touch a large surface area, so the tradeoff was always between moving fast and moving safely. Working across domains also means understanding cross-cutting concerns like multi-tenancy, permissions, and data integrity at a level that siloed feature work would not require.
Outcome
My work contributed to a platform used by national fitness operators across hundreds of locations. Beyond individual features, broad cross-domain contribution built a strong understanding of what it takes to evolve a production SaaS with real customers, operational complexity, and the kind of scale where engineering decisions have immediate visible consequences.