You Have Built a Real EdTech Business. Your Software Stack Is Still Pretending You Are a Startup.

At one hundred people, the EdTech platform is no longer a scrappy early-stage operation. There is a B2B sales team closing institutional deals. There is a B2C counselling team converting individual learners. There is a content ops team producing and maintaining course material across multiple programmes. There is a support team handling student queries, access issues, and complaints. There is an HR team running payroll, performance cycles, and recruitment. And there is a finance team managing enterprise invoices, individual student billing, GST filing, and revenue reporting simultaneously.

Five teams. Five sets of data. Five sets of tools. None of them talking to each other.

The B2B sales team closes an enterprise deal for 50 seat licenses. The finance team does not know until the account manager sends an email. The content team does not know which programme the enterprise client purchased until the ops team updates a shared spreadsheet. The support team does not know which employees of that enterprise are enrolled until three of them raise access issues.

The B2C counselling team converts 40 students in a week. The finance team's instalment tracking is three days behind. The content team cannot see which cohort these students joined. HR is running payroll from data that does not reflect last month's headcount change because the HRMS was not updated until the 15th.

This is not a people problem. It is a data silo problem. And at 100 to 200 people, data silos do not stay contained. They compound, cross every team boundary, and show up in the worst possible places: a missed enterprise invoice, a student with no course access four days after paying, a payroll run with the wrong headcount, and a revenue report assembled manually the night before the board meeting.

This article covers how Zopkit's connected modules eliminate these silos across sales, delivery, and finance — and what changes operationally when all five teams work from one source of truth.

I. The Silo Map: Where Data Dies at a 100-200 Person EdTech Platform

Before the solution, the problem deserves a precise anatomy. At this scale, the data silo is not a single gap between two tools. It is a network of gaps, each one small enough to manage manually at first, each one compounding at scale.

Silo 1: B2B Sales ↔ Finance

The enterprise sales cycle for an EdTech platform ends with a signed contract and a purchase order. The deal is marked Closed Won in the CRM. Then:

Finance needs to raise the enterprise invoice — but the CRM does not push deal data to the billing tool automatically
The invoice amount, the payment terms (30 days, 60 days, advance), and the GST treatment (B2B invoice requires client GSTIN) have to be manually entered by finance from the contract PDF
If the deal includes multi-year terms or quarterly billing, the recurring invoice schedule has to be manually configured
If the client negotiated a custom price, that custom price has to be manually communicated to finance and manually entered

The gap between deal closed and invoice raised is typically 3 to 7 days. For a platform billing Rs. 50 lakh per month in enterprise contracts, that delay is a cash flow problem, not a process inconvenience.

Silo 2: B2C Sales ↔ Academy

The B2C counselling team converts a student. The CRM marks them enrolled. Then:

Ops manually creates the student's account in the LMS
If this step is delayed or missed, the student has paid but has no access
The student raises a support ticket
Support opens the LMS and the CRM separately to diagnose — "they are enrolled in CRM but not in the LMS"
The fix is manual: ops creates the access; support closes the ticket

At 40 enrollments per week, this gap produces 4 to 8 access-related support tickets per week from students who paid and cannot get in. Each ticket takes 15 to 30 minutes to resolve. That is 1 to 4 hours per week of support time doing a job that should not exist.

Silo 3: Content Ops ↔ Sales

The content team is producing and maintaining course material. The sales team is selling it. These two teams almost never share a system.

The content team does not know which programmes are being sold most aggressively, so they cannot prioritise content updates for high-sales products. The sales team does not know when a content update or new module releases, so they are selling based on a curriculum that the content team changed last month.

When an enterprise client asks "what new content was added to the programme in the last quarter," the account manager does not know without asking the content team, who look at their internal tracker, which is a Notion page that may or may not be current.

Silo 4: Finance ↔ HR

At 100 to 200 people, payroll is a meaningful operation. The HR team manages headcount. The finance team runs payroll. These two functions require the same data — who is on payroll, at what salary, with what deductions — but in most EdTech platforms at this scale, they manage it in separate tools.

