Divisi for Enterprise
You already sold the tonnage.
Now see whether it is coming.
Every field in your book, drawn as the farmer walked it and carrying a yield projection that moves all season — so the tonnage you sold stops being a surprise at intake.
Carrying pre-sold tonnage and a quality spec on fields you will next see at the weighbridge? Applying is free, and a person reads it within a working day or two.
Your book is a list of names, and your hectares are what somebody paced out and told you. The first hard evidence that a top-dressing window was missed arrives at intake, four months after the week you could have acted on it — as tonnage short of contract, or a grade that fails the spec.
a look inside
Every field, drawn as the farmer walked it
Coloured by how each crop is doing against what was committed at planting, with the reason on the row beside it — so the output is a route for the week rather than a number to escalate.
The cohort map and the risk list, at per-field resolution. Illustration — the layout, colours and figures a partner account shows, drawn rather than sampled, because a real cohort belongs to the farmers in it.
the ground you are standing on
Two numbers, neither of them ours
What Sub-Saharan maize yields move to on management alone — cultivar, nutrient rate and placement, density, pest control, earlier sowing — across 14,773 smallholder fields. No new land, no new technology.
Nature Communications, 2024The share of Sub-Saharan Africa's food calories grown on farms under five hectares — the fields your book is made of, and the ones the agronomy reaches last.
Samberg et al., 2016
What your outgrowers open every day
This is the part most monitoring platforms skip. A tool that exists only to feed a head-office dashboard is abandoned by week three, and the dashboard quietly fills with nothing. Divisi is a free farming app first — what to plant on this field, when to plant it, the job due this week and why it matters, weather that names the risk, and a diary of what was done. Consistent supply is made on the field, which is why what the farmer gets matters to your book as much as the dashboard does.
See the app, feature by feature →See it on your own phone → One link, both stores — it opens the right one for your device.
impact, and the balance sheet
The pressures already on your risk register
Consistent supply, quality, climate exposure and the traceability and social reporting your buyers ask for are not separate programmes — they are one information problem about the fields you buy from, and the answers come off the same map.
01
Climate exposure, priced early
A shortfall you can see in August is one you can re-contract or buy forward against while the market is still calm. The same figure is the climate-risk disclosure your lender and your insurer keep asking for.
How Each field's projected yield is recomputed when a weather event is confirmed and when field work lapses, and the map colours against what was committed at planting.
02
Traceability to the field, not the depot
Chain-of-custody evidence at field resolution, gathered as a by-product of the season rather than as an audit exercise — which is the level buyers running deforestation and provenance checks now ask for.
How Every enrolled crop is attached to a boundary its farmer walked, a planting date, and a diary of dated, photographed operations.
03
Quality, traced to a practice
A rejection becomes a question with an answer rather than an argument. The practice behind it can be corrected on the fields it came from, which is what stops a grade swinging from one delivery to the next.
How Task completion and diary entries show what was done on a field and when, beside the crop's own stage-by-stage guidance.
04
Youth and gender, without a survey
The workforce figures an ESG report, a development-finance covenant or a buyer's social audit asks for, read off the dashboard rather than reconstructed from a spreadsheet.
How The cohort's gender split and age bands — including the under-35 share on the AU's definition — are counted over people rather than plots, and published only where the group clears ten farms.
How this maps to the Sustainable Development Goals — read the alignment →
What a season looks like when you can see it
Hectares you can stand behind
Boundaries are walked on foot with the phone's GPS and closed into a real polygon, so the area under contract is measured rather than declared. Every hectare on your map was paced by the person farming it.
A projection that moves before delivery does
Each crop carries an attainable yield scored from that field's own soil, terrain and climate through the FAO's GAEZ framework, then moved through the season as field work lapses and weather is confirmed. The number changes in August, not at the weighbridge.
A risk list with the reason on the row
Not “here are your farmers” — the fields below what was committed, sorted by tonnes at risk, each saying whether it was never planted, missed field work, or weather. That is a route plan for the week, not a report.
Evidence, with photographs and dates
Farmers log jobs as they finish them, with a photo and a timestamp, because the diary is theirs and useful to them. For a dispute over whether the inputs went in the ground, that record already exists.
How a programme runs
Apply, and a person reads it
There is no card and no self-serve door, because what an approved account can see belongs to farmers rather than to us. Usually a working day or two.
Open a programme and a season
Name the crop, the window and the terms. You get a six-character code to put on a poster, a radio advert or a WhatsApp message.
Farmers join and consent per field
They install the app free, walk their boundary, and accept the terms for that field and that season. Only then does anything appear to you.
Work the list, not the whole book
Officers go where the map is red. Everything else farms on, with the agronomy already in the farmer's hand.
what your account shows
Resolution follows the relationship
Your programme reads at field resolution for the farmers who joined it, and at area resolution everywhere else in your catchment. Both are on the same map.
Area figures
District and ward totals
Counts, hectares, crop mix, condition and the demographic split for the areas your mandate covers — grouped by the administrative boundaries your own statistics already use. Verification is what moves an account from district totals to ward totals.
Field detail
One field, its season, its evidence
The crop, its walked boundary, its projection, the work done and missed, and the dated photographs — for the farmers who joined your programme and agreed to it, per field and per season. Enrolment is how an account reaches this, which is why the invitation flow is part of the product.
The floor under every published figure
Every area figure stands on at least ten farms. Where a ward holds fewer, it merges into its district and is republished there rather than being hidden — so the map sharpens as coverage grows and never goes blank, and no published set lets a suppressed one be recovered by subtraction. That floor is what makes serving these figures legitimate, and it is why a data-protection review of this is short.
What it costs
Priced per active farmer, per year
Graduated bands — the rate falls as your book grows, and the blended rate falls with it. Larger books are negotiated, and volume, commission and profit-share structures are all on the table.
The first fifty are free, permanently
On every account, including paying ones. A pilot is a real offer rather than a trial that expires into a five-figure invoice.
You never pay for a dormant account
A farmer who accepted but has not finished onboarding is free for fourteen days. One who has not opened the app in a month is free. Our revenue sits downstream of our own retention, which is the alignment worth having.
Invoiced in USD, settled by bank transfer
The dashboard shows the arithmetic behind every line and announces the first invoice thirty days ahead. Ask us for the band table and we will scope a quote against your actual book.
What you can count on
A farmer walks their own boundary and logs their own work because the record is useful to them, which is the only reason it is any good to you. Everything on your map is a by-product of a season somebody was running anyway. So the hectares are paced rather than declared, the photographs taken at the time rather than reconstructed, and the projection moves because the field moved. That is why a contract can sit on top of it.
Questions worth asking
not quite you?
Same platform, different job
Plenty of organisations are two of these at once. The access model is identical; what changes is what the figures are for.
Start with the map, not the contract.
Tell us who you are, where you work and what you are trying to see. We read every application ourselves and scope the rollout with you.
Contract farming and outgrower schemes, agro-processors, aggregators and exporters, input suppliers and agro-dealers, agri-finance and insurance.
Already a partner? Sign in to your dashboard