Build vs Buy: What a Custom Online Academy Actually Costs

Founders hear “we should build our own platform” and picture a unique product. What they are usually describing is bookings, video, roles, and invoices: the same four portals every tutoring business needs. Building that from scratch is a software company, not a tutoring company.

Buy a white-label academy when you need to teach and sell. Commission a custom app when your workflows, integrations, or product idea cannot fit a packaged platform. Both paths exist at Launch Your Academy. Most education businesses should buy first.

What custom EdTech actually costs

A credible custom build for admin, teacher, student, and parent portals, plus payments and live class, routinely starts around $50,000 before you are proud to show it. That number is a floor, not a slogan. Scope expands the moment you add curriculum builders, AI homework help, analytics, and mobile-quality video.

The quote is not the expensive part. The expensive part is what happens after launch:

• A developer (or an agency retainer) for bugs, browser changes, and security patches.
• Hosting, monitoring, backups, and someone who answers when a Friday-night class will not join.
• Payment and identity updates you did not plan for: Stripe API versions, school SSO, new tax rules.
• Opportunity cost. Six months of build is six months you are not enrolling families on a finished product.

If you already employ engineers for a product that is not a tutoring OS, custom can still be rational. If you do not, you are volunteering to become a CTO.

What you get when you buy a white-label platform

You get the unglamorous work already done: four roles, branding on your domain, scheduling, classrooms, Stripe connected to your account, and an AI homework layer for students. You pay a subscription instead of a build invoice. You can be live in days, not quarters.

You give up some uniqueness. You cannot invent a totally new booking philosophy in week one. For 90% of academies, that is a feature. Constraints keep you teaching.

When custom is the right call

Choose a custom education application when the standard product would force a lie about how you operate. Examples:

• You need deep integrations the packaged platform does not have (specific SIS, billing, or internal tools).
• Your product is not 1-on-1 tutoring as the core motion (cohorts, assessments, or a marketplace of your own with different economics).
• Compliance or procurement at a district or large school group requires architecture you must own.

That is what our custom solutions work is for. We would rather tell you to use the standard platform than sell you a build you do not need.

A simple decision rule

1. List the jobs: brand, teachers, students, parents, pay, teach live, homework between sessions.
2. Demo a white-label product against that list. If it covers the jobs, buy it.
3. If two or more jobs are truly impossible, scope a custom app for those jobs only. Do not rebuild the rest for sport.

Build vs buy is not a personality test. It is whether you want to run an academy this term. If you do, start on the platform. If the demo proves a hard gap, book a custom conversation with the gap written down.