Launching a Women’s Health Startup

Create inclusive participant criteria and a recruitment screener for people with varied heavy-flow experiences.

Prepare an informed-consent script and conversational boundaries for sensitive reproductive-health interviews.

Write a behavior-focused interview guide that avoids leading participants toward the proposed solution.

Conduct and document a semi-structured customer interview about current behaviors, unmet needs, and workarounds.

Separate observations, participant interpretations, and founder assumptions in an evidence repository.

Code customer-interview notes to identify recurring behaviors, needs, triggers, and workarounds.

Construct candidate customer segments based on need intensity, context, and behavior rather than demographics alone.

Map the current heavy-flow management journey and the jobs customers are trying to accomplish.

Triangulate interview findings with credible secondary evidence about heavy-flow experiences and care pathways.

Select an initial beachhead segment using evidence strength, problem severity, accessibility, and founder fit.

Generate multiple solution concepts that address the validated customer job without presuming an app is the best answer.

Write a value proposition for the beachhead segment that links a specific need to a credible benefit.

Translate the value proposition into measurable user behaviors and product outcomes.

Prioritize candidate features according to customer value, assumption risk, and validation cost.

Define a narrow minimum viable product and the specific hypotheses it is intended to test.

Distinguish general-wellness functionality from functionality that may trigger US medical-device scrutiny.

Classify proposed product statements as educational information, wellness guidance, or medical claims requiring stronger substantiation.

Identify which major US health-data privacy requirements may apply to a direct-to-consumer prototype and where legal advice is needed.

Create a minimized data-flow map for sensitive menstrual information across collection, storage, use, and deletion.

Define content-review, uncertainty, and escalation rules for communicating health information without diagnosing users.

Map direct competitors, indirect alternatives, and existing customer workarounds by the job they perform.

Estimate the initial market opportunity using a transparent bottom-up model and explicit assumptions.

Distinguish the user, customer, payer, influencer, and clinical stakeholder roles in the proposed business model.

Compare plausible revenue models using willingness to pay, accessibility, trust, and strategic fit.

Create a testable business-model hypothesis covering acquisition, delivery costs, pricing, and retention.

Specify the prototype's core user flow, screen states, acceptance criteria, and excluded functionality.

Use Claude Code to scaffold and run a simple responsive web application in a version-controlled project.

Implement a mobile-friendly flow for recording synthetic or locally stored cycle and flow experiences.

Implement a non-diagnostic summary and reminder experience using transparent rules and safe placeholder content.

Inspect AI-generated code, diagnose common browser errors, and make targeted corrections.

Deploy a testable prototype that uses no real participant health data and clearly communicates its experimental status.

Design a concept and usability test that separates problem, value-proposition, usability, and trust questions.

Facilitate and document a prototype test without selling the concept or interpreting feedback defensively.

Analyze test evidence to identify validated assumptions, contradictions, usability failures, and unresolved risks.

Revise the venture thesis, minimum viable product, and business model in response to accumulated evidence.

Make a documented persevere, pivot, pause, or stop decision and create a 90-day validation roadmap.