Day 01
Sponsor joins
Stripe confirms the monthly gift and creates a sponsor record.
Owner: Sponsor
Four Hunger operating system
A simple monthly loop for sponsor trust.
Sponsor joins. Windell checks in. Zach reviews. The sponsor gets a private update; the public gets aggregate proof.
Monthly calendar
What happens in a normal sponsorship month.
One rhythm. Clear owners. No mystery.
Day 12
Welcome task
Wendell gets a simple welcome-video task for the new sponsor.
Owner: Field team
Week 33
Pod check-in
One phone form captures child rows, notes, evidence, and optional media.
Owner: Windell
Days 24-274
Review window
Zach or a reviewer approves media, edits the update, and confirms boundaries.
Owner: Reviewer
Day 285
Secure update
Email carries the secure link. SMS can nudge without private details.
Owner: System
Interfaces
Three views, one shared record.
Phone form for the field team. Review board for Zach. Secure update for sponsors.
Windell phone
Monthly pod check-in
One phone form. Child rows, attestation, optional media.
Windell
PhonePod
Partner Home One
Meals
School
Wellbeing
Moment
Optional image
PrivateZach desk
Review queue
One table for media, sponsor drafts, and proof readiness.
Zach review
DeskMedia
Draft
Proof
Sponsor inbox
Secure update link
Email carries the update. SMS only nudges to the secure page.
Email
Your Four Hunger update is ready
Open secure page
SMS nudge
Your update is ready. Check your email for the secure link.
Evidence
Every update is backed by a small evidence packet.
Not every sponsor update needs a photo. The stronger pattern is ordinary evidence: receipts, notes, attestations, optional media, and a review trail.
Receipt or ledger
Private file upload, public summary only.
Field attestation
A short signed note: who observed what, when, and where.
Consent-approved media
Sponsor-only, reviewed first, never public by default.
Public proof card
Aggregate count, review level, caveats, and what stayed private.
Donor communication
Email tells the story. SMS just opens the door.
WhatsApp and phone calls can coordinate humans. The official sponsor update resolves to one reviewed secure page.
Email
Primary channel
Full sponsor update
Your private Four Hunger update is ready. Open your secure page to read the reviewed note.
SMS
Optional Twilio
Short nudge only
Your Four Hunger update is ready. Please check your email for the secure link.
WhatsApp / call
Not recordkeeping
Human coordination
Please open the app and finish this month's pod check-in when you have service.
Show Zach
The screens that make the system real.
These are the demo stops I would walk through: sponsor checkout, field form, evidence capture, review queue, and secure sponsor page.
Demo stop
Field form
Monthly child rows, optional image upload, and sponsor update drafts.
Demo stop
Evidence form
Receipts, delivery logs, partner attestations, and public proof batch capture.
Demo stop
Sponsorships
Private child matches, update status, and review/send readiness.
Demo stop
Settings
Stripe, email, SMS, Supabase, and optional integration readiness.
The app is the official record.
WhatsApp helps people coordinate, but it is not the database.
Child photos are sponsor-only, consent-scoped, and reviewed first.
Email carries the full secure update.
SMS only nudges back to the secure page.
Public proof stays aggregate and child-safe.