Case Study 3
Whealth —
Does this problem actually need solving?
A comprehensive women’s health app from wellness to community. Before building, I ran a structured discovery sprint to test whether the problem was real, specific, and worth building for — and to decide whether to proceed at all.
Timeline
Jan 17 – Feb 6, 2026 (3 weeks)
My role
Solo Product Builder
Phase
Discovery
Skills demonstrated
Vision and Mission Framing, User Research, Problem Framing, Prototyping, Hypothesis Testing
| ✓ Done | ✓ Done | → In progress | ◦ Next |
| Research form | Insight synthesis | Prototype & test | Go / no-go decision |
| Distributed to target users to surface needs and frustrations in the problem space. | Identified recurring themes to define the problem clearly before touching any design. | Built initial prototype to test concept resonance before committing to development. | Iterate, pursue partnerships, or kill the idea — based on evidence, not assumptions. |
The Problem I Started With
Women on different continents do not experience life in the same way, nor do they approach their mental and gynecological health in the same way. The problem is unequal access to care and to a supportive community, which could benefit those with chronic illnesses. A specific app for underrepresented communities could connect them with more privileged groups and improve their well-being and co-education.
What the Research Showed
Early responses confirmed the emotional and financial weight of the problem but also revealed the risk: the scope is broad and target users’ needs vary widely. The prototype was designed to test one specific slice of the problem — not the whole vision at once.
The Key Decision I Made
I resisted the urge to design a full app immediately. Instead, I built the minimum prototype needed to get a clear yes or no on the core hypothesis. That decision saved weeks and kept the feedback focused and usable.
Most product failures aren’t execution failures — they’re discovery failures. This project is my commitment to getting that part right first.
Whealth — What I’m Doing Next
After 5 feedback responses and no engagement on LinkedIn, here’s how I’m moving forward — and why.
| Status | Decision |
|---|---|
| ✓ Keep |
I’m not killing the idea.
The research confirmed the pain is real — emotionally and financially. What’s broken is the scope, not the insight. Abandoning the idea at this stage would be the wrong call.
|
| ↗ Rethink |
I’m narrowing the problem and the target — no more comprehensive solution.
My original problem statement covered chronic illness, mental health, gynecological health, geographic inequality, and community access at once. That’s five products in one. I’m picking the one pain that is the most frequent, most urgent, and most underserved — one persona, one problem, one context — and I’ll define a falsifiable niche hypothesis before I talk to anyone.
|
| ↗ Rethink |
I’m going deeper on market research — but with a hard deadline.
I need a clearer picture of the competitive landscape and adjacent products before I go back to users. But I’m time-boxing this to two weeks: map competitors, estimate market size, identify what existing solutions don’t do. After that, I stop desk research and start talking to people.
|
| ↗ Rethink |
I’m dropping LinkedIn forms and going where my users actually are.
LinkedIn didn’t fail because of the platform — it failed because a form link asks strangers to do work for me. I’m moving to spaces where women already talk about these issues: Reddit communities (r/PCOS, r/Endo, r/WomensHealth), Facebook groups, Discord servers, WhatsApp circles, and patient advocacy organizations. I’ll listen first, then ask for a 20-minute conversation.
|
| ✓ Keep |
I’m switching from forms to real interviews — 50 to 100 of them.
Forms gave me 5 responses and no real signal. Conversations build trust, surface nuance, and turn participants into early advocates. I’m committing to 5 interviews per week, which gets me to 50 in 10 weeks and fits within my June deadline. At interview 20, I’ll pause to synthesize what I’ve heard and adjust the niche hypothesis if the signal points somewhere unexpected.
|
| ✓ Keep |
I’m rebuilding the prototype only after the interviews — not before.
A prototype built after real patterns emerge will be nearly pre-validated. I’m not opening Figma until the interview synthesis is done. The prototype I build then will reflect what people actually said, not what I assumed they needed.
|
| ↗ Rethink |
A Bubble beta is still on the table — but only if the interviews earn it.
I won’t build a beta of a vague product. That’s how I’d end up back at the same problem. The beta decision happens in June, conditional on whether the interviews surface a problem slice specific and tight enough to build in 3–4 weeks — not because the calendar says so.
|
| + New |
I’m documenting this pivot as it happens.
A case study that shows how I discovered the prototype was too broad — and how I reframed it — is more valuable than one that pretends the path was always clean. I’m capturing decisions, reasoning, and what changed in real time. This pivot is part of the work.
|
| ◦ Timeline |
Everything wraps by end of June 2026.
March: Market research + niche hypothesis (2 weeks)Mid-March → May: 5 interviews per week Early April: Synthesis checkpoint at ~20 interviews May: Full synthesis + problem reframing Late May → June: Prototype rebuild June: Beta decision (Bubble yes or no) |
Whealth → fuchcia
After structured discovery, 5 research briefs, and a full pivot, Whealth has been renamed fuchcia — narrowed from a broad women’s health platform to a focused, AI-native app for women with endometriosis in France, with a specific lens on migrant and non-Western women. Here’s what changed, and why.
The original name covered everything — and therefore nothing. After research confirmed that the real, unmet, fundable gap was endometriosis care for migrant women in France, the scope narrowed. The name followed. Fuchcia — the c borrowed from my middle name, Francia — signals visibility, defiance, and specificity. Linked to the color fuchsia: bold, unapologetic, impossible to ignore — the color my mother dressed me in as a child, before I knew what it meant to take up space. It is not a rebrand. It is a precision cut.
| Type | Decision | Rationale | Outcome / Next action |
|---|---|---|---|
| ✓ Keep | Didn’t kill the idea |
Research confirmed real emotional and financial pain — 7–10 year diagnostic delays, structural erasure of migrant women, no culturally adapted app in France. What was broken was scope, not insight. |
Reframed the problem. Did not abandon it. Result: fuchcia. |
| ↗ Sharpen | Narrowed to one niche |
The original Whealth problem spanned chronic illness, mental health, gynecological health, geography, and community — 5 products in one. Research across Reddit, Facebook, academic papers, Ivy League and European sources identified endometriosis in migrant women in France as the most urgent, most underserved, and most defensible niche. |
Hypothesis confirmed: “Women with endometriosis in France — especially migrant and non-Western women — lack accessible, culturally adapted health support in their language.” This is now fuchcia’s mission statement. |
| ✓ Keep | Deep market research — time-boxed |
5 research briefs completed: Reddit, Facebook, Academic 2025, Ivy League, European & French. Competitive landscape mapped across 10 apps (Phendo, Clue, Lyv, ENDOless, LUNA, Flutter, MyFLO, Follow Metrios, MyEndo’App, Flo). Lyv Endo and ENDOless identified as most serious French competitors — both have structural blind spots: monolingual, monocultural, mutuelle-gated or English-only. |
Research complete. No competitor serves migrant women with endo in France in their language. Fuchcia’s gap is confirmed and unfilled. |
| ✓ Keep | Async research — no live interviews needed at this stage |
Discovery was conducted entirely through existing data: Reddit threads, Facebook groups, academic papers, app store reviews, and competitor analysis. This was a deliberate choice suited to my neurodivergent working style — zero live social exposure required, full research depth achieved. |
Live interviews were deprioritised during this period — personal circumstances made sustained outreach difficult to maintain, and I chose to keep the project moving rather than stall it. This was a deliberate choice suited to my neurodivergent working style. Async methods (Reddit, Facebook groups, academic papers, app reviews) delivered the same depth of signal without requiring live social exposure. Cultural validation surveys remain on the roadmap for the beta phase. |
| ★ New | Built PRD v1.1 from prototype |
A PRD was built directly from prototype v5 and the research synthesis — covering 15 features, AI strategy across 3 phases, GDPR compliance plan, business model (B2C freemium + B2B + Research-as-a-Service), risk register, and a roadmap to public launch Q1 2027. |
PRD v1.1 active. Status: Maze testing in progress. Next: iterate to prototype v6 based on results. |
| ★ New | Prototype built AI-native, with Claude |
Fuchcia is not an app with an AI feature. AI is the layer that makes every feature intelligent and proactive: flare prediction, personalized daily insights, auto-generated doctor summaries, Endotest eligibility guidance, smart reminders. Built entirely with Claude from the first research session to the PRD. |
AI integration roadmap defined across 3 phases: MVP (flare prediction, doctor prep), Beta (community moderation, real-time translation), V2 (conversational care agent, specialist matching). |
| ↗ Sharpen | Removed pricing from Maze test |
Prototype v4 included a full pricing/Full Access screen. This was removed in v5 and replaced with a neutral placeholder (“Full Access — coming soon / This feature is not available in this test”). Reason: price anchoring distorts usability data. When users see a price mid-task, they evaluate value instead of navigating — and drop-off data becomes uninterpretable. |
Pricing will be tested separately via Van Westendorp survey or a fake door test — not through Maze. Prototype v5 is Maze-ready. |
| ✓ Keep | Test before building |
The original Whealth plan was correct: prototype first, validate, then build. What changed is the depth of validation — Maze usability testing (task completion, drop-off, misclick rate) AND a cultural validation survey (remedies, community format, sex education tab, nutrition) before any backend work begins. |
Beta build begins Q3 2026, conditional on: Maze task completion >70% on all P0 flows, >30 cultural survey responses from target personas, all critical usability issues resolved. |
| + Add | Document the pivot as the case study |
This case study shows I discovered the prototype was too broad, narrowed it to one niche, renamed it, built a PRD, and tested it before building the full app. It is more compelling. This pivot is the work. |
You are reading it. |
| ◦ Timeline | Revised timeline to Q1 2027 |
Original June 2026 deadline was for a Bubble beta of a broad app. Fuchcia is a narrower, deeper, AI-native product. The revised timeline reflects the depth of testing required before any backend investment. |
Now (Mar 2026): Maze + cultural survey
Q3 2026: Beta build (min. viable backend + Claude API) Q4 2026: Closed beta, 50–100 users Q1 2027: Public launch Q2–Q3 2027: V2 — agentic care agent, B2B |
See something that
resonates with your situation?
I’m available for consulting engagements and open to discussing permanent PO/PM roles. Let’s talk about what you’re building.