Cost to Build a Tutoring Marketplace Like Wyzant: What EdTech Founders Actually Pay

A product manager at a mid-size professional services firm gets a budget to build an internal coding skills platform for junior hires. The firm has 200 new grads each year who need to ramp on Python, SQL, and cloud tooling. They consider Wyzant -- 80,000 tutors, instant access, no build cost. The problem: Wyzant is a public marketplace. Their internal tutors (senior engineers willing to teach) cannot set up private sessions only visible to firm employees. The fee structure does not accommodate corporate invoicing. The parent consent workflows built for K-12 users add friction the firm's adult employees do not need. And the 25% take rate applies on top of whatever rate the internal tutors charge.

They are not building a clone of Wyzant. They are building a private tutoring marketplace for a specific community. That distinction changes almost everything about the build.

This article is for founders and product leaders in that position: people building niche tutoring or skill-learning marketplaces -- coding instruction, music lessons, test prep, corporate L&D -- where Wyzant's generalist model is the wrong fit. What follows covers real build costs, what COPPA compliance and 1099 payouts add to scope, how the cold start problem plays out in tutoring specifically, and the thresholds where building beats listing.

How much does it cost to build a tutoring marketplace like Wyzant?

Building a two-sided tutoring marketplace costs $80,000 to $250,000 depending on scope. A V1 with tutor profiles, booking, video sessions, and Stripe Connect split payments takes 14--18 weeks. A full platform with COPPA compliance, background checks, automated 1099 tax filing, and mobile apps takes 28--36 weeks.

What moves cost within these ranges: whether you need COPPA compliance (adds 4--6 weeks for parent consent flows and minor data handling), the complexity of the Stripe Connect payout model (direct charges vs. destination charges vs. separate charges and transfers -- each has different compliance surface area), whether background check integration is in scope, and whether you need native mobile apps. Cross-platform mobile (React Native or Flutter) saves $30,000--$50,000 compared to building iOS and Android natively. The 1099 compliance layer is isolated enough that it can be deferred to V3 -- but the W-9 collection workflow at tutor onboarding must be designed in V1 so you are not retrofitting it when your first tax season arrives.

How Wyzant makes money -- and what your margin looks like when you build

Wyzant charges students the full lesson rate and remits 75% to tutors. The 25% take rate is the platform fee. According to the US Bureau of Labor Statistics Occupational Outlook Handbook, the median hourly wage for salaried tutors and instructors is $28.25/hour (May 2023 data); marketplace tutors who set their own rates typically charge $30-$200+ per hour. At the median US marketplace tutor rate of $50/hour, Wyzant earns $12.50 per session hour. At scale -- with millions of sessions per year -- that is a substantial business. Tutors set their own rates from $30 to $200+ per hour. A tutor charging $75/hour takes home $56.25. The gap is the margin Wyzant monetizes.

When you build your own marketplace, your monetization model is a design choice. The four options used by EdTech marketplaces:

A take rate on each transaction (what Wyzant does). Typical range is 10--25% for tutoring marketplaces. Lower than Wyzant's 25% gives tutors an economic reason to prefer your platform.

A subscription from students. Preply's model: students pay a monthly fee for a set number of lesson credits. Cambly uses a similar structure for ESL. Predictable revenue, but subscription conversion requires more demonstrated value before the first payment.

A subscription from tutors. Charge tutors a monthly listing fee in exchange for visibility and leads. No take rate on sessions. This model attracts tutors with high session volume -- they pay less per session than under a take rate. Risk: tutors have less incentive to complete sessions they can book off-platform after the introduction.

Corporate contracts. L&D teams at companies buy a block of tutoring hours for employees. Invoice billing, not card-on-file. This model has the highest average contract value and the lowest churn. It also requires a procurement-friendly interface that Wyzant's consumer UX does not support.

Most niche tutoring platforms use a hybrid: a modest take rate (10--15%) combined with a premium tutor subscription tier that offers better search placement, more calendar flexibility, or analytics on student outcomes. The hybrid protects revenue on low-volume months and rewards power tutors who drive most of your session volume.

Who builds a tutoring marketplace instead of listing on Wyzant?

Four types of organizations find that Wyzant's model works against their specific goals.

Corporate L&D teams building internal skill platforms

