Independent trainers run their whole schedule over WhatsApp. Turni is a scheduling and payments tool I designed to make that simple, one product for the trainer and the student. I did the brand, the design system, and the UI, and built realistic prototypes in Figma Make that a developer turned into the React build.
Turni started from talking to a lot of independent instructors, gym trainers, tennis coaches, all kinds. They were juggling the same things: scheduling clients over endless WhatsApp threads, sending reminders by hand, and keeping track of payments on the side. Coordinating a single time slot could take a dozen messages.
There are tools for this, but most felt built for features rather than for the person using them, with little thought given to the actual experience. And few fit the Argentine market well, where there's real room for something simple.
The core pain wasn't a missing feature. It was time. Independent instructors run their own admin, and the back-and-forth eats into the hours they could be teaching. The basics they actually needed were simple: reminders over WhatsApp, and a clear handle on payments.
So the goal for Turni was narrow on purpose: cover those basics really well, and make the experience feel calm and obvious instead of piling on options.
Turni is one product with two sides. Trainers get a dashboard to manage their agenda, their students, and their class packs. Students sign up, either to recurring packs or class by class, depending on how each trainer works.
The idea was to keep both sides light. The trainer shouldn't need training to run it, and the student should be able to book in a few taps.



I worked on the whole thing end to end: the brand and visual identity, a small design system to keep it consistent, and the full UI for both the trainer and the student sides. Instead of writing the code myself, I built realistic prototypes in Figma Make and handed them to a developer, who built it in React. That's where my frontend background paid off, I could prototype interactions that felt real and hand off something a developer could build straight from.
Keeping a design system even on a small product meant the two sides felt like one thing, and changes stayed cheap to make.



I tested Turni with real trainers across different disciplines and watched them move through it. The response was strong: more than one asked when they could start using it for real. For a product built by one designer and one developer, that told me we had read the problem right.
Turni is the project where my background comes together most clearly. I framed the problem from real conversations, designed the brand and the system, and created the screens end to end.
It also taught me to keep scope honest. The product worked because it did a few important things well, not because it tried to do everything.
Turni didn't reach the market in the end. It stayed a validated prototype, but it's still the project that shows most clearly how I work: from a problem, through brand and system, to something real enough to put in front of people.