The idea

Stop hunting for the right screen

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.

Try it

Ask a demo farm

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.

New — live now

Say it, rather than thumb it in

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.

It puts the words in the box. It does not send them.

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.

It listens for your names, not just English

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.

It will still get names wrong. So it offers, and waits.

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.

The recording is used once and dropped

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.

What we measured, and what it is worth We recorded a set of real instructions on our own farm and ran them three ways. The phone’s own free recogniser got 39% of this farm’s names. A paid speech service, cold, got 57%. The same service, told the farm’s own names to expect, got 87%. That last arm is what ships. The finding underneath it is the one worth stating plainly: knowing your farm’s vocabulary matters more than which engine does the listening.
Two honest limits on that 87% It was measured against our stored names — which is the point of the design and also the boundary of the test, because a name AIffi has never been given is a name it cannot expect to hear. And it is only as right as your records are: one of our products is misspelt in the database, and the recogniser dutifully returned the misspelling, scoring a hit where plain English had scored a miss. We would rather you knew that than quoted the number at you.
A real exchange

Ordering and spreading urea

This is an actual conversation from Mullinroo Estate, lightly trimmed for length. Nothing has been added, and the numbers are the platform’s own.

Farmer
How much Urea do I have?
AIffi

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?

Farmer
I want Dave to spread Urea on the Crop Paddock in the next few days, 200kg / ha. I think we need to order some from Farmers Warehouse.
AIffi

Let me look up the Crop Paddock and the Urea product details at the same time.

Here’s the picture:

  • Required: 200 kg/ha × 3.74 ha = 748 kg
  • On hand: 166 kg
  • Shortfall: ~582 kg — you’ll need to order at least that much from Farmers Warehouse

Let me set up the job for Dave and the planned spread operation.

Review this change — new job
Spread Urea on Crop Paddock
DaySun, 16 Aug 2026
WhoDave Whelan
NoteApply Green Urea NV® at 200 kg/ha on Crop Paddock (3.74 ha = ~748 kg total). Need to order ~582 kg from Farmers Warehouse first — on hand is only 166 kg.
Approve Decline
Review this change — planned spread
Plan spread on Crop Paddock
ProductGreen Urea NV® — 200 kg/ha
Area3.74 ha
Date16 Aug 2026
StatusPlanned — not yet applied
Approve Decline
Farmer
The Urea will be delivered on Monday so we need to delay Dave’s job until Tuesday. I ordered 1000kg.
AIffi

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?

Review this change — reschedule
Spread Urea on Crop Paddock
DaySun, 16 Aug 2026 → Tue, 18 Aug 2026
Approve Decline
Review this change — stock movement
Green Urea NV® delivery
Stock in1,000 kg (purchase)
SupplierFarmers Warehouse
WhenMon, 17 Aug 2026
Approve Decline
What just happened Six records were created or changed across three different parts of the platform — inventory, the work queue, and planned field operations — from four sentences of ordinary English. AIffi looked up the paddock’s real area, did the arithmetic against real stock on hand, assigned work to a real person, and then handled a compound instruction that rescheduled one thing while recording another. Every single write was shown as a card first.

It asks rather than guesses

Later in the same conversation, the farmer asked for a second job to be created and assigned to himself.

Farmer
Yes — assign it to me.
AIffi

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?

Why this matters more than it looks A system optimised to seem helpful would have guessed — picked the account holder, or invented a plausible name, and produced a record that looked right and was wrong. AIffi is built so that a proposal cannot be drafted until every required detail is resolved. It would rather ask you a slightly annoying question than write a confident piece of fiction into your farm records.
A real exchange

Three days of irrigation, logged in one message

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.

Farmer
We watered Crop Run 4 on Wednesday, Run 3 on Thursday and Run 2 on Friday 7am and 1 on Friday 4pm. The soil moisture was 17% in every case and the speed was 30m/hr. can you do these logs as completed please
AIffi

Runs 1, 3, and 4 resolved cleanly. However, Crop Run 2 is ambiguous — there are two matches on the Monsoon - Irriland:

  • Crop Run 2 (155.6 m)
  • Crop run 2 A (157.3 m)

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:

