goodDeeds

The engagement spanned the full product ecosystem: a native iOS app, a native Android app, and a custom CMS for the goodDeeds team to onboard families, verify them through nonprofit and school partners, manage item requests, and track orders end to end. Three surfaces, one system, and no room for the family-facing side to feel like an afterthought. Our first directive was to remove cash from the equation. Families request specific items such as groceries, baby supplies, and household essentials through trusted retailers, and donors fulfill those items directly. That single decision resolved the trust problem and the stigma problem simultaneously. Donors know exactly what their contribution provides because they picked it off a list. Families aren't asking for a handout, they're sharing a need. Second, we designed for browsing, not pledging. The donor feed had to make choosing a family feel intuitive and personal rather than overwhelming, with matching driven by location, urgency, and the causes a donor gravitates toward. Fulfillment had to collapse into a familiar checkout flow measured in seconds, because friction is where good intentions die. Third, we built the proof loop. Every goodDeed is tracked from purchase through delivery confirmation and surfaced back to the donor as a running record of families helped and items delivered, with streaks and impact tracking to turn a one-time gesture into a habit. Behind it, the CMS gives the team the operational spine to keep verification, requests, and order status accurate at volume. It is the unglamorous layer that makes the transparency claim actually true.