Pocket Tutor

Private tuition, with less admin drag.

A teaching workflow for private music educators: lesson planning, student context, follow-up notes and the small admin tasks that usually sit around the edges of a teaching week.

The teaching week in one place.

Pocket Tutor studio dashboard showing lesson review, upcoming lessons, and tutor overview panels.
A clear studio workspace for the parts of private teaching that usually spread across notes, messages, calendars, and payment tools.
Pocket Tutor directory showing tutor search filters, instrument browsing, and available tutor cards.
The public directory helps students and parents find the right tutor before they enquire.
Pocket Tutor students screen showing connected students and rotation block controls.
Student records and rotation tools keep recurring teaching work close to the schedule.
Pocket Tutor lesson history showing upcoming, completed, needs action, and cancelled lesson states.
Lesson history makes follow-up, payment review, and schedule changes visible in one place.

Status

Active development

Built from the admin problems that show up in a working private studio.

Platform

Web workflow

Web-first so teachers and students can use it across phones, tablets, and computers.

Audience

Teachers and students

Built for educators looking to regain some time in their work week.

Why it exists

Private teachers often need something lighter than a full school system but more dependable than scattered notes, reminders, and spreadsheets.

Pocket Tutor is built on three foundations: tutor discovery, powerful scheduling, and seamless payments, so teachers can be found, organise their week, and get paid without stitching together separate tools.

What it improves

  • Tutor discovery through a clear public directory.
  • Scheduling that can handle the moving parts of private teaching.
  • Payments that fit naturally into the lesson workflow.
  • Less weekly admin for educators who would rather spend that time teaching.

Current direction

The project is being kept deliberately narrow so the core workflow feels calm and reliable before anything broader is added.