Project type: ThriveUp Solution’s own product, built in-house to demonstrate our enterprise software capability. It is not a client deployment, and the figures below describe what was built, not customer results.
The challenge
Schools usually run admissions, fees, attendance, exams, payroll, the library and transport in separate tools or spreadsheets. Staff re-enter the same student and employee data in several places, and leadership struggles to see a single picture. We set out to build one platform that covers these areas and can serve several schools or campuses from the same system.
What we built
ThriveUpSchool is a multi-tenant school ERP: one installation can hold multiple organisations and campuses, each with its own users, roles and data. The platform includes:
- Students and admissions: student records, guardians, enrolment, documents, certificates and admission applications
- Academics: classes, subjects, timetables, substitute teachers, assignments, quizzes and lesson plans
- Attendance and leave: daily attendance and leave requests
- Exams and results: exam schedules, marks, grade scales and report cards
- Finance: fee structures, invoices, payments, payment plans, scholarships, budgets, journals and bank reconciliation
- HR and payroll: employee records, contracts, recruitment, attendance, salary structures, payroll runs and payslips
- Library, canteen, inventory and procurement: book issue and fines, meal ordering with wallets, stock, purchase orders and goods receipts
- Assets and transport: asset tracking and maintenance, vehicles, drivers, routes and stops
- Communication: announcements, messages, notifications and emergency broadcasts
- Reports and analytics: saved and custom reports and dashboards
Role-based portals
Beyond the admin console, students, parents and teachers each get a self-service portal that shows only what is relevant to them. Access is controlled through roles and permissions, and sensitive actions are recorded in an audit log.
AI assistant
The platform includes an AI assistant connected to the Claude API, so staff can ask questions in natural language. It is designed to be switched on per installation once an API key is configured, which keeps AI features optional and under the school’s control.
Technology
- Front end: React 19, TypeScript and Tailwind CSS
- Back end: Node.js with Express, with input validation using Zod
- Data layer: Prisma ORM with a data model of more than 150 entities
- Security: role-based access control and audit logging
What we learned
Building this many connected modules reinforced a few engineering habits we apply on client work: keep each dashboard section independent so one failing data source cannot blank a page, validate every value before formatting or calculating with it, and design permissions early rather than adding them later.
Where it stands
All the modules listed above are built and have been tested with demonstration data. A drag-and-drop form and workflow designer is planned for a later phase.
Need an ERP, portal or management system for your organisation? See our Enterprise Solutions or contact us for a free consultation.