For health-tech and mental health founders
Find out which parts of your health app you can ship now and which need a specialist first
Everything in the MVP Planning Sprint, plus the mapping health products need: where your intended use ends, what sensitive data and claims you're taking on, where the product could touch crisis or clinical situations, and when a lawyer, clinician, security assessor or regulatory consultant has to be involved. This is planning. It isn't legal advice, a clinical opinion or a certification.
What you get
What’s included
Everything in the MVP Planning Sprint
Problem definition, user flows, MVP scope, prioritised backlog, release roadmap, architecture options, risks, acceptance criteria and a build estimate.
Intended-use boundary
A written line between what the product does and what it must never claim to do, so a wellness app doesn't drift into medical-device territory by accident.
Sensitive-data inventory
Each piece of health-related data the product would collect, where it goes, and which items carry obligations.
Claims inventory
The statements your app and marketing want to make, listed in one place, with the ones that need a specialist's review flagged.
Crisis and clinical dependency map
Where a user could reach a crisis, a clinical decision or a provider workflow, and how version one routes around those paths until a specialist has approved them.
Specialist decision points
The points on your roadmap where a privacy lawyer, clinician, security assessor or regulatory consultant needs to be engaged, in order, so you can budget for them in advance.
A good fit if
- Founders building mental health, therapy-adjacent or wellbeing apps
- Wellness and fitness brands adding features that record mood, symptoms, sleep or cycles
- Health-tech teams who need to know which features need specialist review before they budget the build
- Founders who've been told to "just avoid medical claims" and want a more precise answer than that
Not included
- Legal advice, a clinical opinion or regulatory sign-off
- HIPAA, FDA or any other certification. We map where those questions apply; specialists answer them.
- Drafting your privacy policy, terms of service or consent wording
- Building any part of the product
How it runs
From kickoff to handover
- Days 1 and 2
Problem, users and intended use
We define what the product is for and who uses it, and write the first draft of the intended-use boundary.
- Days 3 and 4
Data, claims and crisis paths
We list the data you'd collect and the claims you'd make, and trace where users could reach crisis or clinical situations.
- Days 5 and 6
Scope, backlog and architecture
Version one gets scoped to the side of the boundary you can ship now, with backlog, roadmap and build options to match.
- Day 7
Specialist plan and handover
We sequence the specialist decision points on the roadmap and walk you through the full set of documents.
Questions
Questions about Healthtech & Mental Health MVP Blueprint
Is this a HIPAA compliance assessment?
No. The Blueprint shows which data and features raise HIPAA or similar questions for your product, so you know what to take to a privacy lawyer or compliance specialist. It doesn't certify anything, and we say so in writing.
My app is for meditation or habits. Do I need the Blueprint or just the sprint?
It depends on what the app records and says. If it tracks mood or symptoms, mentions anxiety, depression or other conditions, or could be used by someone in distress, the Blueprint is the safer plan. A simple timer or habit tracker with no health claims usually only needs the sprint.
What does the crisis map cover?
The points where a user in distress could reach your product, what the product does at that moment, and which of those paths version one should avoid until a clinician has reviewed them. It's mapped to your own flows, so the answer is specific to your app.
Can I hand the documents to a lawyer or clinician?
Yes. The inventories and decision points are written so a specialist can read them as a briefing, instead of you explaining the product from scratch in a paid meeting.
Why does it take seven days instead of five?
The extra two days go to the data, claims and clinical mapping. That work has to settle before the scope does, because it decides which features belong in version one.
More from Product Strategy
Keep exploring
Often paired with this
Work with us
Ready to start Healthtech & Mental Health MVP Blueprint?
Tell us about your business. We'll confirm the scope and send you a start date.