where the advice comes from

Advice you can check.
Here is exactly how it is made.

Divisi's crop recommendations are not opinions and they are not a language model's guess. They come from an implementation of the FAO's Global Agro-Ecological Zones method, run against published soil, climate and terrain data for the specific point a farmer pinned. This page explains the whole chain, including what it cannot tell you.

Free forever Works offline Budget phones welcome
Divisi's verdict for one field: grows well here, plant November, harvest April
Also consider: ranked alternatives for this plot — hot pepper, robusta coffee and garlic, each able to grow here with care

Every agritech product claims its advice is data-driven, and almost none of them will tell you which data, or what happens when the data is thin. If you are considering putting your programme's farmers on a platform, that is the first thing you should be able to check.

Divisi's verdict for one field: grows well here, plant November, harvest April
the inputs

Published science, read at one point

Every recommendation starts with the coordinates of one field and reads the environment there: soil properties from global soil mapping, two decades of daily climate reanalysis for temperature and rainfall, and terrain from elevation models. These are the same public datasets used in agricultural research — the work is not in owning them, it is in reading them correctly at the scale of a single smallholding and knowing what they cannot resolve.

Also consider: ranked alternatives for this plot — hot pepper, robusta coffee and garlic, each able to grow here with care
the method

A suitability cascade, not a score somebody invented

The crop's potential is reduced step by step by each thing the field imposes on it — temperature through the growing cycle, water supply against demand, soil chemistry and physical constraints, terrain — in the order and manner the FAO's agro-ecological zoning framework sets out. What comes out is a suitability class and an attainable yield with the reasons attached, so a recommendation can always be interrogated: not '85 out of 100', but which factor cost what, and where.

Two Divisi crop picks for one field, each with a photo, a grows-well-here verdict and the yield to expect
the uncertainty

A range, because a single number would be a lie

Climate averages carry no information about the year you are actually about to have. So alongside the expected yield, Divisi runs the same plan — same field, same crop, same planting date — through a drier and a wetter season, and reports the band. A crop with a narrow band is a crop that behaves whatever the year does, which is frequently the more valuable thing to know.

What happens when a farmer taps 'check my farm'

1

Read the point

Soil, climate and terrain for the pinned coordinates are assembled into one environmental picture of that field.

2

Run every candidate crop

Each crop in the catalogue is run through the cascade against that picture, at each plausible planting date, and ranked.

3

Return the reasons

The farmer gets a class, an expected yield, a range and a planting window — with what limited the crop, in words.

Get Divisi free — set up in 3 minutes

Pin your farm once. From then on the advice, alerts, diary and ledger work anywhere — even with no signal in the field.

No card required Works offline Budget phones welcome

What we don't claim

The limits, plainly. Global soil and climate data resolve to a grid cell, not to a field boundary — so Divisi knows the soil of your neighbourhood better than the soil of your particular hollow, and a farmer who knows their land will sometimes be right where the model is wrong. Yields are biophysical potential at a stated input level, not a promise of what you will harvest; management, seed quality and luck all sit between the two. We publish the method and the reasoning but not the parameter tables, because those are the engine. And we have not run a randomised trial of Divisi's effect on yields — when we do, we will publish what it found, including if it is disappointing.

Questions worth asking

No. The recommendation engine is a deterministic agronomic model: the same field, crop and season produce the same answer every time, and every answer decomposes into the factors that produced it. Language models are used in Divisi for writing and translation work, never to decide what will grow on somebody's field.

Soil properties from global soil property mapping, daily climate reanalysis covering roughly two decades for temperature and rainfall, terrain from digital elevation models, and crop parameters compiled from published farming research including FAO and CABI material. Live weather for forecasts and alerts comes from a commercial provider at the farm's coordinates.

It is honest at the scale it works at, which is a grid cell of a few kilometres — good enough to distinguish two farms in one district, not good enough to resolve a wet corner of one plot. That is why Divisi asks the farmer for the things the data cannot see, such as whether a field is irrigated or under a greenhouse, and why the diary matters: the farmer's own record is the ground truth the model does not have.

Yes. We will walk an agronomy or M&E team through the cascade, the data sources, the calibration and the failure modes, and we would rather do that before a programme starts than after. Get in touch and we will set it up.

Because published together across the whole catalogue they are the engine, and rebuilding it from them is a weekend's work for a competitor. The method is public, the reasoning behind any individual recommendation is visible to the farmer who received it, and the crop, pest and disease guidance is free to read on this site. The rating tables underneath stay ours.

For organisations

Running an outgrower or contract-farming programme?

Ground-truth visibility across member farms, remote agronomic support, fewer field visits — on the app your farmers already use free.

Explore Divisi Enterprise →