Investor Brief · Part 2

Competition: the landscape and where we win

The menopause space is crowded on the patient side and empty on the provider side. Pause-Health.ai claims the provider/payer category before incumbents can pivot in. Every claim about our own capability carries a today/planned pill so you can read plan-vs-reality at a glance.

Landscape

Six categories — and where each sits relative to us

DTC menopause brands

Midi Health, Evernow, Alloy, Winona, Versalie

Primary audiencePatients directly (subscription telehealth + RX)
StrengthBrand recognition and patient demand. Beautiful consumer UX. Have de-stigmatized menopause conversations.
WeaknessCash-pay or limited insurance; capture only the ~10% of women willing to pay out-of-pocket. No integration with the patient's actual longitudinal record.
Overlap with PauseLow — different buyer, different funding source

Employer-benefits platforms

Maven Clinic, Carrot, Progyny, Kindbody

Primary audienceSelf-insured employers, increasingly carrying menopause
StrengthStrong distribution into Fortune 500. Comprehensive women's health benefits across fertility, maternity, menopause.
WeaknessMenopause is one of many lines; not the focus. Most rely on a network of contracted clinicians rather than augmenting the patient's existing provider.
Overlap with PauseMedium — we could plug INTO these platforms as the clinical decision layer rather than competing on benefits brand

Specialty menopause clinics

Independent NAMS-certified practices, hospital midlife clinics

Primary audiencePatients with means and motivation to seek out a specialist
StrengthDeep expertise. Trusted relationships. Often early adopters of new tooling.
WeaknessCapacity-limited; thousands exist, but cannot scale to the ~50M women who need this care.
Overlap with PauseLow — they are buyers, not competitors. Pause amplifies their reach into general OB/GYN and primary care.

EHR-embedded clinical AI

Abridge, Suki, DeepScribe, Nuance DAX

Primary audienceHealth systems, broadly
StrengthStrong EHR integration story. Documented productivity wins.
WeaknessHorizontal: scribes and notes, not condition-specific clinical reasoning. Not a menopause product.
Overlap with PauseAdjacent — coexists. We integrate into the same EHRs but solve a different problem (clinical reasoning, not transcription).

Disease-specific clinical AI

Cleerly (cardiology), K Health (primary care), Aidoc (radiology)

Primary audienceHealth systems and specialty service lines
StrengthProves the model: vertical AI products that win because they go deep into one condition.
WeaknessNone are focused on menopause — the category leader is open.
Overlap with PauseValidating precedent — establishes the buying motion for condition-specific provider AI.

Generalist LLM offerings

Foundation-model providers selling 'healthcare' SKUs

Primary audienceHealth systems experimenting
StrengthPowerful base models. Cheap experimentation surface.
WeaknessNo menopause-specific grounding, no clinical workflow, no evidence base, no integration. Pilots stall.
Overlap with PauseLow — they're a substrate, not a competitor. We build on top of best-in-class foundation models.

Capability matrix · with status pills on Pause

What we have today, what is roadmap

Pills: Shipped wired in prototype today · Today · partial partial today · Planned roadmap / design-partner stage.

Capability	Pause-Health.ai	DTC menopause	Employer benefits	EHR clinical AI	Generalist LLM
Menopause clinical depth	Today · partialPurpose-builtGrounding corpus + Care Router are menopause-scoped; clinical depth deepens as guideline corpus expands.	Limited — visit-level	Partial — multi-line	No	No
EHR-integrated (FHIR / SMART)	PlannedRoadmapSalesforce-side prototype today; SMART-on-FHIR Epic + Cerner apps are roadmap (see /proposal/integration).	No	No	Yes	No
Wearable + PRO integration	PlannedRoadmapDossier surfaces wearable signals via mocked Data 360 today; HealthKit/Health Connect ingestion is roadmap.	Partial	Partial	No	No
Explainable, evidence-grounded recommendations	ShippedGuideline retrieval, liveWired in prototype: every dossier + routing decision cites the federated grounding source (Salesforce, Data 360, mocked SWAN/biobank). Try /demo/intake.	No	No	Partial	No
Sold to providers + payers (not patients)	ShippedYes — B2B by designGTM motion targets IDNs, value-based payers, and AMCs (see /proposal/customers). No DTC.	No	Employer-paid	Yes	Variable
Outcomes telemetry / continuous learning	Today · partialTrace plane shippedAgent Fabric trace plane logs every Care Router decision today (/demo/agent-fabric). Outcomes registry is design-partner-stage (see /proposal/agent-fabric and /proposal/strategy).	Limited	Limited	Limited	No

Why we win

The five compounding edges

Vertical depth in menopause that horizontal scribes and generalist LLMs cannot reach.
B2B provider + payer go-to-market — durable contracts vs. churn-prone DTC subscriptions.
Patient timeline that merges wearable, PRO, and EHR data into a single clinical picture.
Explainability by construction — every recommendation cites the guideline and the data point.
Outcomes registry built into every deployment — compounding evidence advantage.

What we don't claim today

The boundaries of our story

A sophisticated reader will pattern-match a pre-revenue clinical-AI deck against three over-claims. We name them up front instead of getting asked.

We do not have FDA-cleared softwareOur roadmap targets clinical-decision-support that is intentionally non-diagnostic and stays inside CDS Hooks / FDA Software-Functions guidance. Class II/III claims would be Year 2+.
We are not a live SMART-on-FHIR Epic app todayThe integrated-EHR posture is a roadmap commitment. Today the prototype runs against Salesforce + mocked Data 360 (see /proposal/integration).
We do not have first-party outcomes dataThe outcomes registry is a design-partner-stage artifact. Year 1 evidence is co-built with first IDNs/payers; we don't pretend to have it on day one.
We are not a competitor to scribes — we coexistAbridge / Suki / Nuance solve documentation. We solve menopause-specific clinical reasoning. Both can install in the same system without conflict.
We are pre-revenue and pre-design-partnerYear 0–3 milestones, status-tagged per stage, are detailed at /proposal/strategy. No signed customers yet.

Read deeper

How the matrix lines up with the architecture

Technology stackPer-layer status pills on every stack claim — model, data, fabric, frontend.
Integration architectureHow the SMART-on-FHIR commitment is structured, and what is live vs roadmap.
Agent FabricThe trace-plane that backs the “outcomes telemetry” row of the matrix. See the live trace.
Strategy · moats + outcomes registryHow the outcomes registry compounds into the moat we claim, with status pills per stage.
Customer selectionWho the matrix is written for — IDNs, value-based payers, AMCs.