Built by the people who actually run schools.

Teachers, principals, engineers and tech founders, in one room, building the platform each of us wished we'd had.

Why we exist

Five tools were doing the job of one.

A fee register here, an attendance diary there, a WhatsApp group standing in for real communication. None of it was badly built — it was just built alone, and the gaps became someone's extra work every evening.

So a group of teachers, principals, engineers and tech founders sat down and built the thing all of us had been missing: one platform, one shared data model, four experiences.

Systems replaced by one platform5+
Roles designed for4
Modules, one data model3

Four kinds of people, one team.

Everyone in the room had sat in one of these seats — that's the whole reason the product looks the way it does.

Teachers

Knew exactly which parts of the day were eating hours that should've gone to actual teaching.

Principals

Knew what a board meeting actually demands, and how painful it is to assemble by hand.

Engineers

Knew how to make three systems share one brain instead of three separate logins.

Tech founders

Knew how to turn all of that into something a school could actually adopt, not just admire.

"We didn't set out to build software for schools. We set out to remove the parts of running one that had nothing to do with actually educating anyone."

Four seats, one afternoon

The same 3 PM, seen from four different chairs — the gap we designed for.

Principal

Wants this term's numbers on track — without pulling three people off their jobs to check.

Teacher

Has forty minutes between classes and a stack of quizzes that shouldn't eat the weekend.

Student

Is quietly stuck on something two chapters back and won't say so in front of the class.

Parent

Wants a straight answer to "how's my child doing" — not a login to interpret alone.

What we build around

Four principles, tested against real screens — not a poster on a wall.

Clarity over clutter

Every screen shows what a role needs to act on today — nothing more.

One connected system

If two modules can share data, they do — that's the whole premise.

Trust by design

Role-based access and one source of truth — never a stale export.

Built with schools

Feedback from admins, teachers and parents shapes the roadmap.

How we got here

The problem

Attendance that didn't sync with anything

That was the first fix. The same disconnect turned out to be everywhere else in the building too.

The build

One data model, three modules

ERP, LMS and AI Coach, sharing the same student, staff and class records from day one.

Today

Four experiences, one platform

Management, teachers, students and parents — the product this site is showing you right now.

What's next

A deeper concept graph

More subjects, more grade levels, more students getting the "find the real gap" treatment.