PRODUCT CASE STUDY — 01
GymLoop
An all-in-one gym management SaaS for gyms, studios, PT businesses and sports academies.
GymLoop puts memberships, attendance, payments, trainers, classes and member engagement in one multi-tenant dashboard — replacing the spreadsheet-and-WhatsApp stack most gyms run on.
Visit live site ↗Gym owners don't need more tools. They need one operating layer where every member, payment and class lives in the same context.
TYPE
Client product build
DOMAIN
Fitness operations
STAGE
Production-ready
PLATFORMS
Web (member portal + dashboard)
STATUS
Multi-tenant SaaS
ROLE
Full-stack engineering
01 — THE STARTING CASE
Gyms run their entire business across spreadsheets, notebooks and group chats.
Member records live in Excel, payments are tracked on paper or UPI screenshots, class schedules change in WhatsApp groups, and nobody can answer "who hasn't renewed?" without an afternoon of reconciliation.
01
Member data is scattered
Memberships, attendance and payment history sit in separate files and inboxes, so the front desk never has one current view of a member.
02
Money leaks quietly
Dues, invoices and expenses are reconciled by hand at month-end. Renewals slip, pending payments are discovered late, and revenue reporting is guesswork.
03
Scheduling lives in chat
Class timetables, trainer allocations and PT sessions are coordinated in WhatsApp — invisible to members and untrackable for owners.
02 — WHY THIS PRODUCT NEEDS TO EXIST
Gyms need an operating system, not a point tool.
Most gym software stops at a member list. The daily reality is operational: check-ins at the door, dues that renew monthly, classes that need trainers, inventory that needs restocking, and members who go quiet and churn.
GymLoop was shaped around that whole loop — every module reads from the same member and money model, so the dashboard, member portal and automation workers never disagree about the truth.
ONE MEMBER CONTEXT
Attendance, invoices, classes and engagement all hang off the same member record.
MONEY IS PRECIOUS
Invoicing, dues and expense logic is pure, unit-tested domain code — not UI math.
MULTI-TENANT FROM DAY ONE
Branches, roles and permissions are first-class, so one chain or one studio run the same system.
03 — WHAT WE BUILT
The full operating loop for membership businesses.
Every module is wired into the same tenant, member and money model — the dashboard, member portal and background workers included.
01
Memberships & invoicing
Plans, renewals, dues tracking and invoicing with tested money logic — plus an at-risk view that surfaces members likely to churn.
02
Attendance & classes
Check-ins at the door, class timetables, trainer allocation and PT session scheduling in one calendar.
03
Payments & finance
Payments, expenses, point of sale, products and inventory — reconciled against real invoices instead of spreadsheets.
04
Engagement & automation
WhatsApp, SMS and email automations driven by BullMQ workers and cron — renewals reminders, follow-ups and campaigns without manual pushes.
04 — UNDER THE HOOD
Engineered as a production monorepo.
Monorepo
Dashboard & portal
API
Background work
Domain
05 — PRODUCT PRINCIPLES
The rules that keep the platform coherent as it grows.
•
The dashboard is the truth
If a module can't agree on member or money state, the module is wrong — never the data.
•
Tested where it counts
Business rules live in a pure domain layer with unit tests, separate from HTTP and UI concerns.
•
Roles mirror reality
Owners, managers, trainers and front desk each get exactly the permissions their job needs.
•
Automate the follow-up
Workers and crons handle reminders and nudges so staff never have to remember to send them.
A full SaaS platform — product, API and workers — built as one system.
GymLoop demonstrates the complete engineering loop for a vertical SaaS: domain modelling, multi-tenant API design, dashboard and portal UX, and background automation, all shipped as a deployable product with Docker-based infrastructure.
STRATEGY
Modelled the gym business end-to-end before writing screens — membership lifecycles, money flow and attendance became the domain core.
DESIGN
A dense-but-calm operations dashboard: high-information tables, quick actions where staff need them, and charts that answer owner questions.
ENGINEERING
Nx monorepo with shared types and validation, a NestJS API with tested domain libs, and BullMQ workers for everything asynchronous.
06 — WHAT COMES NEXT
A roadmap expressed as capabilities, not speculative promises.
The foundation is in production shape; the roadmap deepens the loop that already exists rather than inventing new directions.
NOW
Now
Multi-tenant operations — memberships, attendance, classes, finance and engagement for gyms and studios.
NEXT
Next
Deeper member engagement: mobile-first member experience, richer campaigns and retention analytics.
LATER
Later
Ecosystem integrations — access control hardware, payment providers and accounting exports on the same domain core.
NEXT PROJECT
Build the next system with AryaStack.
If your product problem is still messy, that is a good starting point. We help turn ambiguity into a system teams can ship and evolve.