Software Requirements — Pregnancy & Conception Module

Vesta today is a cycle-tracking app. It helps users log periods, predict their next cycle, and understand their reproductive health — all in English and Bengali. That is a solid foundation. But it misses a huge chapter of a woman’s life: the journey from trying to conceive through pregnancy and into new parenthood.

Flo Health — the world’s leading reproductive-health app — structures its entire retention strategy around exactly this journey. Their data shows that a user who moves through “Getting Pregnant” and then “Track Pregnancy” stays engaged for roughly 18 months — six to twelve months trying, nine months pregnant — before the question of churn even arises. A pure period tracker, by contrast, faces churn every time a user’s life situation changes.

This document specifies the requirements for a Pregnancy & Conception module that extends Vesta v1. The goal is to keep a woman and her family engaged through every phase of her reproductive journey, deliver genuine value at each stage, and build a monetisation model that grows naturally with her needs.

What this module covers:

• Trying to Conceive (TTC) — fertile-window intelligence, ovulation prediction, cycle-based “best days to try,” cervical-mucus and OPK tracking, conception health content.
• Pregnancy — due-date calculation (three methods), a week-by-week gestational tracker, daily symptom logging, content guides, and safety-awareness prompts.
• Postpartum — recovery support, wellbeing, feeding guidance, newborn milestone tracking, and a smooth return to cycle tracking.
• Public calculators — bilingual, no login required, designed as a top-of-funnel growth engine.

The split between free and paid features is a commercial decision for a later stage and is intentionally left open in this brief. Where a paid tier applies, billing runs through BDApps CAAS direct debit from the user’s mobile balance — no credit card required. The public calculators (§3.4) are open to everyone and require no login by design — they are the top-of-funnel acquisition engine, not a pricing decision.

Deliberately out of scope — see §6 for rationale: fitness and yoga videos, partner sharing, wearable integrations, open community forums, clinical/hospital integrations, symptom-to-condition self-assessment, FSA/HSA reimbursement, native mobile apps, and an AI health chatbot.

The good news: this module is an extension of what Vesta already does, not a rebuild. Vesta today already ships everything these new features need to stand on. Each user account supports up to six family profiles. Every profile has its own cycle history, a three-tier prediction engine that grows more accurate over time, symptom logging (including a Discharge category that maps directly to cervical-mucus tracking), a bilingual content platform, and a full SMS/email reminder system. Subscription billing runs through BDApps CAAS. Data export already exists.

The pregnancy module plugs into all of that. The cycle ring becomes a gestational-week ring. The symptom logger gains pregnancy-specific symptoms. The content platform gains week-tagged and trimester-tagged articles. The export service gains a structured doctor report. The reminder system gains prenatal alerts.

There is also one dormant field that does useful work here. When a user signs up, Vesta asks for their goal: period tracking, trying to conceive, or perimenopause. That goal field has always been collected but never acted on. This module promotes it into a real mode — a per-profile lifecycle state that drives the entire home experience.

Each profile has a mode, and the mode determines what the home screen shows, what content surfaces, and which tools are active. Moving between modes is triggered by real life events — setting a goal, logging a positive test, recording a birth. The app follows the user, not the other way around.

The loss path deserves special mention. It is designed to be quiet and private. There is no countdown, no milestone badge, no push notification. The app simply steps back, offers support content, and waits for the user to decide what she wants to do next.

Because mode is per-profile, this module works naturally within Vesta’s existing family structure. A user can track her own pregnancy in one profile and her sister’s cycle in another — at the same time, from the same account. No new account, no new login, no data mixing. The family differentiator that already sets Vesta apart from single-profile trackers becomes even more valuable here.

A single account might carry:

• Profile 1 (self) — in Pregnancy mode, week 22.
• Profile 2 (wife) — in TTC mode, watching fertile-window odds.
• Profile 3 (daughter) — in Cycle mode, period tracking only.

All three coexist, each with its own home screen, its own content, its own reminders.

