Walk into any working farm office on a Wednesday afternoon. Open the laptop. The accounting is in one app. The spray diary is in another, the one the agronomist insists on using. The treatment records sit as PDFs in an email thread with the vet. The workforce and induction paperwork is in a Google Drive folder. The bank statements are in the accounting software but the lender's covenant report is a Word document. The compliance pack for next quarter is going to be assembled from all of the above, on Thursday night, after dinner.
The most common observation we hear, talking to operators, isn't that any single one of these tools is bad. They're often individually excellent. It's that the agronomist's records and the farm's records aren't the same records. The agronomist's spray recommendation lives in their world, the farmer's spray application lives in another, and the reconciliation between the two happens by phone call, by best-effort, sometimes weeks after the spray has gone on.
This isn't a story about replacing the agronomist. It's a story about removing the spreadsheet between the agronomist and the farmer so the conversation gets faster, the records align by default, and the advice you're paying for is the advice that actually gets executed and audited.
The shape of the split-data problem
For most Australian and international farms, the agronomist is a separate professional running separate software. The most common setup looks like this:
- The agronomist uses a crop-management or planning tool — Agworld, Climate FieldView, MyJohnDeere, a regional product, or in some cases a personal spreadsheet system. Soil tests come in as PDFs. Recommendations go out as PDFs. Prescription maps export to USB or get emailed to the farmer.
- The farmer uses a farm management tool — something for livestock, something for the financials, often something else for compliance. The spray rig has its own controller. The mob assignments live on a whiteboard in the shed.
- The bridge between them is the agronomist's prescription, the phone call, the email, the visit, the verbal “I've sent it through, just look in your inbox.”
The two record sets are similar, never the same. The agronomist's recommendation says one rate; the operator applies a different rate because the boom's calibration drifted; the financial cost of the application gets entered into accounting separately from the spray diary; the compliance pack at quarter end is reconciled from three places.
The cost isn't theoretical. It's measurable in five places:
- The reconciliation tax. Every record kept in two systems is a record that has to be reconciled when it disagrees with itself.
- The prescription compliance gap. The agronomist doesn't actually know whether their recommendation was followed unless they ask, because the recommendation lives in their app and the application lives in the farmer's.
- The season-over-season blind spot. Variable-rate decisions for next season require last season's per-paddock cost and yield, in one place, reconcilable. If that data lives in three tools that don't share identifiers, the analysis is half-done before it starts.
- The audit drift. When the buyer or the auditor asks for “the spray history for the third quarter,” the answer assembled from three sources rarely fully agrees. The version that wins is whichever was re-keyed most recently.
- The phone-call overhead. The agronomist and the farmer end up spending the relationship's time on data-reconciliation instead of agronomy.
What “same data” actually means
It's not enough to say “we integrate with [the farmer's app].” Integration is the marketing word for “we send a daily CSV and you can mostly trust it.” Integration means two systems that talk; same data means one system that both parties read.
Concretely, “the agronomist's data is the same data as the farm app” should mean five things:
- One identity for every paddock, block, mob, animal, batch and load. The agronomist sees the same paddock identifier the farmer does. The same as the spray-rig controller. The same as the accounting software.
- One register for every input, treatment, recommendation and outcome. When the agronomist prescribes a spray, that prescription becomes the open task in the farmer's workforce queue. When the farmer applies the spray, the application closes against the same prescription record. The reconciliation between “what was prescribed” and “what was done” is automatic.
- One historical record per plot. Three seasons of yield, input cost, weather, soil-test results and treatment history attached to the paddock, queryable by the agronomist as easily as the farmer.
- One audit trail. Every recommendation made by the agronomist, every application made by the farmer, every change made by either, signed and timestamped. The buyer's audit, the regulator's audit and the agronomist's prescription audit all read the same ledger.
- One way in. The agronomist invited as a scoped, read-mostly user in the same tenant the farmer runs on. Not a parallel account. Not a federated identity. The same tenant.
What this unlocks for the agronomist
The agronomist's job has always been to combine three things: an understanding of agronomy, a relationship with the operator, and a read of the operation's actual data. The third part is the part that's been hardest, because the data has lived everywhere and nowhere.
In a unified setup, the agronomist gets:
- A multi-client portfolio dashboard. Every client farm in one view. Crop health, soil-sensor readings, satellite passes, season-over-season deltas, all surfaced per farm with a one-click switch between them. The agronomist running fifteen clients stops keeping fifteen sets of bookmarks and fifteen inboxes.
- Soil test ingestion that goes somewhere useful. Drop a lab PDF onto the platform; it overlays on the right paddock; the fertiliser dose engine surfaces a recommendation with assumptions visible. The agronomist's job becomes validating or overriding the recommendation — not transcribing the test results into a spreadsheet.
- Prescription sign-off with the audit trail attached. Send a prescription; sign with the agronomist's registration; the farmer sees it in their task queue with the agronomist's name on it; when it's applied, the application closes against the same record. If the buyer or the regulator ever wants to see who advised what and when, the trail is right there.
- Existing GIS data preserved. GeoJSON, KML or shapefile bundles from John Deere Operations Center, Climate FieldView, Trimble Ag, Google Earth or your own surveys — imported clean, paddock by paddock. The agronomist's existing investment in mapping carries across.
- Season-over-season AI delta reports. Paddock-by-paddock ROI analysis, written in agronomist-voice, ready as a starting point for the next conversation with the farmer.
The agronomist's intellectual product — the recommendation — is unchanged. What changes is the friction around delivering it and verifying it.
What this unlocks for the farmer
For the farmer, the picture is simpler. The records you keep to run the farm are the records the agronomist reads. The records the agronomist creates are the records that satisfy the buyer's audit. The advice you're paying for is the advice that actually executes and gets logged, not the advice that lives in an email.
Two specific wins:
- Prescription compliance verification stops being a phone call. The agronomist can see whether the spray was applied at the right rate, on the right paddock, within the right window — because the application record is right next to the prescription record, in the same view.
- Season-end review becomes a conversation, not a data-gathering exercise. When the agronomist sits down with you at the end of the season, the question isn't “let me try to reconstruct what happened.” It's “here's what happened; what do we do differently next year?”
What this is not
This is the section sales pages usually skip. Worth being explicit.
It is not replacing the agronomist. The recommendation still requires expertise the platform doesn't have. The relationship still depends on trust the platform can't manufacture. The judgement call about whether to spray today or wait three days is still the agronomist's, not the algorithm's.
It is not eliminating the agronomist's tools. The agronomist with deep workflows in Climate FieldView, Agworld or any other product doesn't have to abandon them — but the farm's record of what was prescribed and what was applied lives in the farm's ledger, and the agronomist can read it from theirs or from a shared workspace, depending on the setup.
It is not free of effort. The agronomist still has to invite clients (or accept invitations), bring across their existing GIS data, learn the workflow. The benefit compounds over time as the records build up; the first month is the awkward one.
It is not a substitute for the relationship. The faster you can have the conversation, the more relationship time you get. That's the win — not “the platform replaced the call,” but “the platform made the call about agronomy instead of about data.”
How to actually start
If you're an agronomist:
- Talk to one of your client farmers about it. Pick the one who's most fed up with re-keying records. Get them to invite you, or invite them, into a platform that supports the shared-tenant model.
- Bring across one of your existing GIS datasets first. See how the import looks. You'll know in twenty minutes whether the platform's actually built for the agronomist workflow or just claims to be.
- Spend a season running parallel — your existing tools and the shared tenant — on one or two client farms. Don't migrate all of them in one go. The platform earns its place over a season, not a demo.
If you're a farmer:
- Ask your agronomist what they actually use. If the answer is “their own tool, then they email me the prescription as a PDF,” the gap between your records and theirs is the bottleneck you can close.
- Try inviting them as a scoped user into your farm management platform. They keep their tools; you give them read access to your operating data. Most agronomists, once they see what the farm actually has in real time, never want to go back to PDFs.
The kicker
The platform's job is to remove the spreadsheet, not replace the agronomist. The relationship still matters. The judgement still matters. The recommendation still carries the agronomist's name and registration.
What changes is the friction. Less phone, more agronomy. Less reconciliation, more advice. Less “let me check three apps and call you back,” more “I'm looking at the same screen you are.” The records align by default; the conversation gets faster; the agronomist's product gets executed more reliably; the farmer pays for advice instead of for data-shuffling.
The shape of the problem has been the same for thirty years. The shape of the solution finally isn't theoretical.
— The RedEarthOne team
RedEarthOne is the operating system for agriculture — one account, one ledger, five connected workspaces plus stakeholder portals, designed against the regulators and the buyer programmes from day one.