That’s the theory. Here’s what it looks like in practice, because we’ve had to answer every one of those fears on real farms, not in a slide deck.
Quick recap of the six fears from Part 1, before we go through how each one plays out:
- Fear 1: What if it fails mid-season
- Fear 2: Connectivity out here isn’t what the brochure shows
- Fear 3: Who can actually see or touch my data
- Fear 4: Being told my own knowledge doesn’t matter anymore
- Fear 5: Will this actually pay for itself
- Fear 6: One more system to manage
The tank that couldn’t be trusted
Take The Sustainability Institute in Stellenbosch. Before we got involved, their JoJo tank had no gauge, so filling it meant switching on a pump and hoping. It overflowed more than once. Because the generator room sat right below it, that water tripped the whole electrical supply. Downstream, their irrigation pressure ran blind too, so strong on a single line that staff had to open several lines at once just to manage it. Nobody could see what was actually happening, so nobody could plan around it.
We put in two sensors, one to watch tank level, one to watch pressure, both reporting back to a dashboard the team could check from a phone. That solved the overflow problem and the pressure problem. Along the way, the data caught something nobody was even looking for: water leaving the tank overnight and refilling by morning on its own. A leak, running invisibly, for who knows how long. It only surfaced because someone finally had eyes on the system.
That project answers fear one and fear four directly. The system didn’t take over anyone’s judgement. It gave the team information they’d never had, and they made better decisions with it, faster, without needing to understand LoRaWAN or dashboards to benefit from it.
Built for African connectivity, not around it
Fear two, connectivity, is one we’ve had to design around from day one. Most of the farms we work with are exactly the kind of remote, patchy-signal sites the big agritech brochures don’t picture. Our sensors run on LoRaWAN first, communicating locally without needing constant internet, with cellular as backup rather than the only path. A gateway can store data during a connectivity gap and sync once it’s back, instead of just going blind.
Security as the foundation, not an afterthought
Fear three, security, is the one closest to where I actually come from. My background is cybersecurity, not agriculture. I’ve watched what happens when connected systems get built without security as the foundation. Every sensor on our network has a verified identity. Data moves on an isolated path, not the open internet. That’s how we build by default, because a farm system that isn’t secure is just exposed with extra steps.
What the return actually looks like
Fear five, money, only gets easier to answer with real numbers from real projects, which is exactly why we keep documenting ours. Water saved from catching leaks early. Fertiliser saved from catching salinity build-up before it costs a season’s yield. Hours saved from not having to physically walk a site to check on something a sensor can tell you instantly.
Where this leaves you
None of this means every farm needs every sensor we make. Fear six, complexity, is really answered by keeping it that simple, one platform, one dashboard, one place to check, not five different logins for five different boxes. The fear farmers walk into an expo with is a fair one. The only honest response to it is showing up with real projects, real failures we’ve fixed, and real answers, not a bigger promise.
If you were one of the people who walked past our stand at Agri5 nodding politely, I understand it. If any part of what TSI went through sounds like your farm, water you can’t account for, pressure you’re managing by feel, a system you don’t trust enough to hand anything over to yet, that’s worth a conversation. Not because we want to sell you something, but because we’ve stood on the other side of that same hesitation, and we built this company to answer it properly.
