I farm corn and soybeans with my family and a crew of employees, and I train farmers on precision ag. Like most farms, our busy season ran on texts, ticket photos, and a workbook that was always a few days behind. I didn't set out to build an app. I set out to stop retyping scale tickets at night. Here's how it grew.
The first piece was GrainGrok, working over our farm's Google Voice texts. The crew kept doing what they already did: they texted photos of elevator tickets and grain cart weights from the truck or the cab.
GrainGrok read those photos and logged them in my grain workbook. It matched ticket numbers so a load never got written down twice. It split a ticket by owner when a load belonged to more than one, and it kept the bin flow straight: what went in, what came out, and what was left.
That alone took a nightly chore off my plate, and the numbers were better because nobody was copying them by hand.

Once grain was working, the shop was the obvious next step. ShopGrok keeps the maintenance and service intervals, the fuel log, and parts. Then came daily service checklists: each machine gets its own list, like the combine or the grain cart, and each morning ShopGrok posts the day's lists for the crew to check off as they go.

Texts got us started, but the farm needed one place to look. In October it became an app on the phone and the desktop:
The app replaced texting for the crew. The same ticket photos and notes now go into Crew Chat and Tell the bot instead of a text thread, and the owner reviews them in one Inbox.
It's built around how my operation runs. That's the point: yours runs differently, and it should be built around yours.

These are next on my list. They are plans, not finished features.
A driver posts the scale ticket photo, or types a quick note right from their phone.
GrainGrok or ShopGrok reads it, checks for mistakes like a duplicate ticket or a missing detail, and asks if something doesn't add up.
Notes wait in the Inbox under For you. One tap to approve, ask a question, or mark it not used. The crew sees it move: Sent, Received, Approved, Logged.
Harvest, bins, and shop numbers stay current, on the phone or at the desk.
Screenshots show the Doe Family Farms demo. All names, fields, and numbers are fictional. In the demo, the bots' replies are simulated so you can click through it.


One scroll of section cards with harvest, bins, contracts, shop, and spray at a glance. Jump chips take you straight to a section.


Acres cut, dry bushels, yield, and moisture by crop and field, pulled together from the combine data and the scale tickets.


What's in every bin, how full it is, and who owns what, rebuilt from the tickets as loads come in.


Each machine has its own daily checklist, grouped by season: Harvest, Planting, and Spraying. Switch on the ones you need, edit the tasks, and they post to Crew Chat at 7 AM.


The crew ticks items off as they work. Anyone can add a task or skip one for today, and everyone sees who did what and when.


A driver snaps the scale ticket in Crew Chat. GrainGrok reads it and logs the load to the right field and bin.


Crew notes that need the owner show up under For you. Open one and tap Approve, Ask a question, or Not used. Approving hands it to the bot to log.


Pick "Do this" for a job ("add a grease task to the combine list") or "Ask" for a question, choose GrainGrok or ShopGrok, and the reply shows up in My requests.





People approve and the bot logs. Nothing gets recorded without a person signing off. You decide who sees what, and your crew sees only what they need.
Off the table, by design:

A session online or in person, one-on-one or with a group.
If you'd rather have a hand, I can help you set it up.
It runs on Grok, in your account, with your data.
“I built mine. Let me teach you how to build yours.”
I'll walk you through the Doe Family Farms demo in a one-hour session, and we can talk through what yours could look like.
Email jeffyoung.yfi@gmail.com for a 1-hour demo invite