AGRI_IT

Challenge board

Help shape the future of the ag industry

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.

How it works

Your input shapes what gets attention — not a sales funnel, just a practical way to work on the right problems.

Share what’s broken

Describe a frustration, workaround or gap on your place. We summarise it anonymously so others can relate without names attached.

Vote on what resonates

Read what other farmers and operators have raised. Upvote what resonates, downvote what doesn’t — click again to remove your vote.

Strong themes enter the lab

Challenges with the most support are where we look first. Open experiments and field notes live in the Ag Data Lab.

The Challenge Board

Ranked by net support — upvotes minus downvotes. Click again to remove your vote.

  1. 1

    Farm data won’t move between systems

    Paddock boundaries, yield maps and job records get stuck between FMIS, machinery and agronomy tools — rebuilt every season instead of flowing through.

  2. 2

    Boundary files from hand drawing using AI

    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.

    Being explored in the Ag Data Lab

  3. 3

    AB lines won’t load on another machine

    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.

  4. 4

    Block spray records don’t match contractor apps

    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.

  5. 5

    Broiler chicken operational data is fractured

    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.

Submit a challenge

Something repetitive, broken, or harder than it should be? Describe what happens on your place. We may summarise it anonymously on the board so others can vote — nothing with your name unless you ask us to.

We read these personally. Your email stays private — it’s only so we can follow up if useful.

Follow what we’re testing

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