We debated these honestly. Not every answer is comfortable. Some are unresolved. That's the point — we'd rather surface the hard questions now than discover them after launch.
The line between inspiring and guilt-tripping is thin. We stay on the right side by: no kid photos on the cancel screen, no "if you cancel Daniel suffers" framing, no CTA or renewal prompt on the letter view — just the letter and "thank you."
The kid speaks in his own words. We don't editorialize. If our guardrail metrics detect "guilt" sentiment in cancellation reasons or support tickets, we kill it immediately.
It's real. Real kid, real letter, real handwriting, real foundation. We link to the foundation with verification. We don't claim per-user dollar amounts.
And the 3-arm test will tell us: if users respond equally to better content WITHOUT the giving narrative, then the giving part isn't what's working — and we'll know within 4 weeks.
This needs verification before we build. We need explicit written confirmation that parental consent covers use in the app, that the foundation approves the framing, and that it complies with EU child data protection rules.
Blocker — flagged, not yet resolvedWe don't claim exclusivity. "Meet Daniel" — not "Daniel was assigned only to you." With 38 kids and thousands of subscribers, each kid maps to many users.
This is fine — Compassion International works the same way. Users never compare assignments. And if they did, "5,000 people are supporting Daniel alongside you" is actually more powerful, not less.
We never say that. The framing is "our community helps children like Daniel through [Foundation Name]" — collective, not individual. But this still needs careful copy.
And a real decision: is the donation ongoing? If it's a one-time $5,000 and we imply ongoing giving, that's deceptive. We need a clear, sustainable commitment.
The 3-arm test catches this. If the giving narrative alienates utility-focused users, we'll see it in the subgroup analysis. The impact card is one component on the purchase screen, not the whole screen — users can glance and move on.
If certain segments respond negatively, we personalize in Phase 2.
The sponsorship cards lead with dreams and hobbies — Daniel likes football, Sofia loves art. Kids first, circumstances second. We use empowerment framing ("Daniel is going to school") never pity framing ("Daniel couldn't afford school").
We don't mention ethnicity in the app. The foundation name provides context for those who want to learn more.
Phase 1 is a 4-week test with 38 kids. If the signal is positive, we scale the foundation partnership to hundreds or thousands before full rollout. The content library is thin today — intentionally. We're testing the narrative, not building an encyclopedia.
Possible. That's why we have guardrail metrics: cancellation reason monitoring, support ticket volume, App Store review sentiment, refund rate. And it's behind a feature flag — we can kill it in minutes if sentiment turns negative.
The 3-day build means the downside is 3 days of work, not 3 months.
The whole power is that the subscription already helps. Zero extra action from the user. This is the TOMS model, not GoFundMe.
Our data confirms it — the donated field is zero for all 2025+ users. Nobody donates separately. Baking it into the subscription is the only way this works. A donate button converts 1-2% of users on a good day. Making the subscription itself feel like giving reaches 100%.
Then we lost 3 days and learned that the giving narrative doesn't move weekly renewal for US iOS. That's valuable.
We'd test on monthly subs (different psychology), try the narrative at a different moment, or explore other identity levers. Cheap learning.