Industry Deep Dives

Agritech for 2G Networks and Shared Phones

Most agritech fails on assumptions about connectivity, literacy and device quality. Building for the conditions farmers actually work in.

Purushottam Kumar Suman
Purushottam Kumar Suman
Founder & CEO, Drema AI
8 min read
Agricultural field with crops under an open sky

Agritech products are frequently designed in cities on fast connections and tested on new phones, then deployed to users with none of those things. The failure is not the idea; it is a set of assumptions embedded so early nobody revisits them.

01

Offline is the normal state

Connectivity in the field is intermittent, slow and expensive. Every action must complete locally and sync opportunistically, with small payloads. An app that shows a spinner when a farmer opens it in a field has failed at the first interaction and will not get a second.

If it needs a connection to be useful, it is not an agritech product.

02

Language and literacy are design inputs

Regional language support cannot be retrofitted — layouts break, and translated English phrasing reads as foreign. Design in the target language from the start, and lean on icons, voice input and audio output for users with limited reading confidence.

Offline-firstSmall payloads, opportunistic sync
Vernacular by designNot translated afterwards
Voice and iconsNot text-entry dependent
SMS and IVR fallbackWhere smartphones are not universal
03

Advisory must be specific to be trusted

A broadcast message about a regional pest is ignored; guidance tied to this plot, this crop, this growth stage and last week's local weather gets acted on. Specificity is what converts an app into something a farmer opens deliberately rather than something installed at a demonstration.

04

The season is the deadline

Software timelines can slip a fortnight. Agricultural windows cannot — miss sowing and the next opportunity is a year away. This should shape scope decisions ruthlessly: ship what is useful for this season and defer everything else, because a feature that arrives after the window is worth nothing until next year.

05

Adoption comes through existing trust

Farmers weigh advice by who is giving it. Products that work with extension officers, FPOs and dealers already trusted locally get adopted; products expecting individual download and self-onboarding usually do not. Design the field staff's tooling as seriously as the farmer's.

06

Be honest about precision

Satellite indices and weather models are genuinely useful and genuinely imprecise. Overstating confidence produces one bad recommendation that ends the relationship — and in a sector where the cost of acting on wrong advice is a season's income, that trust does not return.

2G
The network to design for
Plot-level
Advisory, not regional broadcasts
One season
The deadline that does not move
Purushottam Kumar Suman
Written by
Purushottam Kumar Suman
Founder & CEO, Drema AI

Founder and CEO of Drema AI. Builds AI systems, SaaS platforms and industry software — and writes about what actually survives production.

CTA Background

Got a problem like this one?

Bring it to a call with a founder.You will get a straight answer, including when the answer is no.

View Our Work
AI-First Engineering
Secure & Scalable
Built to Deliver Impact