Launching a Digital Health App in the US: FDA Readiness and Go-to-Market

I led the launch and FDA readiness work for Polyfins Technologies, a healthtech startup in San Francisco, and for Eczemaless AI, a skin and dermatology digital health app. Both taught me the same lesson: in digital health, regulatory strategy and go-to-market strategy are one plan, not two. The claims you want to make in your marketing decide how you are regulated, and the evidence you build for regulators becomes your most persuasive marketing.

Here is the sequence I recommend to founders preparing a US launch.

1. Define what your product does, in the regulator's eyes

Everything starts with the intended use: what the product does, for whom, and what decision or outcome it supports. The same app can be a low-risk wellness product or a medical device, depending on what it claims.

• Software as a medical device. The FDA regulates software that meets the definition of a medical device. Its digital health guidance explains which software functions it focuses on, and where it does not intend to enforce requirements for low-risk products, such as many general wellness apps.
• Clinical decision support. Software that supports clinicians' decisions has its own FDA guidance, and small changes in how recommendations are presented can change the answer.
• Pathways. Regulated products usually follow one of three routes: 510(k), which shows substantial equivalence to a device already on the market; De Novo, for new low-to-moderate-risk devices; or premarket approval for higher-risk devices.
• Ask early. The FDA's Q-Submission program lets you request feedback on your plans before you file. It is one of the best investments a startup can make.

Write the intended use statement first, then make sure every marketing claim fits inside it.

2. Build the evidence plan early

Evidence has two audiences: regulators and the clinicians and patients you want to win.

• Technical and clinical validation that the product does what you claim, in the people you claim it for
• Usability testing with real users, because a product that is misused is not safe or effective
• For AI features: representative training and test data, performance reported across relevant subgroups, and a plan for updates. In dermatology, that means performance across skin tones, not just on average. FDA guidance on predetermined change control plans lets AI-enabled devices describe certain future model changes upfront.
• Publications and real-world evidence that clinicians can check for themselves

3. Put quality, security and privacy in place

• Quality management. Design controls, risk management and a documented software lifecycle are the backbone of any submission. The FDA's Quality Management System Regulation, aligned with the international standard ISO 13485, took effect in February 2026.
• Cybersecurity. Premarket submissions for connected devices must now include cybersecurity information, such as a plan to monitor and fix vulnerabilities and a software bill of materials.
• Privacy. HIPAA applies when you work with healthcare providers and health plans, and the FTC's Health Breach Notification Rule covers many consumer health apps that HIPAA does not. State privacy laws add further rules.

4. Take the product to market without breaking the rules

• Claims discipline. Before clearance, do not promote a device as safe or effective for its intended use. You can still build awareness of the problem, tell your company story and recruit for studies.
• Know your buyers. Patients, clinicians, health systems, employers and payers each need a different story and different proof.
• Win clinicians with evidence. Advisory boards, publications, conference presence and peer recommendations matter more than ads.
• Earn patient trust. Plain-language explanations of what the app does and does not do, transparent data practices and accessible design.
• App stores. Apple and Google review health and medical apps more strictly, and may ask for regulatory documentation.

5. A launch timeline

1. 12 months or more before launch: intended use, regulatory pathway, pre-submission meeting, evidence plan and quality system.
2. 6 months before: validation and usability studies, cybersecurity documentation, a claims framework for marketing, and a clinician advisory group.
3. Launch: clearance where required, a staged rollout, clinician education, content and PR, and app store optimization.
4. After launch: post-market monitoring, complaint handling, real-world evidence, and product updates within your approved change process.

A founder's checklist

• Is the intended use written down, and does every claim fit inside it?
• Do we know our regulatory pathway, and have we asked the FDA for feedback?
• Does our evidence cover the people we claim to serve, including skin tones, ages and conditions?
• Are quality, cybersecurity and privacy built into the product, not added at the end?
• Do clinicians and patients each have a clear reason to trust us?

Regulatory requirements depend on your product and claims, so work with qualified regulatory and legal advisers. If you are preparing a US or Gulf launch for a digital health product, see how I lead healthcare marketing and work as a fractional CMO.