A demo is built to be agreed with. Every screen is populated with clean sample data, every workflow is the one the salesperson has rehearsed, and every question you did not think to ask goes unanswered because you did not ask it. The way to see a farm software product clearly is not to watch the demo more carefully. It is to ask the questions the demo was not designed to answer.
What follows is a short list of those questions, in the order they matter most, plus what a good answer and a bad answer to each one actually look like. Ask them of every vendor you are evaluating — and, since this page is written by one, ask them of us too, and check our answer rather than take our word for it.
Read this knowing who wrote it. This page is published by Farm40, a company that sells farm management software, and it tells you how to interrogate vendors like us. Assume a thumb on the scale and hold the questions below to the same standard you would hold any sales conversation.
Can I get my data out, without asking you, in a format I can read
This is the first question, and if the answer is anything softer than a plain yes and a file you can open yourself, stop the evaluation there. Your records are the asset. The software is where you keep them for now, not where they live forever. A vendor who makes export slow, incomplete, or gated behind a support ticket has made a decision about who the data belongs to, and told you the answer.
Ask to see the export before you sign anything, not after. Open the file with the software closed. If it reads as a coherent record of your farm on its own — dates, quantities, identifiers all intact and legible — the vendor passed. If it is a jumble of internal codes that only make sense inside their interface, it failed, regardless of how good the interface itself is.
What happens to my records if you go out of business
Most software companies do not last as long as the farm using them. That is not a criticism of any one vendor; it is the base rate for small software companies generally, and a fair question to put to any of them plainly. The honest answer collapses back to the export question — if you hold a current, readable copy of your data, a vendor closing its doors is an inconvenience. If you do not, it is a loss with no undo.
Watch how the question is received, not just what the words are. A vendor who treats it as reasonable and answers with specifics — how often you can export, what the file contains — is telling you something true about how they think of the relationship. One who treats the question as an insult is telling you something too.
What actually changes my price a year from now
Ask what happens to the number on the invoice when your operation changes shape — a second farm, an extra user, a module you did not start with. A plan that gates one clear thing is easy to reason about a year out: you can predict the bill by predicting one number, the count of farms or seats. A plan with several separate levers — a module fee here, a per-animal charge there, a support tier somewhere else — is much harder to forecast, and the unpredictability itself is a cost, even before any individual lever moves.
Ask the vendor to say, in one sentence, what the paid tier buys that the free or entry tier does not. If they cannot say it in one sentence, the pricing was not designed to be understood; it was designed to be discovered later, a module at a time, after you are already dependent on the product.
Does the compliance field live where the work is logged
Ask to see the actual screen where a treatment or an application gets recorded, and check whether the fields that matter for a buyer or a certifier — a lot number, an interval, a rate — sit on that same screen, or whether they live on a separate “compliance” tab visited only when an audit is booked. A product that quarantines the important fields to a screen nobody opens day to day has designed the record to be optional at the exact moment it matters most, which is discussed at length in what a defensible spray record contains.
Ask, too, whether the record can refuse a bad action — a sale of an animal inside a withdrawal window, say — or only display a warning a busy person can click past. The difference between a warning and a refusal is the difference between software that helps and software that merely watched.
What does the assistant actually do, and what does it refuse to do
If a product advertises an AI assistant, ask the vendor directly whether it performs its own arithmetic on your figures or only quotes numbers the application already computed, and whether it will invent a regulated interval if you ask it one. The two behave identically in a scripted demo and very differently the first time a real number is wrong. Ask, too, what the question limit is and what happens when you hit it — a vague “plenty” is not an answer.
Farm40’s answer, for what it is worth: the assistant is read-only, names which tools it ran to find something rather than claiming to have “analysed” anything, and does no arithmetic of its own — every account gets 10 questions a month before an add-on is needed. The limit is the same sentence as the capability: it cannot act on your data, and it will not compute a figure the application has not already produced.
Who can see my data, and is it actually separated
Ask where the data is stored, who inside the company can read it, and whether your farm’s records are separated from every other customer’s at the database layer, not merely hidden by the interface. A vendor who cannot answer this plainly and quickly has not had to think about it yet, which is a bad sign to learn before you hand over a season of your operation rather than after.
None of these five questions requires trusting a demo. They require a straight answer from a person, in writing if possible, before you pay. If a vendor answers all five without flinching, that is a genuinely useful signal — more useful than any feature list — and it is worth reading how to choose farm software honestly alongside this page, since the two are meant to be used together: one tells you what to evaluate, this one tells you how to catch a vendor who would rather you didn’t. If you are not sure software is the right move at all, the farm software hub is the place to start that decision, not this one.