Case study · public disclosure
PinaFit
An end-to-end gym operations platform for reservations, members, resources, and administration.
- Active users
- Hundreds Jairo Rauda Resume 2026, supplied and approved for this update on 2026-08-08.
Recreated visual for portfolio presentation. Not the original production interface.
Disclosure: Product facts and the active-user range are sourced from Jairo's approved 2026 resume. The visual is recreated; customer data and production screens are not shown.
Product context
PinaFit is an end-to-end gym management platform for class and resource reservations, member management, role-based administration, and operational dashboards. It serves hundreds of active users.
Responsibility
Jairo leads the product and engineering lifecycle: requirements, project scoping, architecture, data modeling, implementation, cloud deployment, client communication, release planning, iteration, and post-launch support.
This ownership connects decisions that are often separated. A reservation rule affects the member experience, staff operations, data consistency, administration, and support at the same time.
Product challenge
The platform has to make availability and reservation state clear to members while giving staff control over schedules, resources, users, and operational work. Capacity, eligibility, roles, and changing availability must remain consistent across customer and administrative surfaces.
Delivery decisions
- Organize the product around member and operator decisions instead of exposing database structure.
- Treat schedules, resources, members, and reservations as connected domain boundaries.
- Keep role-based access and validation explicit across customer and administrative workflows.
- Deliver bounded workflows iteratively so real operational feedback can shape the next release.
- Include performance, accessibility, SEO, security, and maintainability in the delivery process rather than treating them as final-stage checks.
Result
PinaFit is a production platform supporting real gym operations for hundreds of active users. Its shared product and data foundations support reservations, administration, user management, and continued iteration without treating every workflow as a separate system.
What this demonstrates
The project demonstrates independent product ownership rather than isolated feature implementation: understanding operational needs, translating them into a maintainable system, releasing it, and continuing to support it after launch.