The war for K12 students had begun
It was 2017 and every edtech investor in India was in the same conference rooms. BYJU'S was approaching a $1 billion valuation. Unacademy was growing. The market was generating decacorn-sized projections for anyone who could claim traction in K12 learning. In this environment, Vedantu closed its Series A — and found itself sitting on a harder question than "how do we grow?"
The question was: what exactly are we building?
Vamsi Krishna and his co-founders had been here before. They'd built Lakshya, a test-prep chain, scaled it to thousands of students across multiple cities, and sold it to MT Educare. They came back for a second act with a bigger idea — but a more complicated product. Vedantu (from "Veda" — knowledge, and "Tantu" — network) was a live one-on-one tutoring platform connecting students in classes VI–XII with teachers over a custom low-bandwidth video system called WAVE. By 2017, Vedantu had served 40,000+ students across 90 cities with 200+ teachers on the platform.
The pitch was differentiated from the market's default: not recorded videos like BYJU'S, but live personalised attention — the closest thing to having a private tutor, delivered to any smartphone with a 2G connection. Sessions were recorded for revision. Teachers were rated, and anyone below 3.5 out of 5 was removed. The marketplace economics were standard: Vedantu retained 25–35% per session; the teacher got the rest.
Good fundamentals. Real traction. And yet at the Series A, a single question kept surfacing in leadership conversations: where does the product start and where does it end?
The Decision
Getting the product definition wrong at Series A isn't just an academic exercise. It shapes team structure, roadmap allocation, investor narrative, and what you build next. Define too narrowly — "the product is a tutoring session" — and you miss the infrastructure that makes sessions worth anything: teacher selection, quality enforcement, content standards, rating systems. Define too broadly — "the product is learning outcomes" — and you're committing to build things you don't yet know how to measure.
Vedantu's portfolio at Series A was more complex than a single product line. It included live one-on-one tutoring for classes VI–X (CBSE and ICSE), doubt-clearing sessions for classes XI–XII, competitive exam prep (NTSE, KVPY, IMO, JEE Mains), and the WAVE technology platform. Each segment served a different user at a different price point with different teacher requirements. A class VI math tutor and a JEE Mains coach are not interchangeable supply. Treating the portfolio as one product would mean building one metric dashboard, one teacher onboarding flow, and one quality bar for a user base with radically different needs.
The deeper question was about which layer Vedantu was competing on. Was it a teacher marketplace — where the product is matching supply and demand and the platform earns on transaction volume? Was it a live-tutoring SaaS — where the product is the WAVE technology and teaching happens to run on top of it? Or was it a learning-outcomes business — where the product is the student's improved performance, and everything else is a means to that end?
These aren't just semantic distinctions. Each model has a different unit of value delivery, a different metric for success, and a different competitive moat. A marketplace business measures GMV, supply growth, and match quality. A SaaS business measures seats, churn, and NPS. A learning-outcomes business measures grade improvement, conversion to competitive exam success, and lifetime student value.
Vedantu's real answer was that it was all three — but at different depths, in different product lines. The class VI tutor market was primarily a marketplace play. The JEE Mains prep segment was closer to an outcomes business, where parents were paying for results and would churn if grades didn't move. The WAVE platform was a strategic asset, not a product to be monetised separately, but it needed roadmap investment because the tutoring UX rested entirely on it.
The right product framing: Vedantu was a live-tutoring marketplace with an outcomes accountability layer, enabled by proprietary low-bandwidth video infrastructure. Each word in that sentence did work — and the prioritisation hierarchy fell out of it.
What Worked
The clearest success in this period was the WAVE investment. Every competitor in live online tutoring faced the same problem: India's internet was patchy. Zoom was a bandwidth hog. Building a custom whiteboard with optimised audio and video for 2G/3G connections wasn't glamorous engineering, but it was load-bearing. The product literally couldn't function at Vedantu's addressable market without it. This is a case where infrastructure investment preceded product ambition — WAVE was the reason a student in Patna could have a functional tutoring session that felt genuinely live.
The teacher quality enforcement also worked. The 3.5-star floor with enforcement created a marketplace dynamic that elevated overall supply quality over time. Early marketplaces often resist removing low-rated supply because every seller is a supply-side relationship. Vedantu's willingness to cull the bottom of the teacher list made the marketplace more trustworthy for students and premium for teachers who stayed. The quality bar became a recruiting pitch: "only top teachers stay on Vedantu."
The vernacular expansion in content — adding Hindi-medium curriculum alongside English — was a product decision that opened the market beyond metro students and English-medium parents. The total addressable market for K12 tutoring in India is not the English-speaking upper-middle class; it's every family that wants their child to perform better academically. Getting the language and curriculum right for Hindi-medium students was unglamorous but market-expanding.
What Failed
The harder problem was portfolio coherence as Vedantu tried to serve both K12 general tutoring and competitive exam prep simultaneously. These segments have different marketing motions, different teacher profiles, different session formats, and different success metrics. A class VII student and a JEE aspirant share an age group but not a product need. Running both with the same UX, the same teacher onboarding, and the same session format created friction in both — not enough test-prep depth for JEE parents, too much intensity for parents of younger kids just wanting math help.
The marketplace pricing model also had a structural tension. Paying teachers per session meant the incentive was to deliver sessions, not outcomes. A teacher who kept a student engaged for months was earning well whether or not the student's grades moved. Building outcomes accountability into a per-session marketplace requires explicit design — bonus structures for grade improvement, retention-linked pricing, some form of output measurement. At Series A, this layer was underdeveloped.
The doubt-clearing segment was arguably a separate product bundled into the same app. Doubt clearing is asynchronous and demand-spiky — a student needs help with a specific problem, wants a response in minutes, and doesn't necessarily want a 45-minute session. This use case has a different unit economics, a different session structure, and a different teacher-to-student ratio than scheduled tutoring. Forcing it into the same interface and the same marketplace created a confused experience for both students and teachers.
What a PM Should Take From This
Portfolio clarity is not a slide in a deck — it's a constraint that governs every downstream decision. Before Vedantu's Series A team could build a roadmap, they needed to answer three questions explicitly: which product line is the growth driver, which is the moat, and which is the drag? Without that hierarchy, every team pulls toward what they think the product is, and the roadmap becomes a negotiation between factions.
The marketplace-vs-outcomes tension Vedantu faced is endemic in edtech. Any platform that helps students learn faces the same design fork: optimise for engagement (time on platform, sessions booked) or optimise for outcomes (grade movement, exam pass rates). These can align, but they don't naturally. A student who needs six sessions to understand a concept generates more revenue than one who gets it in two. Designing the product to reward teaching effectiveness rather than teaching volume requires deliberate choices about pricing, incentives, and success metrics.
The deeper lesson is about platform layer discipline. Vedantu's WAVE technology was a competitive moat — but only if it stayed internal infrastructure rather than becoming a separate product. Many startups at this stage are tempted to monetise their internal tools. Sometimes that's right. In Vedantu's case, the WAVE platform's value was the marketplace quality it enabled, not its commercial potential as a standalone SaaS. Knowing what not to productise is as important as knowing what to build.