Founder meeting prep (28 October 2026)

Your crib sheet for the meeting. Four parts: say, show (the dev demo, flow by flow), decide together, ask. Decide and ask come before anything else if time runs short.

Before the meeting (15 minutes)

• Reset dev so the demo data is clean. Testers left extra data on 27 October (eight test sign-ups, Kevin fully stopped, extra posts). Reset brings back the normal demo people and their cases.
• Do one dry run of the demo below, so no screen surprises you.
• Have ready: the dev site password; the team Gmail open in another tab (every dev email lands there, so you can show the parent email live); a browser window at laptop size.
• Know the one difference from live: mentor–student chat is on in dev only. On the live site it stays off until the grooming check is running. Say this when you show it.
• Not on dev yet: the team screens for adding schools and inviting staff. They're built and waiting for your check. Either merge them before the meeting or describe them without showing.

1. Say: where things stand (2 minutes)

• thnkrr.com is live on Amazon. It shows only the waitlist. Sign-up is closed; testers get in by invite.
• Backups are locked. One copy of the database a month, kept a year, which nobody can delete. The first runs on 1 November.
• dev.thnkrr.com is our private test copy. Password-protected, updates itself within minutes of each change, can be wiped and refilled with demo people any time. Costs about $11.50 a month.
• On 27 October we tested every role in a real browser.
  • The walls between people held everywhere: a mentor can't reach a student who didn't ask, a teacher can't see another school, the view-only safety admin couldn't act (23 tries, all refused).
  • We found 7 child-safety bugs. The worst: a grooming message could be thrown away automatically with nobody on staff seeing it. All 7 are fixed and on dev.
  • About a dozen bugs that broke a normal task (for example, a mentor who skipped setup could never finish their profile), plus many small ones. Also fixed.
• On 28 October I made 9 product calls (listed in "Confirm" below). Built and on dev. I'd like your yes on them.
• What stands between us and the first school is mostly on your side: names, sign-ups with child-safety bodies, the lawyer, and the first school's agreement. That's the "Ask" part.

2. Show: the demo, one flow at a time

Each flow is one person's path. Use the one-click logins on the dev login page. Keep to what's built; when the founder asks "can it do X?", note it under Decide.

Flow A: A visitor, and a student signing up

• thnkrr.com (the live site): waitlist only. No log-in button on purpose during the pilot.
• dev sign-up as a 15-year-old, with a team Gmail address (thnkrrteam+anything@gmail.com):
  • picks "student", date of birth, school, guardian's name and email;
  • under 13 is turned away; a school not on Thnkrr stops sign-up and keeps only the school's name;
  • nothing goes to the parent yet. First, someone at the school checks the student's age, that they're on the school list, and who the guardian is.
• Then show the parent side: the parent gets an email, reads what Thnkrr is, says yes or no. They have no account and see none of the child's activity. Open the email in the team Gmail.

Flow B: A student's normal day (Maya)

• Feed: posts only from students, no follower counts or popularity numbers.
• Post something: Maya sees it straight away marked "being checked"; nobody else sees it until it's checked. A photo or video waits for a person.
• Like: one tap likes; hover (long press on a phone) opens the three reactions, like LinkedIn.
• Connect and message: both sides must agree before they can message.
• Profile: short shareable link; Maya picks who sees it (everyone, her school, connections). "Who viewed your profile."
• School page: About and People tabs. Only our team can create a school page, so nobody can fake one.
• Safety from her side: report, block, "I don't know this person". Blocked people list with unblock in Settings.

Flow C: Student finds a mentor (Maya → Dev the mentor)

• Mentor list: search by college, subject, hometown, old high school.
• Maya sends a request with a short note. Log in as Dev, accept it. A chat opens. (On in dev only.)
• Show the checks working: a message with a phone number, "move this to WhatsApp" or "keep this between us" never reaches the student; it goes to our team.
• What a mentor sees: only their own mentees, and only name, grade, school, goals, milestones. No feed, no search for students, no way to contact a student first. This is the main safety rule.
• Maya can block her mentor; that ends the mentorship. The chat is kept, never deleted.

Flow D: A teacher and a counsellor (Ms. Rivera, Mr. Okafor)

• Class list: Rivera confirms students really are at her school. It asks before confirming, because it can't be undone.
• School numbers: how many joined, how many have mentors. Downloadable.
• Open a student's profile at her own school: sees what a classmate would see. Can't message, connect or post. The student sees her name in "who viewed".
• Care referral (counsellor): our team flags a student who may be at risk; the counsellor gets an alert with no name or words in the email, then sees the student and the concern on a Student support screen, and checks in with them in person.

Flow E: The safety team (moderator, Kate, Rosa)

• Moderator: one shared review list, most urgent first (child safety, intimate images, self-harm before spam). Opens the actual post, photo or profile, not a description. Photos blurred until they choose to look.
• Actions from the same screen: warn, remove, pause new posts, hide a fake profile, suspend, ban, refer to the school counsellor.
• Kate (Child Safety Lead): a grooming case handed to her. She sees the actual messages, can fully stop the person, and has the clocks (confirm in 4 hours, report in 24).
• Rosa (Safety Admin): sees everything, can't act. Gets the email when a deadline is missed.
• Deadline emails: when something arrives, at half-time, and to the admin if it's missed.

Flow F: The person on the other end of a decision