When a new team member joins, HR adds them to the HRMS. Finance adds them to the payroll tool separately. If one of these steps is delayed, the new hire's first payroll is wrong. When someone resigns, the same dual-update process runs in reverse.

The compliance layer — PF, ESI, PT, TDS — requires data from HR (who is employed, at what salary, in which state) to produce correct outputs. When that data lives in a tool the payroll system cannot read natively, every compliance calculation is only as accurate as the last manual sync.

Silo 5: Student Support ↔ Everything

Support is the team that pays the highest cost for every other silo. When a student raises an issue, the support agent needs:

Enrollment status: are they actually enrolled? (CRM or ops tool)
Payment status: have they paid? (billing tool)
Course access: do they have access to the right content? (LMS)
Previous interactions: have they raised this before? (support ticket system)

In the current stack, answering one support query requires opening four tools. A support team of 5 at 100 to 200 students per day is spending 30 to 40% of their working time switching between tools to answer questions that one connected record would resolve immediately.

II. The B2B Sales Motion: From Enterprise Deal to Live Cohort Without a Single Email to Finance

For a 100 to 200 person EdTech platform with a B2B sales motion, the enterprise deal flow is the highest-value operational process in the business. It is also, in most current stacks, the most fragmented.

The Zopkit B2B Deal Flow

Deal in pipeline:

The B2B sales team manages enterprise accounts in Zopkit CRM with a dedicated B2B pipeline: Prospecting → Qualified → Proposal Sent → Negotiation → Contract Signed → Onboarding → Active.

Each deal record holds: company name, primary contact, deal value, number of seats, programme purchased, agreed payment terms, contract start and end date, and any custom pricing or discount applied.

Deal closes:

When the deal moves to Contract Signed, Zopkit Finance automatically:

Creates a company billing account for the enterprise client
Generates the first invoice based on the deal value and payment terms configured in the CRM
Applies the correct GST treatment: B2B invoice with client GSTIN, IGST if the client is in a different state
Configures the recurring invoice schedule for multi-payment deals

Finance does not receive an email from the account manager. The invoice exists in their queue the moment the deal closes in the CRM.

Seats assigned:

The account manager assigns individual employee contacts to the deal in CRM. Zopkit Academy receives the enrollment list automatically. Each employee gets a course access email. The content team sees the enterprise cohort in the Academy dashboard with the correct programme, start date, and seat count.

Onboarding tracked:

The deal remains in the CRM at the Onboarding stage until a configurable completion criterion is met — typically, 80% of assigned seats have logged in at least once. At that point, the deal moves to Active automatically. The account manager is notified. The onboarding task list closes.

The gap that disappears:

The 3 to 7 day delay between deal closed and invoice raised becomes zero. The manual seat enrollment process that produced 4 to 8 support tickets per week disappears. The account manager stops spending 45 minutes per deal entering data into three separate tools after the contract signs.

III. The B2C Student Journey: Paid to Learning in Under 60 Seconds

The B2C counselling team at a 100 to 200 person EdTech platform is handling 200 to 500 leads per month across multiple programmes. The conversion process involves counselling calls, programme recommendations, scholarship approvals, and payment facilitation. The current stack handles this across a CRM, a payment gateway, an LMS, and a support tool — four separate systems for one student journey.

The Zopkit B2C Enrollment Flow

Lead enters pipeline:

Every lead from every channel — paid ads, organic, referral, webinar — enters the Zopkit CRM pipeline automatically via form embed or manually in under 60 seconds. The counsellor is notified and a follow-up task is created.

Counselling and conversion:

The counsellor works the lead through the pipeline. Every call outcome, every WhatsApp note, every email is logged on the lead card. The counsellor can see the lead's source, their programme interest, and every prior touchpoint before picking up the phone.

Enrollment:

When the student is ready to pay, the counsellor sends the enrollment link from inside Zopkit CRM. The student pays. Simultaneously:

