Why the largest incumbent in UK farm software chose to abandon livestock records rather than combine them with accounting, and what that decision reveals about the market it left behind.
UK farm management software is structurally split between two product categories that rarely overlap: livestock compliance and traceability applications on one side, and farm accounting and bookkeeping applications on the other. The clearest evidence for this split is behavioural rather than theoretical: in 2023, Farmplan, at the time the UK's largest farm software provider, exited livestock record-keeping entirely and referred its users to a rival product, while retaining accounting as a separate offering. This paper examines the structure of the current market, the Farmplan exit as a case study in why an incumbent chose divergence over integration, and the specific product gap that split leaves open.
A note on methodThis paper draws on publicly reported market information, including trade press coverage of the Farmplan and Herdwatch partnership, published pricing and feature information from named vendors, and Defra software adoption data. Company positioning and feature claims are drawn from each vendor's own public marketing material as of the date above and are attributed accordingly; this paper does not have access to any vendor's non-public financial or user data.
A market can be split in two ways: by design, when a regulator or a technical constraint makes combination genuinely difficult, or by historical accident, when the vendors that happened to build first each specialised in one half of a problem and no one has yet found it worthwhile to combine them. UK farm software is split in the second way. There is no technical or regulatory reason a single application cannot both register a calf's birth with the government and record the vet invoice for its subsequent treatment as a VAT-coded expense; the same underlying event, an animal receiving veterinary treatment, generates both a compliance record and a financial one. Yet the current market treats these as separate product categories, built by separate vendors, sold as separate subscriptions.
This paper argues that the clearest evidence for this split being a historical artefact rather than a deliberate market structure is the behaviour of the market's own largest incumbent, examined in detail below.
UK farm software serving livestock farms can be broadly grouped into three categories. The first is livestock compliance and traceability software, exemplified by products such as Herdwatch and Shearwell, built primarily around registering births, movements and deaths with government systems and maintaining assurance-scheme records such as the medicine book. The second is farm accounting software, exemplified by products such as the accounting functions historically offered by Farmplan (now TELUS Farm Accounting) and the accounts products from vendors like Sum-It, built around bookkeeping, VAT and, increasingly, Making Tax Digital filing. Some of these vendors sell livestock modules alongside their accounts, Sum-It among them, so the divide is one of degree, but the two are generally sold and run as separate products. The third is a smaller category of trading or finance-focused platforms, such as Breedr, oriented more toward buying, selling and financing livestock than toward either compliance record-keeping or general bookkeeping.
What is largely absent from this landscape, as of the period covered by this paper, is a product that treats livestock compliance and farm bookkeeping as a single, integrated dataset rather than two separate applications a farm has to run in parallel and reconcile manually. A fuller comparison of the leading named products against this criterion is set out in our own guide to FarmHQ vs Herdwatch vs spreadsheets and an accountant.
The single clearest piece of evidence for this market structure being a genuine gap, rather than a combination nobody wants, comes from the market's own history rather than from any outside analysis. Farmplan, historically one of the largest and longest-established farm software providers in the UK, built and sold livestock recording functionality alongside its accounting products for many years. In 2023, Farmplan exited livestock record-keeping entirely, entering a partnership under which its existing livestock-module users were referred to Herdwatch, a specialist livestock compliance competitor, while Farmplan itself retained and continued to develop its accounting product as a separate offering, which has since become the cloud-based TELUS Farm Accounting, formerly Farmplan Business Cloud.
This decision is significant precisely because it was made by an incumbent with every structural advantage to attempt the opposite move. Farmplan already had an established livestock product, an established accounting product, and an existing customer base using both. If there were a strong commercial case for deepening integration between the two rather than separating them further, Farmplan was better positioned than almost any other UK vendor to make that case internally and build toward it. Instead, the company chose specialisation: concentrate on accounting, where its established product and long-standing accountant relationships gave it durable strength, and exit the livestock category to a competitor better positioned to compete there. The market's own largest incumbent, in other words, revealed through its actions a judgement that these two product categories are better run as separate businesses than combined, at least under its own existing technical architecture and organisational structure.
Several structural factors plausibly explain why no vendor has yet successfully combined the two categories, distinct from any judgement about whether combination is desirable. Livestock compliance software has to integrate deeply with government systems, historically the Cattle Tracing System and now the Livestock Information Service in England, with equivalent but separate systems in Scotland, Wales and Northern Ireland, a genuinely specialised and continuously maintained technical burden discussed further in a companion piece on the 2026-2028 regulatory convergence. Farm accounting software has to integrate with HMRC's own filing infrastructure and meet the specific requirements of Making Tax Digital, a different specialised technical burden requiring its own sustained investment.
A vendor that has built deep expertise in one of these two integration burdens does not automatically possess the other, and building both from a standing start is a materially larger undertaking than building either alone. This plausibly explains why specialisation, rather than combination, has been the rational strategy for most existing vendors, including, as the Farmplan case illustrates, for an incumbent that already possessed both product lines and chose to separate them rather than integrate them further.
The practical consequence of this market structure, for a farm rather than for a vendor, is that combining compliance and financial visibility currently requires manual reconciliation across two or more separate systems. A specific, frequently cited example is the inability to answer a compound question spanning both datasets, such as the actual cost per animal of a course of veterinary treatment, without manually cross-referencing a compliance record in one system against a financial record in another. Answering that question requires the vet invoice, held in the accounting system, and the treatment record, held in the compliance system, to be read together, a task no single-category product is positioned to do because it does not hold both datasets in the first place.
This is not a claim that no other vendor could build such a combination in the future, only an observation, grounded in the Farmplan case above, that the market's own largest and best-positioned incumbent chose not to, and that the specialised integration burden on each side of the divide plausibly explains why. Whether a product built from the outset to hold both datasets changes that calculus is a separate product question, addressed elsewhere on this site, rather than a claim this market-structure analysis makes on its own.
The split between livestock compliance software and farm accounting software in the UK market is better explained as a historical and technical artefact than as evidence that farmers do not want the two combined. The clearest evidence for that reading is behavioural: Farmplan, the incumbent with the strongest existing position to attempt integration, chose specialisation instead, exiting livestock records to a competitor rather than deepening the combination. The specialised, separately demanding technical integration burden on each side, government livestock systems on one side, HMRC filing infrastructure on the other, offers a plausible structural explanation for why this pattern has persisted across the wider market, and identifies the specific product gap that persists as a result.