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.
The paying tenant is the integrator, the feed mill or the commercial farming company — never the farmer, who has neither the budget for software nor a reason to buy it. Poultry contract growing and pond aquaculture are the two sub-segments in scope; dairy is not.
Design-partner stage. Specified to the same depth as EduOps and entering the paid design-partner stage. It starts only if that stage earns it — the gate is a measured one, not a date. 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 record is written on paper, then re-keyed late and wrong
Batch cost, feed conversion and mortality are known only once a production cycle has closed. Field data is captured on paper where there is no signal, then typed in days later by someone who was not there. Contract-farmer settlement is disputed because the underlying records belong to the integrator alone, and the farmer has nothing to check them against.
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.
Batch cost, feed conversion and mortality are known only after a production cycle has closed.
By the time the number arrives, the batch it describes has been sold and nothing can be done about it.
Field data is captured on paper where there is no signal, then re-keyed later.
It arrives late, and it arrives wrong, and both are discovered downstream.
Contract-farmer settlement is disputed because the underlying records belong to the integrator alone.
The farmer has nothing to check the statement against, so the dispute is about trust rather than about a number.
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 list here is finite and nameable, which is the opposite of a consumer market and the reason this product is specified around one tenant type rather than around a farm. The gap figure above is our own research, and it is stated as what we looked for and did not find rather than as a claim about what exists.
What it does
Written as designed, not as delivered. Nimikh AgriOps 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.
Offline field capture
Feed, mortality with a cause code, water and environment readings, weight sampling, medication and photographs — captured one-handed, in about forty seconds, with no network call anywhere in the flow, including validation.
Batch lifecycle
Placement to close, with live metrics on the device rather than after the cycle ends, and threshold alerts while there is still something to do about them.
Feed inventory
Mill dispatch through receipt to consumption, with variance flags where the three do not agree.
Farmer settlement
Settlement runs that produce a statement the farmer can read, so a dispute is about a number both parties can see rather than about whose record counts.
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.
- about 40 secondsTo capture a shed visit one-handed: feed, mortality with a cause code, water and environment readings, weight sampling, medication and photographs.
- ZeroNetwork calls anywhere in the capture flow, validation included. The form does not need a signal to know whether what was entered is valid.
- at least 72 hoursField capture keeps working with no network at all, and syncs afterwards without loss.
- Line by lineA settlement statement the contract farmer can read and dispute item by item, so the argument is about a number both sides can see.
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.
No satellite or NDVI crop monitoring
Sentinel-2’s 10 m pixels give roughly fifty pixels on a half-hectare holding, and the June–October monsoon destroys optical usability without a radar pipeline.
No farmer-facing consumer app, no agri credit, no marketplace
There is no payer for them. The tenant is the integrator.
No feed-conversion or feed-cost benchmarks quoted as fact
The figures circulating for broiler FCR and feed’s share of production cost could not be independently verified, so they are configured per tenant rather than asserted.
The design-partner stage is paid, and it is the gate
AgriOps starts if integrators and feed mills find the discovery work worth paying for, and it does not start otherwise. If your field records arrive days late and your settlements are argued rather than read, that is the conversation worth having.