StatusEduOpsin buildAgriOpsdesign-partner stageVisionEdgevalidation only

Nothing here is shipping yet. Product status

EduOps · designed workflow07:12 → 08:00 · 48 min

Start with the problem, not the software.

A physics teacher reports in sick at 07:12. Four classes have nobody standing in front of them, the first bell is at 08:00, and cover gets arranged by phone calls nobody writes down. We build for those forty-eight minutes — and for the equivalent hour in a feed mill and on a loading dock.

Incident timeline48 min window
  1. 07:12Reported by WhatsApp
  2. 07:34Now: 6 of 7 periods covered
  3. 08:00First bell
≤ 3 sRanked substitute suggestionsPRD NFR-004
≥ 72 hOffline capture, no loss on syncPRD §41
≤ 15 minComplete self-serve exportPRD promise 3

Specified targets, not measurements. Nothing here has been shipped or timed.

19,757 of Bangladesh’s 21,086 secondary-level institutions are privateBANBEIS, via Bonikbarta, 12 Sep 2025

Tuesday 23 SeptemberMorning shift, routine v4

Designed workflow
  1. 07:12Absence reportedShamim A. · WhatsApp
  2. 07:34 · nowRanked, 6 of 7 coveredReason shown per row
  3. On confirmDispatchedMessages ৳ 7.20
  4. 08:00First bell26 min after now
Shamim Ahmed — Physics4 periodsReported 07:12 by WhatsApp
P19-A · Physics · R-203Nasima AkterSubject matchWhySubject match · free period · 14 of 22 this week
P210-B · Physics · Lab 1Jahangir AlamSubject matchWhySubject match · free period · fairness rotation
P48-A · Physics · R-201Nasima AkterSecond coverWhySecond cover · already covering P1 — check the load
P69-B · Physics · Lab 2No eligible substituteResolveWhyAll physics staff at load cap, and the lab needs a qualified teacher
6 of 7 periods coveredMessages ৳ 7.20 across 13 parts, from a wallet holding ৳ 2,140.00
Now 07:34 · first bell 08:00 — 26 min leftPrimary action, in Bangla: dispatch 6 substitutes.
A designed workflow, not a customer screenshot. Nimikh EduOps is in build and has no users yet, so there is nothing to photograph — this is the dispatch board drawn to its specification.
Engineering model

From custom services to vertical products

Both halves are true today. We build custom operational software for businesses here, and that work funds a product line of our own, for three industries where the same problems repeat at every organisation.

Tier 01What exists and pays today

Custom engagements

Point-of-sale systemsclient-owned
Inventory ledgersclient-owned
CRM and booking enginesclient-owned
School and clinic officesclient-owned
Custom software
Tier 02The product line, all unshipped

Vertical products

The same method sits under every one of them. Each product page states exactly where that product is.

Method, in four stepsRule 0: no production code before the shadowing report
  1. 01

    Watch the work

    Shadowing sessions with the person who owns the problem, at the hour the problem happens.

  2. 02

    Find the job

    Separate what was asked for from what someone is trying to get done, and build for the second.

  3. 03

    State a killable hypothesis

    Each bet carries a measure and a falsification threshold, agreed before the build.

  4. 04

    Build for the worst day

    Sized for a 4 GB Android on a weak cell; capture works for at least 72 hours with no network.

Ten steps in full, from watch the work before writing anything down to publish the correctionsHow we work
Failure architecture

The problems we build for

Thirteen of them are written down, numbered, and traced to the requirement each one produced. Here are four, each with the way we intend to answer it.

How a problem becomes a requirement
PB-01Education

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.

Today
Phone calls, in turnPaper chartWhatsApp group
Designed
Absence loggedRanked candidatesOne dispatch, on record
Consequence

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.

PB-03Education

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.

Today
Handwritten challanCounter or bankMatched by name
Designed
Bulk invoiceSettlement fileThree-way match + exceptions
Consequence

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.

PB-09Agriculture

Field data is captured on paper where there is no signal, then re-keyed later.

Today
Paper in the shedRe-keyed later
Designed
Captured on the deviceQueue, ≥ 72 h offline (spec)Syncs without loss
Consequence

It arrives late, and it arrives wrong, and both are discovered downstream.

PB-13Security and video

Recording fails silently — a disk, a power supply, a camera goes offline.

Today
A disk or camera stops writingNobody is told
Designed
Recording health checkedAlert raised
Consequence

