Case study · limited disclosure
PinaFit
An end-to-end gym operations platform for reservations, members, resources, and administration.
Recreated visual for portfolio presentation. Not the original production interface.
Disclosure: This case study uses approved high-level product information. No private customer data, internal metrics, or production screens are shown.
Context
PinaFit is an end-to-end gym management platform that brings class reservations, resource availability, member workflows, and administration into one product surface. This case study is intentionally limited to approved, high-level product information.
Problem
Reservation products are deceptively complex. A clear booking interaction depends on consistent schedules, capacity rules, user state, administrative controls, and feedback when availability changes. The challenge was to make those constraints understandable to members while keeping operations manageable for staff.
Role and responsibilities
Jairo owned product and engineering decisions across requirements, architecture, implementation, data modeling, and delivery. That meant treating customer and administrator workflows as one connected system, rather than as separate screens.
Product decisions
The interface emphasizes the next useful action: discover availability, understand the reservation state, and complete or adjust a booking. Administrative workflows organize operational information around decisions instead of exposing the underlying data model directly.
Technical decisions
The system separates reservation rules from interface components so capacity and eligibility behavior can be tested independently. Shared typed contracts keep customer-facing and administrative states aligned. Data boundaries are organized around members, schedules, resources, and reservations.
Quality strategy
Quality work focused on predictable state transitions, explicit error feedback, responsive layouts, accessible form controls, and maintainable domain logic. Private metrics and production architecture are not included here.
Outcome
The result is a production platform supporting real gym operations and a foundation that can evolve without rewriting each workflow independently. Exact usage and business metrics remain unpublished until approved for public disclosure.
Lessons
End-to-end ownership is most useful when product language, data constraints, and interface behavior are designed together. In operational software, clarity is a reliability feature.