Not another farm management information system.
The market has enough of those and several of them are good. What it does not have is a consumer and brand layer that sits on top of whatever a farm already uses, and that is the only thing worth building here.
Why we are not building a farm management system.
A farm management information system records fields, crops, inputs, applications, movements, compliance and yields. It talks to the sprayer, the drill, the yard scales and the assurance scheme, and it exports the returns a farmer is legally obliged to file.
That is a large, deep, unglamorous product with twenty years of accumulated regulatory detail in it. Several companies do it well, farms are already paying for them, and the switching cost is enormous because the historic field records are the point.
Building a competitor would mean spending three years reaching feature parity with something a farmer already has, in order to sell it to a market of about fifty thousand holdings that is not growing. It is a bad idea and it is the idea everybody has.
What exists, and what does not.
| Farm MIS | Agronomy platforms | Assurance portals | A consumer layer | |
|---|---|---|---|---|
| Records fields and applications | ||||
| Files the regulatory returns | ||||
| Talks to the machinery | ||||
| Tells a customer where the food came from | ||||
| Runs a direct-to-customer shop | ||||
| Handles a farm’s own audience | ||||
| Market is well served | ||||
| Worth building in 2026 |
What the consumer layer would actually do.
-
Read what the farm already records, and translate it.
A field record already contains the variety, the drilling date, the applications and the harvest date. That is a provenance story sitting in a database in a format nobody outside farming can read.
Turning "WW, Extase, drilled 28/09, harvested 12/08, 8.4t/ha" into a page a customer can understand is a translation problem, not an agronomy problem, and nobody is doing it because the MIS vendors sell to farmers rather than to their customers.
The data exists. The audience for it does not have a reader.
-
Give the farm a shop that costs the box before it launches.
Which is the storefront on the next page along, and is the part that actually makes money for the farm rather than for a platform.
-
And keep the audience in one place.
A farm with fourteen thousand followers on one platform has borrowed an audience. A farm with an email list of nine hundred owns a smaller and considerably more valuable one.
Every part of this layer should push towards the list, and the list should be exportable, because the moment it is not, the layer has become the same trap as the platform it replaced.
Where the data would come from.
| Source | What it gives | How hard |
|---|---|---|
| Farm MIS export | Field, variety, dates, yields | Easy if the vendor exports; several do not |
| Assurance scheme records | Inspection dates and status | Medium, and only with the farm’s consent |
| The farm’s own photographs | Everything a customer actually wants | Easy, and constantly underused |
| Weather station or public data | The season the crop actually had | Easy |
| Movement and abattoir records | Traceability for meat | Hard, and legally sensitive |
| Sales data from the storefront | What is worth growing more of | Easy, and the most commercially useful |
What this would not be
Not an agronomy tool. Not a compliance filing system. Not a replacement for anything a farm is currently paying for. Not machinery telematics. And not, under any circumstances, a product that requires a farm to move its historic field records, because that request is how every agricultural software company loses a deal it should have won.
The positioning, in four lines.
Not an MIS
The market has enough, and several are good.
Sits on top
Reads what a farm already keeps.
Audience, not acreage
The customer is the customer.
Exportable
The list belongs to the farm.
The part of it that already makes sense.
A hosted storefront at six per cent that costs the box before it lets you sell.