A technology company running quarterly onboarding cohorts for software engineers needs internal skill routing -- connecting new hires to senior engineers who can teach specific topics. Wyzant is public. Their sessions would require the internal tutor to set up a Wyzant profile, and any student could book them. Corporate confidentiality requirements and fee structure make a marketplace listing unworkable. A private tutoring marketplace -- accessible only to employees, with corporate invoicing, manager-level reporting on session completion, and skill-level tracking -- is worth building at $80,000--$130,000 for a company running 500+ tutoring sessions per year.

Niche skill platforms where community is the product

A coding bootcamp that has been running cohort-based courses wants to offer alumni access to one-on-one mentorship with working engineers. The population of both tutors (engineers willing to mentor) and students (alumni) is a closed network. Wyzant's 80,000 tutors are irrelevant -- the mentors are people the bootcamp already knows. The platform's job is scheduling, payment, and session management for a defined community. A niche marketplace here wins on trust and relevance that a general platform cannot replicate.

K-8 school districts building parent-facing tutoring access

A school district in Texas wants to connect district-certified tutors with families of students who need academic support. The tutors must have passed district-required background checks. Sessions must align to the Texas Essential Knowledge and Skills (TEKS) curriculum. Parents pay through a district-managed portal. COPPA compliance is non-negotiable for students under 13. Wyzant's onboarding flow was not designed for district procurement, curriculum alignment, or FERPA compliance at the district level. Building a purpose-fit platform at $130,000--$180,000 is the only option that meets all of those requirements simultaneously.

Test prep companies converting group content to 1:1 instruction

A company that runs SAT/ACT group prep courses wants to add a 1:1 tutoring layer -- matching students with instructors who know their specific weak areas from diagnostic assessments. The instruction is not generic; it is tied to diagnostic data the company already holds. Wyzant tutors do not have access to the company's proprietary diagnostic data or curriculum. Building a tutoring marketplace that integrates with the company's existing diagnostic engine, routes students to matched tutors based on assessment results, and tracks improvement over sessions is a product extension that requires a custom build.

What features does a tutoring marketplace V1 actually need?

How the build timeline breaks down week by week

Most tutoring marketplace builds fail in one of two places: the Stripe Connect payout model is chosen incorrectly in week two and requires a rewrite by week ten, or the video session integration is scoped as a feature addition rather than a core architectural requirement and gets rushed. Both failures cost more to fix than to design correctly from the start.

Weeks 1--2: Data model and payout architecture. The tutor--student relationship model (can a student have multiple active tutors? can a tutor set different rates per subject?). The Stripe Connect payout model decision: direct charges keep funds in the connected account and are simpler but limit platform-level reporting; destination charges route through the platform account and give you full visibility on every transaction. For a marketplace where take rate reporting and 1099 tracking matter, destination charges or separate charges and transfers are the right choice. This decision cannot be changed without rebuilding the payment integration. Make it in week one.

Weeks 3--5: Tutor onboarding and profile system. Tutor registration form with credential fields, subject area taxonomy, availability calendar setup, hourly rate configuration. W-9 data collection fields (required for 1099 compliance later -- design them in even if V3 is months away). Stripe Connect account creation for each tutor, linked to their platform profile. Admin verification queue.

Weeks 6--8: Student-facing search and booking. Search index with filtering by subject, price range, availability, and rating. Tutor card grid. Profile detail page. Booking request flow: student picks time slot, platform checks tutor availability, sends booking request, tutor accepts or declines. Confirmation emails triggered on booking state change.

Weeks 9--11: Payment processing. Stripe Checkout or Stripe Payment Element for student card capture. Destination charge creation on session confirmation. Platform take rate calculation and application. Tutor payout on configurable schedule (weekly payouts for V1 are standard). Refund workflow for cancelled sessions within the cancellation window.

Weeks 12--14: Video session integration. Daily.co room creation API tied to booking record, or Zoom SDK embedded session. Session start and end triggers. Session duration tracking for billing validation (if session ends early, refund logic). Tutor join link vs. student join link generation and delivery by email and in-platform.

Weeks 15--18 (V1 launch): Basic messaging between booked student and tutor. Admin dashboard with session volume, payout totals, and tutor status management. QA pass on payment edge cases (failed charges, partial refunds, payout delays), booking conflicts, and video session reliability.

