How we are built
Six things that shape
what gets shipped.
Not values — six structural facts about the team that explain why the product refuses the things it refuses.
01
Practising teachers on staff, not on an advisory board
Our curriculum leads have taught to a board syllabus for five years or more. They write every rubric, define what earns partial credit, and hold a veto on any generated paper. It is a staff role with authority, not a quarterly consultation.
Veto rightsFull-time
02
Marking accuracy is reviewed by everyone
Agreement rates between the marker and reviewing teachers are read by the whole team every fortnight — not just by the ML engineers who could explain away a bad number.
FortnightlyWhole team
03
We publish what did not work
Every case study on this site names what got worse before it got better, and which figures we would defend least strongly. A case study with no cost in it is marketing.
In every storyNamed
04
Two school visits a year, for everyone
Including engineers. It is not optional and it is the single thing most people here say changed how they build. You cannot design a teacher’s review queue from a backlog ticket.
Not optionalEveryone
05
Student work never trains a model
A contractual commitment rather than a setting, written into the privacy policy. It is the question parents ask most, so the answer is fixed rather than configurable.
ContractualNo exceptions
06
India-first, and priced that way
Built for CBSE, ICSE and state boards, on IST support hours, priced in rupees. Not a Western product with a rupee price list bolted on.
CBSE, ICSE, stateIST hours