How to Conduct Farmer User Research That Actually Changes Your Product Roadmap

Table of Contents

You ran the demo. The grower seemed interested. You followed up twice. Silence.

That is not a sales problem. It is a signal that something in your product does not match how that grower actually works. And the only way to close that gap is through farmer user research that goes deeper than a survey or a five-minute post-demo call.

This article covers how to do that research well — how to ask the right questions, how to find what actually matters, and how to turn what you hear into roadmap decisions that move adoption.

Why Most Farmer User Research Goes Nowhere

Most agtech founders do some version of user research. They talk to farmers, take notes, and build features based on what they heard. Then adoption stays flat.

The problem usually is not that they skipped the research. It is that the research confirmed what they already believed.

Farmers are polite. They will tell you your product sounds useful. They will nod through your demo. What they will not tell you is that they have no intention of changing the workflow they have used for fifteen years. That is not dishonesty — it is just how people talk to someone who clearly cares about what they built.

Good farmer user research is designed to get past that politeness. It surfaces the real workflow, the real friction, and the real reason adoption stalls.

What Makes Farmer User Research Different

Farmers are not typical software users. A few things shape how these conversations go.

Time is a hard constraint. Planting season, harvest, weather — the calendar runs the operation. If your research asks for more time than a grower can spare, you will get rushed, surface-level answers. Or no answer at all.

Trust is earned slowly. Growers have seen a lot of products pitched by people who do not understand what it takes to run an operation. They are skeptical by default, and that skepticism will show up in how much they share with you.

They think in problems, not features. Ask a farmer what software features they want and you will get a blank stare or a polite list of things they will never actually use. Ask them what slows them down on a Tuesday morning in October and you will get something real.

This is why the framing and sequencing of your questions matters more in agtech than in most other verticals.

Before You Talk to a Single Farmer

Do not start with the interview. Start with your hypothesis.

Write down what you currently believe about why adoption is stalling — and be specific. "Growers don't see the value" is not a hypothesis. "Growers are not completing onboarding because the data entry required in week one is more work than their current spreadsheet" is a hypothesis.

That specificity tells you what to listen for. Without it, you will walk into the conversation without an anchor and come out with a lot of interesting quotes that do not connect to anything actionable.

Before you go into the field, it is also worth reading this piece on why agtech startups fail the design gap. It will sharpen your sense of what you are actually diagnosing.

How to Structure the Conversation

Aim for 30 to 45 minutes. One grower at a time. No product demo — that comes later, if at all.

Start with context. Where are they in their operation? What does their day look like right now? What season are they in? This is not small talk. It tells you what headspace they are in and which problems are actually live for them today.

Then move into the three areas that matter most.

Get to the workflow, not the wish list

Ask them to walk you through how they handle the specific task your product addresses. Not how they think they handle it — how they actually handled it last time.

"Can you walk me through the last time you tracked [X]? What did you do first?"

You are looking for the real sequence of steps, the tools they use, the people involved, and the moments where something breaks down. That sequence is the workflow you are asking them to leave behind when they adopt your product.

If your product does not fit that sequence, it will not get used. Better features will not fix that.

Listen for what they tolerate, not what they want

Farmers are pragmatic. They have workarounds for everything — the spreadsheet that takes three hours every Sunday, the notebook in the truck, the phone call to the agronomist instead of the app.

Those workarounds are not evidence that the problem does not exist. They are evidence that nothing has been good enough to replace them yet. Your product has to be meaningfully better than the workaround, not just better than nothing.

Ask: "What's the most annoying part of how you handle this right now?" Then ask: "Why haven't you changed it?"

That second question is where the real answer lives.

Ask about the last time, not the next time

Future-focused questions — "Would you use a tool that did X?" — produce optimistic, hypothetical answers. Past-focused questions — "Tell me about the last time this caused a problem" — produce honest, specific ones.

This is the core principle behind the Mom Test framework, and it applies directly to agtech research. If you want to go deeper on this approach, this piece on the Mom Test in agtech is worth reading before your next round of interviews.

How to Turn Research Into Roadmap Decisions

The research is only useful if it changes something.

Separate signal from noise

