Why Octavia Is Different

Most studio software is built to manage administration.

Octavia was built to support teaching as a practice, with administration designed to reinforce learning, not take centre-stage.

That difference shows up everywhere: how roles are separated, how access is handled, how features are designed, and how real teaching workflows are respected.

Below are the principles that guide those decisions.

Teaching workflows come first, not generic admin

Many studio platforms focus primarily on billing, scheduling, and record-keeping. Those tools matter, but they are only part of the job.

Music teaching involves:

lesson preparation and follow-up,
student engagement between lessons,
communication with families,
and careful handling of student work and access.

Octavia was designed from the perspective of how lessons actually run, not just how studios are billed. Screens, flows, and defaults are shaped around teaching tasks and the real contexts in which teaching happens.

Lesson notes are a teaching space, not a textbox

In many apps, lesson notes are little more than stored text.

In Octavia, lesson notes are treated as a continuation of the lesson itself. Notes can include:

interactive tools such as metronomes, recorders, and practice trackers,
listening activities and flashcards,
games, challenges, and media attachments.

This allows teachers to design homework that reflects how students actually learn, and helps students stay connected to their lessons between sessions.

The goal is not just to record what happened, but to support what comes next.

Administration that reinforces learning

Scheduling, invoicing, and communication tools are designed to be efficient, but they are not isolated from the teaching experience.

Administrative actions in Octavia are deliberately shaped to:

be fast and easy to use, so information stays accurate,
tie into real teaching events, like lessons, performances and exam records,
and surface information for parents in a way that’s simple and low-effort, so it’s actually read.

When administration is easy to do, it actually gets done.

In Octavia, administration is treated as infrastructure for teaching, not a separate layer teachers have to mentally switch into.

Related reading:
→ Reducing Friction So Things Get Done

Access Designed for Real People

Education software deals with children, families, and personal records. Treating access casually creates risk, but overcomplicating it makes participation harder than it needs to be.

Octavia designs access differently, around a small set of principles:

access is not the same as identity,
different roles need different levels of visibility,
and only the most relevant information should be surfaced to each person.

Parents and students don’t need to learn a complex system to participate. That’s why access is role-aware, invitation-based, and deliberately bounded.

Designed for family contexts

Music education rarely involves just one relationship. Parents, grandparents, and extended family often support a child’s learning, and Octavia is designed so they can all participate, without needing to create accounts or learn a new system.

respect real family dynamics,
avoid unnecessary account creation,
and keep teachers in control of what is shared and when.

A free plan that reflects values, not limitations

Octavia offers a Free Forever plan that is genuinely usable.

Teachers can run an entire studio at no cost, with core teaching and administrative tools included. Paid plans focus on added convenience while the foundations remain available even after a trial ends.

Designed deliberately and explained openly

Where design decisions affect safety, access, or correctness, they are made deliberately and explained openly.

Explore the Product Design articles:
→ Designing Identity for a Multi-Role Music Platform
→ Why We Refactored Identity Without Touching the Teacher App