aaron8.
  1. Home
  2. Industries
  3. Agriculture & agribusiness

Seasons don't wait for paperwork.

Everything on the land is a weather call plus a compliance form. My live tool Rain Check exists because "what's the forecast" is the wrong question and "can we do the job on Thursday" is the right one; the same thinking applies to spraying windows, harvest logistics and the paperwork that follows every one of them.

Live proof

Use it. Right here.

Pick a paddock and a product, see which days the forecast and the label allow, and log an application with the withholding date computed.

live demoSpray window finder

This working build runs in your browser and needs scripts enabled. Everything on the page describes what it does; turn them on to use it.

The same shape works for harvest windows, irrigation and stock movements: rules plus forecast plus your paddocks, with the compliance record written as you go.

The work

Where the hours go, and come back.

Decisions with the weather in them

Rain Check answers whether Thursday's concrete pour survives the weather, live and free. The identical pattern serves spray windows, harvest scheduling and contractor bookings: your rules plus real forecasts equals a straight answer.

Compliance assembled, not retyped

NVDs, spray diaries, chemical records and audit evidence built from data captured once in the paddock, not reconstructed at the kitchen table in September. The auditors get provenance; you get your evenings.

The numbers reconciled into decisions

Yield, price, inputs and agistment reconciled across the spreadsheets and the accounting file, per data & reporting, so the decision about next season leans on arithmetic instead of memory.

Tools that work where reception doesn't

Offline-first capture on the phone, syncing when the ute finds bars, per mobile apps. Any tool that assumes coverage was designed in a city, and it shows.

Straight about it

Country problems, checked answers.

I am Adelaide-based, not farm-raised, and the proof I offer is the same as everywhere on this site: a live weather-decision tool anyone can use, a public platform build anyone can compile, and a habit of learning a domain properly before building for it. Agriculture also gets my honest scepticism about ag-tech platforms: I sell nothing but the work.

Fair questions

Before you ask.

Reception is patchy at best.
Then nothing I build for you will assume otherwise: capture works offline, syncs opportunistically, and never loses a record to a dead zone. This is a design decision on day one, not a patch after harvest.
We run the farm on spreadsheets and it mostly works.
Spreadsheets are legitimate farm software and I will not sneer at them. The upgrades that pay are usually narrow: the one double entry automated, the one report assembled, the one record that must survive an audit made durable.
Every ag-tech company wants to sell us a platform.
And each platform wants to be the only one. My advice is independent: I integrate what earns its keep, decline what does not, and have no reseller margin riding on the answer.