LerenGO

One platform for practical skills, project building, and university collaboration.

AboutContactTermsPrivacyRefund Policy
LerenGO logo
DirectoryTrust ModelStates
Sign inBrowse mentors
MentorGO

Book focused guidance from verified mentors.

MentorGO is the LerenGO guidance layer for structured mentor profiles, availability, paid sessions, and booking states. It should launch as a trust-first marketplace, not as a casual advice feed.

Review trust modelContinue with LerenGO
Foundation

The directory starts with verification, not volume.

Published mentor cards appear only after the mentor profile, session offer, availability direction, and admin approval model exist. No placeholder mentors are rendered.

01

Verified mentor profiles

Mentor cards and profiles need display pictures, headlines, expertise, session offers, pricing, availability, and verified status before they are published.

ProfilesExpertiseVerification
02

Structured paid booking

Booking cannot be a loose contact form. It needs session types, future slots, student goals, price snapshots, payment status, and booking lifecycle states.

SlotsPaymentBooking status
03

Mentor operations

Mentors need a controlled workspace for profile completion, availability, bookings, reviews, and earnings without exposing student context outside its role boundary.

DashboardReviewsEarnings
Published directory

Approved mentor profiles

These cards are backed by `mentor_profiles` and `mentor_session_types`. Only approved and published profiles are eligible here.

Backend state

MentorGO schema is not applied yet.

Apply web/supabase/module_expansion_schema.sql before using MentorGO directory, booking, and admin review workflows.

Trust rules

A mentor marketplace fails if quality and payment states are vague.

  • Only approved and published mentors should appear in the directory.
  • Students, mentors, and admins see booking context according to role.
  • Payment and booking state must stay separate and explicit.
  • Double booking must be prevented below the UI layer.
Directory state

Only approved mentor inventory is rendered.

The backend now separates mentor approval, publication, bookings, and payment state. Payment capture still needs the provider webhook boundary before live transactions.

Sign in to continue
Booking lifecycle

Booking and payment states must stay explicit.

The MVP should store snapshots for price, currency, time, and payment reference. UI controls should derive from status, not ambiguous booleans.

pending_paymentpayment_failedpending_mentor_approvalconfirmedreschedule_requestedcompletedrefunded
Next build step

Implement the trust layer before marketplace polish.

The next slice should add MentorGO schema, approved-profile reads, and admin verification. Booking and payment should come after slot generation is safe.

Back to foundation