LaunchGood — Case Study

$495K surplus. 46% more donations. Three giving systems unified.

$495K
Giving-pool surplus (vs. $600K deficit prior year)
46%
Increase in average donations
37%
Drop in scheduling-related support tickets
Higher avg donation with flexible scheduling
2 wks → 1 day
Campaign setup time
9+ weeks
Dev time saved per cycle (Builder.io)
Role
Design-Led Product Manager
Timeline
6 months
Company
LaunchGood
Team
PM, PD, Engineering, Data, Marketing
LaunchGood Ramadan giving preferences interface

The problem

LaunchGood had three separate scheduled-giving systems that worked independently but didn't talk to each other. Donors navigated between them depending on how they wanted to give — but the systems weren't built around how donors actually think. The result: a $600K giving-pool deficit the prior year, high support volume, and a campaign setup process that consumed engineering time every single cycle.

“I want to give during the last 10 nights specifically, but the system makes me choose all 30 days.”

— Donor

“Every year we're rebuilding the same thing. We can't experiment or iterate. We're just trying to get it working in time.”

— Engineering team

What I owned

  • Systems design: mapped the three existing giving flows and identified consolidation points.
  • Cross-functional leadership across engineering, data, marketing, and CX.
  • Shipped smart tips and flexible "specific days" scheduling into the unified giving flow.
  • Builder.io integration enabling self-service campaign configuration — no dev required per cycle.
  • Mentored a product designer on this project while leading it cross-functionally.

Key decisions

Decision 1

Unify three systems — don't improve three systems

LaunchGood had three separate scheduled-giving systems that worked independently but didn't talk to each other. Donors navigated between them depending on how they wanted to give. The answer wasn't to fix each one — it was to consolidate into a single flow with smart scheduling built in.

Decision 2

Flexible "specific days" scheduling over all-or-nothing

Donors wanted to give during specific nights (e.g., the last 10 nights of Ramadan) — the old system forced all-30-days or nothing. The new flexible scheduling option became the highest-performing giving mode, averaging 2× the donation amount of the legacy model.

Decision 3

Builder.io integration for self-service campaign ops

Campaign configuration previously required engineering involvement each cycle — 2+ weeks of setup time, ~60 hours of manual work. Integrating Builder.io gave the ops team self-service control, cutting setup to 1 day and saving 9+ weeks of dev time per cycle.

Outcome

  • $495K giving-pool surplus — a swing from a $600K deficit the prior year.
  • 46% increase in average donations within 3 months.
  • 37% drop in support tickets related to donation scheduling.
  • 2× higher average donation among donors using the new flexible specific-days scheduling option.
  • Campaign setup time cut from 2+ weeks to 1 day, saving ~60 hours of manual work per cycle.
  • 9+ weeks of development time saved per cycle via Builder.io self-service integration.
← All work