01 — Operations layer
FarmerOS
Every farmer, farm and field in one structure.
FarmerOS holds the operational record: who is farming, what they planted, what they were given, what came off the field and what they were paid.
The chain it holds
Farmer
Farm
Field
Crop cycle
Inputs
Harvest
Payment
What it does
Farmer register
Profiles, groups, contacts and history — one farmer, one record.
Production cycles
What was planted, when, on which field, under which contract.
Inputs and training
What was issued, to whom, and what it was meant to achieve.
Harvest and payment
Deliveries logged against the farmer who produced them, then settled.
In the product
Interface mockup · FarmerOSFarmerOSFarmers · 2026-B cycleBusia hub
FarmerFieldCrop / stageInputs issuedExpectedStatus
F-041203A · 1.8 haChilli · floweringSeed, 2× fert.1.9 tSpray due
F-041804B · 2.0 haChilli · harvestSeed, 2× fert.2.4 tHarvesting
F-043106B · 2.7 haBeans · floweringSeed only3.1 tRecord gap
Illustrative interface — values shown are example data.
Decisions it supports
- Who is ready to produce this season
- Which farmers need a field visit
- What volume the network can commit to
- What is owed, to whom, for what
Connects to
- Field boundaries from FarmTrace
- Weather instructions from WeatherIQ
- Contracts and prices from AgroIntel
- Buyer requirements from MarketDirectory
Who uses it
Cooperative managers, field officers, agribusiness operations teams, programme staff
Next layer
FarmTrace