Weeks 19--26 (V2): COPPA parent controls (age gate, parental consent flow, parent dashboard, under-13 data handling). Background check integration (Checkr or Sterling API, tutor badge, admin review queue). Review and rating system with post-session prompt. Session notes for tutors with parent-visible access for minor accounts. Full messaging system with admin access for trust and safety review.

Weeks 27--36 (V3): 1099/W-9 automation. AI tutor matching engine. Corporate training module. Native mobile apps. Advanced analytics dashboard.

Compliance your platform must get right

COPPA for under-13 users

COPPA applies to any online service that knowingly collects personal information from children under 13. A tutoring marketplace serving K-8 students cannot allow a child to create an account, be matched with a tutor, or participate in a video session without verifiable parental consent first.

The compliance requirements in practice: an age verification gate at registration that cannot be bypassed by a child entering a false birthdate (courts have found that age gates requiring only a birthdate are inadequate -- a parental consent email confirmation is required). A parent consent flow where the parent receives an email, must click through to a consent page, and must provide a verifiable parent name and email address. A parent account that controls the child's bookings -- the child cannot book independently. Parental notification for any new tutor connection. Restricted data collection on the child's profile -- no photo uploads, no location data, limited personal information.

Session recordings involving minors require special handling. Storage access must be parent-controlled. Retention must be limited and disclosed in the privacy policy. Tutors must be informed that sessions involving minor students may be subject to parental review.

The FTC enforces COPPA with civil penalties up to $51,744 per violation per day. The YouTube settlement in 2019 was $170 million, and the Musical.ly settlement that same year was $5.7 million. According to Grand View Research, the global online tutoring services market is projected to reach USD 23.73 billion by 2030, growing at a CAGR of 14.5% -- a market where trust and safety compliance is table stakes for platforms serving minors. A tutoring platform that allows under-13 users to interact without parental consent faces the same exposure. Build the parent control layer in V2 scope. Do not defer it.

Background checks for tutors working with minors

A tutoring marketplace that connects its tutors with children under 18 cannot rely on self-reported credentials. The liability exposure for facilitating a session between an unvetted adult and a minor is significant. Background check integration with Checkr or Sterling adds a verification layer: criminal background, sex offender registry check, and identity verification. The result populates a tutor's verification badge on their profile.

The practical workflow: tutor completes onboarding and submits consent for the background check. Checkr or Sterling returns a result (clear, consider, or dispute). Clear results automatically activate the tutor's profile. Consider results route to an admin review queue. Tutors whose background check is not cleared cannot appear in student-facing search results. Parents and school districts will ask whether your tutors are background-checked before committing to the platform. The answer must be yes, and it must be verifiable.

1099/W-9 tax compliance for marketplace payouts

Any tutor who earns $600 or more on your platform in a calendar year must receive a 1099-NEC. The platform is the payer. The IRS holds the marketplace operator responsible for collecting W-9 information (legal name, address, Tax Identification Number), issuing 1099-NEC forms by January 31, and filing the corresponding data electronically with the IRS.

Stripe Connect supports 1099-K reporting for high-volume card transactions, but 1099-NEC for services income is a separate requirement. Services like Track1099 or Yearli can automate the electronic filing step. The platform still needs to collect W-9 data at tutor onboarding (design the fields in V1 so they are not retrofitted later), track each tutor's cumulative annual earnings in a dedicated ledger, generate 1099-NEC PDFs for qualifying tutors in January, and confirm delivery to the IRS before the deadline.

Penalties for failing to file required 1099 forms run from $50 to $290 per form, depending on how late the filing is. For a platform with 500 qualifying tutors, late filing at $290 per form is $145,000 in penalties. Build the W-9 collection in V1. Build the cumulative earnings tracker alongside the payout module. The filing automation can wait until V3 when session volume justifies it.

State tutoring regulations

Several states regulate tutoring as an educational service and require tutor credentials or platform registration. California's Commission on Teacher Credentialing has guidance on private instruction. Some states require tutoring businesses serving K-12 students to register as private schools or instructional entities. Texas has no state-level tutoring license requirement, but school district procurement channels require vendor registration.