RunDayStartRuntimeWaterDepthFuel
Crop Run 4Wed 16 Sep6:26 am4h 31m163,984 L18.9 mm27.1 L
Crop Run 3Thu 17 Sep6:26 am5h 38m204,707 L18.9 mm33.8 L
Crop Run 1Fri 18 Sep4:00 pm5h 8m186,890 L18.9 mm30.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.

Review this change
Log irrigation on Crop Run 4
RunCrop Run 4
PaddockCrop paddock
Starts16 Sept 2026, 6:26 am
StatusCompleted (finish is in the past)
Runtime4.51 h (4 h 31 min) (planned)
Speed30 m/h
Length135 m
Nozzle pressure4 bar
Start moisture17%
Water163,984 L
Depth on the lane18.9 mm
Fuel27.1 L

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.

Recorded
Log irrigation on Crop Run 3
Thu 17 Sep, 6:26 am · 5 h 38 min · 204,707 L · 18.9 mm · 33.8 L fuel
Recorded
Log irrigation on Crop Run 1
Fri 18 Sep, 4:00 pm · 5 h 8 min · 186,890 L · 18.9 mm · 30.8 L fuel
Recorded
Farmer
Crop Run 2 not 2A
AIffi

Got it — Crop Run 2 (155.6 m). Logging it now at Friday 7am.

RunDayStartRuntimeWaterDepthFuel
Crop Run 2Fri 18 Sep7:00 am5h 11m188,708 L18.9 mm31.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!

Log irrigation on Crop Run 2
Fri 18 Sep, 7:00 am · 5 h 11 min · 188,708 L · 18.9 mm · 31.1 L fuel
Recorded
The Alffi irrigation calendar for 14 to 20 September 2026, week view by hour, filtered to the Monsoon - Irriland and showing completed logs: Dam Run 13 on Monday and Tuesday, Crop Run 4 on Wednesday at 6:26 am, Crop Run 3 on Thursday at 6:26 am, and on Friday Crop Run 2 at 7:00 am and Crop Run 1 at 4:00 pm.
Afterwards, on the irrigation calendar. The four logs from that conversation sit on Wednesday, Thursday and Friday as completed, each block as long as its runtime. The two Dam Run 13 logs on Monday and Tuesday were already there.
What the farmer didn’t have to do Two messages, four logs, and nothing written until each card was approved. Along the way AIffi:
  • found each run by name on the right irrigator — and where one name matched two runs, asked rather than picked;
  • took each run’s length, and the flow from the 4 bar row of the irrigator’s own chart (606 L/min);
  • worked out the runtime from length and speed, then the water, the depth on the lane and the fuel, run by run;
  • noticed every run already had logs, and said plainly that these would be added, not swapped in.
The alternative is the log form, four times over. Here it was one sentence and one correction.
A real exchange

From three paddock photos to a grazing budget

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.

Farmer
can you do a pasture observation, feed quality, grazing budget
Photo 1, 9:15 am: ryegrass and flowering white clover around the Alffi pasture ruler, with the photographer's shadow and hills behind. Photo 2, 9:17 am: the pasture ruler half hidden in ryegrass and flowering white clover. Photo 3, 9:19 am: the pasture ruler leaning in a ryegrass sward, with a tall white-flowered broadleaf plant and purple-flowered vetch above the canopy.
AIffi

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:

  • Which mob is actually grazing Arthur’s Acres?
  • What’s the pasture type? (e.g. temperate improved, subtropical, native, winter cereal) — this is required for the budget calculation.

Once the analysis is approved and you tell me the mob and pasture type, I’ll run the grazing days budget straight away.

Review this change
Record and analyse this pasture photo
PaddockArthur’s Acres
Observed13 Sept 2026, 9:15 am (from the photo’s clock)
ObservationFeed quality
Photos3 photos
Reportcomposition, condition, pest pressure, grazing readiness, recommendations
Costup to $0.22, charged on what it actually uses

“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.

Analysed — Ryegrass / oats, reproductive, graze now · 960–1,800 kg DM/ha
AIffi · the pasture report

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.

