Tutoring Marketplace Platform

Skill Bridge

A tutoring marketplace where students discover tutors, book live sessions, pay securely, and manage learning workflows through role-aware dashboards.

Full-stack SaaS PlatformMVP
Skill Bridge project thumbnail
Live

Overview

What the project is

SkillBridge is a SaaS-style tutoring platform built around the full journey from tutor discovery to session management. Students can find suitable tutors, book available slots, complete payment, and track sessions, while tutors and admins get dedicated dashboards for operating the platform.

Problem / Purpose

Why it was built

The project was built to solve the friction of scattered tutoring workflows. Instead of separating discovery, scheduling, payment, and communication into different tools, SkillBridge brings the core marketplace flow into one structured product experience.

Key Features

Important product capabilities

Student Features

  • Tutor discovery with subject-aware browsing and detailed tutor profiles.
  • Availability-based booking flow with protected checkout states.
  • Student dashboard for sessions, notifications, profile updates, and reviews.

Tutor Features

  • Tutor profile management for expertise, subjects, pricing, and visibility.
  • Availability scheduling and session lifecycle management.
  • Finance, review, and notification surfaces for day-to-day operations.

Admin Features

  • Management tools for users, tutors, bookings, categories, subjects, and degrees.
  • Moderation-oriented dashboard views for keeping the platform organized.

Payment Features

  • Stripe checkout with temporary booking holds before final confirmation.
  • Payment result handling that verifies state before showing success or failure.

Tech Stack

Technology choices by responsibility

Frontend

Next.jsReactTypeScriptTailwind CSS

Backend

Node.jsExpress.jsTypeScript

Database

PostgreSQLPrisma

Authentication

Better Auth

Payment / Services

StripeZoomCloudinary

Deployment

VercelRender

Architecture / How It Works

Simple system flow

SkillBridge uses a split frontend and backend architecture where the frontend handles role-aware experiences and the backend owns business rules, authentication, payments, and persistence.

01

Discovery to Booking

Students browse tutors, inspect profile details, select a subject and available slot, then start a booking flow that is validated by the backend.

02

Booking Hold to Checkout

The backend creates a temporary booking hold before Stripe checkout so the selected slot is not treated as confirmed until payment succeeds.

03

Payment to Session

Successful payment updates booking and session state, then dashboard surfaces reflect the confirmed tutoring session for the right roles.

04

Role-aware Dashboards

Students, tutors, and admins see different dashboard modules while sharing a consistent protected route and session model.

Screenshots / Visual Walkthrough

A guided look through the experience

Skill Bridge visual preview

Marketplace Landing

The public entry point explains the tutoring marketplace and routes users toward tutor discovery.

Tutor Discovery

Students can compare tutors by subject, profile strength, and availability before booking.

Dashboard Workflows

Role-specific dashboards keep student, tutor, and admin actions separated and easier to scan.

Checkout Flow

Payment screens are tied to booking state so users receive clear success and failure feedback.

Challenges & Solutions

Engineering decisions that mattered

Challenge

Keeping the booking and payment states reliable.

Solution

I treated checkout as a multi-step workflow with temporary booking holds and backend verification before rendering final payment states.

Challenge

Supporting multiple user roles without making the UI feel fragmented.

Solution

I separated dashboard surfaces by role while keeping shared layout, navigation, and protection patterns consistent.

Challenge

Balancing product depth with maintainable code organization.

Solution

I used feature-oriented frontend and backend boundaries so bookings, payments, users, and admin tools could grow independently.

What I Learned

Growth from the project

  • This project improved my understanding of SaaS-style product flow, especially where authentication, payments, and role-specific dashboards meet.
  • It also strengthened my backend thinking around state transitions, validation, and business-rule ownership.

Final Links / CTA

Explore Skill Bridge

Open the live product, review the repository, or return to the full projects archive.