All answers›Online Tutoring Platforms

How do you run an online tutoring business with multiple tutors?

Running an online tutoring business with multiple tutors is a different job from being an indie tutor with a lot of students. The lesson-teaching problem you solved as a solo tutor stays solved for each individual tutor on your team — but three new problems land on your desk the day you take your first hire: keeping lesson content and pedagogy consistent across tutors who don't teach the same way, presenting a single branded experience to families instead of "my kid is on Tutor A's Zoom account and Tutor B's Google Meet", and doing the operations work (scheduling, invoicing, quality review, tutor support) at team scale without becoming full-time tech support. The three real shapes multi-tutor tutoring businesses land on are a stitched-tools stack (each tutor on their own free tools, held together by shared docs and a spreadsheet — cheap, familiar, breaks at ~3 tutors), a shared per-seat solo platform (every tutor has their own paid classroom account, no shared admin — works to ~10 tutors, weak on brand and curriculum control), and a purpose-built multi-tutor platform (branded classroom on your domain, admin dashboard over your team, one lesson library that can be shared across tutors — the shape most working tutoring companies end up on). This page walks through what actually breaks at each seat count, what a platform needs to ship to carry the format, how Koala for Business handles it (including our Copy Activities feature, which is the piece that fixes the shared-lesson-library problem), and when scaling into a small team is the right move vs. when you're better off staying solo.

What "multi-tutor tutoring business" actually means (three shapes)

The line between the shapes matters because each one is a different business, not just a different tutor count:

  • Solo tutor with student overflow. One tutor, more students than hours. The obvious move is to either raise prices or refer overflow to a colleague — not to hire. Very few solo tutors actually need to become a company; most just need a tighter waitlist policy.
  • Solo tutor + 1-3 subcontracted tutors. You still teach yourself, but you route overflow to trusted colleagues at a per-lesson revenue split. Your "company" is really you plus a Rolodex; each tutor uses their own account on whatever platform they already use; families pay you (or pay the tutor, and the tutor pays you a referral fee). Cheapest shape to try; the highest per-hour margin stays with each individual tutor.
  • Small tutoring team (3-15 tutors) under one brand. You're now running a business, not a practice. Families see one brand name, one booking link, one invoicing address; internally you have multiple tutors delivering lessons with an expected consistent shape. This is where the operational overhead starts to matter — curriculum consistency, tutor onboarding, quality review, tutor support all become jobs somebody has to do. Some tutors are employees, some are contractors; the classroom platform is usually shared and branded.
  • Established tutoring school (15+ tutors). Full operations team, HR, curriculum lead, dedicated admin dashboard, formal quality-review process, LMS-adjacent tooling. Not a solo-tutor evolution any more — a different kind of business with different problems and different platform needs. Named customers on Koala for Business at this size include Tutor Doctor.
  • Enterprise / district / franchise tutoring network. Multi-country, multi-currency, multi-brand-line. Different again; not what this page is about.

This page mostly covers the transition from "solo tutor" to "small tutoring team (3-15 tutors)" — because that's the shape where the platform decision matters most, and where the wrong platform decision hurts the business fastest.

The three operational problems multi-tutor businesses actually hit

Every tutoring-company operator we've spoken with runs into the same three problems roughly in the same order:

  • Lesson quality drifts across tutors. The reason your first ten families signed up is a specific style of lesson — your style. Your second tutor teaches almost the same way; your fourth tutor doesn't. Six months in, one family loves you and another has quietly churned because their new tutor's lessons feel generic. The cause isn't usually that the new tutor is bad — it's that there's no shared source of truth for "how a lesson at our company runs," so every tutor rebuilds it from their own habits. The fix is a shared activity/lesson library the whole team teaches from, not a Notion doc titled "how we teach."
  • The tools stack fragments across tutors. You started on Zoom; Tutor 2 came from Google Meet; Tutor 3 uses Skype for older students. Each tutor sends parents a different lesson link, a different scheduling link, a different invoice format. Families experience three different tutoring companies wearing the same logo. This is the "professional-with-parents" pain point that indie tutors already flag as a differentiator; at a small tutoring company it compounds into a churn problem.
  • The operator becomes full-time tier-1 tech support. Every parent connection issue, every "which link do I click" question, every Zoom-crashed-mid-lesson escalation ends on your desk because you're the visible face of the brand. You can either staff around the clock (expensive), let tutors lose lessons (churny), or move to a platform whose support team handles it for the tutor and the family directly. This is exactly the case for a purpose-built tutoring-company platform — the support cost you offload matters more than the license cost you take on.