Farmer
Cibo labs satelite has it at 3000-4000 DM/ha
AIffi

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:

  • Photos (agronomist AI): 960–1,800 kg DM/ha
  • Cibo Labs satellite: 3,000–4,000 kg DM/ha

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?

Farmer
no mob at the moment, its winter pasture
AIffi

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:

  • How many head?
  • What class? (e.g. growing steers/heifers, dry cows, bulls)
  • Approximate liveweight? (kg per head)
Farmer
we will put the finishers in there after they leave the Dam River Paddock
AIffi

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 endMidpointHigh end
Cover (kg DM/ha)3,0003,5004,000
Available DM (kg)9,29512,61515,934
Grazing days19.22632.9

How it’s calculated:

  • Residual left: 1,600 kg DM/ha (intake floor — PROGRAZE growing class)
  • Daily demand: 404 kg DM/day (40 head × 10.1 kg/head) + 20% wastage = 485 kg DM/day
  • Growth rate assumed: zero (spring growth would extend this — worth adding if you have a PGR estimate)

Important caveats:

  • Cover disagreement. Cibo Labs satellite (today): 3,000–4,000 kg DM/ha, used for this budget. Photo analysis (today, 09:15 am): 960–1,800 kg DM/ha. Earlier photo reads on this paddock: 3 Sep ranged from 400–4,000 across four separate observations, suggesting significant within-paddock variability. A walk with the pasture ruler across multiple points would help you judge which is closer.
  • Near By Finishers mob is recorded in Arthur’s Acres with 0 head — I’ve excluded them from the budget, but if any animals are actually there, the days figure is overstated.
  • Weights are 16 days old — the Finishers were last weighed 28 Aug. If they’ve gained since, intake demand is slightly higher.
  • No pasture growth rate applied — if you know the PGR (kg DM/ha/day), I can re-run the budget with it — it could add several days.

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.

Farmer
can you learn from this?
AIffi

Two things I’d like to lock in — both cards are in your tray to approve:

  • Arthur’s Acres pasture type — temperate improved (ryegrass/clover/oats), winter pasture. Next time someone asks for a grazing budget on that paddock, I won’t need to ask.
  • Cibo Labs as the preferred cover source — when you give me a Cibo Labs satellite figure, I’ll use it over the photo analysis for the budget. I’ll still flag any big disagreement between the two, but won’t hold up the calculation asking which to use.

Two things I can’t save as facts but will carry through this conversation:

  • Finishers mob — 40 head, ~448 kg, going into Arthur’s Acres after they leave Dam River
  • Arthur’s Acres — 6.64 ha, Near By Finishers mob currently showing 0 head (effectively empty)
Review this change
Remember: Arthur’s Acres pasture type
SubjectArthur’s Acres pasture type
FactArthur’s Acres is winter pasture (temperate improved — ryegrass/clover/oats mix)
Shared witheveryone on the farm

I’ll use this on every question from anyone on the farm. You can remove it in Settings → AIffi’s memory.

Approve & apply Decline
Review this change
Remember: Cibo Labs satellite for pasture cover
SubjectCibo Labs satellite for pasture cover
FactWhen the operator states a Cibo Labs satellite reading, use that as the cover figure for grazing budgets in preference to the photo analysis
Shared witheveryone on the farm

I’ll use this on every question from anyone on the farm. You can remove it in Settings → AIffi’s memory.

Approve & apply Decline
What to notice
  • It didn’t pick between two numbers that disagreed. It showed both, said why they might differ, used the farmer’s, and labelled it the farmer’s.
  • Every figure has a source. The residual is the PROGRAZE intake floor, named, and the arithmetic is on the page to check.
  • It said what it didn’t know — weights sixteen days old, no growth rate, a mob recorded with no animals in it.
  • Asked to learn, it proposed two facts and waited for approval, and was plain about the two things it couldn’t keep.
Cibo Labs is a separate satellite service. AIffi doesn’t connect to it — the farmer read the figure off it and typed it in.
Analytics

You don’t build the dashboard. You ask for it.

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.

