About QXP
Software that outlives the people who set it up.
A Nairobi software company. QXP is our first product, and the standard for the next one.
Mission
What we build
Quadrant Experience Limited builds software. QXP is our first product: one system carrying a Kenyan school from a KICD curriculum design through schemes, lessons, the register and assessment to the report card - and on to the invoice, the M-Pesa reconciliation and the ledger. One record per learner, one database per school. We are building a second product now, for corporates. There is nothing to show yet, so this page is about the one that exists.
Vision
Where this goes
Most school software is replaced within a few years, and every replacement costs a school its history. We would rather build the one that does not need replacing: data a school still owns and can still read when the staff who entered it have moved on, and claims that hold up years after they were written. Schools first, because that is the hardest version of the problem.
Our promise
A learner record that survives the teacher who created it, the term that produced it and the system that replaced the last one. QXP is the first thing we have built to that standard, and the standard for everything after it.
Why
The questions we get asked, answered plainly
Why curriculum-first?
Most school software starts with fees or admin. We start with what schools actually do: plan lessons, teach, assess, and report. Everything else connects to the curriculum.
Why Kenya first?
We are based in Nairobi. We understand CBE, KNEC, KICD, TSC, M-Pesa, and how private schools actually buy software. We build here, then expand.
Why not just use spreadsheets?
Excel is flexible but disconnected. One teacher’s marks do not flow into a report card. A parent cannot check attendance on their phone. There is no audit trail. QXP connects the workflow.
Why one platform?
Two tools mean two versions of the same learner, and the day they disagree nobody can say which is right. One record per learner, one database per school, so the register the teacher marked is the register the report card counts and the invoice bills against.
Why does software this boring matter?
A school that changes system loses its history. Marks, attendance, discipline notes, fee ledgers - years of it, stranded in an export nobody can read. We build for the school that is still on QXP when the people who set it up have left.
Why a second product?
Because the problem is not specific to schools, and because a company building its second product intends to be here for the first one's second decade. It is early and there is nothing to show, so we are not going to describe it.
Principles
How we build
Curriculum-first
Every feature traces back to teaching and learning. Admin follows academics, not the other way around.
Reporting-ready
Data entered once flows through to report cards. No re-typing, no assembly, no last-minute panic.
Built for adoption
Teachers will only use software that saves them time. If it adds work, it fails. We design for the busiest teacher.
Multi-campus ready
School groups need one view across campuses. QXP is multi-tenant from the ground up.
Secure and role-based
Granular roles. Full audit trail. Every action logged. Each school in its own database, so isolation is structural.
Kenya-first
CBE and 8-4-4, the KICD strand structure, the official EE1-BE2 levels, and every Kenyan county mapped down to the ward.
Company
Facts
Want to join us?
We are hiring engineers and implementation specialists. There is no listings page - write to sales@qxp.global with what you would want to work on, and it reaches the founders.