Buy vs Build: The Real Bill for Custom-Building an Education Platform

TL;DR

• Building a commercial-grade education platform (website + classroom + scheduling + CRM + payments + multi-client) starts with a 5–8 person product-and-engineering team and a 12+ month timeline
• Conservative first-year build cost is in the $250,000 class — 25x or more the buyout route (Professional from $10,000)
• The real build risk isn't money, it's shipping a half-product: most internal projects stall between "works" and "commercial-grade"
• The decision frame: is technology your core competency? If not, buy. Even if it is, price the opportunity cost first

The Full Build Bill

Minimum viable team

A commercial platform for education businesses — website, live classroom, scheduling and class-hour tracking, teacher management, student CRM, sales, online payments, multiple clients (admin/teacher/parent/student):

That's 7–10 people. At competitive fully-loaded rates for Southeast Asia / Middle East ($3,000–5,000/month/person), payroll alone runs $250,000–600,000 per year.

Timeline

• MVP (core loop): 4–6 months
• Commercial grade (stable, secure, multi-language, multi-currency, polished UX): 12+ months
• Ongoing iteration: forever

The underestimated hidden costs

1. Third-party integrations: RTC cloud, payment gateways (Stripe/Airwallex), SMS, email — each an independent commercial negotiation and integration effort
2. Multi-language and multi-timezone: five interface languages (EN/ZH/AR/VI/ID) and cross-timezone scheduling engineering far exceeds expectations
3. Security and compliance: payment security, data protection (GDPR/PDPA), permissions hardening — endless polish
4. Attrition risk: losing a core engineer is typically a body blow to an internal platform project

Buyout Comparison

The Half-Product Trap

The most common outcome of internal platform projects is not failure — it's stall:

• Core course features ship, but scheduling, attendance and teacher settlement — the "tutoring-flavored" parts — never finish, because the product manager doesn't know school-operations details
• The admin console works, but the parent app can't survive comparison with commercial products
• After launch, "edge cases" like multi-currency payments and multi-timezone schedules turn out to be core requirements

Every stalled month is another month the institution runs enrollment and attendance on legacy tools and manual processes.

When Is Building Actually Right?

Three cases:

1. You are already a technology team — the headcount exists; marginal cost is manageable
2. The education platform IS your product — you're selling the platform itself; technology is the moat (in which case you're XueyeEdu's peer, not customer)
3. Extreme regulatory or business uniqueness — commercial products genuinely can't cover it

The Middle Route: Buy + Customize

For most institutions the optimum isn't either/or:

Buy a mature platform for the 90% standard capability + custom-develop the 10% that's genuinely unique

This combines launch speed, delivery certainty and business fit. Enterprise source-code delivery preserves the long-term right to evolve the system independently — effectively a "semi-build" starting point at buyout pricing.

FAQ

Isn't custom development the most flexible option?

Flexibility presupposes shipping it. Commercial platforms respond to business change through custom development too — starting from a high-completion baseline. Build flexibility is theoretical, bounded by your team's bandwidth.

How do I trust the quality of a purchased platform?

Three checks: does the vendor demo the full flow live; do real customer cases exist; what do contract terms say about delivery and support. A mature commercial product has been stress-tested by many institutions' real operations — a first internal build hasn't.

Can a $10,000 platform really be comparable to a $250,000 build?

The difference is "exclusive," not "quality." Commercial vendors amortize R&D across customers; a build pays full freight for one institution. Education businesses run remarkably similar flows (enroll → schedule → teach → track → renew) — exactly the territory of standardized commercial products.

---

Torn between build and buy? Run the 18-question self-hosted selection checklist first, or contact us for a needs-fit assessment for your institution.