Illustrative engagement. A representative scenario showing how we approach this kind of work in education. It does not describe a specific client; outcomes are described qualitatively.
Industry overview
What is shaping education
Schools, universities, edtech companies and education programmes need evidence from students, parents and teachers, and marketing that reaches families at the right time.
- Parents research schools and courses online
- Edtech usage depends on teacher and parent support
- Programmes must show learning outcomes
Client background
A chain of schools, working in Gujarat. This is an illustrative engagement: a representative scenario showing how we approach this kind of work, not a named client project.
- Organisation
- A chain of schools
- Sector
- Education
- Team engaged
- IT & Development
- Services
- ERP development, Mobile app development
Client challenge
Each school used different spreadsheets for fees and attendance, and parents had little visibility.
Research objectives
- Deliver on the brief: a school management system for a growing chain.
- Define requirements and success criteria the solution would be tested against.
- Deliver a reliable, secure solution the team can run and extend.
Target audience
Scope: 12 schools.
Audiences we typically reach in education
StudentsParentsTeachers and principalsEdtech usersEmployers
Geographic coverage
Coverage: Gujarat. Market: India. 12 schools covered.
- India
Research methodology
An iterative delivery approach: discovery, design, build and test in short cycles, with the client reviewing each step.
- 1Brief
- 2Admissions, fees and attendance modules
- 3Parent app
- 4Insight
We built a school ERP covering admissions, fees, attendance and exams, with a parent app for notices and payments.
ERP developmentMobile app development
Sampling strategy
- Users and stakeholders from every affected team took part in discovery workshops and acceptance testing.
Data collection
- Requirements were gathered through workshops, process walk-throughs and a review of existing systems and data.
Data quality & validation
- Peer code review on every change
- Automated and manual testing
- User-acceptance testing with the client
- Release checklist and rollback plan
Data analysis
- Usage and performance monitoring after launch
- Defect and support-ticket trends
- Process time before and after
Key findings
- Parents value visibility as much as results.
Recommendations
- Build on the core insight: parents value visibility as much as results.
- Track adoption and support tickets, and plan the next release from real usage.
Business impact
- Fee collection became more predictable, and parents received attendance alerts the same day.
Impact is described qualitatively.
Deliverables & next steps
- Deployed solution with documentation and handover
- Support and maintenance plan
- Repeat the measure after changes are in place to track progress.
- A natural follow-on question: is the edtech product being used?