Most farm management software demos go the same way. A slick UI tour. Four claims you don't have time to verify on the call. A question about your operation that turns into a twenty-minute sales pitch. A follow-up email asking when you're ready to sign. Most operators end up choosing a platform for reasons that have very little to do with whether the platform actually fits — schedule pressure, the agronomist's nudge, the sunk-cost feeling from the third demo this month, the fact that the salesperson was the friendliest.
This is a different kind of checklist. Ten questions you can take to any farm management software demo — including ours — that separate platforms that fit a working farm from platforms that are marketed to look like they do. Each question has a specific evidence test: what to ask, what answer to listen for, what the answer reveals about the platform underneath the demo.
The framework is deliberately neutral. We've written it to fail any platform that can't back up its claims — and that includes us, on the days where a particular module isn't ready. Use it on your shortlist. If a platform you're seriously considering can't pass most of these on a live demo, it's not the right platform yet, regardless of how good the marketing site looks.
The ten questions
1. What does one entry do?
This is the unified-platform test, and it's the single most useful question in farm software evaluation.
Ask the demo presenter to enter a single spray application — chemical, paddock, rate, operator, conditions — on the live platform. Then ask them to show you every place that entry appears. Listen for:
- the spray diary (table-stakes)
- the audit pack (does the regulator's evidence pack update?)
- the withholding-period calendar (does the next harvest window adjust?)
- the paddock-level P&L (does the chemical cost attribute to the right block?)
- the worker's timesheet (is the operator's hours record updated?)
- the lender's covenant view (is the treatment register populated?)
- the buyer's chain-of-custody log (is the consignment provenance updated?)
- the agronomist's prescription audit trail (is the spray reconciled against the recommendation?)
One spray entry, captured once, should appear in five to seven places on the live demo, in real time. If the answer involves a nightly sync, a CSV export, a webhook, or “that's a roadmap item,” the platform is stitched, not unified. The difference between the two compounds — every gluing point is a place your records will quietly disagree with themselves over time.
2. Can the mobile app work with no signal, no GPS lock, and a flat battery?
The demo platform should be able to demonstrate this directly. Ask the presenter to put the laptop on airplane mode, capture a spray entry, a mob movement, a weight, and a safety check on the phone, then bring the laptop back online and watch the records appear without losing anything.
If “offline mode” is a sync queue that drops entries when the queue overflows, the platform isn't field-first. If the demo presenter can't demonstrate this on the call — or has to schedule a separate call to show you — that's a strong tell. Working farms don't have signal in half the places work happens; if the mobile experience isn't built for that, the office is going to keep being the place data is typed in.
3. Where does worker safety live?
If the answer is “in a separate HR module” or “we integrate with [HR product]”, the platform doesn't treat safety as core.
Ask specifically: when a spray rig fires up, does the platform know who's driving it, whether they hold the chemical-handling certification, whether they're inside their hours-of-work limit, and what to log if something goes wrong? That should be one question with one answer, not five integrations. WHS / OHS / OSHA isn't a bolt-on. The records that prove safety compliance are the same records that prove labour-standards compliance and the same records that drive the geofenced timesheet — if any of those are in a separate system, you'll be keeping the same data three times.
4. What buyer-mandated programmes does it cover, by name?
Regulator compliance — Fair Work, APVMA, USDA, EPA, OSHA, NLIS, LPA — is table stakes. Every credible platform claims it. The harder question is buyer-mandated programmes: the contractual attestations your processor, exporter, retailer or buying program now requires before they'll take your produce.
Ask the demo to enumerate the programmes they cover for your specific operation type by name. For livestock: LPA, PCAS, MSA, BQA, USDA PVP, NAIT, NZFAP. For cropping: GTrace, vendor declarations, sustainable-sourcing programmes. For cotton: BCI, myBMP. For horticulture: Freshcare, HARPS, SQF, GlobalG.A.P. For wine: Sustainable Winegrowing Australia. For coffee: Rainforest Alliance, Fairtrade, 4C. For aquaculture: BAP, ASC, MSC. Cross-industry: Climate Active, Modern Slavery Act, EUDR.
Generic answers (“we cover all major schemes”) mean they don't. Specific answers with current programme names and a demonstration of where the evidence comes from mean they do.
5. Can my bank read the platform directly?
Or: my agronomist, my buyer, my processor.
The answer is either “yes — we invite them as a scoped read-only user in the same workspace” or “we generate a PDF report you can email them.” The second answer means you are still the bottleneck for every audit, every covenant review, every quality bid, every prescription. The first means audit fatigue collapses — the operator's lender can be looking at live debt-service coverage; the operator's buyer can be looking at live lot quality; the operator's agronomist can be writing prescriptions against the actual paddock condition. None of this is theoretical; the technology to do it has been around for a decade. Platforms that haven't built it have chosen not to.
6. What writes the audit pack?
If the audit pack is assembled from data exports each quarter, it isn't real-time and it isn't trustworthy in the buyer's eyes. If the audit pack is a query against the live ledger — Merkle-rooted so the chain of custody is provable, append-only so retro-edits leave an audit trail, scoped so the buyer sees only what they're meant to see — it's audit-grade.
The shorthand: ask “if I capture a record right now, when does it appear in next month's audit pack?” The right answer is “immediately — the audit pack reads from the same ledger as the record you just captured.” The wrong answer is “the audit pack is generated at the end of the period from a data warehouse copy.”
7. What happens when my buyer adds a new attestation requirement next season?
This is the question that exposes whether the platform is built for a moving target.
Every year, every major buyer and certifying body adds new line items to their attestation. Carbon baseline last year. Deforestation-free this year. Modern Slavery Act statements the year before. Five years from now there will be three new ones nobody is publicly talking about yet.
If you have to rebuild your records to satisfy the new requirement, the platform is fragile. If the platform's vendor toggles on a new template and the trail is already there in the records you've been keeping, the platform is genuinely unified and you're insulated from the moving target. Ask for a specific example: what new attestation requirement landed on the platform's customers in the last twelve months, and what did those customers have to do?
8. What is your pricing?
If pricing is published on the website, with tier features enumerated and a clear “contact us” only for genuinely complex enterprise deployments, you're dealing with a transparent platform. If pricing is “contact us” only for everyone, you're entering a sales cycle where the price scales with how much you appear to need the tool, how big your turnover is, and how aggressive your procurement is.
The difference matters particularly for SMEs and family operations. A platform whose pricing is genuinely scaled to operation size and modules turned on is one you can budget against; a platform that won't quote until you've sat through three demo calls is one whose price is mostly negotiation and not mostly value.
9. What happens when I leave?
Can you export every record you've ever entered, in a machine-readable format you can open without paying anyone? Is your data deleted on cancellation, or held for a defined window? Who owns the data while you're a customer? Who owns it after?
This isn't paranoia. Every platform you ever leave becomes a data-recovery problem if you didn't think about exit before entry. The right answers are: full export, in a standard format, on demand, at any time — and ownership of the data sits with the operator, not the vendor. The wrong answer is anything that involves a fee for export, a tier-locked export, or a phrase like “our records are proprietary.”
10. What did the team ship in the last ninety days?
Roadmaps are easy to write. Shipping is hard.
A platform with a visible, dated, public log of what's actually been delivered in the last quarter is meaningfully more trustworthy than one whose product page hasn't changed in two years. Ask them. Or look at their public updates page. A team that ships every month — even small things — is a team that has a working development cycle. A team that hasn't shipped in six months is a team you'll be waiting on for the feature you need.
This isn't about chasing the platform with the highest velocity. It's about avoiding the platform that's stopped moving.
Five red flags
- “All-in-one” or “unified” without a live demo of one entry appearing in multiple places. Most platforms claim unified; few can demonstrate it on the call.
- “Coming soon” features that appear on the marketing site but not in the actual demo build. If you can't see it working, assume it isn't.
- Pricing not published, particularly when the salesperson asks about your turnover before quoting. A platform whose price is mostly a function of your turnover and not its capabilities is a platform that's harder to budget for than it should be.
- Bank, buyer, lender or agronomist described as “integration partners” rather than first-class workspaces. “Integration” is the marketing word for “they pay separately and the connection might work and you're the one chasing it when it doesn't.”
- A roadmap that's longer than the changelog. Companies that promise a lot but ship a little tend to keep promising a lot and shipping a little.
Five green flags
- The demo team is willing to capture a record live, on the call, and show you every system it touched in real time.
- The mobile app demo runs on airplane mode without preparation.
- A public updates page with dated entries, including features that didn't ship as planned and what changed.
- Pricing published, tier features enumerated, and a clear “contact us” only for genuinely complex deployments.
- A founder-shaped human on the demo call, willing to answer hard questions about what the platform doesn't do.
The questions you don't need to ask
A counter-intuitive section, because most evaluation guides ask the wrong things.
- “Is it secure?” Every serious platform claims security. Better questions: where is my data hosted, what's the data-residency story, who at your end has access to customer records?
- “Is it customisable?” “Customisable” is the marketing word for “we'll bill you separately for it.” Better question: what fields and workflows ship out of the box for my operation type?
- “Will it work on iPad / Android?” Yes, every modern platform does. Better question: does the mobile app capture data, or does it just display the data the office types in?
- “Does it integrate with [accounting tool]?” Probably. Better question: does the accounting integration write in both directions, reconcile automatically, and post the same identifier so financial entries trace back to operational records?
How to actually run the evaluation
A short version, for time-poor operators:
- Shortlist three platforms — no more. More than three becomes a research project, not a decision.
- Ask all three for a live demo with the questions above written down in front of you. Take notes. Compare answers.
- Pilot the top one for thirty days, free, with concierge onboarding. Any platform that won't pilot is one that doesn't believe its own demo.
- Use it for thirty days the way you'll actually use it. Capture in the field. Generate one audit pack. Run one paddock-level P&L. Test the offline behaviour. Talk to one of your buyers or your bank about what they can see.
- At the thirty-day mark, decide. Renew or walk. Don't drift. The cost of running parallel systems for a month is small. The cost of running them for a year is enormous.
The kicker
The hard part of choosing farm management software isn't comparing feature lists. Every platform's feature list looks more or less the same — and most of the features on those lists are technically present and practically broken.
The hard part is figuring out which platforms can demonstrate what they claim, and which ones are coasting on the assumption that you won't ask.
The framework above isn't tilted at any particular product. It's tilted toward what a working farm actually needs — and toward platforms honest enough to fail some of the questions and tell you about it. If a platform passes most of these, it's probably fine to pilot. If it passes all of them, it's probably worth signing. And if a platform won't let you ask these questions live on a demo call — that's the loudest signal of all.
— The RedEarthOne team