The Pilot 1 story
Yield iQ did not start with a software feature list. It started with a practical problem.
Farm businesses already generate large amounts of useful information, through accounting systems, farm-management platforms, livestock records, weather services, sensors, spreadsheets, handwritten notes and years of practical experience. But those sources rarely come together in one place.
When conditions change, the person making the decision is often left to bring that information together manually, interpret what it means and work out what should happen next. For a complex farm business, that can mean hours, or days, spent reconciling information before the decision itself can even begin.
Pilot 1 was created to test whether there is a better way.
From a regional challenge to a working pilot
The project emerged through work with Regional Development Australia Adelaide Hills, Fleurieu and Kangaroo Island around drought resilience and the practical challenges facing farm businesses across the region.
Drought resilience provided a particularly useful starting point because it exposes the weaknesses of fragmented decision-making very quickly. When rainfall changes, feed becomes tight, input prices move, yields shift or cashflow comes under pressure, operational and financial decisions become tightly connected. A decision about one part of the farm can quickly affect another.
Could we bring those different sources of information together in a way that helps farmers understand the whole business more clearly and make decisions earlier?
That became the foundation for Yield iQ. Pilot 1 was designed as a real-world proof of concept, not a theoretical exercise: to build and test the platform inside an operating farm business, using real systems, real data, real workflows and real decisions.
Why Bellevista?
Bellevista Graziers on Kangaroo Island provides a demanding environment in which to test the idea. It is a complex mixed-enterprise farming business operating across cropping and livestock, with the additional realities of Kangaroo Island logistics, freight costs, seasonal variability and significant capital investment.
The business is already well managed. It also already uses a substantial amount of information. That is precisely what makes it a useful pilot environment. The challenge is not a lack of information. It is bringing together information from different parts of the business quickly enough to support the decisions being made.
Bellevista uses combinations of farm-management systems, financial software, livestock records, paddock information, spreadsheets, seasonal forecasts, operational records and practical experience. Like many farm businesses, some of the most important planning and scenario work still relies heavily on manual modelling.
Pilot 1 began by understanding how those pieces currently fit together.
Starting with the way the farm actually works
The first stage of Pilot 1 was not about designing dashboards. It was about understanding the business. We spent time with the Bellevista team looking at:
- how the season is planned;
- where information comes from and which systems are relied on;
- how paddocks, cropping and livestock decisions interact;
- how financial forecasts are maintained, and where spreadsheets are still essential;
- which information needs to be reconciled manually, and where assumptions are updated during the season;
- which decisions consume the most time or carry the most uncertainty.
Yield iQ is not being designed to force a farm business into a predefined software process. It is being designed to understand the business first, then connect the information and intelligence around the way decisions are actually made.
Connecting the physical farm with the financial business
One of the strongest themes to emerge from Pilot 1 is that farm decisions rarely stay within one category. A change in rainfall can affect crop performance. Crop performance affects expected yield. Expected yield affects revenue. Revenue affects cashflow. Cashflow can influence purchasing, machinery, livestock, debt and investment decisions.
Yet the information supporting each of those decisions often sits in a different place. Yield iQ is being developed to bring those layers together: paddock activities, crop plans, input requirements, purchase commitments, inventory, livestock, seasonal conditions, weather and climate, farm financials, cashflow and scenario assumptions.
The goal is not simply to display them in the same application. It is to help show how they affect each other.
Moving from reporting to decision support
Traditional farm software is often very good at recording what has happened. Yield iQ is trying to go further. Pilot 1 is testing how the platform can help a producer move through increasingly useful questions:
- What is happening?
- What is the current position across the farm and the business?
- What has changed?
- Which assumptions, costs, conditions or outcomes are moving away from the plan?
- What does that mean?
- What are the likely operational and financial consequences?
- What are my options?
- How do different responses change the outcome?
Yield iQ is not intended to replace judgement. It is intended to give that judgement better context.
Scenario planning is a major part of the pilot
Farm decisions are rarely binary. They often involve trade-offs between cost, risk, timing, labour, yield, cashflow, enterprise mix and future flexibility. Pilot 1 is therefore testing scenario modelling as a core part of Yield iQ. For example, what happens if:
- rainfall is lower than expected, or fertiliser costs increase?
- yield assumptions are revised, or livestock numbers change?
- a purchase is delayed, or an investment is brought forward?
Instead of manually rebuilding the analysis each time, the longer-term objective is for Yield iQ to help producers compare those options more quickly and understand the effect across the wider business.
Trust matters as much as intelligence
Bringing information together is only useful if the user can trust it. Farm data comes from very different sources: some is measured, some manually entered, some modelled, estimated or forecast. Those differences matter.
Yield iQ is therefore being designed so users can understand where information came from, when it was last updated, whether it is measured or modelled, which assumptions have been used, where information is missing and how confident the system is in a conclusion. The intention is not to hide uncertainty. It is to make uncertainty easier to work with.
Beyond the desktop
Pilot 1 is also helping shape how intelligence should appear in different parts of the farm business: desktop planning and scenario modelling, spatial and map-based views, tablet and mobile field workflows, and centrally managed connected displays using Presto and ESP32 devices.
Useful intelligence should appear where the decision is being made.
That might be in the office, in the ute, in a paddock, or on a connected display in a workshop or shed. Yield iQ is being designed as a connected intelligence layer rather than a single screen.
What Pilot 1 is really testing
Pilot 1 is ultimately testing whether Yield iQ can reduce the distance between information and action. Not "can we build another farm dashboard?", but "can we help a producer understand the business more quickly, compare the right options, and make a better-informed decision?"
That means testing whether Yield iQ can help move from what is happening? to what does it mean for the business? to what are my options? to what should I consider doing next?
The lessons from Bellevista are now shaping the next stage of Yield iQ.