Key technology: Ruby on Rails, PostgreSQL, AngularJS, Salesforce Marketing Cloud, Redis, Elasticsearch, Google BigQuery, Wordpress, Locomotive CMS, MongoDB, Chargify, Paypal, Facebook, MyFitnessPal, Fitbit, Withings, Brightcove, Online Payment Systems,
One of Australia’s most successful and enduring health & fitness products, featuring a comprehensive fitness and nutrition program created by celebrity trainer.
What started life as a basic MVP is now a fully fledged lifestyle platform, with thousands of active members at any one time. Members sign-up for a 3 month “round” which gives them access to a personalised weekly plan for exercise, meal planning and mindset. Members feel fully supported on their transformation journey with tailored dynamic content, including a weekly motivational video session with Michelle Bridges.
It’s all digital - no physical meals, meetings, DVDs etc. You pay to join, then set up your goals (eg: “I’d like to lose 5kg for my wedding in March”). Based on who you are and what you’re trying to achieve, you can then pick from a menu of programs - weight loss, running, strength and so on. Everyone starts with 4 weeks of Pre-Season, which is all about getting prepared. Then you go into 12 successive weeks of training and nutrition. Everyone starts together at the same time, and progresses through at the same pace.
We started on this way back in 2011. Back then there was a basic MVP built with a CMS, that was having some pretty significant growing pains. Which isn’t unusual - a big part of MVP is working out what you don’t know. We rebuilt the tech stack in Ruby on Rails over about 10 weeks, including a new payment system and a more evolved management system.
One of the interesting things about working on this project is that they have a very large group of highly engaged members, each of which is on a quite personal journey. There are a lot of them, they seem to use it pretty much all the time, and they are highly passionate and involved with the product.
All of which means we get pretty immediate feedback. And if you’re going to ask for feedback, you’d better be prepared to do something about it. I won’t bore you with details, but one morning we pushed a new feature. It became quickly apparent that while they liked some parts, other bits (that we’d de-prioritised) were in fact required. We scrambled and got two teams (front end and back end) working on an update, which we pushed out later that afternoon. I’m glossing over a few things here, like the reason that we were able to build and release a significant update quickly was partly due to all the foundation work before - the boring stuff like an automated test suite, continuous integration, and seamless “no downtime” deploy flow.
Anyway - back to the actual product. Probably the best way to check it out is to sign up yourself. You never know - you might really enjoy yourself! I actually was talking to a someone the other day who had signed up as a way of evaluating our work, and he ended up doing 3 rounds.