AI on the farm — Daniel Cassese
daniel cassese
About Blog AI on the farm Templates Free tools Work with me

ai on the farm — the honest picture

Put AI to work on your farm — without losing the plot.

Most advice treats AI like a tool you need to get good at. On a farm it works better to think of it as help you hire — and like any hire, it's only as good as the farm you hand it.

Why it hasn't stuck ↓ skills · workers · agents ↓

sound familiar?

Why AI hasn't stuck on your farm.

If you've tried it and quietly gone back to the notebook, you're in the majority. It usually fails one of three ways — and none of them is your fault.

trap_01

The pocket chatbot

You ask a chatbot for advice and get someone else's farm back. Generic answers, confidently wrong about your beds, your flock, your market — because it knows nothing about them.

trap_02

The walled-in tool

One of your tools grows an AI button. But your farm lives in five places, so it can only see a sliver — it summarises the notes app while the answer sits in the spreadsheet.

trap_03

The unbriefed hire

You're told to "get better at prompting". But you wouldn't hand a new hire the keys with no walkthrough — and that's what AI without your standards, rules, and records is: willing, capable, completely unbriefed.

the pattern: it's not the AI — it's what the AI has to work with

the hidden rules

Your farm already runs on rules — they're just not written down.

You make a hundred calls like these on autopilot every morning. That's judgement — and it's exactly the kind of thing AI can follow, but only once it exists outside your head.

Writing your rules down is the first real step toward AI — and it makes the farm easier to run even if you stop right there.

if it's pushing 25° by nine, the tunnel gets watered first

when salad runs short, the restaurant gets shorted before the box scheme

skip paddock_09 after overnight rain

written down: nowhere

three ways to hire it

Skills, workers, agents — know which one you're hiring.

"AI" hides three very different kinds of help. Naming them keeps you from paying for an agent when a skill would do — and from expecting judgement out of a routine.

you trigger it

level_01 · skill

A recipe for one job

Written instructions the AI follows when you call on it — your voice, your format, your standards. You trigger it, you check it.

e.g. "turn this voice note into a clean harvest log entry"

start here — cheap to try, easy to fix

a trigger runs it

level_02 · worker

A routine that runs itself

A fixed sequence on a trigger — same steps, every time, no judgement. Something lands, the routine fires, the records update.

e.g. whiteboard photo at day's end → totals filed → pick list updated

it watches & decides

level_03 · agent

A hired hand with judgement

Watches, decides within the limits you set, and asks when it's unsure. The most powerful — and the most demanding of structure and trust.

e.g. frost in the forecast → sowings re-planned → changes flagged for your ok

Most farms should start with one skill and let trust build. Agents come last — they need the most structure underneath them, which is the point of everything below.

in use at bladrika — not a demo

I voice-log harvests from the field and photograph tray counts. A worker reads both, interprets them, and files kilos, bed, and crop into the right databases in my Farm OS — before I'm back at the wash station.

what that looks like in the records

voice note · 07:41 · "fourteen kilos salad off bed three"

harvests · bed_03 · salad mix · 14 kg · logged 07:42 ✓

why the system comes first

Everything on that ladder needs the same three things.

They happen to be the three parts of the trellis every Farm OS I build is shaped around.

posts · structure

The job, written down

Your areas, standards, and rules on paper — the briefing that turns a chatbot into a skill that works your way.

wires · connection

One connected place

So a worker can move information on its own — and see the whole farm, not the sliver one lone tool holds.

growth · records

Your farm's own story

Real records are the context that makes an agent's judgement yours — answers from your seasons, not the internet's.

AI is what climbs the trellis. Without the frame, it just sprawls.

That's why every build starts with the system, not the AI — it's the Trellis Framework, the same way I build every Farm OS. Curious where your farm stands? The farm check measures exactly these three parts.

from idea to daily habit

How AI actually lands on a farm.

Not a framework and a pat on the back. The same four moves, whether you build it yourself or we build it together.

01

Walk the workflow

Follow one job end to end — where information enters, where it gets re-typed, where it leaves. This is where the hidden rules surface.

most farms find half of it was never written down

02

Pick one clear win

For each step, one question: who should do this — you, the AI, or both? Choose the step where the rules are clear and the payoff shows within weeks.

one enterprise · one workflow · one win

03

Rebuild, don't bolt on

Reshape the step so AI can genuinely take part: rules written down, records structured, and a checkpoint where you approve before anything sticks.

the system gets better even before the AI does

04

Let it earn more

The first version is never the last. What starts as "it drafts, you approve" becomes "it handles, you spot-check" — one season of trust at a time.

trust is granted by results, not promised up front

asked straight, answered straight

What farmers ask about AI.

The rest belongs in a conversation — that's what the free discovery call is for.

No. The setup is the technical part, and it happens once. After that, using it looks like leaving a voice note or snapping a photo — if you can send a text from the field, you can run a skill.

Start there — a chatbot is a skill without a system, and it's genuinely useful for drafting and thinking out loud. But the ceiling comes fast: it can't see your beds, your records, or your numbers. The moment you're re-typing your farm's context into every conversation, you've hit the wall this page is about.

Sometimes, yes — like any new hire. That's why everything starts with a checkpoint: it drafts, you approve, and nothing touches your records without your ok. Autonomy is earned as it proves reliable, never granted on day one.

Your records live in your workspace, and the AI reads only what you point it at. Nothing is sold, and nothing trains someone else's model. Worth saying plainly: most AI models run in the cloud — if that's a hard line for you, say so, and we design around it.

Less than you'd guess. Most of it runs on tools you may already pay for; a skill costs cents per use, and even a busy worker is coffee money per month. The real investment is the setup — which is why you start with one clear win, not twelve.

ready when you are

Want a farm AI can actually work on?

I build the system and the help that runs on it — with you, on your operation, starting with a free discovery call.

Work with me or start with the templates →
daniel cassese
Home About Blog Work with me Templates Free tools Farm check
beyond spreadsheets · © 2026