GymOS
Designing a connected operating system for multi-gym membership, attendance and front-desk operations.
A multi-gym SaaS brief could have been treated as a list of screens. HL approached it as an operating-system problem—mapping how gyms, branches, members, memberships, payments, attendance, renewals, staff and member experience needed to work together before building the interactive prototype.
Software prototypes should validate end-to-end operational logic, not just UI styling. By connecting platform governance, access decision rules, and front-desk workflows, HL demonstrated how multi-location operators can eliminate daily friction.
Diagnosing the Operational Reality of Multi-Gym Networks
In August 2026, HL Business Developers was presented with a pre-sales opportunity for a multi-gym management and attendance SaaS platform. Rather than jumping immediately into static screen designs, HL began by diagnosing how gym networks actually operate—and where daily friction creates revenue and administrative loss.
A multi-location fitness operator required a modern SaaS concept to govern multiple gym brands, individual branch facilities, membership plans, real-time member check-ins, payment tracking, and staff roles.
The goal was to demonstrate how modern web technologies could replace fragmented legacy spreadsheets, standalone barcode scanners, and disjointed front-desk accounting tools with one cohesive operating ecosystem.
Physical check-in stations rarely evaluate membership expiration in real time, leading to unauthorized entry and missed renewal revenue.
Front desks struggle to verify whether a member holds a single-branch or all-access multi-branch pass during check-in surges.
Reception staff are forced to navigate complex owner dashboards instead of fast, purpose-built check-in and payment intake tools.
Members whose visit frequency drops precipitously go unnoticed until they formally cancel their memberships.
Two Operational Chains That Prevent Siloed Screens
HL structured the system around two fundamental operational relationships. By designing clear connections across these chains, every front-door access decision is directly informed by live membership and financial records.
Establishes tenant isolation and granular delegation: Platform Admins oversee multiple gym brands, gym owners manage multiple physical branches, and branch managers assign role-specific permissions to receptionists and trainers.
Connects customer profile, plan parameters, payment logging (Cash, JazzCash, Easypaisa, Bank Transfer), real-time attendance, expiration triggers, and proactive re-engagement into one continuous operational loop.
Five Interconnected System Modules
Rather than presenting a generic feature list, GymOS organizes operational capabilities into five logically linked modules that share live state.
Platform & Organization
- Platform Admin console
- Multi-gym tenant management
- Individual branch configurations
- Staff role assignments & RBAC
Membership Operations
- Member directory & profiles
- Flexible plan catalog & tiers
- Expiry & dues tracking
- Payment-recording workflows
Daily Operations
- Real-time attendance ledger
- Fullscreen QR Station simulator
- Reception Desk Mode
- System notifications UI
Management & Engagement
- Member Engagement workspace
- "Gone Quiet" inactivity surfacing
- Branch utilization reports
- Operational audit logs
Member Mobile Experience
- Digital membership card & validity status
- Dynamic QR code for front-door check-in
- Branch access verification indicator
- Attendance history and streak tracking
The 4-State QR Access Decision Engine
The strength of GymOS lies in treating QR check-in as a contextual access rule engine rather than a simple barcode scanner. At the instant of token scan, the system evaluates:
ACCESS APPROVED
Valid active membership with full multi-branch access rights. Member checked in successfully.
Live headcount incremented (+1). Access timestamp logged to attendance ledger.
Reception Mode vs. Management Dashboard
Front-desk staff have fundamentally different daily tasks than gym owners. GymOS introduced a dedicated Reception Mode engineered for speed, high-volume member queues, and fast payment logging.
Streamlined front-desk console removing complex analytics so receptionists can process members in seconds:
Search by full name, phone number, or digital pass ID in milliseconds.
Quick manual override when member forgets their mobile device.
Record Cash, JazzCash, Easypaisa, or Bank Transfer instantly.
Real-time occupancy counter updated with every scan and checkout.
Surfaces members expiring today for greeting and verbal reminder.
Toggle to fullscreen tablet mode facing the turnstile or counter.
Consolidated financial overview across all branches without exposing sensitive metrics to reception staff.
Configure staff login credentials, shift assignments, and branch access controls.
Manage membership packages, single-branch limits, and multi-location upgrade pricing.
Bridging the Operator Console with the Member Experience
GymOS was designed from the perspective that operational efficiency at the front desk depends on clarity in the member's hands. The member mobile prototype gives members clear visibility into their status before arriving at the turnstile.
Dynamic Digital Check-In Pass
Members present a clean, high-contrast QR token directly from their phone screen to the QR Station scanner for instant verification.
Live Expiry & Validity Indicator
Clear countdown timer showing days remaining on current plan, eliminating surprises at the door and encouraging prompt renewal.
Branch Access Verification
Clearly displays which physical gym branches the member is authorized to access, preventing cross-branch confusion.
Surfacing Member Inactivity: The "Gone Quiet" Workflow
Most gym cancellations happen weeks before formal non-payment. The prototype designed a structured workflow to surface declining attendance for timely staff follow-up.
Member check-in frequency drops below threshold (e.g. 0 visits in 14 days).
System automatically categorizes member into the front-desk re-engagement queue.
Assigned staff member triggers check-in call or personalized WhatsApp message.
Member resumes attendance or updates membership status with staff assistance.
Context-Aware Prototyping
Software prototypes succeed when they reflect the real-world operational context of the target market. GymOS incorporated local Pakistan currency, geography, and payment methods to create an authentic simulation.
Membership plans, dues calculations, and fee tables formatted in Pakistani Rupees.
Multi-branch routing simulated across DHA Phase 5, Bahria Town, and F-7 branches.
Payment-recording workflows included locally relevant settlement options.
Demo accounts (Ahmed Khan, Hamza Ali, Sara Malik, Usman Shah) tailored to regional context.
What Was Built, What Was Simulated, and Technical Boundaries
HL maintains complete honesty regarding prototype scope. The matrix below defines the exact capabilities built into the prototype versus simulated elements and production boundaries.
- Full React 19 / TypeScript / Vite web application
- Platform Admin & multi-gym switcher
- Branch management and staff role interfaces
- Member directory, profiles & plan catalog
- Real-time client-side attendance state
- 4-state QR decision workflow engine
- Reception Desk Mode front-desk console
- Member mobile UI simulation
- Payment recording & renewal dialogs
- Deployed on Vercel
- Member records and check-in counts
- Branch revenue & dues collection reports
- Payment receipt dialog states
- Client-side QR token validation
- Notification triggers & alert queues
- Engagement & inactivity follow-up lists
- Audit log events
- No production backend database (PostgreSQL/Node)
- No live JazzCash / Easypaisa gateway APIs
- No live WhatsApp or SMS gateway integrations
- No physical turnstile or biometric access hardware
- No production auth (Supabase/Auth0) or hardened RBAC
- No real gym client, live gym deployment or members
Architectural Capabilities Designed for Multi-Location Operators
Because this project was an interactive prototype, the areas below represent intended operational value designed into the architecture—not achieved client metrics.
Multi-Branch Governance
Designed to provide gym owners with one coherent operating structure across multiple facilities, brands, and staff tiers.
Context-Driven Entry Decisions
Designed to make membership validity and branch rights relevant to operational access at the exact moment of physical entry.
Surfacing Expiry as an Action
Designed to surface expiring memberships as an immediate front-desk renewal opportunity rather than passive revenue leakage.
Role-Specific Workflows
Designed to simplify common reception workflows, accelerating check-in speed and minimizing staff error during peak queues.
Inactivity Follow-Up Triggers
Designed to surface member attendance declines for timely staff outreach before members cancel.
Dual Experience Continuity
Designed to connect operational status directly with the member experience through digital passes and status transparency.
Translating Broad Briefs into Connected Operating Systems
The GymOS prototype demonstrates HL’s core engineering philosophy when tackling complex operational challenges:
Problem Mapping
Understanding operating friction and multi-role realities before prescribing wireframes or technology stacks.
Workflow Engineering
Architecting relationships between financial status, physical access, and staff permissions rather than isolated screens.
Front-Line Empathy
Engineering interfaces tailored to the distinct workflows of owners, front-desk receptionists, and members.
Functional Validation
Building interactive, testable React applications to validate architectural decisions with stakeholders.
“HL did not simply design another dashboard. HL translated a broad product brief into a connected operating model and then built an interactive system around that model.”
Have an operating problem that doesn’t fit neatly into one service?
HL starts with the friction, maps the systems around it, and determines what should be built, connected, improved, automated—or left alone.