CRM
Customer relationship management
- Enquiries & leads
- Follow-ups and calls
- Admission pipeline
Write it once.
It is everywhere.
SMS, ERP and LMS on one database. Enter a student once and every document the school issues — ID card, grade sheet, fee receipt — comes off that one record.
2M+ Students
1,000+ Institutions
11 Years
ISO Certified
Three systems. One database.
Admissions, teaching and administration run on the same records, so a change entered once is current everywhere it matters.
LMS
Learning management system
- Courses & lessons
- Assignments & exams
- Progress tracking
SMS
School management system
- Students & staff
- Attendance & fees
- Notices & reports
Unified platform
One record per student across all three systems — no exports, no re-keying, no two versions of the truth.
Centralised & secure
Role-based access over a single database, so every office sees exactly what it should and nothing else.
About
Eleven years of Nepali institutions,on one platform.
Digital Nepal builds the systems Nepali institutions run on: admissions, teaching and administration on one database, deployed and supported from Kathmandu.
- Founded
- 2014, Kathmandu
- Certified
- ISO 9001:2015
- Deployed across
- Nepal, on one platform
- Partner institutions
- 1,000+
- Active students
- 2M+
The questions we get before the demo.
Answered in full, on the page, rather than in a call you have to book to hear them.
01Where does our data live, and who can reach it?
On managed cloud infrastructure, behind role-based access over a single database. Every office sees its own records and nothing else.
02What are you certified against?
ISO 9001:2015 — a quality-management standard covering how the system is built and supported. It is not a security certification and we do not present it as one.
03Will it hold at our size?
It runs single schools and full universities on the same deployment, across more than a thousand institutions today.
04Are we buying three separate products?
No. Admissions, teaching and administration are three faces of one database — which is what the diagram above this is drawing.
05Does the app show what the office sees?
Yes. Web and mobile read and write the same records, so there is no export step and nothing to reconcile at the end of a term.
06How does attendance actually get taken?
Biometric devices or the app, with live tracking. The register updates as it is taken rather than at the end of the day.
07Can it talk to our website and our other systems?
Through an API — the public website, published results, and the third-party services your institution already runs.
08What can we actually see from it?
Dashboards and institutional reporting on today's figures, rather than on last month's exported spreadsheet.
09Who do we call when something breaks?
A support team in Kathmandu, on the numbers at the foot of this page. Not a ticket queue in another time zone.
See it running on your own school.
Thirty minutes on your own timetable, your own fee structure and your own reporting, with someone who has set this up before.
We build for Nepali institutions from Kathmandu, and we are hiring. See open roles