A friend runs Fitcon, a gym with locations in Gulshan and KMC. Like most gyms, he was running things the way most gyms do — a mix of registers, spreadsheets, and manual check-ins that worked, but only just. Haider Shah set out to build him something better: a simple system to track members, plans, and payments in one place.
What started small kept growing
What started as a straightforward CRM kept growing — Face ID check-in so front desk wasn't stuck manually logging every entry, membership freezes, staff permissions, multi-branch support as Fitcon opened a second location. Each feature came from a real problem at a real gym, not a feature checklist.
From one gym's tool to a real product
At some point it became clear: if Fitcon needed this, other gyms probably did too. That's the moment GymlyCRM stopped being one gym's internal tool and became a real product — built the same way it started, by actually working through what a gym's front desk deals with every day.
Why it's still built this way
GymlyCRM is built the way it started — grounded in what an actual gym's front desk needs, not abstract feature lists. That's why things like Face ID check-in, membership freezes, and multi-branch support exist: they were needed at a real gym before they were ever built into the product.
Where it's headed
Fitcon is still a GymlyCRM gym today. Every gym that signs up afterward gets the same software, built to the same standard — does this actually help someone running a gym, not just look good on a features page.