MamaMatch AI removes the friction between donor intent and maternal health impact — connecting everyday givers to the right partner faster, and bringing them back with personalized context that makes every next gift count.
Most proposals address 1-2 challenge areas. This addresses all three as interdependent layers — each strengthens the others.
The gap: Donors want to give but feel paralyzed by 50+ organizations — most leave without giving.Helps donors navigate a complex, multi-layered cause. AI identifies donor preferences — country, type of support, and urgency — and matches them to 1-3 partners whose work resonates. Turns "I want to help mothers" into "Here's the organization doing exactly what you care about."
The gap: Donors on a partner page have intent but not enough conviction — last-mile hesitation is where donations die.Establishes a clear, simple pathway from motivation to meaningful contribution. AI-driven personalization across channels — seasonal campaigns, donor re-engagement, targeted outreach — makes the act of giving easier for everyday donors across different countries and communities.
The gap: Giving is often a one-time action. Donors lack clear pathways to deepen their impact, access information, and maintain an ongoing connection to the mothers they support.Based on data on where donations went, combined with public health data models, our AI solution will provide the donor with impact estimates and suggestions on how to make deeper, transformational change.
All three moments are shown below.
MamaMatch AI guides donors three ways: a Direct Match for donors with a partner in mind, a Guided Match (cause + region + urgency), or region-first browsing. Every path is designed so partner relationships are protected and donor intent is honored.
Scope note: the Year 1 chatbot is English-only. Multilingual support (Arabic, Urdu, French, Indonesian) requires cultural-register advisors and is out of scope for this grant — tracked as complementary-funding work.
The matching engine is deterministic — rule-based filters, mortality ranking, Zakat eligibility flags. The AI has one job: when a donor types instead of clicking. That first free-text message is where intent is fragile, phrasing is unpredictable, and keyword routers break. The AI extracts what it can, asks only for what's missing, and hands off to the rule-based engine. These examples show the full range of what it handles.
When a donor types instead of clicking, the AI is what prevents the "I don’t understand" dead end. It reads intent, fills in gaps, answers questions — then hands the rest to the rule-based engine. The structured flow handles the journey. The AI handles the door.
The donor journey doesn't end at checkout. On a donor's return visit (7+ days later), MamaMatch AI recognizes them via client-side localStorage and opens with a personalized follow-up — limited to the same device and browser without cleared history. Two post-donation features close the loop from barrier "Understanding impact" and "Knowing what to do next."
Stored under mamamatch.donations — partner slug, amount, timestamp, impact string. No email, name, or device fingerprint.
Longitudinal partner outcome reporting — where partners submit updated field data months after a gift — is out of scope and requires complementary funding. Year 1 delivers three things: the immediate post-donation message in chat, the Ramadan return recognition via device memory, and the 3-month follow-up email — all generated from data captured at checkout, with no partner data submission required.
Three months after donating, donors receive a personalised impact email grounded in donation-time data: the partner they supported, the country context, and the impact estimate generated at checkout. Content is built from donation data (amount, partner, timestamp from the secure payment processor), a conversation summary compressed into topic tags at session end, and country context from the partner selected — no name, device fingerprint, or browsing history is used, and no new partner data submission is required.
A snapshot built from the data captured when you gave in Ramadan 2026. No new partner data was required.
The email is scheduled at the moment of donation and sent automatically 90 days later. All content — the impact estimate, country context, and partner summary — is drawn from data captured at checkout. No partner data submission is required for this email to send.
Every estimate combines four inputs: (1) the partner's output count — how many PPH bundles delivered, CYP provided, attended births, etc., reported by the partner (captured once, usually from the existing Every Pregnancy dashboard; no longitudinal re-submission required); (2) the partner's reported cost-per-unit for the specific intervention, so each dollar can be attributed to a defensible output share; (3) a published effectiveness coefficient from a peer-reviewed RCT or Cochrane meta-analysis; (4) a country mortality baseline from IHME Global Burden of Disease (free, public, annually updated). The calculation method is the Lives Saved Tool (LiST) from Johns Hopkins — the same standard used by UNICEF, WHO, UNFPA and GiveWell. When the partner's output maps to a validated coefficient, MamaMatch AI shows both the modelled lives-saved estimate and the partner's reported activity. When it doesn't, the activity is shown on its own without a modelled estimate. Every modelled figure passes a four-condition validity gate and is clearly labeled as a projection, not a measured outcome.
A $50 gift is not a dedicated bundle purchase. It enters the partner's program and is allocated alongside all other funds received. The impact estimate is a proportional attribution — your gift's share of the partner's reported program work at their reported cost-per-unit. Industry standard: MSI Reproductive Choices, UNFPA and GiveWell use the same convention.
Every figure shown is labeled as a modelled estimate — never a measured outcome, never a dedicated-commodity claim. The chatbot passes the donor's selected cause to the donation record so the partner can allocate it appropriately within their program.
Uncontrolled bleeding after childbirth causes ~27% of all maternal deaths. The E-MOTIVE bundle (oxytocin + tranexamic acid + guided response) cuts severe PPH by 60%. Partners report: bundles delivered + country. Everything else is public data.
Both were originally developed with Bill & Melinda Gates Foundation funding — IHME Global Burden of Disease (founded 2007 with a $105M Gates grant) and LiST (Lives Saved Tool, built at Johns Hopkins with Gates support as part of the Lancet Child Survival Series). LiST is now the standard used by UNICEF, WHO, UNFPA and GiveWell. When a Gates reviewer reads "we apply LiST methodology with IHME country data," they recognize it — it is the same standard their program officers use internally. This makes estimates auditable, not proprietary.
If any condition fails, show the partner's reported activity count and program description — never a fabricated modelled number.
| Intervention | Evidence | Effectiveness | Primary Source |
|---|---|---|---|
| PPH Bundle (E-MOTIVE) | RCT | 60% reduction in severe PPH | Nature Medicine 2024, E-MOTIVE trial · N=10,000+ across Kenya, Nigeria, South Africa, Tanzania |
| Antenatal Corticosteroids | Cochrane | 30% reduction in neonatal deaths | Cochrane CDSR 2020, McGoldrick et al. — 27 RCTs |
| Kangaroo Mother Care | Meta-analysis | 20–41% reduction in neonatal deaths | Cochrane 2023, Conde-Agudelo & Díaz-Rossello |
| Modern Contraception | DCP3 Model | 38/100K maternal deaths averted per 1% coverage gain | Ahmed et al. 2012, Lancet · LiST methodology · IHME GBD cause fractions |
| Skilled Birth Attendant | Multi-country | 21% reduction in neonatal deaths | Lee et al. 2011 · meta-analysis |
| Obstetric Fistula Repair | Clinical series | 65% quality-of-life improvement post-repair | WHO 2018 clinical guideline; Arrowsmith et al. fistula outcomes |
All effectiveness coefficients are from peer-reviewed published sources. Applied via LiST methodology with IHME GBD country-specific baselines. Estimates are labeled as modeled projections, not clinical claims.
Six workstreams that turn a working prototype into a production AI system — from infrastructure to measurement. Each phase builds on the last; the knowledge base and partner data pipeline feed every downstream component.
Language scope: Year 1 build is English-only. Multilingual support (Arabic, Urdu, French, Indonesian) is treated as complementary-funding work — it requires faith-literate translation and cultural-register advisors, not just language-pack swaps.
Data protection. The chat conversation never collects personally identifiable information — donors type causes, regions, urgency, and amounts; never names, emails, addresses, or payment details. Personally identifiable information is collected only at checkout under the existing Every Pregnancy privacy notice, stored in encrypted columns separate from conversation traces and analytics events. The language model never receives personally identifiable information — personalized follow-up emails are filled server-side from a deterministic template using checkout data, not generated by the model from donor records. Donors can request deletion via the existing Every Pregnancy data-rights endpoint. Country-level IP geolocation is used for analytics only (country only, no precise location, no linkage to donor identity) and is disclosed in the privacy notice.
Accessibility. MamaMatch AI is built to WCAG 2.1 AA — full keyboard navigation, screen-reader-compatible chat stream, AA color contrast, and visible focus indicators across every interactive element. The interface is mobile-first: chat layout, touch targets, and impact-estimate cards are designed for narrow viewports and low-bandwidth mobile connections, which is the actual context most global-south donors reach Every Pregnancy from.
The design test would be three-layer validation (AI evals + A/B + phased rollout) paired with four-aspect measurement (volume, size, completion rate, impact accountability) to measure the success — and donor–AI interactions generate actionable learning for the philanthropic sector.
impact_gate_result event with {pass, failed_condition} per completed donation