Skip to content

Built for the field, not the office

Agritech users work in sunlight, on budget phones, with patchy networks and often in their own language. I design marketplaces, advisory apps and supply-chain tools that work where the work happens.
Start a project
Travellers bent against a gust of wind that scatters papers into the sky

The problems I hear most

  1. .01

    Designed in a city, used in a field

    Small text, low contrast and long forms fail outdoors, one-handed, on a cracked screen. Most agritech apps are tested indoors.

  2. .02

    Sign-ups that never come back

    Farmers try the app once. If the second visit isn't easier than calling a trader, it doesn't happen.

  3. .03

    Language and literacy as blockers

    English-first labels and text-heavy flows exclude the people the product is for.

  4. .04

    Two very different users in one product

    Farmers, buyers, field agents and ops teams need different things from the same data.

What good looks like in Agritech

  • Large targets and high contrast, tested outdoors at midday
  • Voice, pictures and local languages before typing
  • Flows that survive dropped connections and resume where they left off
  • Prices, weather and payments: the three numbers people check, made obvious
  • Field-agent and ops tools designed alongside the farmer app

How I can help

  • Product & UX Design

    Apps, websites and dashboards for products with real complexity underneath. I design the flows first and the pixels second, so the result is calm to use and straightforward to build.

    Discuss this

  • UX Research & Audit

    Evidence before opinion. I find out what users actually do, where the product loses them, and which fixes will move the numbers you care about.

    Discuss this

Agritech, asked often

  • Yes. A day or two in mandis, fields or collection centres changes more decisions than weeks of remote research. I plan it around your users' work, not mine.

  • That is the default for agritech. I design and test on budget devices and slow networks, and work with engineering on what actually loads quickly.

  • Layouts that survive longer words and different scripts, icons that carry meaning, and voice where it helps. I test with native speakers, not just translated strings.

Other industries