Brief
You describe the users, the job to be done, current tools and any hard date or constraint. A page is enough.
Solutions
Education software for the academic calendar, not a generic CRM
Schools and training organisations run on cohorts, calendars, people and evidence of learning. Hirvex Technologies builds education management software: admissions, enrolment, timetables, attendance, staff coordination and portals that parents or learners can actually use.
Who this is for. School leaders and training businesses tired of stitching SIS fragments together.
Problems we typically meet
These are the patterns that show up before a useful first release—not abstract “digital transformation” language.
- Admissions is a mailbox and a spreadsheet.
- Attendance is collected but never analysed.
- Parents only hear from the institution when something is wrong.
- Teachers keep a private parallel record “just in case”.
How we approach the work
We model the academic year first. Then people (applicants, learners, guardians, staff) and the documents that move with them. Portals are designed for the least technical guardian, not for a developer demo. Reporting follows what a principal or registrar actually has to file.
What a serious first release can include
Scope is confirmed in discovery. This is the shape of work we are equipped to deliver—not a menu you must buy in full.
- Admissions and enrolment pipelines
- Class, cohort and timetable structures
- Attendance and basic academic records
- Staff and room coordination
- Parent, student or learner portals
- Fee-adjacent workflows where you already have a payment method
What we need from you
A useful brief is better than a long one. If you can answer most of the following, we can propose a first slice instead of a theatre estimate.
- Who will use this, and what must they finish in a session?
- Which systems must stay (accounting, payments, identity, a shop)?
- What is already live that we should not break?
- Any hosting region, language or compliance rule that is non-negotiable?
- The date that actually matters—and why.
How an engagement runs
Four steps. No mystery bench.
Scope
We reply with clarifying questions and a first-release outline: modules, roles, integrations and what “done” means.
Build
Named engineers work in visible increments, with staging you can click and a weekly written status.
Run
Launch, handover and a support path. The system is yours to operate—not a black box we disappear from.
Questions we are asked
Do you replace our national student information system?
Only if that is the explicit project. Often we sit beside a mandated system and improve the operational layer around it.
Can teachers use this on a phone?
If attendance or messaging is a mobile job, we design for that. We do not shrink a desktop SIS and call it an app.
Start a conversation
If this is the work in front of you
Send the users, the job to be done and any hard constraint. We will answer as engineers—not with a canned brochure.