Databricks Healthcare Global

Flo Health

Marketing Personalization · Real-time Analytics

Flo Health needed a better way to support women's health predictions, experimentation, and self-service analytics because a decentralized analytics estate could not keep up with the scale, experimentation cadence, and product intelligence required by tens of millions of users.

400 increase in internal monthly active users of the platform
45% building a better future for female health
46% analytics experiments run per quarter

Reported impact

Business outcome

Flo Health improved women's health predictions, experimentation, and self-service analytics with measurable results including 45% building a better future for female health, 400 increase in internal monthly active users of the platform, and 46% analytics experiments run per quarter, while giving teams a faster path from governed data to production decisions.

  • Customer Experience
  • Productivity Improvement
  • Scalability

Solution

Flo Health uses Databricks Data + AI Platform to support women's health predictions, experimentation, and self-service analytics. The implementation replaced a legacy state where a decentralized analytics estate could not keep up with the scale, experimentation cadence, and product intelligence required by tens of millions of users. Health app events and cycle and symptom data move through Lakeflow Jobs and land in Delta Lake, giving teams one trusted data foundation. Unity Catalog governs access, lineage, and compliance across sensitive datasets. Databricks SQL, MLflow, and Genie operationalize models, agents, and analytics that deliver health predictions and recommendations and product experiment insights.

Data flow

Health app events and cycle and symptom data land on a shared platform, pipeline services clean and standardize them, governance controls enforce trusted access, and AI, model-serving, and analytics services deliver health predictions and recommendations and product experiment insights.

Solution architecture

8 components · 5 layers
  1. Compute
    • Databricks Data + AI Platform Databricks Data + AI Platform unifies engineering, analytics, governance, and AI workloads for women's health predictions, experimentation, and self-service analytics.
    • MLflow MLflow tracks experiments, versions, and release workflows for models that support women's health predictions, experimentation, and self-service analytics.
  2. Storage
    • Delta Lake Delta Lake stores curated health app events and cycle and symptom data so every team works from one trusted data foundation.
  3. Serving
    • Databricks SQL Databricks SQL serves curated dashboards and ad hoc analysis to health predictions and recommendations and product experiment insights.
    • Genie Genie gives business users natural-language access to governed data for faster decisions around women's health predictions, experimentation, and self-service analytics.
    • Agent Bricks Agent Bricks packages domain-specific agents that automate parts of women's health predictions, experimentation, and self-service analytics.
  4. Orchestration
    • Lakeflow Jobs Lakeflow Jobs schedules ingestion and transformation of health app events and cycle and symptom data into reusable datasets.
  5. Governance
    • Unity Catalog Unity Catalog applies centralized access controls, lineage, and auditability across sensitive datasets.

Architecture clues

  • 45% building a better future for female health
  • Automated ingestion and transformation pipelines keep source data synchronized for downstream analytics and AI.
  • Centralized governance, lineage, and access controls are enforced through Unity Catalog.
  • Delta Lake provides the shared storage layer for curated lakehouse datasets.
  • Operational AI workflows are deployed directly beside governed data and analytics assets.

Evidence from the source

Databricks enables us to innovate without limits. The scalability and security have been game changers for our team,
Our previous systems couldn’t handle the scale and complexity of our data. Databricks provided the centralized platform we needed to innovate faster,
The ability to run experiments at this scale has fundamentally changed our approach to product development,
What is our MAU for last month?
Transparency Evidence & methodology 100/100 reference value · 89% confidence · 1 source

Review how this reference was scored and trace each normalized claim back to its documented source.

01

Scoring methodology

How scores are calculated

Customer Reference Value measures usefulness as a customer reference. Evidence Confidence measures the quality and traceability of available evidence, not independent verification.

Customer reference value100/100
  • Problem clarity20/20
    Measures whether the customer's operational problem is specific enough to compare.
  • Implementation depth25/25
    Rewards named components, data flow, integrations, and architecture detail.
  • Outcome specificity20/20
    Measures whether the reported benefit is concrete rather than a generic claim.
  • Quantified impact25/25
    3 metrics describe measurable impact.
  • Deployment scale10/10
    Rewards evidence of a live or scaled deployment and meaningful integration scope.
Evidence confidence89%
  • Source authority20/25
    The main evidence is an official vendor-published customer story.
  • Claim traceability21/25
    10 of 12 key fields link to a named source.
  • Direct evidence20/20
    4 direct source quotes retained.
  • Date provenance10/10
    The publication date comes from the source page or publisher.
  • Source transparency8/10
    1 source reference document publisher, URL, authority, retrieval, and supported fields.
  • Implementation specificity10/10
    Rewards source-backed components, data flow, quantified impact, and a specific outcome.
02

Traceability

Sources & provenance

Field coverage shows which facts each source supports. Dates are shown only when documented by the source.

  1. Databricks

    Flo Health customer story

    First-party
    https://www.databricks.com/customers/flo-health
    Source type
    Vendor-published customer story
    Published
    Mar 10, 2025
    Supports
    • Customer
    • Business problem
    • Solution
    • Products
    • Solution components
    • Data flow
    • Integrations
    • technical area
    • use case category
    • Business outcome
    • outcome category
    • Metrics
    • Architecture
    • evidence quotes
    • Publication date

Date evidence

  • Published on source page Mar 10, 2025 · Databricks · First-party
    Open date source
Not separately sourced Industry, Region, Company size. Treat these normalized attributes as lower-confidence until a dedicated source is added.