A bilingual gym-management platform for Bangladesh that replaces paper ledgers with dependable membership coverage, billing, attendance, receipts, offers, and role-aware operations.
Liftuno is a web application created to make a real workflow clearer, faster, and easier to trust. It turns a focused product idea into something people can use, evaluate, and understand without needing to inspect the source code.
Why Liftuno exists
Local gyms often track members, payments, attendance, and outstanding balances through paper records or staff memory. That makes daily work slow and allows financial history, access boundaries, and membership state to become ambiguous.
The goal is not simply to add another tool. Liftuno is designed to reduce the friction around that problem and give people a more dependable way to complete the work.
What it delivers
- Gym staff can replace fragmented paper tracking with one member, payment, and attendance ledger.
- Prepaid coverage, outstanding balances, partial payments, offers, and reversals retain explicit financial meaning.
- Organization and role boundaries are enforced by the backend rather than inferred from navigation state.
- The same product foundation supports responsive web use now and Android validation as a separate release step.
The experience
A bilingual gym-management platform that gives Bangladeshi gyms a dependable alternative to paper ledgers for membership coverage, billing, attendance, receipts, and staff operations.
The project brings the important parts of the workflow into one coherent experience. Its interface and behavior are shaped around the people using it, while the implementation stays focused on predictable results and honest feedback.
What to know
Every product has boundaries. These are the most important considerations for Liftuno:
- Membership accounting must distinguish expired coverage from actual debt instead of inventing fees when a member stops attending.
- Platform operators, gym administrators, staff, and members require different permissions with strict organization isolation.
- The product must support English and Bangla, Bangladeshi taka, Asia/Dhaka dates, phone-first workflows, and future Android delivery.
- Payment and attendance retries must remain idempotent so unreliable connections cannot create duplicate financial or operational records.
These limitations are presented openly so visitors can understand where the project works well, what it depends on, and what may change in future versions.
Current status
Private client build with verified development backend flows. The current release demonstrates the core value of the project and the main end-to-end experience.
My role was client product architecture and full-stack engineering, covering multi-tenant operations, billing rules, authentication, localization, and cross-platform delivery. The related case study explains the decisions and delivery process in greater depth for visitors who want the engineering story behind the product.