Share what’s broken
Describe a frustration, workaround or gap on your place. We summarise it anonymously so others can relate without names attached.
Challenge board
An open board for farmers and industry. Submit a problem anonymously, vote on challenges that sound familiar, and help decide what we take into the Ag Data Lab to investigate and build.
Your input shapes what gets attention — not a sales funnel, just a practical way to work on the right problems.
Describe a frustration, workaround or gap on your place. We summarise it anonymously so others can relate without names attached.
Read what other farmers and operators have raised. Upvote what resonates, downvote what doesn’t — click again to remove your vote.
Challenges with the most support are where we look first. Open experiments and field notes live in the Ag Data Lab.
Ranked by net support — upvotes minus downvotes. Click again to remove your vote.
Paddock boundaries, yield maps and job records get stuck between FMIS, machinery and agronomy tools — rebuilt every season instead of flowing through.
A rough hand-drawn paddock boundary should become a GIS-ready file for FMIS and machinery — but only if the AI output can be checked before it goes to the field.
Guidance lines that work on one display need reformatting or redrawing before they’ll load on another — burning time at the start of a job when you should already be running.
What went on which block lives in the vineyard system, the contractor’s app and a paper diary — and they rarely agree when audit time comes.
Temperature, humidity, feed, mortality and placement records sit in different controllers, spreadsheets and shed books — nothing gives one operational picture across the grow.
Supported challenges are prioritised for the Ag Data Lab. Submit yours to add to the board.
When a challenge gains traction, it moves into the Ag Data Lab — open experiments, honest results, and field notes on what worked and what didn’t.
Explore the Ag Data Lab