These are not platform-level technical requirements -- they are legal registration requirements that vary by state and by the age of students your platform serves. Legal counsel with EdTech experience should review your platform's operation in the two or three states where you will launch before you open student registration.

The technical challenges teams underestimate

Supply-demand cold start: tutors first, students second

The cold start problem is the defining operational challenge of any two-sided marketplace. Every tutoring marketplace build that fails due to cold start has the same root cause: the team acquired student demand before securing tutor supply. Students registered, searched, found a thin catalog of available tutors, booked nothing, and left. First impressions in a marketplace are not recoverable in the same cohort.

As Sal Khan, founder of Khan Academy, put it in an April 2023 New York Times interview: "The right model for tutoring at scale is matching, not instruction -- the platform's job is to get the right human in front of the right student, not to replace the human." The quality of the match depends entirely on the depth of the supply catalog.

The sequencing that works: seed tutor supply before opening student registration. Reach out directly to independent tutors already active on Wyzant, Tutor.com, or university tutoring centers. Offer a zero-commission or reduced-commission period for the first three to six months. Target 30--50 tutors in your core niche before accepting the first student booking. Then run a targeted student acquisition campaign: paid search, school district outreach, or direct B2B if you are targeting corporate L&D.

The 30--50 tutor threshold is not arbitrary. A student searching for a specific subject should see at least three to five available tutors. For a niche marketplace with ten subject areas, you need three to five tutors per subject at launch to deliver a credible search result page. Below that threshold, the first students find empty result sets and leave before the tutor supply grows.

Trust and safety for sessions involving minors

A video call between an adult tutor and a child is a trust and safety surface that most marketplace builders do not plan for at the architecture level. The minimum requirements: tutor identity is verified (not just email-confirmed), session rooms cannot be joined without both a valid booking link and an authenticated account, session recordings cannot be downloaded by the tutor without parent consent, and the parent has access to session history including duration and any in-session notes.

Beyond the technical requirements, there is a moderation layer. A trust and safety review process that allows parents to flag sessions, a tutor suspension workflow that the platform can trigger immediately (not after a review cycle), and an admin interface that surfaces sessions flagged for review. These are not features that can be added after launch. A single incident involving a minor on a platform that lacked proper safeguards results in regulatory scrutiny, media coverage, and platform collapse.

Scheduling across timezones

A tutoring marketplace with tutors and students in different timezones needs timezone-aware scheduling from day one. This is not a feature -- it is a data model requirement. Every availability slot, every booking, and every session notification must be stored in UTC and displayed in the user's local timezone. Tutors in California booking sessions for students in New York, or corporate tutors in the US serving an international team, will generate timezone errors immediately if the booking system stores local times without timezone metadata.

The practical implementation: tutor availability calendar stores UTC times with the tutor's timezone context. When a student in a different timezone views the calendar, available slots are converted to the student's local timezone for display. Booking confirmation emails show the session time in each recipient's local timezone. Session reminders trigger based on UTC time relative to the UTC session start, not local time.

Teams that build the availability calendar with local times and add timezone conversion later typically find that existing bookings have incorrect times after the migration. Design the UTC-first data model before the first tutor enters an availability slot.

Build vs. Wyzant: when does the math tip?

Keep using Wyzant when: your tutors are generalists who benefit from Wyzant's existing student traffic. You do not have a distribution channel to acquire either side of the marketplace independently. Your platform budget is under $50,000. You are testing whether a tutoring niche has product-market fit before committing to a build.

List on Preply when: your niche is language learning. Preply has strong SEO and brand recognition in language tutoring specifically and a subscription model that converts language learners who want multiple sessions per week. The 18--33% commission is lower than Wyzant's 25% for high-volume tutors.

Use Cambly when: your niche is English language instruction for non-native speakers. Cambly owns that niche in several international markets and has the lowest barrier to tutor entry.

Build your own when: at least three of these apply.

You have a defined niche where Wyzant's breadth is a disadvantage. Coding tutors, music instruction, K-8 test prep in a specific state, corporate compliance training -- a focused community makes the cold start problem tractable because tutor and student acquisition channels are more specific.

The 25% Wyzant take rate would allow you to run a 10--15% take rate and still make margin. Tutors who net more per session on your platform than on Wyzant have an economic reason to shift session volume to your platform.

