HerPattern

The description states:

• HerPattern is a personalized symptom-forecasting platform for people living with endometriosis and related hormonal health conditions.
• Users record daily information such as pain, fatigue, sleep, stress, cycle phase, medication, and other symptoms.
• The system analyzes these patterns and estimates the user’s likely symptom burden for the following day.
• It provides uncertainty ranges, trend visualization, symptom-state tracking, and voice-based summaries.
• It is designed as a planning and research-support tool, not a diagnostic or replacement for professional medical care.

The platform uses:

• Hierarchical Bayesian autoregression
• Switching state-space model
• CatBoost
• OpenAI for explanations
• ElevenLabs for optional voice summaries

Inference: The product is built to be a daily tracking and forecasting tool, not a clinical diagnostic system. It emphasizes personalization and transparency in its outputs.

The description states:

• HerPattern aims to turn daily symptom tracking into personalized insights.
• It is positioned as a planning and research-support tool, not a medical device or diagnosis platform.
• The authors emphasize that it is inspired by real people’s experiences, not technology alone.

Inference: The positioning has evolved from a personal project rooted in empathy to a technical solution for a specific health condition, with an emphasis on user experience and responsible data use.

The description states:

• HerPattern is designed for people living with endometriosis and related hormonal health conditions.
• It targets users who are tracking symptoms daily and want to plan ahead based on predicted symptom burdens.

Inference: The target customer is a woman or person with endometriosis, likely in a recurring, fluctuating symptom pattern, who seeks personalized insights for daily planning and possibly research participation.

The description states:

• No pricing information is provided.
• No evidence of revenue streams or monetization strategy.
• The platform is described as a planning and research-support tool, not a commercial product.

Inference: There is no evidence of a business model or pricing structure. The project appears to be in an early prototype stage, with no indication of how it would generate value or income.

The description states:

• Built using Lovable for interface and user journey.
• Uses statistical modeling techniques: hierarchical Bayesian autoregression, switching state-space model, CatBoost.
• Integrates OpenAI for explanations and ElevenLabs for voice summaries.
• The system separates model output from user-facing language, to avoid presenting predictions as medical conclusions.

Inference: The technical stack is moderate complexity, involving machine learning models and integration with AI services. It shows a clear intent to build a user-centric, explainable system rather than just a black-box prediction engine.

The description states:

• Team size: 0
• No mention of customers, users, or adoption.
• No evidence of revenue, ARR, or funding rounds.
• The project is described as a hackathon submission, not a commercial product.

Inference: There is no evidence of traction. The product is at an early stage and lacks any indication of user engagement or market validation.

The description states:

• No mention of competitors.
• No evidence of existing solutions in the market for personalized symptom forecasting in women’s health.

Inference: The competitive landscape is not evidenced, but it likely includes other symptom-tracking apps, wearable devices, and health platforms. However, no direct comparison or differentiation from existing tools is provided.

The description states:

• No team size or members listed.
• No evidence of revenue, customers, or traction.
• The project was built under strict hackathon constraints, which may limit long-term viability.
• The system is described as a planning and research tool, not a clinical solution.

Inference: Key risks include:

• Lack of team or execution capability beyond the hackathon phase.
• No commercial traction or monetization strategy.
• Unclear path to scaling from prototype to product.
• Potential regulatory or ethical concerns in health tech without clinical validation.

1. What is the current status of the project beyond the hackathon? Is it being developed further?
2. How are you planning to validate the forecasting accuracy with real-world data?
3. Have you engaged with endometriosis patients or clinicians for feedback and usability testing?
4. What is your plan for building a sustainable business model or revenue stream?
5. How do you intend to handle privacy, data ownership, and ethical concerns in health data collection?