There's a quiet fork happening in health-AI naming right now, and most founders aren't paying attention to it until they've already picked a name.

On one side: companies building clinical decision support, hospital workflow tools, prior authorization automation. Their buyers are procurement teams. The naming logic is mostly institutional — clear, credentialed, forgettable in the right way.

On the other side: companies going direct to consumers. Symptom checkers. Medication trackers. Mental health intake tools. Insurance navigation assistants. These products sit in people's phones, next to their banking apps, and they're asking questions that feel more personal than almost anything else a piece of software asks.

That second category has a branding problem that isn't really about branding. It's about trust infrastructure — and the domain is the first piece of that infrastructure a user encounters before they've opened the app.

The consumer health context has changed

HIPAA compliance is table stakes, not a differentiator. Users know this. What they've become more attuned to — especially after a decade of data broker stories and post-Dobbs conversations about medical data and law enforcement — is who is actually holding this data and what does their name tell me about their values.

That's an unfair amount of weight to put on a company name and domain. But it's the weight being put there.

When someone is using an app to track a chronic condition, or to figure out whether a symptom is worth a doctor's visit, or to navigate Medicare Advantage plan options during open enrollment, they're not in a purchasing mindset. They're in a vulnerable one. The name and domain are doing emotional work that founders trained on B2B naming instincts often don't account for.

What this means for naming choices

Consumer health products are starting to bifurcate along a specific line: names that signal capability versus names that signal custody.

Capability names lean into what the product does. Think anything with "health," "care," "med," "rx," "symptom," "check" in the root. These are search-friendly and literal. They work well for SEO-driven acquisition and exact-match search behavior — a point worth taking seriously if you're targeting the health category of the domain market, where exact-match domains in Medicare Advantage and chronic care verticals have held value precisely because users search literally.

Custody names signal something different. They emphasize that the company is a steward of your data, not just a processor of it. Words like "vault," "private," "shield," and "own" start appearing. These names trade SEO clarity for trust positioning.

The collision is coming because most early-stage consumer health companies pick a capability name (it tests better in early user research, when people are evaluating the feature), and then discover — usually at the Series A or when a PR story goes sideways — that they need to make a trust argument they don't have the naming infrastructure to support.

Why domains are harder to fix than messaging

You can update your website copy in an afternoon. Changing a domain after you have users, app store listings, insurance partnerships, and a HIPAA BAA trail is a different kind of project. It affects link equity, email deliverability history, legal filings, and — in health specifically — potentially the CMS plan finder listings and broker portals that drive Medicare Advantage enrollment.

This is the same dynamic that makes exact-match health domains valuable as portfolio assets: they're hard to replicate after the fact, and the cost of not having the right one compounds over time rather than staying flat. If you're evaluating assets in this space, the /domains portfolio has a few worth looking at through this lens.

The practical question for founders

Before you finalize a consumer health product name, ask not just "does this describe what we do" but "does this domain pass the late-night vulnerable-moment test" — would someone using your app at 2am about something that worries them feel like they're in a place that takes their data seriously?

If the answer requires explaining, the name is doing too little work.