Every part of this module is built for the Bangladesh market, not translated from a Western product.

This module builds on what Vesta already has. The dependencies are:

• The existing per-profile cycle engine and prediction math.
• The existing symptom logging system (including the Discharge category).
• The existing bilingual content platform and Tiptap CMS.
• BDApps SMS and CAAS infrastructure (already integrated).
• Resend transactional email (already integrated).
• The existing data export service (extended for the doctor report).

The one cost that cannot be reused is content authoring. A full pregnancy tracker needs content for all 40 gestational weeks — baby development, body changes, weekly to-dos, FAQs — in both English and Bengali. That is the dominant downstream effort and will need a dedicated authoring and medical-review plan, likely phased by trimester rather than written all at once.

These are public, bilingual pages — no login required. They answer the most-searched reproductive-health questions with a simple, beautiful tool, then invite the user to sign up for Vesta to track their results. This is Flo’s number-one user acquisition channel, and it costs almost nothing to build because the underlying math already exists in Vesta’s cycle utilities. Each result page includes a gentle prompt to create a Vesta account to track results over time.

All seven calculators are available in English and Bengali from day one.

Priya has been using Vesta to track her periods for three months. One evening, she and her husband decide they’re ready to start trying. She opens Vesta, switches her goal to “trying to conceive,” and her home screen transforms — the familiar cycle ring now highlights her fertile window, with daily odds shown as low, medium, high, and peak. The app tells her the next two best days to try, based on her own cycle history. She starts logging her cervical mucus each morning using the existing symptom logger, and picks up a prenatal vitamin reminder through BDApps SMS. Six weeks later, her fertile-window predictions have grown more accurate as her three-tier cycle engine adds another cycle to its model.

Three months after switching to TTC mode, Priya logs a positive pregnancy test. Vesta shows a warm, celebratory transition screen, and asks for her LMP date to confirm the due date. Her home screen is now a gestational-week ring at Week 6. Each week she comes back to see what’s new — the baby’s development, what her body is doing, and a short checklist of things to think about. She logs her symptoms daily: nausea rated 7/10, fatigue 8/10. In week 12, after logging several symptoms together, she sees a calm nudge: “Some of these signs are worth mentioning to your doctor at your next visit.” She books an appointment, brings the doctor health report the app generates, and the doctor is pleased to have a clean summary. She continues through all 40 weeks.

Two days after her daughter is born, Priya logs the birth in Vesta. The app shifts quietly to postpartum mode. Over the next weeks, content covers physical recovery, feeding support, and emotional wellbeing — including a gentle reminder to talk to a professional if she’s feeling low. A simple newborn milestone tracker lets her log her daughter’s first smile and first roll-over. Four months later, she tells the app she feels back to normal, and the cycle tracker wakes up again, ready for her next chapter.

Not every pregnancy journey follows the expected path. When a user logs a pregnancy loss, Vesta responds without celebration, without a countdown, and without any intrusive prompt. A quiet, warm message acknowledges what has happened, support content is offered (emotional wellbeing, talking to a professional), and then the app simply waits. There is no pressure to choose a next step immediately. When she is ready, the user can return to cycle tracking, to TTC, or simply leave the mode as it is. The loss path is private — nothing is shared, nothing is surfaced to other profiles. The experience is designed with the understanding that grief is not a feature to be optimised.

This brief is a decision artifact. Its job is to help the product sponsor decide which features to fund and in what order. It is not any of the following:

• Detailed functional requirements — no FR-* specifications are written here. Those follow once features are approved and will be added to the main SRS.
• A change to the main SRS — SRS.md remains unchanged. This document is a companion, not a replacement.
• Code, schema, or migration work — no database changes, API contracts, or implementation decisions are made here.
• Authored content — no articles, weekly guides, or bilingual copy are produced by this document.
• Final legal wording — all medical disclaimer language in this document is placeholder. It is pending review by a qualified legal and medical advisor in Bangladesh before any feature goes to production.