School ERP MVP
Built a multi-tenant School ERP SaaS in Laravel + MySQL after seeing how fragmented school management tools are for small and mid-sized schools.
The platform supports:
• Multi-school tenancy
• Student & staff management
• Fees & accounting
• Attendance
• Parent/student portals
• Exams & report cards
• Payroll
• Transport & hostel
• Online exams
• SMS/email notifications
• Role-based access control
It’s designed so each school operates independently under one centralized system.
Current stage:
- MVP completed
- Core modules working
- Multi-tenant architecture implemented
- Ready for customization/deployment
Tech stack:
Laravel, MySQL, RBAC, multi-tenant architecture
I’m considering:
- Selling ownership
- Finding a technical/business partner
- Licensing it to schools
Would love feedback from founders who’ve sold B2B SaaS products in the education space.
Happy to share screenshots/demo privately.
Trending on Indie Hackers
This looks like a serious build, especially because multi-tenant architecture is already in place. For school ERP, that matters more than the feature list, because every school needs separation, permissions, reporting, billing, and parent/student access without the system becoming messy.
The main thing I’d tighten before selling, licensing, or bringing in a partner is the positioning. Right now it reads like “School ERP with many modules,” which is useful, but also puts you in a crowded category. The stronger angle may be a deployment-ready operating system for small and mid-sized schools that do not want fragmented tools for fees, attendance, exams, payroll, and parent communication.
I’d also pressure-test the brand early. If this is going to be licensed or sold as a real B2B education SaaS, the name should feel more like a serious school operations platform, not just a Laravel ERP project.
Beryxa .com would fit that direction well because it gives the product a cleaner enterprise SaaS feel while still leaving room for education operations, accounting, portals, and workflow modules under one brand.
The product may already be technically useful. The next step is making it feel packaged, trusted, and easy for a school owner or buyer to understand quickly.
The main thing I’d tighten before selling, licensing, or bringing in a partner is the positioning. Right now it reads like “School ERP with many modules,” which is useful, but also puts you in a crowded category. The stronger angle may be a deployment-ready operating system for small and mid-sized schools that do not want fragmented tools for fees, attendance, exams, payroll, and parent communication.
If you think about it . both are the same thing.
The stronger angle may be a deployment-ready operating system for small and mid-sized schools that do not want fragmented tools for fees, attendance, exams, payroll, and parent communication. 100% correct.
I don't know how to do positioning. I am not good at these things.
Product is technically useful. I am trying to make it feel packaged trust and easy for a school owner or buyer to understand. Demo site is live . I am trying my best. But, things takes time. It is very very new.
Yes, both ideas are close, but the difference is how the buyer feels it.
“School ERP with many modules” sounds like software features.
“Deployment-ready operating system for small and mid-sized schools” sounds like a complete business system a school owner can trust.
That distinction matters because your buyer is not only checking features. A school owner or admin is thinking: will this handle fees, students, parents, exams, payroll, records, and daily operations without becoming risky or messy?
So the product needs to feel packaged before they even enter the demo.
That is also why I mentioned the brand. If the current name feels too close to a Laravel ERP/project name, it may make a technically strong product feel smaller than it is.
Beryxa.com would give this a much cleaner SaaS/operations-platform feel. It sounds more like a serious education operations system that can hold fees, attendance, exams, parent portals, payroll, and reporting under one trusted brand.
Not saying the tech is the issue. The tech sounds useful. The risk is that the brand and positioning may not yet make school buyers feel the same level of trust the product deserves.