PRODUCT · GYMDOCK · 2025
GymDock runs a small gym's front desk. Members, payments, expiries and renewals sit in one place, so the owner can spend the day on the floor instead of in a register.
- Role
- Co-founder & engineer
- Year
- 2025
- Build
- React · Supabase · multi-tenant
- Status
- Live at gymdock.in
8
Modules, one login
100%
Every gym walled off
2
Built by two
Frame
A small gym runs on relationships and a register. The owner knows every member by name. They also have to know who paid, who's three days from lapsing, who's overdue, what came in this month and what went out. That second job lives in a notebook or a spreadsheet, and it's the one that pulls them off the floor.
The problem
The admin doesn't fit the gym. Memberships expire on different days. Money arrives as cash, as UPI, as "I'll pay next week." And the only way to spot a member about to drop off is to scroll a sheet and hope you notice. Miss it and they lapse quietly: the cheapest customer to keep, lost to a follow-up nobody made.
Process
So I put the whole operation behind one login. Add a member and GymDock tracks their plan, their expiry, and every payment against them. The dashboard surfaces what actually needs doing today (who's unpaid, who's expiring this week) instead of making the owner go looking for it. And each gym's data is sealed off from every other gym's at the database level: one product, many gyms, each one seeing only its own.
Key decisions
The dashboard does the noticing.
Instead of a sheet you have to read, the home screen puts the expiring and unpaid members first. The follow-up happens because the software remembered, whether or not the owner did.
It eats messy data.
Every gym arrives with years of records in a spreadsheet, and no two are formatted the same: wrong date formats, columns in the wrong order, junk rows. The importer reads the file, works out which column is what, and skips what it can't parse instead of choking. Onboarding is just dropping in the old sheet.
One product, every gym sealed off.
Built multi-tenant from the first table. A gym signs up, gets its own walled workspace, and never touches another's data. The same codebase quietly runs all of them.

Results
The owner opens GymDock and the day is already laid out: who to message, who's overdue, what the month looks like. The register, the payment history, the renewals, the expenses: one place, on the phone, on the floor.
Run the gym. Not the spreadsheet.

Next project
Royal Enterprise
Open →