Case study

A modular school management platform customised for different schools and how they worked

Built to replace disconnected ERPs, spreadsheets, Tally and paper with one configurable system.

Client
Edizy
Industry
Education Technology
Region
India
Timeline
3 days
Solution
Management Platform

Summary

Edizy helps schools manage admissions, students, staff, fees, attendance, examinations and documents. However, its previous product could only be sold as a complete suite and required development work whenever a school needed different rules or reports.

We built a modular platform where schools subscribe only to what they need and configure their own workflows without changing the underlying software.

About the client

Edizy helps schools manage their daily operations through one platform

Edizy is developed by Aronxt Technologies and led by Bhavya KN, who has more than 10 years of experience in school ERP systems.

The platform brings admissions, student records, staff, fees, attendance, examinations and documents together. Each school can choose the modules it needs instead of purchasing the complete system.

The Edizy team at their office
School records kept in paper registers alongside a spreadsheet

The challenge

Schools worked differently, but existing systems treated them all the same

Edizy's earlier in-house ERP became unusable because it was not properly maintained or version controlled, leaving Bhavya with schools ready to pilot but no reliable product.

Schools relied on older ERPs, spreadsheets, Tally and paper registers. Records were entered repeatedly, attendance was transcribed, and fees and reports were prepared manually.

The product also forced schools to buy the complete suite and required code changes for different fee rules and report formats, making it difficult to sell and scale.

The solution

One configurable platform that schools can buy module by module

  1. Modules and billing, with each module priced and switched on per school

    Modules priced separately

    Before

    Schools had to purchase the complete suite, even when they needed only a few modules.

    After - with Creatr

    Each module has its own price and can be activated separately for every school.

  2. School setup, configuring classes, sections, departments and houses

    Custom setup for every school

    Before

    Different fee rules, reports and approval steps required new development work.

    After - with Creatr

    Schools configure their own rules, reports, fields and approvals from the platform.

  3. The student register, with admission number, class and enrolment status

    Streamlined Record-Keeping

    Before

    Student and staff details were repeatedly entered into ERPs, spreadsheets, Tally and reports.

    After - with Creatr

    Admissions, students, staff, fees and documents use one shared set of records.

  4. Analytics and forecasting, with enrolment trend, fee collection rate and anomaly alerts

    Attendance, fees and reports from live data

    Before

    Attendance was transcribed from paper, fees were calculated manually and reports were compiled separately.

    After - with Creatr

    Attendance, fee calculations and reports are generated from the latest school data.

  5. Tenant management, listing each school on the platform with its own domain

    One platform built for multiple schools

    Before

    Every new school added more development work, while the previous product lacked a reliable technical foundation.

    After - with Creatr

    Schools use separate workspaces with private data, configurable workflows and recorded approvals.

The build process

How the solution was built with Creatr

Day 1
Week 1
Week 2
Week 3
Week 4
  1. Discovery call, Day 1 to Week 1
  2. Plan - FRS doc, Day 1 to Week 1
  3. Frontend Prototype, Week 1 to Week 2
  4. Backend Build, Week 2 to Week 3
  5. Validation & Testing, Week 2 to Week 3
  6. Migration and go-live, Week 3 to Week 4
  7. Post Launch Support, Week 3 to Week 4

Founders quote

Working with Creatr made the process of building Edizy feel much more structured and collaborative. They took the time to understand our vision, challenged our thinking in the right places, and helped us turn it into a flexible platform that schools can actually use. Their team was responsive, thoughtful and genuinely invested in getting the product right.

- Pivu, SalesCRM

The takeaway

Flexibility should be built into the product, not added through custom development.

By making modules, fee rules, reports and approvals configurable, Edizy can support schools with different needs on the same platform. Schools get a system that fits their operations, while Edizy can grow without rebuilding it for every customer.

View Case StudiesBook a discovery call