Customers

Three patterns. Three pilots. One platform.

Edullent's earliest partners chose us quietly. We publish what we changed, on their terms — anonymized until they're ready to be named.

Every Edullent rollout maps to one of three shapes: a multi-branch group needing one view, a single-campus school stuck on operational drag, or a Pre-Primary institution needing parent transparency without putting a child on a screen.

Become a partner school Why intelligence, not ERP

Implementation stories

What changed, in their own framing.

Pilot School A

Multi-branch CBSE group · South India

A two-campus CBSE group running on spreadsheets, three disconnected mobile apps and one half-built ERP. Roughly 1,400 students between Pre-Primary and Grade 10.

What was breaking

Owner could not see both branches in one view. Attendance for one campus came on email, the other on WhatsApp. Fee reports lagged by a fortnight. Risk students surfaced only at the parent-teacher meeting — by then a term had been lost.

What was deployed

Owner Dashboard with cross-branch comparison
Principal Dashboard at both campuses
Teacher app for all class-teachers
Parent Connect across both branches
AI Risk Predictor on day one

Outcomes after first term

~6 weeks earlier

first risk-student intervention vs. the previous year

92%

parent-side engagement on Parent Connect within 8 weeks

1 screen

replaces the WhatsApp+email+spreadsheet stack for the owner

“For the first time, I open one screen on Monday morning and I can already tell which campus needs me this week.”
— Pilot School A · Group Owner

Pilot School B

Single-campus K-10 · Tier-2 city

A growing single-campus K-10 school with ~900 students. Strong academics, weak operational discipline. The principal was personally chasing daily attendance and term-end reports.

What was breaking

Reports took the academic team three working days at the end of every term. Teacher quality was anecdotal — no composite score, no ranking, no coaching list. Parents were demanding more transparency than the school could supply.

What was deployed

Principal Dashboard
Teacher app + AI lesson summarizer
Parent Connect with daily intelligence
Automatic term-end report generation
Teacher composite scoring

Outcomes after first term

3 days → 4 hours

to generate end-of-term reports across grades

Composite score

replaces gut-feel teacher evaluations

Daily parent ping

replaces the quarterly PTM as the engagement primitive

“My academic team used to fight reports for three days. Now reports just exist — and we use those days for actual teaching.”
— Pilot School B · Principal

Pilot School C

Pre-Primary + Primary · Hybrid model

A Pre-Primary + Primary school with ~420 children, ages 2–10. Parents wanted a daily window into their child without an app the child should ever touch. Teachers wanted to stop building photo collages in WhatsApp.

What was breaking

Pre-Primary class teachers were spending the second half of every day editing photos and writing parent updates by hand. Photos were leaking across WhatsApp groups. Daily routines, milestones and meals were not being captured anywhere durable.

What was deployed

Pre-Primary Teacher dashboard (operator surface)
Pre-Primary Parent dashboard (monitor-only surface)
Photo Studio + Gallery (per-child)
Daily timeline · meals · sleep · milestones
Strict no-child-facing-surface policy enforced in product

Outcomes after first term

~60 mins/day saved

per Pre-Primary class teacher on parent updates

Per-child gallery

replaces WhatsApp photo dumping

Zero

child-facing UI — by product policy, not afterthought

“Parents stopped asking what happened today. They could already see it. That changed every parent meeting we ran after.”
— Pilot School C · Founder

Pilot institutions are anonymized at their request. Outcomes are reported from the school's own first-term measurements. We do not invent institutions, fabricate quotes, or attribute outcomes to schools that did not produce them.

What repeats

Five outcomes show up in every pilot.

The story differs by institution. The shape of the result does not.

Risk surfaces earlier

On average ~6 weeks earlier than the school's previous reporting cadence.

One screen per role

Owners, principals, teachers and parents stop juggling four tools each.

Reports collapse

End-of-term reporting goes from three days of work to an afternoon — or zero.

Parent engagement compounds

Daily intelligence to parents pushes engagement past 85% within the first term.

AI is not an add-on

Risk Predictor, composite teacher scores and summarizers ship on day one, not at "v2".

Becoming a partner

How a new institution gets onboarded.

1Discovery call. One 25-minute walkthrough with the founder. We map your school to one of the three pilot shapes.
2Pilot scoping. We decide which dashboards go live in week one and which integrations carry over from your existing stack.
3Two to three weeks. Single-campus deployments hit production in two weeks. Multi-branch groups bring the owner-side view first; campuses follow in week-long waves.
4First-term review. At the end of the first term we compare outcomes to baseline. If you choose to go public, that's the moment the case study becomes named.

FAQs

Questions every new institution asks.

Pilot institutions chose to participate quietly while the platform matured. We publish outcomes with the partner's consent but withhold the institution's name until they're ready to be public. Edullent never invents school names or fabricates testimonials.

Yes — these are the three patterns Edullent sees repeatedly: a multi-branch group needing one view, a single-campus school stuck on operational drag, and a Pre-Primary institution needing parent transparency without exposing children to an app. Every Edullent rollout maps to one of these three shapes.

Two to three weeks from contract to first live dashboard for a single-campus school. For multi-branch groups, the owner-level view comes online first, individual branches follow in week-long waves. Edullent is multi-tenant by design — adding a campus is not a re-deploy.

Edullent typically replaces the spreadsheet + WhatsApp + standalone-ERP stack. Where a school has a payments or accounting system in place, Edullent integrates rather than displaces. The first 30 days establish what gets retired and what stays.

Yes — at any time. The default is anonymized until the partner explicitly opts in to a named case study. Many institutions choose to go public after the first full academic year on Edullent, when the numbers are unambiguous.

Continue exploring

Education Intelligence Platform

The category these institutions chose over a traditional ERP.

Use cases

Browse Edullent by the operational problem you want to solve.

School ERP vs Intelligence

Why every pilot moved off the ERP framing.

For School Owners

The owner-side view that Pilot A relies on.

Become Pilot D.

Edullent partners get the founder on the call, the dashboards in two weeks, and outcomes measured at end of term — anonymized by default.

Talk to the founder Browse use cases

Read how we think about it on the Insights blog