Anthropic Nonprofit Burkina Faso

International Rescue Committee

Real-time Analytics

IRC wanted proof that AI could turn inconsistent frontline health data into useful local decision support despite electricity constraints, poor connectivity, and ministry-defined indicators that varied across facilities.

2,700+ health facilities across 40 countries
20 minutes to create HTML dashboards in Claude
close to 23,000 healthcare facilities in sub-Saharan Africa that have the same problem

Reported impact

Business outcome

The Burkina Faso pilot showed that IRC teams could create dashboards in about 20 minutes, adapt them without engineers, and give nearly 3,000 facilities facing similar constraints a repeatable way to turn local data into faster program decisions.

  • Productivity Improvement
  • Risk Reduction

Solution

The IRC Q&A describes the Burkina Faso pilot as a deliberately simple, chat-built analytics system on Claude Enterprise. Rather than redesigning upstream collection, the team focused on one variable: visualization. Measurement specialists and health teams use Claude to create and revise an HTML dashboard template around the indicators they already track, then send the lightweight file to facilities where local Excel data can be dropped in with no internet connection. The team explicitly notes that they did this in chat, without Claude Code, which made it practical for non-engineers to adapt the dashboards themselves. That combination of local files, natural-language customization, and repeated facility-level use turned a previously manual reporting process into a reusable pattern that can scale across thousands of sub-Saharan health facilities facing the same data problem.

Data flow

Facility staff enter aggregate figures into paper registers and Excel, IRC teams use Claude to build an HTML dashboard template, and each site loads its local Excel file into the template to produce charts and summaries offline for local health discussions.

Solution architecture

1 components · 1 layer
  1. Serving
    • Claude Enterprise Lets IRC staff build and modify offline health-data dashboards directly in chat.

Architecture clues

  • Facility teams can adapt the HTML template themselves with natural-language changes.
  • The dashboard workflow was built directly in chat rather than with Claude Code.
  • The same pattern is intended to scale across many sub-Saharan facilities with low connectivity.

Evidence from the source

20 minutes to create HTML dashboards in Claude
It’s close to 23,000 healthcare facilities in sub-Saharan Africa that have the same problem.
Then they can take their Excel file from that local facility and just drag and drop it in there. No connectivity needed.
We just did it in the chat. We didn’t even need Claude Code
When you consider that nearly 3,000 health facilities across sub-Saharan Africa face the same data challenge, what works in Burkina Faso has the potential to change how health teams across the region use data.
Transparency Evidence & methodology 90/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 value90/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 impact15/25
    1 metric describe measurable impact.
  • Deployment scale10/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-qa
    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 Sep 28, 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.