Overview
PinTeach is a SaaS for online language teachers. It replaces the “Frankenstein stack” (Calendly + Stripe + Drive + WhatsApp + Excel) with a single platform for:
- Public profile pages with service catalog and booking
- Service management (1:1, groups, courses, subscriptions)
- Scheduling with timezone-aware slot calculation and Google Calendar sync
- Payments via Stripe Connect (teacher collects directly)
- Student CRM with lifecycle tracking, mood, notes, and contact log
- Resource library with Google Drive integration, templates, and auto-copy to student folders
- Cancellation policies (configurable rule engine per service)
- Legal documents (contracts, terms, privacy — versioned with student acceptance)
- Review system (in-app + external imports, embeddable widgets)
- Waitlist for capacity-limited services
- Audit logging and GDPR compliance (data export, erasure, retention)
- Embeddable widgets (booking, storefront, reviews)
The class itself happens outside the platform (Zoom, Meet, Skype). PinTeach handles everything around it.
What PinTeach is NOT
Section titled “What PinTeach is NOT”- Not a marketplace
- Not an LMS
- Not a video platform
- Not an in-app classroom
Teacher (Owner)
Section titled “Teacher (Owner)”- Connects Google Calendar + Stripe
- Defines services (3 dimensions: delivery x group x structure), availability, pricing, policies
- Manages students, sessions, payments
- Receives trial booking requests
- Manages review system, widgets, materials
Student
Section titled “Student”- Books trial class from public page
- Purchases services (enrollments)
- Books sessions using enrollment credits
- Views session history, resources, homework
- Submits reviews and mood feedback
- Manages preferred booking hours
- Can join waitlists for full services
- GDPR rights: data export, erasure request
Documentation Map
Section titled “Documentation Map”| Document | Purpose |
|---|---|
| Product Overview | Business logic, user flows, algorithms, decisions |
| Database Schema | Every table, column, enum, relation |
| REST API | Every endpoint with request/response shapes |
| Conventions | How to write routes, services, hooks, components |
| Audit History | Architectural audit (32 findings, all resolved) |
| Task Registry | 13 phases of completed work |