Case study — 01 / HORSCH
The software around the machines.
Situation
A modern agricultural machine does not ship alone. Farmers expect to see their machines and fields in an app. Problems in the field need a reliable path back to the engineers who can fix them. For HORSCH, this digital landscape has become as much a part of the product as the machine itself. Over several years, we have become the engineering team behind a growing share of it.
Constraint
Nothing here was greenfield. Backends already existed, some owned by partner companies. Web tools were already in daily use. Every product we built or took over had to fit an existing landscape and improve it without interrupting the people working in it.
What we did
-
01
Building myField, the product farmers use to see and track their machines and fields, across web and mobile. It brings many separate systems into one consistent whole, built with HORSCH's teams on backends that already existed, some owned by partners. The work is to make it one product, not a set of tools.
-
02
Took over HORSCH Report, the Jira-connected system where issues with machines in the field are raised and tracked. Refactored, extended, and improved it in continuous operation.
-
03
Built the reporting app in React Native, complementary to the existing website: push notifications, offline functionality, designed for where the work actually happens: in the field, not at a desk.
-
04
Built the frontend of the translation platform their teams use to manage translations across very large projects, on top of an existing backend.
-
05
Ran all of it as product development, not a ticket queue: feedback iterations with HORSCH’s teams and, where it matters, with the farmers themselves. Anonymized usage data informs what gets built next. The roadmap comes from that conversation.
[ Screenshot — myField: the machine and field view a farmer opens ]
[ Screenshot — HORSCH Report: an issue from the field with its Jira link ]
What runs today
Farmers track their machines in an app we built. Issues from the field reach engineering through a system we carry. Translations across the product landscape run through a frontend we built. The engagement is ongoing. That is how we prefer to work.
Facts
- Products
- myField · HORSCH Report · Translation platform
- Status
- In production, ongoing
- Stack
- React Native · Web · Jira integration
Next case study
Case study — 02 / Almanach A learning platform where every step makes sense.