After five to eight interviews, you will have a lot of notes. Some of it is signal. Some of it is one farmer's specific situation that does not generalize.

Signal is a pattern — something three or more farmers described in different ways without being prompted. Noise is a feature request that one enthusiastic grower mentioned twice.

Build your roadmap around the patterns, not the loudest voice in the room.

Map findings to your product's specific friction points

Take each pattern and ask: where in the product does this show up? Onboarding? The core workflow? The data entry step? The moment after the first report is generated?

This mapping is what turns research into action. Without it, you end up with a list of "things growers care about" that never connects to a specific product decision.

If growers are dropping off during onboarding, that is a different fix than if they are ghosting you before they even start a trial. Both are adoption problems. They require different solutions.

Prioritize by adoption impact, not feature popularity

Not every finding carries the same weight. Some friction points are annoying but not deal-breakers. Others are the reason growers quietly stop using the product after week two.

Ask yourself: if you fixed this, would it move a grower from "interested but not committed" to "paying and staying"? If yes, it goes to the top of the roadmap. If it would make current users happier but would not change the conversion problem, it can wait.

Common Mistakes That Waste Everyone's Time

Interviewing the wrong farmers. Early adopters will give you very different feedback than the mainstream growers you actually need to reach. Make sure your research includes the skeptics, not just the ones who already like what you are building.

Showing the product too early. Once a grower sees your product, the conversation shifts from their reality to your solution. You lose access to the honest workflow. Keep the product out of the room until you have heard what you need to hear.

Asking leading questions. "Do you think it would be useful to have real-time data on soil moisture?" is not a research question. It is a confirmation request. Ask open questions that do not contain the answer you are hoping for.

Treating research as a one-time event. One round of interviews before launch is not enough. Grower behavior changes by season, by operation size, by market. Research should be an ongoing part of how you build, not a box you checked in year one.

Skipping the synthesis step. Talking to farmers is the easy part. Turning what you heard into a clear product decision is where most founders stall. Block time after every research round to synthesize before you build.

FAQs

How many farmers do I need to interview before I can make roadmap decisions?

Five to eight interviews will usually surface the main patterns. More is better, but do not wait until you have twenty before acting. If you are hearing the same friction point in every other conversation, that is enough signal to move.

What if farmers are too busy to talk to me?

Meet them where they are. Early morning calls before the workday starts, brief conversations at ag trade shows, short check-ins during slower seasons — all of these work. Respect their time and keep the ask small. A 20-minute call with a clear purpose is easier to say yes to than a 60-minute "user research session."

Should I pay farmers for their time?

It depends on your relationship with them. For existing users or warm contacts, a genuine thank-you and follow-through on what you heard is often enough. For cold outreach, a small honorarium shows respect for their time and tends to improve the quality of the conversation.

How do I avoid confirmation bias in my research?

Write down your hypothesis before you start. Then actively look for evidence that contradicts it. If everything you hear confirms what you already believed, you probably asked leading questions or interviewed the wrong people.

What is the difference between farmer user research and a customer discovery call?

Customer discovery is typically about validating whether a problem exists and whether people would pay to solve it. User research goes deeper — it maps the specific workflow, the existing tools, the workarounds, and the moments of friction. Both matter, but user research is what tells you how to build the product, not just whether to build it.

How do I know if my research is actually changing my roadmap?

If you finish a round of research and your roadmap looks exactly the same as before, something went wrong. Either the research confirmed a genuinely strong direction, or you are not letting what you heard challenge your assumptions. Good research should produce at least one uncomfortable realization.

Can I do this research remotely, or do I need to be on the farm?

Remote interviews work for most of the conversation. But if you have never spent time on a working farm, you are missing context that shapes everything — the noise, the pace, the physical constraints, the way decisions actually get made. If you can get to the field, go.

What to Do Next

Farmer user research is not a methodology problem. Most founders already know they should talk to growers. The harder part is knowing what to listen for, how to structure the conversation, and what to do with what you hear.

If your product is getting interest but not converting — if growers are ghosting you after demos, or churning after onboarding — the answer is almost never a new feature. It is a clearer picture of the gap between what your product does and how growers actually work.

Learn more at thinksid.co.