The chart on the Platform page is one of these The finishers’ average daily gain across six weigh sessions, drawn against the farm’s own target — nobody configured it, chose its axes or set its date range. Somebody asked how the mob was doing. That is the whole of the effort involved.

What you can ask it

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.

Questions it answers

  • “How much diesel did the pump burn last week?” Consumption across any asset and any period, with a chart if it helps.
  • “Is this paddock safe to graze yet?” Withholding periods checked against everything actually sprayed on it.
  • “How many days will Dam River carry the Finishers?” Days of feed as a midpoint with its range, from the mobs actually in the paddock — every figure cited to its source.
  • “How heavy is this heifer?” Send a photo and get an estimated liveweight. Record it and it’s kept apart from scale weights.
  • “What does the web say about…?” With sources, labelled general information, and unable to change your records. A farm switches it on.
  • “Where is the weaner mob?” Current location from movement history, not from a stale field someone forgot to update.
  • “What did that crop cost me per hectare?” Input costs, dollars per hectare and per tonne, gross margin.
  • “What’s the tank mix order for these three products?” Mixing sequence worked out from each product’s formulation type.

Work it records

  • Livestock events Births, weights, treatments, mob moves, sales and dispositions.
  • Consignments Prepare, complete, sign and submit a National Vendor Declaration, then attach the tags once the truck arrives.
  • Field operations Spraying, spreading, sowing and harvest — drawing product from stock at the rate you applied.
  • Running costs Fuel, deliveries, servicing, registrations, parts and input purchases against the right asset.
  • Jobs Create, assign, reschedule, complete or dismiss work for anyone on the team, add a note, book equipment or ask for a resource.
  • “Lay out 20 m lanes in Dam River Paddock from Monday” Every lane from the paddock’s real boundary, on one card, in one approval. Then “close today’s lane — grazed to about 5 cm”.
  • Pasture readings Photos of a paddock — drop, paste, or pick several at once from the phone — on one card, analysed and filed against the paddock.
Memory

It gets to know your farm

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.

Farmer
remember My Fergie is Massey Ferguson MF S.125
AIffi

Once approved, I’ll know that “My Fergie” refers to the Massey Ferguson MF S.125 whenever you mention it.

Review this change — remember a fact
Remember: My Fergie
SubjectMy Fergie
FactMy Fergie is Massey Ferguson MF S.125
SharedEveryone on the farm
RemoveSettings → AIffi’s memory
Approve Decline
Farmer
how many hours on my fergie
AIffi

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?

Farmer
I filled fergie yesterday and the hours where 946, she took 184 lt of deisel
AIffi

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.

Review this change — fuel record
Massey Ferguson MF S.125
Fuel184 L Diesel (consumption)
Hours946 h
WhenYesterday — 30 Aug 2026
Approve Decline
Look at that third message again It was typed exactly as you see it — “fergie” in lower case, “where” for “were”, “lt” for litres, “deisel” spelled the way most of us spell it at the end of a long day. AIffi worked out the machine from a nickname it had been taught minutes earlier, resolved “yesterday” to a real date on the farm’s clock, found the diesel store, read 946 as an engine-hour reading and 184 as litres, and put the whole thing on a card to be checked. Farm software usually demands you meet it halfway. This is the other way round.
Being straight about AI

What we don’t claim

Plenty of products will tell you their AI is never wrong. We won’t, because no honest one can.

What we do guarantee

  • The model cannot write to your data — only propose
  • Every change is shown to you before it happens
  • Approved changes are applied by tested, deterministic code
  • It runs under your own permissions, so it can never reach data you couldn’t
  • A proposal can’t be drafted with details missing
  • Tested, not just asserted — a read-only account is refused at both approval and execution, and the change never leaves “proposed”

What we don’t

  • That every sentence it writes is correct. Language models get things wrong, and we measure ours rather than pretend otherwise.
  • That you should approve a card without reading it. The card exists precisely because you are the check.
  • That it replaces your judgement on anything that matters — agronomy, animal health, or compliance.

The guarantee we can make is architectural, not statistical: whatever AIffi gets wrong, it cannot quietly put into your records.

See it against your own farm

The best demonstration is your data, your paddock names, your questions.