Diagnosing a crop from a photo, or a voice note
Farm Buddy is a farmers-first advisory tool. A farmer describes a problem by typing, uploading a photo, opening the camera, or recording a voice note, and gets back a diagnosis of the plant, an assessment of the soil, and what to do about both.
Illustration, not a screenshot: cassava showing mosaic mottling, the kind of leaf a user photographs. Public domain (CC0) via Openverse.
TreeInAPool
Agricultural advisory
Own product
Built across two framework generations
Problem
Agricultural extension officers are the people who look at a sick crop and tell a farmer what to do about it. There are nowhere near enough of them to reach every farm, and the farmers who most need one are often the least able to travel to find one, or to describe the problem in written English. The expertise exists. The distribution does not.
Approach
The camera is the primary input
A photograph of the affected plant carries more diagnostic signal than a paragraph describing it, and it is far easier for the farmer to produce. Live capture and upload are both first-class, not an afterthought behind a text box.
Voice counts as a description
Requiring a typed description in English excludes the people the tool exists for. A recorded voice note is accepted as a full input, so a farmer can simply say what they are seeing.
Answer with actions, not a label
A diagnosis on its own changes nothing in a field. Every response returns the plant condition, an assessment of visible soil condition, and concrete recommendations for improving each.
Stack
Working with us
You do. Repositories and accounts are transferred to you at launch, not licensed back to you.
A weekly demo on a live URL, plus an async channel for day-to-day questions. No status-report theatre. You see the actual product every sprint.
30 days of support are included with every full build. After that, a maintenance retainer is optional. Nothing is forced.
About two hours a week: one demo, plus decisions when a question is genuinely yours to answer. Everything else is our job.
Often, yes. It starts with an audit of what exists so nobody promises a timeline before reading the code.
Have a process that looks like this?
Bring the messy version. Thirty minutes on a call and you will have a scope, a price, and a date.