Client and payment management without slowing down
isipici is a production PWA that centralizes clients, payments, debt, and due dates for recurring payment businesses such as gyms and clubs. It was designed to be intentionally limited and direct, covering the few daily flows that matter most, with traceability through email receipts and automated email reminders.
Client
isispici
DELIVERABLES
Mobile and web
Year
2025
Role
Prodcut designer
Context - My role - goals - pain points - user persona - solution - Project duration - team - Impact
Context
Context
In gyms and similar businesses, daily operations combine front desk tasks, recurring payments, and due date follow up, with little tolerance for complex tools. In many cases, records are split across spreadsheets, notes, and memory, which weakens traceability and allows debt to build up without clear control. After early conversations with my gym instructor and validation with other small gyms and clubs, a consistent pattern emerged: the pain was not collecting payments, it was maintaining order, clarity, and operational discipline across the same flows that repeat every day. The project also came from a personal motivation to contribute to communities with less access to well designed tools. Large companies usually have support, but smaller businesses often need the biggest push to grow. The decision was not to build something huge or paradigm shifting, but to execute what already exists with high quality, listening to real needs and shipping with focus.
My role
My role
I delivered the project end to end, from product definition and user research to brand identity, UI design, flows, implementation, and production launch. I built the PWA from scratch across frontend, backend, and database, designed the navigation and screens, implemented auth and security, integrated APIs, and set up hosting and deployment. I also designed and implemented the email layer for receipts and reminders, and ran QA to ensure stability before real world usage.
Goals
Goals
The primary goal was to reduce overdue payments and accumulated debt through a reliable and easy to read payment record. The second goal was to speed up daily operations with quick actions and screens that show only what matters for execution, reducing cognitive load. The third goal was to professionalize small businesses without technical friction, enabling fast adoption on desktop and mobile with cloud backup. The fourth goal was to improve traceability and client communication by automating receipts and reminders so order does not depend on the owner’s memory.
Pain points
Pain points
I delivered the project end to end, from product definition and user research to brand identity, UI design, flows, implementation, and production launch. I built the PWA from scratch across frontend, backend, and database, designed the navigation and screens, implemented auth and security, integrated APIs, and set up hosting and deployment. I also designed and implemented the email layer for receipts and reminders, and ran QA to ensure stability before real world usage.
User persona
User persona
The primary user is a gym or club owner or manager running recurring payments who needs a daily view of payment status and due dates, with the ability to act fast. They have limited time, switch between operational tasks and decisions, and prefer tools that are limited but dependable, with minimal learning curve. The secondary user is a front desk operator who records payments, answers questions, and updates client info during busy hours. They need speed, clear visual signals, and a flow that minimizes mistakes, because they work with constant interruptions and cannot afford to interpret or infer information.
Solution
Solution
isipici is delivered as an installable PWA with a single dashboard that brings together clients, payments, debt, and due dates. The experience is intentionally limited to avoid noise and match real workflows. On the main clients table, only the most operationally relevant data is visible. Supporting fields live in each client profile, keeping the daily view focused on execution. The primary flow is payment registration, and most of the logic and testing concentrated around it. To make status instantly understandable, I introduced a dual calendar that visually marks paid days and debt days. This allows operators to grasp history at a glance without reading long lists, reduces confusion, and enables faster answers when clients ask questions. To enforce operational discipline, the system includes clear rules. New payments cannot be registered if the client has an active debt, which makes debt settlement mandatory before continuing. This protects the operator, prevents silent debt accumulation, and establishes a rule backed by the system rather than personal negotiation. At the same time, the platform stays flexible with plans, amounts, bonuses, and date ranges to adapt to different payment models across businesses. In the background, the platform automates key communication. Email receipts are sent with plan, period, bonuses, and any debt details, and they remain logged for reference. Automated reminders are sent days before the due date, including the date and any existing debt, reducing last minute payments and minimizing manual follow up. On security, I implemented token based sessions plus a 4 digit PIN lock before showing the dashboard, designed for shared devices and to protect sensitive information without adding complex steps.
Timeline
Timeline
The project was delivered in 4 weeks, from exploration and early validation through build, QA, and production launch. The product is now used in real environments, and the current phase is focused on gathering time based feedback, observing friction in daily operations, and evolving the product without breaking the core principle of simplicity.
Team
Team
I worked solo across design and development. Validation was done with gym and small club owners who provided real operational context, domain language, and direct feedback on priorities, rules, and critical flows.
Impact
Impact
Within two weeks of the beta launch, isipici was adopted by two gyms, with more than 2,000 registered users and more than 180 active users within those gyms. The most consistent feedback was operational clarity and the peace of mind of having cloud backed records accessible on both desktop and mobile. From a perceived value standpoint, the product landed through simple but firm decisions. The calendar based status view, the no debt carry rule, and automated receipts and reminders reduce mistakes and sustain order without adding extra effort. In an environment where operations are intense and management often depends on memory or scattered tools, isipici acts as a control layer that keeps the most critical business flow consistent: collecting payments, recording them, and tracking due dates.