Your compliance requirements are beyond Wyzant's scope. COPPA-compliant parent controls for K-8, district credentialing for school partnerships, corporate invoicing for L&D teams -- none of these are available on Wyzant.

You need features that support a recurring relationship rather than one-off sessions. Session notes tied to curriculum, progress tracking aligned to learning goals, package-based pricing where a student buys ten sessions at a discounted rate -- these are product features, not marketplace features.

How the tutoring platform competitive landscape stacks up

Wyzant is the dominant US tutoring marketplace by tutor count. Approximately 80,000 tutors, broad subject coverage from K-12 to college to professional skills. 25% take rate. Student-first search experience with strong Google SEO. Weakness: the 25% take rate pushes tutor earnings down and creates an incentive to take sessions off-platform after the first introduction. No corporate L&D module, no COPPA-compliant parent controls for K-8, no curriculum-aligned session notes.

Tutor.com (owned by Nerdy, NYSE: NRDY) focuses on on-demand synchronous tutoring, with strong partnerships with school districts, libraries, and the US military. Revenue share model for tutors. Strength: institutional channel through school systems. Weakness: on-demand model means tutors are not dedicated to specific students -- no recurring relationship building.

Preply raised $66 million in a Series C in 2022 and is strongest in language tutoring. Subscription model for students. International student base. Strength: strong SEO and brand for adult language learners. Weakness: limited presence in K-12 academic subjects, test prep, and corporate skill training outside language.

Cambly targets ESL learners who want to practice conversation with native English speakers. On-demand, pay-per-minute model. Strong in international markets. Not a general tutoring platform.

Superprof is strong in the UK and France. Tutor subscription model (tutors pay a monthly fee to list). Active in music, arts, sports, and academic tutoring. US presence is limited compared to the European market.

A custom build beats all five on niche vertical depth, take rate economics, and compliance features that general platforms cannot justify building for niche segments.

Where tutoring platform builds go wrong

The failure mode we see most consistently in tutoring marketplace builds is building student-facing demand before locking in tutor supply. The sequence looks logical: acquire students, show tutors there is demand, tutors join. The reality: students who find no available tutors in their subject leave and do not return. Tutor acquisition after a failed student launch is harder because the platform's early reputation in the market is already set. Cold start sequencing is not a product decision -- it is a survival decision. Seed tutor supply first, then activate student acquisition.

The second failure mode is choosing the wrong Stripe Connect payout model in week one and discovering the constraint in week ten. Direct charges are simpler to implement but limit the platform's visibility into session-level revenue and make 1099 earnings tracking harder to implement later. Destination charges or separate charges and transfers give the platform full transaction visibility from the start. Teams that choose direct charges because they are easier to configure spend 4--6 weeks rebuilding the payment integration when they hit the reporting or compliance constraint. The payout model is an architecture decision, not a payment configuration detail. It belongs in the week-one scoping conversation.

The third failure mode is treating video session integration as a feature plug-in rather than a reliability requirement. Daily.co and Zoom SDK both offer embed-friendly APIs. But session reliability -- what happens when a student's browser blocks camera access, when a tutor's internet drops mid-session, when the session room times out before the tutor joins -- requires explicit handling in the session management logic. A tutoring session that fails on the student's first booking is a churned student. The video session integration must be QA tested across device types, browsers, and network conditions before launch.

How RaftLabs fits

We build two-sided marketplaces, and tutoring platforms sit squarely in our delivery history. The Stripe Connect payout model decision, the COPPA parent consent flow, background check integration with Checkr, and the cold start sequencing plan are all problems we have worked through before writing a line of product code. We scope them as architecture decisions, not feature tickets.

For a tutoring marketplace build, we work in fixed-price cycles of 12--14 weeks. V1 scope is defined in a two-week scoping engagement: we map the tutor onboarding flow, model the payout architecture, identify which compliance requirements apply to your audience (K-8 vs. adult vs. corporate), and design the cold start playbook before we build anything. The number in the proposal is the number you pay.

If you are building a niche tutoring or skill-learning marketplace -- for a corporate L&D team, a school district, a test prep company, or a focused community -- a scoping call is the right next step. Tell us your vertical, your target tutor and student populations, and your compliance requirements, and we will give you a realistic cost and timeline within two business days.