CRM card moves to Enrolled
Zopkit Academy creates the student account and grants course access
Zopkit Finance generates and emails a GST-compliant invoice (SAC 999294, CGST/SGST or IGST based on student's state)
Welcome email sequence starts

The student is inside the course in under 60 seconds from payment. The support ticket that says "I paid but cannot access the course" does not exist.

Post-enrollment visibility:

The counsellor who converted this student can see their course progress from the CRM record. If the student drops off — no login in 7 days — the counsellor is notified automatically. They reach out. This is the retention touchpoint that most EdTech platforms miss because the CRM and LMS are separate and nobody is watching the gap between them.

IV. Content Ops at Scale: When the Course Is a Living Product

At 100 to 200 people with multiple active programmes, the course is not a static asset. It is a living product. New modules are added. Outdated content is updated. Industry expert sessions are recorded and added mid-cohort. Assessment rubrics are revised based on student performance data. The content ops team is managing this continuously, across programmes, for cohorts that are actively running.

What Zopkit Academy Gives the Content Ops Team

Content management without a developer:

Adding a new lesson, replacing a video, attaching an updated PDF, or reordering module content is done by the content team directly in Zopkit Academy. No engineering ticket. No CMS login. The content team owns the course content end-to-end.

Version-aware content delivery:

When a module is updated mid-cohort, the content team configures whether the update applies to the current active cohort, the next cohort only, or all cohorts. Students in an active cohort are not disrupted by updates intended for future cohorts.

Programme-level performance data for content decisions:

The content team sees, for every lesson:

Average completion rate: what percentage of enrolled students watched the full video or completed the reading
Average time spent: are students spending 2 minutes on a lesson designed for 15?
Quiz performance: average score, most commonly missed question, pass rate
Drop-off point: the specific lesson where the most students stopped progressing

This data tells the content team exactly where the programme is weak and exactly which module needs a revision. Not based on intuition or student complaints after the cohort ends — based on behaviour data from the cohort that is currently running.

Content calendar visible to sales:

The content team maintains a programme update log in Zopkit Academy. The B2B account management team can access this log to answer enterprise client questions about programme freshness without calling the content team.

V. Support at Scale: One Screen Instead of Four Tabs

At 100 to 200 people with an active student base of 2,000 to 10,000, the support team is the operational nerve centre. Every silo in the rest of the platform shows up as a support ticket.

Zopkit eliminates the most common support ticket categories by removing the conditions that create them:

When the support team does receive a ticket that requires investigation, the Zopkit student record gives them everything in one screen: enrollment status, payment history, course progress, previous tickets, and all communication history. The average resolution time drops from 20 to 30 minutes (opening four tools, finding the relevant data, diagnosing the issue) to 3 to 5 minutes (opening one record, reading one screen).

VI. HR and Payroll: Where Indian Compliance Meets EdTech Scale

A 100 to 200 person EdTech platform in India has a specific HR complexity profile. The team is typically spread across multiple cities — tech and content in Bengaluru, sales in Delhi and Mumbai, support in a lower-cost location. This means multiple Professional Tax slabs running simultaneously. It means PF and ESI managed at different contribution rates for different salary bands. And it means TDS calculations varying across hundreds of employees by tax regime, investment declaration, and projected annual income.

What Zopkit HRMS Handles Natively

Statutory compliance:

PF at 12% employee + 12% employer, with EPS and EPF splits calculated correctly
ESI at 0.75% employee + 3.25% employer for eligible employees
PT configured per state for each employee based on their work location
TDS calculated monthly under old or new regime per employee's declaration
Form 16 generated for all employees by June 15 of every year
EPFO and ESIC challan data generated without a separate reconciliation step

The payroll-finance connection:

When payroll is approved in Zopkit HRMS, the salary cost is automatically posted to the relevant cost centres in Zopkit Finance. The content team's payroll cost posts to the content operations cost centre. The sales team's cost posts to the sales cost centre. The finance team sees actual departmental cost without manually entering payroll data into the accounting module.

The HR-resource connection:

When a new team member is added in Zopkit HRMS, they appear in the relevant team in Zopkit Projects within 24 hours. When someone resigns, their capacity is removed from the resource pool automatically. The operations team's resource planning is always working from current headcount, not last month's org chart.

Performance management:

Goal setting, mid-year reviews, annual appraisals, and calibration are managed within Zopkit HRMS. The performance rating from the annual review feeds into the salary revision workflow. The revised salary updates payroll automatically. No separate salary revision entry in a different tool.

VII. The Revenue Dashboard That Runs Itself

For a 100 to 200 person EdTech platform with B2B and B2C revenue streams, accurate revenue reporting is not a once-a-month exercise. It is a continuous operational requirement. The founding team or management needs to know, at any point, the answer to these questions:

What is our total revenue this month, split by B2B and B2C?
What is our MRR from enterprise contracts versus one-time course enrollments?
What is the outstanding receivables position across all enterprise clients?
What is the blended gross margin per programme after content and delivery team costs?
Which B2C acquisition channel is producing the highest LTV students?
What is the instalment collection rate this month and which accounts are at risk?

In the current stack, these questions require a finance person to pull data from the billing tool, the CRM, the LMS, and the payroll system, assemble it in a spreadsheet, and present it at the weekly leadership meeting. The assembly takes half a day. The data is 48 to 72 hours old by the time it is presented.

In Zopkit, this dashboard exists natively. All the data — revenue, pipeline, enrollment, payroll cost — lives in one platform. The report does not need to be assembled because it was never disassembled.

VIII. The Migration Plan for a 100-200 Person EdTech Platform

At this scale, migration cannot be a cutover. It is a phased transition with parallel running at each phase to verify accuracy before retiring the legacy tool.

Phase 1 — Weeks 1 to 3: CRM and Sales Pipeline

Migrate B2B deal pipeline and B2C lead pipeline into Zopkit CRM
Import all active leads and enterprise accounts
Train sales and counselling teams on the new pipeline workflow
Run parallel with existing CRM for 2 weeks; verify data parity
Retire existing CRM at week 3

Phase 2 — Weeks 4 to 6: Academy and Content

Build active programme structures in Zopkit Academy
Migrate enrolled students into the correct cohorts
Upload or re-embed existing content
Run parallel enrollment flow for 1 week to verify auto-enrollment on payment
Retire existing LMS at week 6

Phase 3 — Weeks 7 to 9: Finance and Billing

Configure GSTIN, SAC codes, and invoice templates
Migrate enterprise billing accounts and active instalment schedules
Run one billing cycle in parallel with existing tool
Verify GST invoice output and payment matching
Retire existing billing tool at week 9

Phase 4 — Weeks 10 to 14: HRMS, Payroll, and Consolidated Dashboard

Migrate all employee records with salary structures, state configurations, TDS regime elections
Run one payroll cycle in parallel; verify PF, ESI, PT, and TDS outputs
Activate the unified leadership dashboard
Retire existing HRMS and payroll tool at week 14

Total migration: 14 weeks. At week 15, five teams are working from one platform. The data silos that were producing support tickets, delayed invoices, wrong payroll runs, and assembled revenue reports are gone.

Conclusion

Indian EdTech Has Outgrown Its Tools. The Platform Has Not Caught Up. Until Now.

The EdTech platforms that reach 100 to 200 people in India have already proved the hard things: product-market fit, a content engine, a sales motion, and a team. What they have not yet solved is the operational layer underneath all of it — the data infrastructure that should make five teams work as one connected organisation.

The tools that got you here were not wrong for the stage you were at. They are wrong for the stage you are at now. A CRM that does not talk to your LMS. A billing tool that does not know what the sales team closed. An HRMS that is three weeks behind the actual headcount. A revenue report assembled by a person every Monday morning from six different sources.

Indian EdTech operates in one of the world's most complex compliance environments — GST on digital services, PF, ESI, PT by state, TDS by regime, Form 16 at year end — while simultaneously managing the product, sales, and delivery complexity of a real technology platform. The software that supports this needs to be built for this reality. Not configured to approximate it.

Zopkit is built for this reality. One platform where the deal that closes in the CRM raises the invoice in Finance, creates the course access in Academy, and updates the resource planner in HR — without a single manual handoff. Where the support agent answers every query from one student record. Where the revenue dashboard is live before the leadership meeting starts.

Book a free demo at zopkit.com and see every part of your EdTech operation running on one platform.