NUTRISYNCBuilders Hub
🏠 🛠
NUTRISYNC · Docs

NutriSync — Product Requirements Document (Phase 1 Beta)

Tagline: Hormonal care made easy — sync your cycle, fuel your mind. Document owner: Product (Lucia Cebrian, COO) Status: Built · Phase 1 beta · Live web app + native apps sharing one backend (July 2026)


1. Problem

Healthcare and mainstream nutrition were designed around male biology. Men run on a roughly 24-hour hormonal cycle; women run on a roughly 28-day cycle with four distinct phases (menstrual, follicular, ovulatory, luteal). "One-size-fits-all" diet and training advice ignores this, leaving women to self-experiment with food and movement across phases — with the cost showing up as later diagnoses, worse outcomes, and everyday frustration.

The opportunity: the FemTech market is projected to grow from roughly US$10B (2018) toward roughly US$70B by 2030 (Grand View Research). Existing apps (Flo, Clue, 28, Flo Living) lead on period tracking but only partially cover science-backed cycle-synced nutrition, integrated movement, personalization, and clinician-partnered distribution. That gap is NutriSync's wedge — and, crucially, we now have a working product occupying it rather than a pitch deck describing one.

2. Vision

A cycle-synced nutrition and movement intelligence companion that adapts daily food, training, and wellbeing guidance to where a woman is in her cycle — grounded in clinical evidence, personalized to her own logged data, and backed by community. The product's core intellectual property is the CAS (Cycle Alignment Score): a single, explainable 0–100 number that tells a user how well her day aligned with her current phase, and recomputes in real time as she logs.

3. Target users

Primary persona — "Olivia," 25–45, cycle-aware self-optimizer. She already tracks her period, exercises, and cares about nutrition, and she is tired of generic advice. She wants to know what to eat and how to move today, given her current phase, without doing the research herself.

Secondary personas: - Women with cycle-related symptoms (PMS, low energy, bloating) seeking relief through nutrition and movement. - B2B end-users: female employees reached through employer wellness programs (€35–€50 per employee/year is the B2B unit).

Validation to date: 120+ interviews, an early cohort of 100 women (96% cycle-aware, 86% engaged), and 13K+ content views. The current phase moves validation from interviews toward in-product behaviour, with the beta instrumented to observe real logging and CAS engagement.

4. Goals & success metrics (Phase 1 beta)

The product is built, so success metrics now frame the beta: are real users logging, and does the CAS keep them coming back? These are the north-star signals we watch during the Madrid tester cohort and early beta.

Goal Metric Beta target
Daily relevance D7 / D30 retention D7 ≥ 40%, D30 ≥ 20%
Habit formation Logging streak (meals / symptoms / movement) ≥ 3 days/week median
Engagement WAU / MAU ≥ 45%
CAS engagement Users who see their score move after logging majority of active users each session
Monetization signal Free → premium intent ≥ 10% (deck assumption, to be validated)

North-star metric: weekly active women completing ≥1 phase-aligned action (logged a recommended meal, completed a movement item, or read phase guidance) — the action that both drives the CAS and signals real habit.

5. Scope — what is built

The app is now effectively 1:1 with the Figma prototype. Every screen below is built, functional on live data, and wired to the Supabase backend and the CAS engine. The same backend powers both the native mobile apps and the live web application, so a user's cycle, logs, and score are identical wherever she signs in.

5.1 Onboarding — built

Welcome → Auth (sign up / sign in) → a multi-step Wizard that captures cycle data (including the critical last period start date), health, nutrition preferences, NutriGoal, Nutri avatar, city, and consent. Answers persist to users and cycles, so every downstream recommendation is filtered to the individual from the first session.

5.2 Daily gate — built

A "Before we Sync" mood/energy gate that appears once per calendar day on first open, feeding the CAS biomarker and logging components.

5.3 Main tabs — built

5.4 Edit Period — built

Real Figma emotes, flow droplets, and symptom logging (mood-state, pain, digestion, cravings, sleep, energy, and more) writing to daily_logs and feeding biomarkers.

5.5 Edit Health / Health Profile — built

A NutriGoal carousel (locked until two full cycles are completed), Allergies chips, and Health Conditions chips, writing to users.nutrigoal / allergies / health_conditions.

5.6 Notification Center — built

A live feed computed from real cycle, phase, and logging state — phase tip, check-in nudge, today's score, and milestones — reached via the 🔔 on the home header. Nothing here is canned; it reflects the user's actual state.

5.7 Settings — built

A Settings hub plus Personal Information, Sign-in & Security, Data Privacy (JSON export + delete account), Community Privacy, Notifications & Reminders, Choose Your Nutri, App Preferences (units, week-start, haptics, appearance — saved on-device), and Nutritional Preferences (diet type + allergies, written to users).

5.8 Visual polish — built

The official Figma NutriBubble orb appears throughout, alongside an animated "looking-around" branded loading screen and real Figma emotes. Poppins is the app-wide typeface; brand orange is #FF5509 with an orb gradient #FF9269 → #FF5509.

Intentionally deferred (known non-Figma gaps): wearable connectors (native-only, roadmap 2028) and 2FA / passkeys.

6. Non-goals (still out of scope)

7. Cycle-sync content model (the core IP)

Guidance adapts to the user's menstrual phase, and phase boundaries personalize from her own logged cycle data rather than a fixed 28-day assumption. Under the hood the CAS uses five internal phases (menstrual, follicular, ovulatory, early_luteal, late_luteal); the user sees four display phases.

Display phase Approx. days Colour Nutrition focus Movement focus
Menstrual 1–5 #E8472A Iron, warming foods, hydration Gentle movement, rest
Follicular 6–13 #6B9E6B Fresh/light, complex carbs, protein Build intensity, strength
Ovulatory 14–16 #D4A017 Anti-inflammatory, fiber Peak performance, HIIT
Luteal 17–28 #7B5EA7 Magnesium, complex carbs, mood support Steady-state, deload late

The phase is derived as cycleDay = today − last_period_start + 1, wrapped to cycle length. Everything on Home, NutriLog, Movement Log, and the Notification Center keys off this. Content is reviewed by the clinical advisor (Constanza Ramirez Milli) and evidence-tagged before publish.

8. Compliance, safety & trust

9. Monetization (context for product gating)

10. Release plan (current reality)

  1. Phase 1 beta (now, July 2026): the full screen set is built and live. Native iOS + Android apps and the web application share one Supabase (EU) backend and the same CAS engine. The web app and marketing site are live on Cloudflare Pages; both mobile and web ship continuously via automated CI/CD (mobile OTA via EAS Update, web via Cloudflare Pages). The immediate focus is remote testing with the Madrid tester cohort (Android APK is the recommended distribution; iOS TestFlight is gated on paid Apple Developer enrollment) and instrumenting the beta metrics above.
  2. Hardening: complete the data-protection layer (full auth-record deletion, consent/cookie surface), wire the admin MIS/KPI console to live data, and add observability.
  3. 2027 roadmap: EU expansion, stronger B2B/seat management, menopause module, deeper personalization.
  4. 2028 roadmap: wearable connectors (native dev build) and US market entry.

11. Open questions