Nobody notices for weeks, and the failure is discovered on the one day the recording was needed.

Illustrative. The register states these problems and never quantifies them, so the diagrams carry no numbers of their own.

Vertical stack

Our own products

Three industries, one platform underneath. Each product page states exactly where that product is, because none of them is finished.

All products
In build
Education

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.

Capabilities
  1. Routine
  2. Substitution dispatch
  3. Attendance
  4. Fees and reconciliation
  5. Export
5 capabilities specifiedInspect specs
Design-partner stage
Agriculture

Nimikh AgriOps

Captures field data inside a shed with no signal, tracks a production batch from placement to close, and settles contract farmers against records both sides can read.

Capabilities
  1. Offline field capture
  2. Batch lifecycle
  3. Feed inventory
  4. Farmer settlement
4 capabilities specifiedInspect specs
Validation only
Security and video

Nimikh VisionEdge

Runs detection on a box at the site, sends events rather than video, and produces evidence a dispute can actually be settled with.

Capabilities
  1. Edge-only video
  2. Temporal validation before an alert
  3. Evidence with a chain of custody
  4. Device and recording health
4 capabilities specifiedInspect specs
Radical transparency

What we know, and where we got it

We have no customer logos to show you. What we have is the research the products were specified against — every figure with the publication it came from and the date it was published, so you can check it.

Education93.7% private
19,757of Bangladesh’s 21,086 secondary-level institutions are private — 93.7%
Private 19,757Government 1,329

The buyer is a proprietor with their own cheque book. There is no tender and no committee procurement cycle.

BANBEIS, via Bonikbarta12 Sep 2025
Education
6,587registered coaching centres, teaching about 917,000 students

Unregistered centres far outnumber registered ones: one city survey found 401 centres, of which 120 were registered.

BBS Private Educational Institutions Survey 2024, via UNB7 Apr 2026
Infrastructure
ZeroAWS, Azure or GCP regions, local zones or edge zones in Bangladesh

In-country hosting is colocation plus a self-managed database, not a managed-service purchase.

Provider region listings, checked23 Sep 2026

Every figure carries its source and date. We would rather it be checkable than impressive.

Figures we could not verify independently — the widely repeated ones about hours lost to scheduling, spreadsheet usage and false-alarm rates — appear nowhere, because the requirements document that specified these products disowned them, and using them here would be worse than having no number at all.

Integrity architecture

What we will not do

Each of these costs us something, which is why they are worth more than a list of features.

The rest of them
Rule 01

We will not hold your money

The institution stays merchant of record. Aggregating payments is a licensed activity in Bangladesh — a trust and settlement account, T+5 settlement, about BDT 1 crore of capital, and personal liability for named officers. We orchestrate collection; we never sit in the flow of funds.

Flow of funds
GuardianInstitution, merchant of record
Nimikh: orchestrates collection, not in the flow
Rule 02

We will not publish a false-alarm reduction figure

No independently audited figure exists for this class of system. We commit to the mechanism and to a baseline measured on your own cameras, at your own site. A percentage quoted before that is a claim about somebody else’s footage.

Where the figure comes from
A percentage quoted in advanceA baseline measured on your own cameras
Rule 03

We will not quote a camera count before measuring your site

How many streams one box handles depends on resolution, frame rate, scene complexity and the accelerator fitted. Quoting it in advance is guessing with your capital.

What decides capacity
ResolutionFrame rateSceneAcceleratorMeasured at your site
Rule 04

We will not ship AI in a first release

Substitute ranking is rules-based, and payment matching is an honest exceptions queue rather than a probabilistic guess. A silent wrong match in a fee ledger is worse than a queue somebody has to work.

When the rules cannot decide
Rules-based rankingNo confident matchExceptions queue, a person decides
Services

Or we build yours

Most of what we do today is custom: a point-of-sale system, an inventory ledger, a CRM, a school office, a booking engine. Same method, same engineering standards, on a system that belongs to you rather than to us.

Engineering

How it is built

A constraint solver that explains why a timetable is impossible. Capture that survives seventy-two hours with no network. Money that reconciles three ways against the bank’s own settlement file. Isolation enforced by the database and proved by a test that runs the whole API suite as the wrong tenant.

Start here

Tell us what breaks every week

Not a feature list — the thing that goes wrong on a Tuesday and costs somebody their morning. If we are the wrong people to fix it, we will say so, and we will usually know who is right.