Build tools you’d use in the shed. Stand where the users stand. It is possible to write software and still get dirt on your boots.
Leave the row better than you found it.
We believe the next wave of farm software will be built by small teams who stand in the rows they write code for. We run one of those rows ourselves — the software is tested on our own farm at Arriga before it reaches anyone else’s.
Working at AgCore, the season is part of the job. When it’s picking time you will see your feature used from a quad bike the same week you shipped it — and hear about it plainly if it doesn’t survive the shed.
Here’s how we build for farms:
Walk the Rows
Decisions get made where the work happens. Go and look before you build.
Harvest Pace
Seasons don’t wait. Ship the fix while the crew still needs it.
One Record
If it’s written twice, it’s wrong somewhere. Build so it’s written once.
No Demo Farms
The software runs on our own farm first. Real paddocks, real payroll.
Plain Words
A grower shouldn’t need a glossary. If a feature needs explaining, rewrite it.
No Backlog
If the idea’s good, it’ll come back. If not, it was noise.
Fix the Fence You Find
Small repairs now beat big rescues later. Leave the row better than you found it.
Make It Beautiful
Working isn’t enough. The 5 am screen should be a pleasure to open.
We’re building one record for the Australian farm
No advertised roles right now — the one below is real, permanent, and read by a human.