Nimikh EduOps
Builds a school’s routine, dispatches a substitute teacher when one calls in sick, records attendance offline, and reconciles fees against the payment gateway’s own settlement report.
It is scoped for urban private schools of roughly 400 to 2,500 students and multi-branch coaching centres in Dhaka and Chattogram. Government and MPO-aided institutions, universities and madrasas are outside the first release, and we would rather say that than take the meeting.
In build. The first release is in build. Its scope depends on a documented capacity decision taken at the end of month one: with four engineers it ships routine, substitution, attendance and collections together; with two, collections move to a second release and the first ships as routine and register. It has no users, no pilot institutions and no customers, so everything below describes what it is specified to do rather than what anyone has yet done with it.
The wedge is 07:15, not the annual timetable
Building a conflict-free routine is hard, and it hurts twice a year. A teacher calling in sick at 07:10 hurts every weekday. Cover gets arranged by sequential phone calls, marked on a paper chart, announced in a WhatsApp group not everyone reads, and remembered by nobody. By 08:00 a class or two is still unattended, and afterwards there is no record of who covered what — so workload disputes cannot be settled and the substitute is neither credited nor paid.
The problems it addresses
Each of these is a numbered entry in the requirements document, and every capability further down traces back to one of them. They are described problems, not measured ones, so none of them carries a figure.
A teacher calls in sick at 07:10 and cover is arranged by sequential phone calls, marked on a paper chart, and announced in a WhatsApp group not everyone reads.
By 08:00 a class or two is still unattended, and afterwards nobody can say who covered what — so the workload dispute cannot be settled and the substitute is neither credited nor paid.
Building a conflict-free routine across sections, shifts, rooms and shared labs is done in a spreadsheet and takes weeks.
The routine is fragile by the time it is published, and every subsequent change is made by hand against a document nobody else can safely edit.
Fee charts live in a spreadsheet, challans are handwritten, guardians queue at a counter or a bank, and a clerk matches deposits to students by name.
Names are ambiguous in a country where many students share one. The bank statement arrives days later, arrears lists are stale, and reminders go to whoever is remembered.
Attendance, cover, waivers and edits leave no trustworthy record.
The owner cannot answer "what happened", and the institution cannot answer a guardian, an auditor or a departing employee.
Guardians are reached through WhatsApp groups and rumour.
There is no receipt and no proof that notice was ever given.
The market it was specified against
We have no customers to point at, so this is what we have instead: the structure of the market, each figure carrying the publication it came from and the date it was published, so you can check it rather than take it.
The buyer is a proprietor with their own cheque book: no tender, no committee procurement cycle, no state contractor incumbency. That is the structural reason this vertical is first, and it is a fact about the market rather than a result we have produced.
What it does
Written as designed, not as delivered. Nimikh EduOps is not built, and each entry below is a specified behaviour a buyer can hold us to once it is — which is the only reason to write it this precisely before it exists.
Routine
A constraint solver assigns every lesson a slot, a competent teacher and a suitable room. When a routine is impossible it names which constraints make it impossible and what would have to change — a solver that says no without saying why is worse than a spreadsheet.
Substitution dispatch
An absence logged at 07:10 produces ranked substitute candidates, a dispatch to everyone affected, and a front-desk board the reception screen can display. The ranking is rules-based, not learned.
Attendance
Session marking that keeps working with no network for at least 72 hours and syncs without loss. The queue carries exactly one write shape, so nothing else can drift into it.
Fees and reconciliation
Invoices issued in bulk, payments taken at the counter or online, and a three-way reconciliation against the gateway’s settlement file with an exceptions queue for anything that does not match.
Export
Every record you gave us and every record we created for you, in open formats, self-serve, within fifteen minutes. Government reporting is an export, not an integration — BANBEIS publishes no API.
The thresholds it has to meet
Almost every number in the specification is a threshold with a consequence attached rather than a figure chosen to impress. These are the ones a buyer would notice, published before the software exists so that they can be held against us rather than discovered afterwards.
- 3 secondsFrom an absence being logged to ranked substitute candidates on the screen.
- about 25 secondsTo mark a session’s attendance, exceptions included.
- about 35 secondsTo take a payment at the counter and print the receipt for it.
- under 60 secondsTo generate 2,500 invoices in a single run.
- 60 secondsFor a routine solve to surface its first feasible answer, rather than leaving a coordinator watching a spinner with nothing to look at.
- 10 minutesFor that same solve to finish.
- at least 90%Of unchanged lessons keep their slot, their teacher and their room after a single change to a published routine. A solver that reshuffles the whole week to absorb one edit is not usable in a real school.
- at least 72 hoursAttendance keeps working with no network at all, and syncs afterwards without loss.
- under 15 minutesFor a complete self-serve export at a 2,500-student institution, in open formats, with nobody from here involved.
- 10 working daysFrom contract to the first substitution dispatched without our help.
Design commitments, not results. Not one of these has been measured on a running system, because there is no running system. They are what the software has to do before we would call it finished, and none of them becomes a claim until it has been measured.
What it deliberately does not do
Nothing here is an omission, and this section matters at least as much as the one above it. Every entry was decided in the requirements document with a reason attached, and every one of them costs us a feature a competitor will happily claim. A product defined only by what it does is a product whose boundaries you find out about after you have paid.
Nimikh never holds or settles tuition money
The institution is merchant of record. Aggregation is a licensed activity in Bangladesh requiring a trust and settlement account, T+5 settlement, about BDT 1 crore of capital and personal officer liability.
There is no silent auto-debit
bKash Tokenised Checkout lets a guardian skip wallet entry and OTP, but still requires their PIN on every payment. What the product does is orchestrate collection, not deduct from anyone.
No money is captured while the counter is offline
The offline queue carries attendance and nothing else. A payment recorded on a disconnected device is a reconciliation exception waiting to happen.
Not a forty-module ERP
Twenty vendors compete on module count at BDT 8–25 per student per month. Two jobs done properly beats forty done nominally.
When the counter is offline, the paper receipt book is the fallback
Not a degraded screen pretending to be online. The institution writes its own receipt against a paper serial the system checks for uniqueness when the connection returns, so the gap is visible in the ledger rather than hidden inside it.
There is no guardian account and no guardian app
A guardian gets a signed link that expires, can be revoked, and is bound to one student and one phone number. An account is a password to forget, a support queue to staff and a profile of a child to hold, and none of those buys the guardian anything they wanted.
Tell us what your 07:10 actually looks like
Not a module list — the morning itself. Who gets called first, who ends up covering, what gets written down, and what nobody can answer afterwards. We are looking for institutions willing to let us watch that morning before any of this is built.