It can read anything. It cannot change anything without your say-so.
Farm software makes you learn its filing system. Which menu holds fuel logs, which tab has the withholding period, which report shows what you spread and where. The information is in there somewhere, and finding it is your problem.
Ask AIffi inverts that. You describe what you want in your own words — a question, or a job that needs doing — and it works out which records to read, what arithmetic to run, and what needs to change. Then it shows you the change and waits.
That last part is the whole design. AIffi’s language model has no ability to write to your data. None. It can only draft a proposal. When you approve one, tested and deterministic code applies it, running under your own permissions. There is no second path into your records.
Which makes the two halves deliberately lopsided. Reading is wide open — ask anything, in any words, about anything you have recorded. Writing goes through a small, fixed set of doors, every one of them typed, tested, and shown to you as a card before it does anything. The flexibility is in the asking; the discipline is in the changing.
It also remembers. Anything you tell AIffi about how your place works — with your say-so — it keeps, so it starts each conversation knowing more about your operation than it did the last one.
Wallah Demo Farm is a working AIffi farm with made-up records: cattle and sheep, paddocks, irrigation, fuel, machinery and jobs. Ask it what you would ask about your own place, in your own words.
You can make changes too — ask it to create a job and give it to Sam, or record some rain. It shows you each change as a card, and nothing happens until you approve it. It’s a shared farm, rebuilt every night, so others see what you add until then. Photos, voice and eNVD are switched off here. More about the demo farm.
You register with your name, email and mobile, and we email you a code. Twenty questions each. We keep your demo questions and AIffi’s answers to review and improve it — see our privacy policy. Please don’t type other people’s personal details into the chat.
Standing in a paddock you can read an answer perfectly well. What you can’t comfortably do is type the thirty-word sentence that produces one — one-handed, in the sun, with a glove off.
So now you don’t have to. Tap the microphone, say what you want, and the words appear in the message box — on the field screen, on the dashboard, anywhere you can type. It works on the phone you already have, and like the rest of the AI it draws a small amount from your prepaid balance each time you speak.
What you said arrives as ordinary text you can read and correct, exactly as if you had typed it. You press send. Nothing reaches your records because you stopped talking.
While the words are still the machine’s rather than yours, the screen says so — and that marker disappears the moment you edit them.
Before it listens, AIffi hands the recogniser your own paddocks, mobs, products, properties and machinery — read straight off your records. Nothing to maintain: name a paddock and it becomes a word AIffi expects to hear.
On our own farm that took farm names from two in five to roughly nine in ten. Ordinary words were never the problem — it is the paddocks, mobs and products that trip a recogniser that has never heard of your place.
Say something it mangles — “Boonegala”, “Hepper”, “Cydictin” — and AIffi puts the name it thinks you meant beside the box as something you can tap. It never quietly swaps a word for you.
That rule is deliberate. A wrong name applied silently books work against a paddock nobody named, and you would have no way of knowing.
Your audio goes to an Australian endpoint, comes back as text, and the bytes go no further — not stored, not kept for replay. The request is also marked so the speech provider cannot use your farm’s audio to train its models.
If the paid path is unavailable it falls back to the phone’s own free recogniser, still matching against your names, and the screen tells you which one produced the words.
This is an actual conversation from Mullinroo Estate, lightly trimmed for length. Nothing has been added, and the numbers are the platform’s own.
You have 166 kg of Green Urea NV® on hand.
That’s based on 1 purchase in and 1 application out, with the last movement on 16 July 2026.
Want me to check how much you’d need for a specific paddock, or look into ordering more?
Let me look up the Crop Paddock and the Urea product details at the same time.
Here’s the picture:
Let me set up the job for Dave and the planned spread operation.
Let me handle all three things at once — reschedule Dave’s job, record the Urea delivery, and find the Urea store.
Once both are approved, you’ll have 1,166 kg on hand — well above the 748 kg needed for the Crop Paddock spread. Do you want me to record the cost of the delivery as well?
Later in the same conversation, the farmer asked for a second job to be created and assigned to himself.
I’d be happy to create that job for you — but I don’t have your name on file. What’s your name so I can assign it correctly?
From Mullinroo Estate, lightly trimmed, and the numbers are the platform’s own. The farmer said which runs were watered and when. AIffi did the rest — and stopped to ask about the one run it couldn’t be sure of.
Runs 1, 3, and 4 resolved cleanly. However, Crop Run 2 is ambiguous — there are two matches on the Monsoon - Irriland:
Which one did you water on Friday at 7am?
In the meantime, I’ll get the dates resolved and kick off the three unambiguous logs right away.
Three cards are ready to review. Here’s a summary:
| Run | Day | Start | Runtime | Water | Depth | Fuel |
|---|---|---|---|---|---|---|
| Crop Run 4 | Wed 16 Sep | 6:26 am | 4h 31m | 163,984 L | 18.9 mm | 27.1 L |
| Crop Run 3 | Thu 17 Sep | 6:26 am | 5h 38m | 204,707 L | 18.9 mm | 33.8 L |
| Crop Run 1 | Fri 18 Sep | 4:00 pm | 5h 8m | 186,890 L | 18.9 mm | 30.8 L |
All at 30 m/h, 4 bar, 17% start moisture. Each run already has prior logs — these will be added as new entries, not replacing any existing ones.
Operating point: the 4 bar chart row (606 L/min).
Crop Run 4 already carries 8 log(s) — latest “Crop Run 4 · #8”. Approving adds ANOTHER log, it does not replace one.
Got it — Crop Run 2 (155.6 m). Logging it now at Friday 7am.
| Run | Day | Start | Runtime | Water | Depth | Fuel |
|---|---|---|---|---|---|---|
| Crop Run 2 | Fri 18 Sep | 7:00 am | 5h 11m | 188,708 L | 18.9 mm | 31.1 L |
30 m/h, 4 bar, 17% start moisture. Same note as the others — it already has prior logs, so this adds a new entry rather than replacing one.
All four runs are now ready to review and approve!
Arthur’s Acres at Mullinroo Estate, 13 September. Lightly trimmed, one crop name corrected, and the numbers are the platform’s own. The photos and a satellite reading told two different stories. AIffi said so, used the farmer’s figure, and showed its working.
Good — Arthur’s Acres is confirmed on Mullinroo Estate. There’s a mob called Near By Finishers currently in Arthur’s Acres (though it shows 0 head — that may need checking).
The Near By Finishers mob in Arthur’s Acres currently has 0 animals on the roster — so I can’t run a grazing budget against them as-is.
Pasture analysis — ready to approve. Please review and approve the analysis card in your tray.
Grazing budget — need a mob. To run the grazing budget I need:
Once the analysis is approved and you tell me the mob and pasture type, I’ll run the grazing days budget straight away.
“Three photos taken at Arthur’s Acres at 9:15–9:19 am on 13 Sept 2026. Feed quality observation for grazing budget.”
I’ve dated this from the photo’s own clock, using the time zone the camera recorded — so this is the actual moment it was taken, wherever you were standing.
These photos look like a copy rather than the camera original — dragging from Photos often sends a small preview. Detail matters here: a canopy height read off a scale reference needs the full-size image, so the estimate will be less reliable.
Arthur’s Acres is carrying a lush mixed ryegrass/oats and white clover sward sitting at 10–15 cm across the three measurement spots, with a biomass estimate of 960–1,800 kg DM/ha. The clover is in full flower and the grass is starting to push into reproductive growth — it’s at the top of the quality window and the message is clear: graze it now, any longer and you’ll lose quality as the clover sets seed and the grass stems up.
What’s uncertain: The three spots showed meaningful variation — background grass in the first two frames looks taller than where the ruler was sitting, so the paddock isn’t uniform. The wide biomass range (960–1,800 kg DM/ha) is honest about that; treat it as a spread across the paddock, not a single reliable figure. There’s also a tall broadleaf plant with white/pink flowers above the canopy in frame 3 — possibly wild radish or capeweed, but it can’t be identified from the photo alone and is worth a walk to see how widespread it is.
Good context — with a Cibo Labs satellite reading of 3,000–4,000 kg DM/ha, that’s significantly higher than what the photos estimated.
Two readings, two different pictures:
These disagree substantially. The satellite reading integrates over the whole paddock; the photos were taken at specific spots which may be lower-cover areas. The agronomist noted the paddock wasn’t uniform. I’d weight the satellite figure for a whole-paddock budget but flag that the grazeable feed may be patchy. You know the paddock — which feels closer to right?
Got it — no mob in there yet, and it’s winter pasture (I’ll use temperate improved as the pasture type, which covers ryegrass/clover/fescue mixes).
The tool needs a mob with animals to calculate against — since there’s no mob in Arthur’s Acres yet, I need you to tell me a bit about what mob you’re planning to put in:
Great — I have everything I need. 40 Finishers (mostly heifers, avg ~448 kg, weighed 28 Aug), and Dam River paddock is Mullinroo Dam River Paddock.
Arthur’s Acres — Grazing Budget
Cover used: your Cibo Labs estimate — 3,000–4,000 kg DM/ha (operator-stated) · Paddock: 6.64 ha · Pasture type: Temperate improved (ryegrass/clover) · Mob: 40 Finishers · Avg weight: 448 kg (weighed 28 Aug)
Grazing days: 26 days (range: 19–33 days)
| Low end | Midpoint | High end | |
|---|---|---|---|
| Cover (kg DM/ha) | 3,000 | 3,500 | 4,000 |
| Available DM (kg) | 9,295 | 12,615 | 15,934 |
| Grazing days | 19.2 | 26 | 32.9 |
How it’s calculated:
Important caveats:
Bottom line: On the Cibo Labs figure, you’re looking at roughly 3.5–4 weeks of grazing for 40 Finishers — anywhere from 19 to 33 days depending on where in the cover range the paddock actually sits. Given the photo analysis read much lower in spots, I’d suggest a paddock walk before moving them in to confirm the bulk is there.
Two things I’d like to lock in — both cards are in your tray to approve:
Two things I can’t save as facts but will carry through this conversation:
I’ll use this on every question from anyone on the farm. You can remove it in Settings → AIffi’s memory.
I’ll use this on every question from anyone on the farm. You can remove it in Settings → AIffi’s memory.
In most farm software, a dashboard is furniture you have to assemble before it’s any use. You pick the charts, track down the right data, wire up the filters, get the date ranges right. It takes time and a certain amount of technical confidence — so on most farms it happens once, if at all.
The setup cost isn’t even the real problem. You have to know what you want to see before you have it. So you build for the questions you could anticipate, and the question you actually have on a Tuesday in July isn’t one of them. Changing the dashboard needs the same skill all over again, so nobody does, and it slowly drifts out of step with the business until no one quite trusts it.
AIffi does that work instead. Ask the question in your own words and it works out which records to read, what arithmetic to run, and what shape of answer fits — a trend over time, a breakdown by machine or mob, a single number. Then it draws it. No field-picking, no filter-building, no date ranges to fiddle with.
And the answers worth keeping, you keep. Save one and it becomes a report you can run again. Which turns the usual order on its head: rather than guessing up front what you’ll want to watch, your dashboard accumulates out of the questions that actually mattered.
Ask however the question comes out — there is no phrasing to learn and no list to memorise. AIffi works out which of your records to read and what to calculate. Changing things is deliberately narrower: a closed set of typed actions, each one shown to you before it runs. Below is a sample of both.
A great deal of what makes a farm run lives in somebody’s head and nowhere else — which gauge is the house one, which paddock floods after 40mm, who supplied that bull, what you actually mean by “the back block”. New software makes you re-explain all of it, every time.
AIffi has a memory. Tell it something once and it keeps it, so the next conversation starts from what it already knows rather than from scratch. The longer you use it, the less explaining you do — and the more of your operation it can reason about without being walked through it first.
Two rules keep that comfortable rather than creepy. AIffi asks before it remembers anything, so nothing is quietly inferred and filed away. And everything it has learned sits on one settings page where you can read it, correct it, or delete any of it. Your farm’s memory is yours to inspect.
The payoff is immediate as well as cumulative: once a fact is stored, a question that used to mean looking things up is simply answered.
Once approved, I’ll know that “My Fergie” refers to the Massey Ferguson MF S.125 whenever you mention it.
Let me look up the Massey Ferguson MF S.125 for you.
No engine-hour readings have been recorded against My Fergie yet — neither via fuel logs nor service events.
Hours are captured as a meter reading when you log fuel (“put X litres in My Fergie at 1,250 hours”) or record a service. Once you log one, I’ll be able to tell you the latest figure. Want to record a reading now?
I’ll resolve yesterday’s date and find the diesel fuel store at the same time.
Got everything I need. Nothing is recorded until you approve the card.
Plenty of products will tell you their AI is never wrong. We won’t, because no honest one can.
The guarantee we can make is architectural, not statistical: whatever AIffi gets wrong, it cannot quietly put into your records.
The best demonstration is your data, your paddock names, your questions.