Anthropic Nonprofit Burkina Faso

International Rescue Committee

Real-time Analytics

IRC teams needed to analyze frontline health data quickly enough to influence staffing, outreach, and supplies, but the information came from ministry-run facilities in inconsistent paper and Excel formats and often had to be used in low-connectivity environments.

4+ hours per month saved by half of surveyed pilot users
Offline HTML dashboards covering more than 15 core health and reproductive health indicators
Under 30 minutes to prepare management-ready analysis that previously took a full working day

Reported impact

Business outcome

IRC reduced management-ready analysis from a full working day to under 30 minutes, saved every surveyed pilot user time, and used the dashboards to validate youth outreach, uncover prenatal-care gaps, and catch infection trends early enough to adjust staffing and supplies.

  • Productivity Improvement
  • Risk Reduction

Solution

IRC used Claude Enterprise to create a lightweight offline analytics workflow instead of trying to standardize every upstream data source. In Burkina Faso, staff compile aggregate facility data into Excel and drag those files into a single HTML dashboard template generated and refined with Claude. The template covers more than 15 core health and reproductive-health indicators, runs locally without coding or internet connectivity, and keeps data off Claude's servers. Because the dashboard is just one portable HTML file, measurement specialists and health teams can adapt it in natural language instead of waiting for engineers. The same locally loaded data then supports cross-facility trend analysis, portfolio-level synthesis, and investigations into service gaps, outreach effects, or emerging infection spikes.

Data flow

Facility data moves from paper registers or DHIS-2 into local Excel files, staff drag those files into an HTML dashboard template generated with Claude, and the offline output surfaces indicator trends and anomalies for health teams to discuss and act on locally.

Solution architecture

1 components · 1 layer
  1. Serving
    • Claude Enterprise Generates and iterates the offline HTML dashboard workflow used by frontline health teams.

Architecture clues

  • Claude helps teams customize visualizations without bringing engineers into every change.
  • The dashboard is a single HTML file that runs locally with no connectivity.
  • The workflow uses aggregate facility data rather than individual patient records.

Evidence from the source

A drag-and-drop workflow where staff load facility Excel files locally, no connectivity or coding required
Across three health facilities, the dashboard flagged STI consultations among people under 18 jumping from an average of 21 per month to 88
No connectivity or coding is required, and the data is not sent externally or stored on Claude’s servers.
Offline HTML dashboards covering more than 15 core health and reproductive health indicators
One program user now prepares analysis and slides for senior management in under 30 minutes, work that previously took a full day.
Transparency Evidence & methodology 95/100 reference value · 79% 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 value95/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 scale5/10
    Rewards evidence of a live or scaled deployment and meaningful integration scope.
Evidence confidence79%
  • 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
    5 direct source quotes retained.
  • Date provenance0/10
    The publication date has no documented provenance.
  • 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. Anthropic

    International Rescue Committee customer story

    First-party
    https://claude.com/customers/irc
    Source type
    Vendor-published customer story
    Supports
    • Customer
    • Business problem
    • Solution
    • Products
    • Solution components
    • Data flow
    • Integrations
    • technical area
    • use case category
    • Business outcome
    • outcome category
    • Metrics
    • Architecture
    • evidence quotes

Date evidence

  • First archived Oct 4, 2026 · Internet Archive · Independent First Wayback Machine capture; confirms the page existed by this date, not when it was published.
    Open date source
Not separately sourced Industry, Region, Company size. Treat these normalized attributes as lower-confidence until a dedicated source is added.