The full story
The challenge
The founders of Bloom Wellbeing had done the hard thinking. They understood the problem their product solved, had spoken to potential users, and had a clear picture of what the first version needed to do. What they did not have was a technical team to build it.
They had considered hiring. The timeline and cost did not work for where they were. They needed something live before their early audience’s interest moved on.
The brief was tight but sensible. User registration and a structured onboarding flow. A subscription model with a free trial period. A set of daily check-ins and health tracking features built around their specific methodology. A clean, accessible experience on both iOS and Android.
No scope creep. No version-two features sneaking into version one. Just a product that worked, felt considered, and gave real users a reason to come back.
The solution
We scoped the MVP in the first week and agreed on what was in and what was not. That single decision made everything else faster. Every question that came up during development had a clear answer: in scope or later?
The build used a cross-platform approach so that iOS and Android could be delivered without doubling development effort or timelines. The architecture was set up to scale, so adding features after launch would be straightforward rather than requiring a rebuild.
The onboarding flow was designed to minimise drop-off. Short, purposeful, and guiding users directly to the part of the product where they get value fastest. Subscription payments run through Stripe, with a free trial period that converts automatically at the end. The payment logic was tested thoroughly before launch, including edge cases around cancellations, failed payments, and upgrade paths.
Health tracking was built to the Bloom Wellbeing methodology directly. We did not adapt a generic framework and hope it fit. We built to the brief.
We reviewed progress with the founders each week. Nothing appeared on their screen for the first time on a handover call. Feedback was worked into the build continuously, which meant the final product matched their vision rather than approximating it.
The result
The product went live fourteen weeks after the first briefing session. The first user cohort was onboarded in the week of launch using the same flow that all future users would go through. No manual workarounds. No placeholder features. A real product.
Subscription revenue started from the first week. The Stripe integration handled sign-ups, trials, and conversions without any manual intervention.
Bloom Wellbeing had something they could demonstrate to investors, talk about publicly, and learn from in production. An MVP should be a platform for learning as much as a platform for users. Both happened here.
Fourteen weeks is not a shortcut. It is what focused scope, clear decisions, and disciplined development makes possible.
If you have a product idea and need a technical partner to take it to market, we can help you scope it.
What changed
After go-live, the shift showed up in the week first. Then it showed up in the numbers. Here is what that looked like on the ground.
from initial brief to production launch
with Stripe fully integrated and tested
with the full onboarding flow in place
How we approached this