CycleSync — the spec

CycleSync is a SaaS client portal for small teams (2–10 people) that connects each member's hormonal phase data to a shared calendar, surfacing energy-aware guidance so the team can schedule work around biological reality rather than against it. It targets team leads and individual contributors who want to stop fighting their cycles and start planning with them.

---

Decisions locked

---

The core loop

1. A team member logs in and enters today's cycle day plus their current hormonal phase (menstruation, perimenopause, or menopause).
2. CycleSync maps that input to a pre-defined energy profile for that phase and day range.
3. The portal displays a personalised energy-level summary for the current day and the week ahead.
4. The user's connected Google Calendar or Outlook calendar renders alongside the energy summary, highlighting where high-demand events land on low-energy days.
5. The user receives in-app prompts suggesting how to approach today's workload given their phase.
6. The team view (visible to permitted members) shows an aggregated, anonymised energy overlay so the team lead can spot low-energy clusters before scheduling.

---

v1 scope

Phase & cycle day entry
A daily check-in form where the user selects their phase and enters their cycle day. This is the front door of the product; every other feature depends on data entered here. Lives on the Dashboard screen.

Calendar integration (Google Calendar and Outlook)
OAuth-based read/write sync with both platforms. Pulls existing events into the portal view and writes energy-context labels back to calendar entries. Lives on the Integrations settings screen and surfaces throughout the Calendar screen.

---

Deliberately later

• Cycle logging with predicted phase timeline — prediction accuracy earns trust; introduce it once baseline phase entry is validated with real users.
• Personal energy-level forecast by day — requires enough logged history per user to be credible; premature in week one.
• Team energy heatmap overlay on calendar — high-value feature, but consent and privacy UX must be solid before team-level visibility ships.
• Meeting-rescheduling suggestions for low-energy clusters — depends on heatmap data and calendar write patterns that v1 is still establishing.
• One-click task intensity labeling system — useful workflow tool; scope it after the core energy-guidance loop proves sticky.
• Privacy-first data controls (no identifiable sharing) — the policy must exist from day one, but granular user-facing controls belong in a dedicated privacy settings release once the data model is stable.
• Weekly energy-planning email digest — retention mechanic; build it once there is enough per-user history to make the digest meaningful.

---

Data model sketch

• users — id, name, email, team_id, phase_type (menstruation / perimenopause / menopause), created_at
• cycle_entries — id, user_id, cycle_day, phase, logged_at, energy_profile_id
• energy_profiles — id, phase_type, day_range_start, day_range_end, energy_label (high / moderate / low), guidance_text
• teams — id, name, owner_user_id, created_at
• team_members — id, team_id, user_id, visibility_consent (boolean)
• calendar_integrations — id, user_id, provider (google / outlook), access_token, refresh_token, last_synced_at
• calendar_events — id, user_id, external_event_id, provider, title, start_at, end_at, energy_label_applied

---

Screens

• Dashboard — daily phase check-in form plus today's energy summary and week-at-a-glance.
• Calendar — synced calendar view with energy context overlaid on events.
• Team View — anonymised energy overlay across all consenting team members; visible to permitted roles.
• Integrations — connect, disconnect, and re-authorise Google Calendar and Outlook accounts.
• Profile & Settings — manage phase type, notification preferences, and account details.
• Onboarding — guided setup: phase selection, calendar connection, team join or creation.

---

How to use this document

• Bring it into Mind Palace, where the guided platform and its AI coach pick up from exactly this document and build the product with you step by step.
• Hand it to a developer as the complete v1 brief — scope, data model, and screens are all here.
• Keep it as the single source of truth throughout the build; every feature decision traces back to what is written here.