Stakeholder showcase
Presenter runbook
Five-minute scripts per audience. Open /connect/ on a phone or laptop and follow the guided tour.
Before you present
- Set NEXT_PUBLIC_SHOWCASE_MODE=true on Vercel for softer empty states (optional).
- Confirm SUPABASE_SERVICE_ROLE_KEY passes npm run verify:service-key for portal/admin demos.
- Use /connect/ as your opener — not the homepage.
- For mixed rooms: start at /connect/system/, then split tours.
Future participant
See if this is for you — about 60 seconds, no signup required.
- Readiness snapshot — Three taps — no account. Shows what support is and what we do not provide.
- Readiness path — Four short modules: scope, checklist, referrals, and your next step. Progress saves locally.
- Resources — Crisis lines and navigation links — always external for emergencies (911 / 988).
Partner / connector
Refer safely with attributed links — no cold calls, clear MOU scope.
- Partners hub — Async-only onboarding — email-first interest, pilot MOU review within five business days.
- Partner kit — Share attributed links and embed the readiness path — privacy-first, consent-based referrals.
- Attributed snapshot — This link tracks partner attribution without collecting participant PII on the referral.
- MOU template — Written referral agreement — either party may decline outside published scope.
Multicultural BC organization
Community workshops, Punjabi path, and outreach within safeguarding scope.
- Multicultural BC program — Workshop-ready readiness tools for diverse communities — survivor-led, not a replacement for settlement services.
- Punjabi hub — Community language entry point — links to the Punjabi readiness path.
- Punjabi path — Module 1 in Gurmukhi — peer-reviewed tone, plain language, no machine-only translation.
- Translation Sprint — Submit peer-reviewed Punjabi UI strings — aggregate progress only, no public leaderboard.
- Partner kit — Share with your team — attributed links for workshops and outreach events.
Investor / funder
Trust infrastructure, honest aggregates, and published accountability.
- Governance — Survivor-led policies, safeguarding, and scope — governance capital as the moat.
- Trust infrastructure — How trust systems scale the mission without scaling staff headcount.
- Funder pack — Program model, evidence approach, and LOI outline — aggregate impact only.
- Impact note — Quarterly narrative with modest, verifiable metrics — no individual stories without consent.
Advisor / ally
Scoped volunteer roles with safeguarding and training first.
- Get involved — Explore vs Build — choose readiness learning or joining a guild to contribute.
- Ally role example — Each role publishes scope, time commitment, and boundaries — typically 2–4 hours per month.
- Safeguarding — Crisis routing, no public naming, escalation paths — required reading before facilitating.
- Facilitator training — Self-paced modules — mark complete as you go; required before cohort facilitation.
Builder / tech ally
Guilds, GitHub, and scoped AI — clear contribution lanes.
- Guild index — Six contribution lanes — developer, translation, partnership, community, research, AI.
- Developer guild — Good-first-issues, portal hours, merged PR credit — privacy-first infrastructure.
- AI guide — Try scoped prompts — watch refusals for legal, clinical, and crisis topics.
- AI allies — Onboarding for engineers, designers, and AI safety reviewers.
When stats are low
Say: "We are in pilot validation — metrics are aggregate and honest. The product works; we are measuring carefully before scaling claims." Enable showcase mode to show "Pilot phase" instead of "Pre-validation" on impact pages.