Fitness Training Platform

Pranav was stuck at a classic non-technical founder bottleneck: he had a strong idea for a platform that personal trainers and clients could both use, but no way to turn it into a working system.

His biggest barrier was design and structure: "The biggest challenge was understanding the features and UI… trying to figure out what would be a good and easy-to-navigate web design for users."

Existing no-code tools didn't provide the flexibility or backend logic he needed. He knew the platform should exist — but not how to start building it in a way that wouldn't become bloated or confusing.

His goal was straightforward: "To create a working web portal for my idea that both personal trainers and users can utilise."

In the early scoping discussions, what stood out to Pranav was how quickly the core of the idea crystallised. Instead of drowning in optional features, the process focused on identifying the essential first version — the smallest complete system that trainers and clients could both use meaningfully.

He describes the early meetings this way: "The initial discussions were quite smooth. The Zorentia team was able to understand and note down the main points of my idea, as well as what an MVP needs to function."

One piece of documentation played a major role: "I found the MVP scope document… really helpful. It clearly outlined the MVP deliverables and the development process."

The delivered MVP included: a functional PT dashboard, a clean, easy-to-navigate interface, user → trainer communication flows, essential PT–client interactions, and a WhatsApp integration he hadn't originally considered but found valuable.

He highlighted one specific enhancement: "The addition of a WhatsApp interaction button… I didn't think of it, but it's quite useful and would help communication between users and PTs."

And on the interface itself: "I found the PT dashboard quite user-friendly and easy to use." The MVP included everything he had identified in the initial meeting: "Yes, the MVP had all the features I discussed during the initial meeting."

Pranav found the feedback cycles clear and helpful: "Getting input at key points helped me stay on track and avoid going off scope. I was distracted by a lot of useless features… but the teams's input and focus on launching the MVP and gaining traction were quite helpful."

He also appreciated how Zorentia managed project momentum: "Your timely feedback has helped prevent scope creep and kept the project on track for delivery."

On UI/UX: "The UI and UX are clean, with core principles well applied to make user testing seamless."

He feels confident using this MVP to test the market: "I feel quite confident using this MVP to gather initial customer feedback. It captures the core idea well and gives me a good starting point to gain traction."

Pranav now has: a functional product ready for testing, a clear understanding of what belongs in later versions, a focused pathway to gather user feedback and traction, and a foundation he intends to build on, not discard.

The MVP's structure gives him clarity on what to prioritise next — rather than drifting into unnecessary features. His next steps are grounded in validation, not assumptions.

He closes his feedback simply: "Nope, I am very happy with the MVP."