Why SMS still wins in rural advisory.

The instinct is to reach for an app. We think that’s the wrong first move — because in rural advisory, bandwidth is not the bottleneck. Trust is.

A farmer reads an SMS advisory on a phone in a maize field
The last mile of rural advisory is a phone in a field — and a decision about whether to trust what arrives on it.

We get the same question from most new partners: shouldn’t we be building an app for this? Our answer keeps coming back the same. Not yet. Maybe not ever — and the reason has almost nothing to do with technology.

The myth of the bandwidth bottleneck

It’s tempting to assume that the gap between a smallholder farmer and good advisory is a technology gap — that smartphones, 4G coverage and polished apps will close the distance. They won’t. At least not on their own.

Mobile penetration across rural Kenya is high and rising. Most farmers carry a phone. Coverage is uneven, but it is rarely the binding constraint on whether good advice reaches someone and changes what they do that week.

The binding constraint is attention — and behind attention sits trust. A farmer will not act on advice from a number she doesn’t recognise, in a language that doesn’t fit her week, sent at a time she can’t do anything with it.

Which is why our first project is a study

If trust and attention are what actually limit rural advisory, then the useful question is not which channel to build on. It is what this information is worth to the person receiving it — because value is the clearest evidence that something is trusted enough to act on.

That is what our willingness-to-pay study sets out to establish: what rural ecosystem players already spend on information, and what they would pay for information they can act on. Almost all rural advisory is currently given away, which is precisely why nobody in the sector can say what any of it is worth. We would rather find out before we build.

Three assumptions we hold going in — and intend to test rather than assert:

  1. Cadence beats content. A short, weekly, predictable message is more likely to be opened and remembered than a longer, denser monthly bulletin — even when the information in the bulletin is better.
  2. Sender identity matters more than channel. A message recognised as coming from the farmer’s own cooperative should carry far more weight than the same message from a generic shortcode.
  3. Verification closes the loop. Advisory without a way to check it — a price to compare against, a peer conversation, a leader’s readout at a meeting — decays fast. Verification is what turns information into a decision.

Why SMS — still — today

SMS isn’t exciting. It doesn’t demo well. It looks like the past. But it has four properties no app currently matches at the last mile in rural Kenya:

1. It works on every phone in the catchment.

We never want to say to a farmer, “your device isn’t supported.” That sentence is itself a form of exclusion, and SMS avoids it entirely.

2. It survives bad coverage.

A message sent when a tower is patchy will land when the tower is back. A real-time app session that drops on a hilltop just drops.

3. It costs little enough per message to sustain a cadence.

A cooperative can afford to be in weekly contact with its members — which means cadence (see above) becomes an actual operating choice, not a budget compromise.

4. It carries the cooperative’s identity, not ours.

Branded shortcodes let messages arrive as if from the co-op itself. The platform stays invisible. That’s the right architecture: the farmer’s trust belongs to the institution they already trust.

What this means for the work ahead

The same logic runs through our cooperative training program. It starts with a needs assessment inside one cooperative rather than a curriculum written somewhere else — because a training program, like an SMS, only lands if it comes from somewhere the recipient already trusts and speaks to something they already know is broken.

The instinct to build something sophisticated first is strong. We’re resisting it. The study begins in 2026 and we’ll publish what it finds, including the parts that contradict what’s written above. If you’re working on something similar — or want to challenge what we’re betting on — we’d like to hear from you.

· Keep reading

More field notes.

  1. Coming soon

    Designing with women’s groups: listening first

    On why we plan to prototype second — and the quiet work of building a brief with producer groups.

    Gender · Design
  2. Coming soon

    What digitizing a cooperative actually takes

    The system is the easy part. A short reflection on the records, habits and people that have to move with it.

    Digitization · Practice
  3. Coming soon

    The case for cooperative-anchored delivery

    Why we keep coming back to the co-op as the unit of change — and why we’re making that bet.

    Cooperatives