How We Built a Women's Wellness App MVP in 6 Weeks (and What We Cut)

The situation

A founder came to me with a women's wellness app called CherryStripes. Journaling, menstrual cycle tracking, breathwork exercises, and calming music -- all in one app. She had already tried building a version before. It didn't work out. So we were starting from zero with a hard deadline: six weeks to a working product.

The challenge

Wellness apps have a scope problem. Meditation timers, habit trackers, community forums, in-app purchases, personalized recommendations -- every feature sounds reasonable on its own. The founder had a long list. My job was to cut most of it.

The hard part wasn't code. It was deciding what the app needed on day one versus what it could become in month three. We had to pick the features that would get real women to open the app daily and ignore everything else. That meant some tough conversations early on about what "done" actually looks like when you have six weeks and a budget that doesn't stretch to eight.

What we built -- and what we didn't

Four core modules: journaling, menstrual cycle tracking, guided breathwork, and a calming music player. That was it. Each one simple, focused, and solid. No bells, no extras.

Here's what we deliberately cut:

Live chat support. The founder wanted in-app messaging from day one. I pushed back. You don't need live chat when you have 20 users. Email works fine. Live chat adds build complexity and creates an ongoing support burden before you even know if people want the product.
A shopping list feature. Tied to a future wellness product marketplace. Cool idea, wrong time. Building e-commerce into a wellness app MVP is a fast way to blow your timeline on something nobody asked for yet.

Those cuts saved us about two weeks. That time went into polishing the four features that actually mattered.

The result

The first 20 users confirmed what I suspected: nobody missed live chat or the shopping list. Dead weight. But something unexpected happened. Users started asking for a "challenge a friend" feature -- a way to invite friends to complete breathwork or journaling streaks together. We built it. That single feature, one that wasn't in the original plan, took the app from 20 users to over 100 in three weeks.

The lesson

Your first users will tell you what to build next -- but only if you ship fast enough to ask them. Every feature you add before launch is a guess. Some guesses are expensive. The founders who win launch with less, listen, and build the thing their users actually want -- not the thing they imagined in a planning doc six months ago.

I offer a free 30-min call to review your idea and tell you exactly what I would and wouldn't build first. Book it here