- 10
- sprints from kickoff to beta
- ~15 min
- of founder time per week
The story
Regent is a marketplace where personal trainers meet their clients. Trainers publish their sessions, clients book them, and money moves inside the app through a built-in wallet. The founder wanted the whole product designed and built from nothing, and started with a free assessment and discovery phase before committing.
The hard part was not the feature list. It was the edge cases. Almost every screen touches real money, and sessions run on waitlists, so if scheduling is a few minutes off, a trainer loses a paid session. That is the one thing Regent exists to prevent. We mapped every payment, scheduling and notification flow end to end until each edge case was covered.
We delivered booking, the wallet and payments, face verification, workout and meal plans, chat, a dispute process and an admin panel in 10 sprints. The founder spent about 15 minutes a week on the project, and we absorbed change requests without adding to that. Regent is now live on the App Store.
What was hard, and how we solved it
Problem
Scattered booking
Trainers juggle sessions across chats, calls, and notes, so slots get missed or double booked.
Payment risk
Cash and off-app transfers leave both sides unprotected when a session is cancelled or disputed.
Plans lost in chat
Workout and meal plans get buried in message threads, so clients lose track of what to do next.
Solution
Built-in booking
Clients book and manage sessions with their trainer directly inside the app.
Wallet and disputes
Payments run through an in-app wallet with a dispute system, so both sides are covered.
Plans in one place
Trainers assign workout and meal plans that clients can open any time.
Inside the app