Two secondary problems tend to arrive later, once the first three are handled: (a) tutor onboarding — how quickly can a new tutor be productive on lesson one? — and (b) quality review — how does the operator watch a lesson without derailing it, and how are shared decisions about "we don't teach it that way" made? Both are downstream of the three above and are best handled by the same shared platform, not by yet another tool.

The three real shapes past 3 tutors

Small tutoring companies converge on one of three platform patterns:

  • Stitched-tools stack. Zoom (or Google Meet) for each tutor + a shared Google Drive for lesson materials + a spreadsheet for the team schedule + separate scheduling and invoicing tools per tutor. Cheap; every tool is free or nearly free. Familiar. Fails at ~3 tutors because the Google Drive folder becomes a compost heap that only the founder can navigate, the shared spreadsheet drifts out of sync with what each tutor's actual calendar says, and there is no way for parents to book across the team from one place. The hidden cost is the founder's time: at 3 tutors and 30-40 families the ops overhead usually hits 15-20 hours a week of unpaid coordination.
  • Shared per-seat solo platform. Every tutor buys their own paid seat on whatever solo-tutor classroom platform the company standardizes on (Koala Go's paid tiers are one option in this category). Each tutor gets a strong classroom, each family gets a consistent lesson experience within a single tutor, and the company's tech stack finally rhymes across tutors. Works to about ~10 tutors. Where it stops scaling: there is no shared admin over tutors (you can't see all lessons across the team in one dashboard), no branded classroom (families still see the platform's name and not yours), no shared lesson library (Tutor A's Reading Level 3 activity has to be rebuilt from scratch by Tutor B), and each tutor's invoicing is their own — families experience 5 different bills or a manual reconciliation you do every month.
  • Purpose-built multi-tutor platform. A branded classroom hosted on your domain (or a subdomain the platform provisions for you), an admin dashboard over your team, one shared lesson library the operator can push into any tutor's library, unified billing and scheduling, and one support team the tutors and families both talk to. This is the shape most working small-and-mid tutoring companies land on eventually. Tradeoffs: it's a real commitment (a contract, a minimum monthly floor of hours, and a launch project rather than a signup), and you're tied to the platform's shape rather than to individual per-tutor choices. For most tutoring companies past 5 tutors the operational math flips in favour of this shape — but not before.

The choice is usually between the middle two (per-seat solo vs purpose-built multi-tutor). The stitched-tools stack is the pre-decision state; anything with 15+ tutors or a formal HR structure is a different problem and usually needs a full LMS layered on top of whichever classroom you pick.

Sharing lesson content across the team (the hardest sub-problem)

Of the three operational problems above, curriculum consistency is the one operators most often underestimate. "We'll keep our activities in a shared Drive folder" is the plan; six months later, half the team teaches from files they've since re-edited on their own laptops, the shared folder has three subfolders named "READING v2" / "reading final" / "reading NEW", and new tutors get a Loom video that no longer matches the current lesson shape. The fix is not more Notion pages — it's a mechanic that takes one lesson from one tutor's library and copies it into the libraries of the specific tutors you want teaching from it.

Concretely, the pattern that works is:

  • One tutor (or the company's curriculum lead) authors the canonical version of an activity. Not "the master copy in Drive" — the actual working activity, inside the classroom, that has been taught in real lessons and refined based on what worked.
  • The operator selects one or more activities and one or more recipient tutors, and copies. Each recipient gets a private editable copy in their own activity library — not a link to someone else's file, not a template they have to open-then-save-as. The copy is theirs, they can adjust it for their students, and their edits don't propagate back to the original.
  • Recipients see the copies clearly labeled (usually inside a distinct group in their library) so they can tell what the operator sent them apart from what they authored themselves. This matters because tutors are protective of their own material; a shared library that overwrites their personal work is a shared library nobody uses.
  • Copies from the platform's public marketplace (activities purchased from third-party sellers) are not redistributable inside the team. If your curriculum lead bought a phonics pack on a marketplace, the licensing usually restricts redistribution — a good platform enforces that guardrail server-side so you don't accidentally break a licence.

Everything else — versioning, editing rights, "please update your copy," change-log — is downstream of this basic push-copy mechanic. Without the copy step working cleanly, curriculum drift is inevitable.

What a platform needs to ship for the multi-tutor case

A shortlist for judging whether a virtual classroom is set up for a tutoring company rather than a solo tutor:

  • Branded classroom on your own domain (or a company subdomain the platform provisions). Families should see your name, your logo, and your colors — not the platform vendor's. The classroom URL is the primary thing families type into their browsers weekly; if it doesn't say your brand, you're building someone else's brand every lesson.
  • Admin dashboard over your team. The operator needs a view of all tutors, all connected families, all lessons, and lesson-level session recordings — from one login, without asking each tutor to screenshot their calendar. This is the difference between "we have a company" and "we have a group of freelancers wearing our shirt".
  • Shared, copyable lesson library. Per the previous section — the operator (or a designated curriculum lead) can push activities into any tutor's personal library, cleanly grouped so recipients know what came from the company vs. what they authored.
  • Unified scheduling and booking. Families book across the team from one URL. Cross-tutor double-booking (a student booked with two of your tutors at the same time) is prevented at the platform layer, not by a spreadsheet check.
  • One invoicing surface, with your brand on it. Whether you bill families directly or the platform bills on your behalf, the families see one company name on the invoice — not five tutors' individual PayPal accounts.
  • Support for both tutors and families that doesn't route back to you. Live human support (in-app chat, phone, email) that a tutor or parent can reach directly during a lesson-day incident. Every escalation the platform handles is an hour you don't spend on it.
  • Multi-device support that isn't a footnote. Your families are on Chromebooks, iPads, Android tablets, older Windows laptops. If any student's device is the "not supported" one, that family churns — and at a multi-tutor company you feel the churn on the team's revenue, not just one tutor's hour.
  • Session recording pipeline for quality review and absent-student catch-up. The operator needs recorded lessons for occasional QA (was Tutor 4's new-family trial delivered the way we teach?) and for family catch-up when a student is out sick. This is a platform capability, not a bolt-on.
  • An API for the standard operations. At some point (usually past 10 tutors) you want to pull teaching-time reports, lesson lists, and session data into your own reporting or accounting system. An enterprise API that speaks the standard nouns (teachers, lessons, sessions, teaching-time) matters more than a slick admin UI at that scale.

How Koala for Business handles it specifically

If you're evaluating Koala for Business (the multi-tutor / white-label version of Koala Go, which we set up for tutoring companies who've grown past the solo-tutor shape), here's what you actually get and where the current limits sit:

  • A branded version of Koala hosted on your own domain. Your tutors and families see your logo, your colors, your name — not "Koala". The underlying platform is Koala Go with the full Pro feature set (cobrowser, 3D Playground, PDF and PowerPoint uploads on the interactive whiteboard, in-lesson rewards) available for every tutor on your team, on a classroom URL that reads as your brand.
  • An admin dashboard over your team. The Koala for Business portal gives your operator a view of all tutors, teaching-time reports, per-teacher session lists, and recording access. The routes that matter are exposed both as an admin UI and as an enterprise API (/v1/teachers, /v1/lessons, /v1/sessions) authenticated with a Bearer token, so you can also plug the data into your own reporting and accounting.
  • Copy Activities — the shared-lesson-library mechanic. This is the feature we shipped specifically for the curriculum-drift problem above. From the Copy Activities tab in the business dashboard, an admin picks a source teacher, ticks the activities to share (individually or "select all"), and ticks the recipient teachers. Copies land in each recipient's activity library inside a group called "Sent by admin", clearly labeled so the tutor can tell operator-pushed content apart from their own. Guardrails we ship on purpose:
    • Activities that were bought from the Koala Marketplace can't be copied — the licensing on marketplace activities restricts redistribution, and we block that server-side so you can't accidentally break it.
    • Name collisions get auto-suffixed ("Alphabet Practice", "Alphabet Practice (2)"…) — one activity can be pushed to a team twice without overwriting a tutor's earlier edits.
    • Copies stay editable by the recipient tutor; their edits do not propagate back to the source. Curriculum is pushed, not shared-and-locked — because tutors legitimately need to adapt a shared plan for individual students.
    • In production, Koala staff accounts can't be a copy source (we enforce this on the server too) — the team library you're building is yours, not a mirror of Koala's demo content.
  • 24/7 live in-app support for every tutor and every family. Our support team replies in under two minutes — often in seconds — around the clock. Your tutors and their families reach us directly during a lesson-day incident; you don't get pulled into it. Every escalation the support team handles is an hour you don't spend on it.
  • Direct access to a Customer Success Manager via Slack. Not a ticket queue; a Slack channel with a named CSM. This is the mechanic that keeps a multi-tutor customer's operational asks from being routed through a support form.
  • Session recording pipeline for enterprise sessions. Session recordings are processed on a dedicated GPU pipeline (custom-built FFmpeg with NVENC hardware acceleration) and made available for quality review and family catch-up.
  • Multi-device support for how your families actually connect. Chromebooks, iPads, Android tablets, and computers — all first-class. If a family's device runs a modern browser, the classroom runs.
  • Contractual 30-day launch. From signature to your team running live lessons is 30 days. That includes the branded classroom setup, DNS work if you're hosting on your own domain (five-minute DNS change on your side; we do the rest), Koala for Business account provisioning for each of your tutors, and testing.
  • Billing floor: 100 active hours per month. Koala for Business is priced with a minimum billable floor of 100 active teaching hours per month (we bill the minimum whether or not your team teaches all of them). Below that floor you're better off staying on individual Koala Pro seats ($25.99/mo monthly, $21.99/mo annual per tutor) — the multi-tutor overhead we ship isn't paying off for you yet. Above that floor, the platform-plus-support-plus-branded-domain math starts to work.
  • Case studies of what this looks like in production. Koala for Business is currently in production at Tutor Doctor, The Literacy Corner (a specialized reading-intervention practice for students with learning differences, running Orton-Gillingham instruction), Nihaoma Mandarin, Ladder Learning Services (an Atlanta-based reading nonprofit), Imerica Education, and Learning Success Academy. Different subject, different scale, same platform.

Honest limits to flag up front: Koala for Business is the right pick past 5-ish tutors, not before. At solo or 2-tutor scale the fixed costs (100-hour floor, launch project, contract) don't repay themselves — you're better off on individual Koala Pro seats and revisiting when the team crosses the "curriculum is drifting and I'm the bottleneck" threshold. And for tutoring schools running formal 20-student cohorts with an LMS-shaped assignment loop, Koala for Business is still a tutoring platform — you'll likely want an LMS beside it. If any of that describes your business shape, we'd rather tell you honestly than pull you into a plan you don't need yet.

Where a multi-tutor shape is the right business move

Signals it's time to hire or subcontract:

  • You have a waitlist that keeps repopulating faster than you can teach. If raising rates twice hasn't cleared the queue, that's real demand. A trusted colleague you can route overflow to is the smallest-step version; hiring is the larger one.
  • You're turning away students in a category adjacent to yours (a different subject, a different age range, a specialization you don't teach). An adjacent-subject tutor on your team expands your practice's footprint without you re-training.
  • Your reputation is bigger than your teaching hours. When parents recommend "the [Your Name] school" more than they recommend you individually, that's the brand outrunning the founder — the multi-tutor shape lets you deliver on the brand.
  • You want to trade some per-hour margin for capacity and calendar freedom. A team of tutors under your brand can generate more revenue than you personally can teach, and it eventually gives the founder days off. Solo tutoring, done well, is a demanding job with a hard ceiling.

Where staying solo is the right business move

Signals to not hire:

  • Your competitive edge is specifically you. A dyslexia intervention specialist with 20 years of clinical experience is not easily replicated. Families pay a premium for that specific person. Hiring dilutes what they're actually buying.
  • Your operational overhead is already 15+ hours/week and you'd rather teach. A team makes the ops problem bigger before it makes it smaller; if you're already resenting your admin load at 20 students, growing to 5 tutors and 100 families will not fix your calendar — it will destroy it for the first six months.
  • You've never enjoyed managing anyone. This is a real answer. Some of the best solo tutors are terrible small-business owners and know it. Recognize this before the third resignation letter.
  • Your rates aren't yet at the top of your local market. Raising prices is almost always cheaper than hiring. Do the pricing work first (see how much should I charge for online tutoring?).

Common failure modes to avoid

  • Hiring before your solo practice is a real business. If your own solo practice is unprofitable, adding tutors under your brand does not fix it — it multiplies the loss. Get the unit economics right on one tutor before hiring a second.
  • Skipping curriculum standardization. Assuming your new tutor will "figure out how we teach" is the leading cause of quality drift. Write the lesson shape down, teach it explicitly during onboarding, and use a shared library your tutors are actually copying from — not a Drive folder no one opens.
  • Under-investing in tutor onboarding. A new tutor's first ten lessons determine whether they'll retain families or churn them. Plan a real onboarding week — shadow lessons, walk-through of the shared library, a supervised first trial — not "here's the classroom link, good luck."
  • Contractor vs employee misclassification. Every country (and in the US, every state) has different rules on when a tutor working for your company is legally a contractor vs an employee. Getting this wrong is expensive on back-taxes and potentially on penalties. This is a "check your local rules and talk to an accountant and a lawyer" call — the specifics vary by jurisdiction and are not something a page like this can conclude for you.
  • Founder becoming tier-1 tech support. If every parent's connection issue reaches you, you'll spend your growth phase in the wrong role. Pick a platform whose support team the tutors and families talk to directly.
  • Fragmented brand across tools. If Tutor 2's parents click a Zoom link and Tutor 4's parents click a Google Meet link, families experience two different tutoring companies. Consolidate onto one branded classroom before your first hire's first lesson.
  • Not tracking teaching-time per tutor. At 5+ tutors, "how many hours did each tutor teach last month?" is a real payroll question and a real quality signal. If your platform can't tell you that from one dashboard, you'll spend a day a month rebuilding it from tutors' spreadsheets.
  • Under-pricing the seat. Sub-contractor rates that leave you with a $2/hour margin per tutor after platform fees are a business that fails at the first rough month. Do the margin math per tutor before you sign your first hire (see how to structure lesson packages for the pricing side).
  • Buying a platform you can't grow into. Every switch is a project — new links for parents, retraining tutors, rebuilding the shared library. Pick a platform whose top tier covers the size you plausibly hit in the next 24 months, not just the size you are today.

How to decide, in one paragraph

If you're still under 3 tutors, stitched tools plus a shared Drive is genuinely fine — don't over-build. If you're between 3 and about 10 tutors and each tutor is a fully solo practice under your brand, per-seat solo classroom licenses for each of them is usually the right shape, and Koala Pro at $25.99/mo per tutor is one honest option in that category. If you've crossed roughly 5 tutors, you're carrying real operational overhead, and any of the three problems above (curriculum drift, fragmented tools, founder-as-support) is costing you a day a week or more — a purpose-built multi-tutor platform starts making the math work, and Koala for Business is one of the ways to get there (30-day launch, branded classroom on your domain, Copy Activities for the shared lesson library, 24/7 live support your tutors and families reach directly, 100 active hours/month floor). Whichever shape you pick, do the curriculum-standardization and tutor-onboarding work regardless — those are business problems, not platform problems, and no software can substitute for having written down how a lesson at your company runs.

If you're considering Koala for Business specifically, the honest starting point is a conversation, not a signup — the setup is a real project and we'd rather scope it against your actual team shape than have you self-serve into the wrong plan. You can apply at business.teachwithkoala.com/apply or write to koala@teachwithkoala.com with a sentence about the size of your team and how you teach today, and we'll give you an honest read on whether it's the right time.

Related answers

More answers on this topic