Brief
You describe the users, the job to be done, current tools and any hard date or constraint. A page is enough.
Industries
Education software for institutions that run on calendars and people
Education software fails when it ignores term dates, guardians and the registrar’s reality. Hirvex Technologies builds systems around admissions, cohorts, attendance and communication that a busy office can run without a full-time IT department on site.
Who this is for. School leaders, registrars and training operators.
Problems we typically meet
These are the patterns that show up before a useful first release—not abstract “digital transformation” language.
- The academic year is a folder of spreadsheets.
- Parent communication is one-way and late.
- Teachers are asked to feed a system that never gives anything back.
- A mandated national system exists, but the operational layer around it is missing.
How we approach the work
Calendar and cohort first. Then roles (staff, learner, guardian). Portals are tested with non-technical users. We integrate with a mandated SIS rather than pretending to replace it when that is the political and legal reality.
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 pipelines
- Enrolment and cohort management
- Attendance and operational academics
- Staff coordination
- Guardian and learner portals
- Reporting the institution actually files
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
Can one platform serve multiple campuses?
Yes, with explicit tenancy or campus records. Permissions are designed so campus A does not browse campus B by accident.
Do you build learning management systems?
We can build or integrate LMS-style features. A full academic LMS is scoped as a product, not as a plugin.
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.