cd ../case-studies
~/case-studies/tutors-hub.md
Architectural Deep-Dive

Tutors Hub

A shipped tutor marketplace designed like a workflow engine, where the recovery path matters as much as the happy path.

Tutors Hub screenshot

Product context

Tutors Hub is a tutoring marketplace shaped as an operations workflow. A parent request is not a clean ecommerce transaction: requirements change, tutor constraints matter, and the operator needs recovery paths when a match fails.

Workflow model

The product organizes intake, assignment, tutor shortlisting, verification, matching, and payout-related work as explicit business state transitions. The system is designed around the handoffs between people, not only the public listing page.

Engineering decisions

  • Next.js provides the onboarding and operator-facing product surface.
  • Spring Boot owns the workflow-heavy backend direction.
  • PostgreSQL/Supabase support relational state and identity workflows.
  • Firebase supports notification needs.
  • Sensitive data and role boundaries are treated as backend responsibilities.

Evidence and limits

This is a shipped product direction that demonstrates workflow modeling and product judgment. The portfolio does not claim a specific marketplace volume or a fully automated matching engine. Human review and operational recovery remain part of the design.