Schedules that hold together
One-off and recurring lessons, conflict checks, studio events, blackout dates, and payer change requests share one source of truth.
For independent music teachers
Soloist brings lesson schedules, payment state, teaching context, and family communication into one dependable place—while working with the calendars, payment methods, and habits teachers already trust.
The product foundation is working. Soloist is not yet publicly available while the teacher experience and private-beta operations are completed.
Implemented
These capabilities work in Soloist today. Some are still waiting for their final teacher-facing screens.
One-off and recurring lessons, conflict checks, studio events, blackout dates, and payer change requests share one source of truth.
Prepaid lesson credits, adjustments, receipts, invoices, monthly projections, and payment-attention signals keep balances legible.
Lesson history, progress records, homework, and student context preserve the thread from one lesson to the next.
Durable message threads keep ordinary notes, schedule requests, decisions, and useful receipts together—without read receipts or live-chat pressure.
Live teacher and student calendar feeds, personal busy-time import, and human-readable export and restore keep Soloist from becoming a closed box.
Role-based access, service agreements, family data download and deletion, teacher exit controls, and privacy-safe diagnostics are built into the foundation.
In progress
Current work is focused on the shortest path from capable software to a calm, trustworthy daily tool.
Teacher view
The signed-in overview already shows today’s lessons, payment attention, studio pulse, and activity. A responsive timeline, safe lesson completion, and preparation context come next.
Message Assist
The product core supports a manual @soloist path for private scheduling drafts in English or Simplified Chinese. The inbox interface and evaluation continue; ordinary messages are not analyzed automatically.
Private beta
Secure deployment, production email, stronger token storage, scheduled backups, recovery checks, and one end-to-end release path remain gates before teachers are invited in.
Stay in the loop
If this sounds useful, or if there is something you wish existed for your studio, I would like to hear it.
Write to [email protected]