• Marcus: a removal notice that names which comment, with its first words and date.
• Ethan: suspended; the sign-in screen says why and until when, in his time zone, with "Ask us to look again".
• Andre: banned; it says the ban is permanent.
• Elijah: held self-harm post: "You're not in trouble" plus crisis lines. No "not approved", no prompt to reword it.
• "Ask us to look again" is tied to the account and the decision, so the reviewer knows what it's about.

3. Decide together

Product questions only. Each has my suggestion so the founder can just say yes or no.

Paths we haven't built yet

1. When a student finishes high school, what does the account become? Today nothing happens; it stays a student account. Options: alumni, a move to mentor, or closed after a grace period.
2. Can a student become a mentor later? Today a role is fixed for life. Suggest: yes, as a deliberate switch when they start college, re-checked like a new mentor.
3. Professors and college staff. Several have asked; there's no place for them today. The key question: can they only reply to students who ask first, like mentors? (The full 9 questions are in the roles-and-journeys note.)
4. Teachers on a personal email have nobody who can confirm them, so they get no teacher tools. Suggest: require a school email, or let the school's page admin vouch for them.
5. A mentor whose college isn't on our list can carry on but shows "not confirmed". Allowed in the mentor list, or hidden until we add the college?
6. Someone limited while we look into them (for example, "asked a younger student for photos") can still be suggested to younger students, like posts and accept connection requests. Suggest: hide them from suggestions and search, and switch off likes and accepts while limited.

Pages (LinkedIn-style)

7. Follow a school or college page? Suggest: yes, with no follower count.
8. Can a school post updates into students' feeds? If yes, who at the school posts?
9. What should pages have: alumni, events, summer programs, scholarships, internships?
10. College pages: run by our team or by college staff? Should a student's "committed to" college link to its page? Should a college page list its mentors?

Turning things on for the pilot

11. Mentor chat on the live site: what has to be true first? Suggest: the grooming check is running (Thorn or Hive) and mentors have a background check. Mentor background checks aren't decided yet.
12. How the first school's students get in: our team creates the school, invites its page admin, and students join through the school's join link, a few classes at a time. Suggest: yes; the live site stays invite-only otherwise.
13. Every photo and video checked by a person before it shows? Suggest: yes for the pilot.
14. Longest video: 15 minutes today. Suggest: start at 3 to 5; we can raise it any time.
15. The student's full-quality original video file: kept forever today. Suggest: delete after 30 days unless it's evidence in an abuse report.
16. Suspend and ban rules: only the Child Safety Lead and Grievance Officer can ban; a moderator can suspend for at most 7 days; the person is always told why, except in child-safety and intimate-image cases. Confirm?

Confirm: calls I made on 28 October (built, on dev)

17. Chats are never deleted by anything a member does, even deleting their account. The personal details go; the chat stays for the other person and the safety team. This is a promise to families. The lawyer needs to see it, and the Privacy Notice has to say it.
18. Warnings and removal notices name the post or comment.
19. "Ask us to look again" is tied to the account and the decision.
20. A held self-harm post comforts and never scolds.
21. A student can block their mentor; it ends the mentorship.
22. Like works on one tap; reactions on hover.
23. The urgent list puts the most serious concerns first, then the oldest.
24. The Child Safety Lead also sees care referrals.
25. Teachers can open their own school's students' profiles (never another school's), and the student sees they looked.
26. Plus two from the bug fixes: a declined connection request keeps looking "pending" to the sender, so nobody learns they were declined; a student declined by a mentor waits 30 days before asking that mentor again.

4. Ask

Names (needed before the first real student)

• Two moderators to check posts daily.
• Child Safety Lead: is it Vidhi? Who backs her up? Is she also the person who files reports with NCMEC (the US centre for child-abuse reports) and the Indian police?
• Grievance Officer for India. The law puts their name and contact on the site.
• Safety Admin: you or me?
• The reviewers' support: a counsellor from day one, and a heads-up about distressing material.

Paperwork: where is each one?

• Registering Thnkrr with NCMEC.
• Applying to the five free lists of known abuse images and videos: PhotoDNA, NCMEC's list, IWF, Project Arachnid, Google CSAI Match.
• The two drafted emails to Thorn and Hive (grooming detection). Mentor chat waits on this.
• The WebPurify quote, with our conditions (they keep nothing, never train on our images, signed data agreement).
• The lawyer: final Terms and Privacy Notice, the Community Guidelines, the deadlines, the at-risk student procedure, and now "chats are kept for good".
• Community Guidelines text: will the founder send it, or should we draft it?

The first school

• Which school, and roughly when?
• How many students first, and which classes?
• The school agreement: two named staff (a parent checker, who confirms a parent's details before we email them, and a care contact, who we alert if a student may be at risk); the school decides whether to tell parents about an at-risk alert; paper consent forms ready.

Small things only the founder controls

• The support@thnkrr.com mailbox needs creating. Until then every alert and complaint copy goes to the team Gmail. Needed before the first real student.
• GitHub billing: a failed payment has stopped our automatic tests on GitHub. Who fixes the card?
• Professors: how many have asked, from which colleges, and what do they want?

Don't

• Don't give a date for mentor chat on the live site. It depends on Thorn or Hive replying.
• Don't describe graduation, college pages or professors as if they exist. They're questions, not features.
• Don't get into hosting or tool choices. Those are ours. If asked, one line and the monthly cost.
• If they bring up something new mid-demo, write it under Decide and keep going.