Stakeholder pitch

Every food parcel reaches the right person.

A mobile-first web application using staff OTP login and beneficiary face verification to prevent duplicates and restore dignity to distribution. Beneficiaries do not need phones or email addresses to receive support.

Open live demo Stakeholder PDF

The operating problem

Paper lists and ID checks can be forged, duplicated or updated too late.

Paper lists collapse under pressureManual registers are slow, duplicated, and often cleaned up after the event.

Identity is hard at the tableMissing documents, changed details, proxy collection and repeat collection create uncertainty.

Donor proof is thinLeadership needs evidence of delivery without exposing private beneficiary data.

The product

One record from onboarding to handout to reporting.

EnrollConsent, available details and face capture

VerifyStaff-run beneficiary face check-in

ServeParcel logged to event and volunteer

ReportDashboards and event close-out

Live demo

This is a working handover, not a mockup.

Beneficiary journeyOpen profile, re-onboard, scan face, hand out parcel, check history.

Role journeyPastor, volunteer, admin, donor and beneficiary each see a focused dashboard.

Open live app

Role onboarding

Staff access is OTP. Beneficiary login is facial recognition.

Owner / AdminCreate organisation, set rules, invite team, review dashboards.

PastorOpen event, manage roll call, approve exceptions, close out.

VolunteerSelect event, scan, verify, hand out, move to the next person.

BeneficiaryNo phone, email or OTP required; after enrolment they sign in with face.

DonorSee aggregate verified impact without beneficiary PII.

Founder AdminOwner-only oversight, pilot support, governance visibility.

Presenter talk track

What to say when switching roles.

Pastor"This is the site lead view: today's event, roll call, exceptions and close-out."

Volunteer"This user only needs the scan-and-handout flow. It is intentionally simple."

Org Admin"This is the operational control room: beneficiaries, events, KPIs and activity."

Beneficiary"This view shows only the person's own collection history and next status."

Donor"Funders see verified impact without unnecessary private data."

Founder Admin"This is owner-only oversight and should not be used as a field role."

Risk controls

Designed for real-world abuse and error scenarios.

Scenarios addressed

Duplicate collection across events or sites
Proxy collection without approval
Early repeat collection during cooldown
Identity confusion when documents are missing
Staff-side shortcuts under queue pressure

Golden Thread controls

Beneficiary face verification
Collection history and cooldown checks
Pastor/admin override with reason
Roll call per event
Audit trail for sensitive actions

Governance

Privacy and accountability are product features.

POPIA

Consent-first enrollment and controlled access.

RBAC

Different role views reduce unnecessary exposure.

Audit

Logins, handouts, overrides and changes are traceable.

Stakeholder value

Less leakage. Faster reporting. Higher trust.

OwnersKnow what happened at each distribution.

TeamsRun a simpler flow at the table.

FundersSee verified aggregate impact.

Demo accounts

Staff roles use OTP. Beneficiary uses face.

nolsdebeer@gmail.com founder admin
nolsdebeer@gmail.com pastor dashboard
nolsdebeer@gmail.com volunteer scan and handout flow
nolsdebeer@gmail.com organisation admin
nolsdebeer@gmail.com donor view
Staff OTP: 000000
Beneficiary: Sign in with face

Decision ask

Approve a controlled pilot.

One organisation. One distribution team. One beneficiary group. Measure enrollment completion, parcel traceability, duplicate prevention, time per handout, user confidence and reporting quality.

Open marketing site Open demo