Orbits Umbrella

Systems for schools that spend more time on admin than teaching.

Schools and training centres accumulate systems: one for enrolment, one for results, one for fees, and a spreadsheet joining them.

Who it's for.

Schools

Enrolment data retyped into timetabling, attendance and billing.

Training centres

Attendance recorded on paper and entered days later, if at all.

Training providers

Results assembled manually at the end of every term.

Admin and finance teams

Fee tracking in a spreadsheet that only one person understands.

Our own platform.

EduSphere

Launching soon

Tutoring, self-paced courses and school cohorts on one platform. Built and verified, not yet deployed. Founding tutors and schools wanted.

How a project runs.

  1. 1

    Discovery

    We learn how your school works today and where staff enter the same information twice.

  2. 2

    Planning and design

    A written proposal, then designs you approve before we build.

  3. 3

    Build

    Regular demos and a clear status update, so you always know where things stand.

  4. 4

    Testing

    We check the software against how your staff actually work.

  5. 5

    Launch

    We take it live with your team.

  6. 6

    Support

    Maintenance and support after launch.

Why us.

  • Founder-led. Our CEO is involved in every client relationship.
  • Working on Gulf hours. Our teams overlap your working day for real conversations, not overnight handovers.
  • Registered in the UAE, Pakistan and Malaysia. A local contract for GCC clients, with delivery teams in Pakistan.
  • You interview every engineer before they join your team.

Questions.

How is student data handled?

Student data usually includes minors' records. Access is restricted per role and logged.

Can guardians see what staff see?

Guardian access is separated from staff access, with different permissions.

Where will our data be hosted?

Hosting region is chosen to suit where the institution operates.

How is the cost worked out?

It depends on scope. We work it out after a 30-minute scoping call, and you get it in a written proposal.

Who owns the code?

You do. IP is assigned to you on payment and the work stays in your repositories.