Growing Beyond One Mentor: Planning for Scale

Starting Small, Building Big

When I first built James Music Academy, it was designed for one mentor: me. Every student would be my student. Every session would be with me. Simple.

But I knew that wouldn't scale. There are only so many hours in a week. So even though we're launching with just me, we built the platform to handle multiple mentors from day one.

This was v1.3 — one of our biggest updates. 30 requirements completed, transforming the entire authorization model.

Why Mentor Fit Matters

Research consistently shows that the student-teacher relationship is one of the strongest predictors of learning outcomes. A meta-analysis by John Hattie found that teacher-student relationships have an effect size of 0.52 — well above the 0.4 threshold for significant impact.

The ABRSM (Associated Board of the Royal Schools of Music) has found that students who feel connected to their teacher are significantly more likely to continue learning and achieve their goals.

Not every mentor is right for every student:

• Maybe you need someone who specialises in electronic production
• Maybe you want a mentor who understands jazz theory
• Maybe you need patience with complete beginners
• Maybe you click better with certain teaching styles

As we grow, you'll be able to browse mentor profiles, see their specialties, and choose someone who fits what you're looking for.

The Technical Challenge

Moving from single-mentor to multi-mentor sounds simple, but it touches everything. The key question: should a mentor be a separate entity, or just a user with special permissions?

We chose the simpler model: a mentor is just a user with a role. This keeps the data model clean and avoids duplication. We added:

• A mentor profile linked to the user account
• Student assignment tracking (who mentors whom)
• Assignment history (for when students switch mentors)
• Per-mentor availability and booking calendars

Privacy by Design

When you work with a mentor, your sessions, goals, and progress are visible only to:

• You (obviously)
• Your assigned mentor
• Your parents (if you're under 18 — see our safeguarding approach)

Other mentors can't see your information. We built this authorization at the database query level — the data is scoped from the start, not filtered after fetching.

We also added audit logging for security events. Every access attempt is recorded, especially denied ones. If something goes wrong, we need to know what happened.

Continuity When Things Change

Life happens. Mentors might take time off. Schedules change. You might want to try working with someone new.

If you ever need to switch mentors, your history comes with you. A new mentor can see your past sessions and goals (with proper handoff), so you don't have to start from scratch.

This is similar to how medical records transfer between doctors — continuity of care matters in education too.

Quality Over Quantity

I'm not looking to add dozens of mentors overnight. Every mentor on the platform will need:

• Real experience — Years of actually making and teaching music
• Enhanced DBS check — Non-negotiable for working with young people
• Alignment with our approach — Goal-based mentoring, not just generic lessons
• Genuine care — You can't fake caring about your students

I'd rather have three excellent mentors than thirty mediocre ones.

The Lesson for Builders

One of the biggest decisions early on was whether to build a simple single-mentor system or invest the time to build something that could scale.

We chose to build for growth. It took longer — v1.3 was 30 requirements on its own. But it means we won't have to rebuild everything when the time comes to expand.

That's been a theme throughout this project: making decisions now that our future selves will thank us for.