Fintech
Scaling a payments platform
We helped a fast-growing fintech company redesign and scale their core payments platform.
Read case studyOne school ERP
for every office.
How Leonstride brought admissions, attendance, fees, exams and parent communication for Indirabai Lalawani Jr. College & Primary School into a single system.
A school run
on registers.
Indirabai Lalawani Jr. College & Primary School teaches children from the primary years through junior college. Every day brings admissions, roll calls, fee payments, exams and messages to parents, across two wings with their own staff and records.
Leonstride designed and built a school ERP that keeps all of it in one place, so staff spend their time on students instead of paperwork.
Client
Indirabai Lalawani Jr. College & Primary School
The
challenge.
Running a school is mostly records, and most of them lived on paper.
Admissions sat in registers, fees in ledgers and marks in teachers’ notebooks. Report cards were typed one by one, and notices went home in school bags, if they arrived at all.
With a primary school and a junior college under one roof, the same work was done twice. The school needed one system for every office, simple enough for staff who had never used one.
- Paper admission registers
- Fees tracked in ledgers
- Manual attendance roll calls
- Report cards typed by hand
- Notices sent home on paper
- Two wings, two sets of records
Our
solution.
Leonstride built a web-based ERP around the school’s daily routine, with one student record shared by every module.
- 01
Admissions and student records
- 02
Daily attendance for students and staff
- 03
Fee collection, receipts and dues
- 04
Exams, marks and report cards
- 05
Classes, sections and timetables
- 06
Notices and alerts for parents
- 07
Role-based login for management, office, teachers and parents
- 08
One switch between the primary school and the junior college
Execution
& delivery.
Architecture
Modular and role-based: each office gets its own module, all sharing one student record.
Process
A documented scope, fortnightly demos to school management, and every issue tracked to closure.
Delivery model
Phased around the academic calendar: admissions and fees before the new session, exams before term end.
Training
Hands-on sessions for office staff and teachers, with short guides for each daily task.
Team composition
- 1Project manager
- 1UI/UX designer
- 2Developers
- 1QA engineer
Tech stack
- React
- Node.js
- MySQL
- REST APIs
- SMS gateway
- AWS
Key outcomes
& impact.
One system, both wings
Primary school and junior college run from one login, each with its own view.
Paperless office
Receipts, report cards and notices now come out of the system, not a typewriter.
Parents kept informed
Absences, dues and notices reach parents directly, the same day.
- 01
Admissions, attendance, fees and results kept in one place, entered once.
- 02
Fee receipts generated automatically, with pending dues visible at a glance.
- 03
Report cards produced straight from the marks teachers enter.
- 04
Parents informed of absences and notices without paper slips.
- 05
Primary and junior college records managed side by side, never mixed up.
- 06
Management sees each day’s attendance and collections on one dashboard.
Project
lifecycle.
- 01
Requirement gathering
Sessions with the principal, office and teachers.
- 02
Scope document
Modules, roles and reports agreed in writing.
- 03
UI/UX
Screens designed for non-technical staff.
- 04
Development
Built module by module, demoed every fortnight.
- 05
Testing and feedback
Checked against real school data and workflows.
- 06
Deployment and training
Rolled out before the new academic session.
- 07
Support
Fixes and small changes after go-live.
Notable
highlights.
- 01
Planning releases around the academic calendar avoided changes during admissions and exams.
- 02
Migrating existing student records early meant staff started with familiar data.
- 03
Simple screens and short training sessions made adoption easy for office staff.
- 04
Separate views for the two wings kept one system without mixing their records.
- 05
Fortnightly demos let school management steer priorities as the work progressed.
Let’s build something
that works.
Tell us what you’re trying to solve. We’ll help you figure out the right technology, team and approach.
Start a conversationReal challenges. Meaningful outcomes.
A look at some of the products we’ve built, the teams we’ve scaled, and the impact we’ve created for our clients.
Healthcare
Digital transformation for a multi-speciality clinic
We built an end-to-end clinic management system that streamlined operations and improved patient engagement.
Read case study
Logistics
Real-time tracking for a logistics network
We developed a real-time tracking platform that improved delivery visibility and cut avoidable delays.
Read case studyE-commerce
Building a scalable D2C platform
We designed and developed a D2C commerce platform built to hold up as its catalogue and traffic grew.
Read case study