Founder Presenter Notes
Use this as the founder-facing run sheet while presenting. The external pack remains stakeholder-demo.pdf; these notes are for the presenter only.
Links To Send
Main landing page: https://gta.cleva-ai.co.za/
Demo login: https://gta.cleva-ai.co.za/demo-login
Beneficiary face login: https://gta.cleva-ai.co.za/demo-login, then choose Sign in with face
Pastor demo: https://gta.cleva-ai.co.za/demo-login?demoRole=pastor
Stakeholder PDF: https://gta.cleva-ai.co.za/stakeholder-demo.pdf
UAT guide: https://gta.cleva-ai.co.za/uat.html
Beneficiary workflow: https://gta.cleva-ai.co.za/beneficiary-face-login-workflow.html
Presenter notes: https://gta.cleva-ai.co.za/presenter-notes.pdf
Demo account: nolsdebeer@gmail.com | PIN 000000
Opening Script
"Golden Thread is built for the actual food parcel handout moment. It helps the organisation know who was served, when, by whom, under which event, and with what verification. Beneficiaries do not need phones or email addresses to receive help. Staff can enroll them, capture consent, verify by face, and record the parcel."
Demo Run Sheet
- Start at the marketing landing page. Show the value proposition, role onboarding, risk controls, and stakeholder-ready message.
- Open the Pastor demo. Use nolsdebeer@gmail.com and PIN 000000. Explain that this is the site lead view for distribution day.
- Show dashboard and events. Point to today's event, roll call, served/outstanding status, exceptions and close-out.
- Open beneficiaries. Show records, consent, collection history and re-onboarding. Say clearly: phone and email are optional for real beneficiaries.
- Show beneficiary face login. Return to the login page, choose Sign in with face, scan the enrolled person and show the beneficiary dashboard.
- Show scan and handout. Demonstrate face verification, cooldown/eligibility, handout logging and the next-person workflow.
- Switch roles only if asked. Use the UAT role buttons for Founder Admin, Org Admin, Volunteer, Donor and optional Beneficiary view.
- Close with the pilot ask. One organisation, one team, one beneficiary group, clear measurements.
Key Talk Tracks
Founder Admin
Say: "This is owner-only oversight for governance, setup, demo support and escalation."
Show only if needed: platform-level view and controls.
Org Admin
Say: "This is the operations control room: beneficiaries, events, KPIs, activity and exceptions."
Show: dashboard, beneficiary list, calendar and reporting.
Pastor / Site Lead
Say: "This person manages the distribution day and sees who has been served, who still needs help and where an exception needs approval."
Show: today's event, roll call, scan flow and override explanation.
Volunteer
Say: "Volunteers get a simplified workflow: select event, scan, verify, hand out, move to the next person."
Show: scan action and parcel log.
Beneficiary
Say: "Beneficiaries do not need a phone or email to receive support. After enrolment, they can sign in by face to see their own status."
Show: face login, status and collection history.
Donor
Say: "Donors see impact and verified totals without unnecessary private beneficiary information."
Show: aggregate impact and reporting story.
Risk Language
Use This Framing
"The system is not built on the assumption that vulnerable people are dishonest. It is built because busy distribution environments create predictable risk: duplicate collection, proxy collection, lost details, pressure at the gate and staff-side errors."
Control Message
"Golden Thread gives the team evidence and accountability without removing human judgement. Pastor/admin overrides are allowed, but they require a reason and become visible in the audit trail."
Fallbacks
| If this happens | Say / do this |
|---|---|
| Camera permission blocks | Allow camera in the browser, then show beneficiary history and roll call while it reloads. |
| Face match is slow | Explain AI requires internet/API response; show the manual review/override path. |
| Stakeholder asks about privacy | Point to role separation, consent capture, audit trail and donor view without unnecessary PII. |
| Stakeholder wants next steps | Ask for pilot approval, pilot site, pilot users, POPIA sign-off, data import and go-live date. |
Closing Ask
Decision requested: approve a controlled pilot with one organisation, one distribution team and one beneficiary group.
Success measures: enrollment completion, parcel traceability, duplicate prevention cases, time per handout, user confidence and reporting quality.