Episode 47

When UX Meets LoRaWAN - Ofer Tenenbaum at Meter.me

Ofer Tenenbaum, CEO of meter.me, talks about bringing LoRaWAN into one of the toughest real-world environments: rural water infrastructure. Instead of focusing on radio specs or backend architecture alone, Ofer approaches IoT as a UX problem. His mission is to “friendlify” complex systems so plumbers, pump installers, and ranch operators can deploy and manage LoRaWAN without needing to understand SNR, payloads, or networking jargon.

The conversation begins with the scale of water loss in rural environments, where silent leaks can multiply annual usage by hundreds of percent. Ofer explains why visibility, not just connectivity, is the first step toward solving these losses. From there, he outlines how meter.me combines monitoring and control, effectively operating in SCADA territory where reliability is non-negotiable. Water for cattle, irrigation, and fire suppression demands backend redundancy, disciplined change management, and a deep respect for LoRaWAN’s constraints.

A major focus of the discussion is how AI fits into industrial IoT. Rather than using AI as a marketing layer, meter.me deploys it for anomaly detection and conversational setup, allowing installers to configure automation through natural language instead of complex forms and thresholds. Ofer also shares how constant user observation, field visits, SaaS interaction analytics, and structured feedback loops shape product evolution.

This episode offers practical insight for LoRaWAN business leaders, engineers, and system integrators: real differentiation often comes not from the radio, but from how seamlessly the technology fits into the workflow of the people using it.

Ofer on LinkedIn

Meter.me

  • Helium Global IoT Coverage - Want to know if Helium coverage exists where you need it? Check out this map!
  • Helium Foundation - The Helium Foundation's IoT Working Group (IOTWG) has generously provided support for the first 6 months of shows, please go check them out and consider using the Helium LoRaWAN as a primary or backup on your next deployment. With over a quarter million gateways deployed worldwide, it's likely that you have and can use Helium coverage.
  • Support The Show - If you'd like to support the MetSci Show financially, here's where you can donate on a one-time or an ongoing basis. Thank you!
  • MetSci Show - If you'd like to use our IoT or AI Data Value calculators, or you'd like to contact me, the MetSci Show site is the best way to do it.
  • MeteoScientific Console - Use LoRaWAN - The MeteoScientific Console allows you to use LoRaWAN today. As long as you have Helium coverage (and you probably do, about 90% of populated areas in the world have a gateway within 2 miles), you can onboard a sensor. You can always check coverage at https://explorer.helium.com and switch to the "IoT" tab in the top right.

Transcript
Speaker:

Today's guest

2

:

on MeteoScientific's

The Business of LoRaWAN is Ofer Tenenbaum,

3

:

CEO of meter.me

a company focused on bringing visibility

4

:

and automation

to rural water infrastructure.

5

:

Ofer approaches LoRaWAN from a different

angle than most engineers.

6

:

As a UX driven builder

whose mission is to friendlyfi complex

7

:

technology so plumbers, pump installers

and ranch operators can deploy and use it

8

:

without ever talking about sensor payloads

or gateways.

9

:

In this conversation,

we discuss the scale of rural water loss

10

:

and why silent leaks can multiply water

usage by hundreds of percent.

11

:

How UX discipline can become

a competitive advantage in industrial IoT,

12

:

and how meter meat uses AI,

including a monitoring agent

13

:

nicknamed Maggie,

to detect anomalies and simplify system

14

:

setup through natural language

instead of forms and thresholds.

15

:

We also get into back end reliability.

16

:

SCADA-evel responsibility

17

:

and why you have to pay your dues

to the LoRa gods before declaring that

18

:

it doesn't work.

19

:

This episode is sponsored

20

:

by the Helium Foundation and is dedicated

to spreading knowledge about LoRaWAN.

21

:

If you'd like to try Helium’s

publicly available global LoRaWAN for free

22

:

and support this show.

23

:

Sign up at metsci.show/console.

24

:

Now let's dig into the conversation

with Ofer Tenenbaum.

25

:

Ofer,

thanks so much for coming on the show.

26

:

I'm super excited to have you on.

27

:

Thank you Nik.

I'm super excited to be here.

28

:

So our mutual friend

Dana connected us and said that

29

:

I must have you on,

and you graciously agreed to come on.

30

:

Perhaps we start with,

what is it that you do for folks

31

:

that may not have heard of you, or only

briefly seen your profile on LinkedIn?

32

:

Sure.

33

:

Meter Me is a company focused

34

:

on rural water infrastructure.

35

:

We're trying to bring visibility to our

stakeholders, our users, installers.

36

:

You know, I've heard on your podcast

before, people talk about water loss.

37

:

It's a significant, you know, portion.

38

:

You know, I think the number

that one of your guests mentioned,

39

:

40 to 50% of the water that comes out,

never reaches its destination.

40

:

I think that's actually an underscore

of what happens in rural areas.

41

:

Just as an example, 1 35

42

:

gallon leak silently

leaking on a road in a rural area

43

:

would lose one acre of water in one week.

44

:

And I think the 40 to 50%

45

:

they were talking about what

I always thought this is a funny

46

:

term, non-technical losses,

which is what refers to stealing.

47

:

But you're not talking about that at all.

48

:

It's just like, hey,

this is out in the country. Things happen.

49

:

You know, some pig will go rooting around

and break something

50

:

and you don't know about it

unless you're monitoring it.

51

:

Is that right?

52

:

Or is there a lot of water thievery

in out in rural areas? No.

53

:

Not so much.

54

:

It's the cow stepping on the pipe.

55

:

The earthquake breaking

or cracking a pipe underground.

56

:

The rodents.

57

:

And again, the amount of losses usually.

58

:

I know it's the mathematical

here is weird, but it's hundreds

59

:

of percentage of your normal use.

60

:

So you might have a household

in rural area that should only use

61

:

about 100,000 gallons a year,

but they will lose 500,000.

62

:

Jeez.

63

:

So so there's a lot

64

:

of water loss that we're dealing with,

and that's what we're focused on.

65

:

And you know, water

66

:

water cost money to get get to your place

both in energy and the the water itself.

67

:

So I can see that there's savings there.

68

:

Now, you made it pretty clear to me

before we started.

69

:

You're like, hey, I'm more focused on

making sure normal people

70

:

can understand this

than I am in like deep engineering work.

71

:

Am I getting that right that you're like,

you're more focused on like, hey, I want

72

:

I want this to be understandable.

73

:

Yeah, I'm a UX designer in my background.

74

:

I've been doing UX design

for the better part of my life.

75

:

And so for me to friendlyfi

something is kind of my life's mission.

76

:

I look at technology and again,

77

:

not like some of your podcast guests.

78

:

I am the non geek guest

that you're bringing on.

79

:

And even though like, you know,

my team would drag me into the geeky,

80

:

especially like somebody like Dana.

81

:

Oh yeah, I spend my entire effort

my entire day.

82

:

How do we friendly find this?

83

:

How do we don't talk about Laura?

84

:

How do we don't talk about NTN or

85

:

or 5G or sensors or, you know, payloads.

86

:

Modbus I don't care.

87

:

I just like, how do we don't talk

about any of those things.

88

:

And we bring it

so that, you know, regular layman users

89

:

could do is it the end user could use it?

90

:

I really want a plumber, a person

that knows how to operate a wrench,

91

:

maybe a voltmeter at the most

to be able to deploy Lora and IoT.

92

:

That's the bar.

93

:

Okay. I like it.

94

:

I want the same thing.

It seems pretty difficult.

95

:

What do you see?

96

:

Or what do you think

you see as a UX focused builder?

97

:

That maybe an engineer would be different

than what an engineer sees.

98

:

Everything.

99

:

That's okay.

100

:

I still get it.

101

:

Yeah. No, the list is long.

102

:

Is like when you try to friendly

five things.

103

:

There is a challenge

104

:

that you get familiar

105

:

with the product

and you get comfortable with it.

106

:

Oh, what's the,

You know, we talk about signal, so,

107

:

you know, you'll have a technician that,

you know, you've deployed your app to

108

:

and you go like, oh,

we can't do this with this S and R.

109

:

Like what?

110

:

Like, you need to, like, wait, wait, wait,

what's snow?

111

:

Because the next time

you meet the next plumber

112

:

and you haven't educated them,

what's S and R?

113

:

They have no idea what it is. Right.

114

:

So you got a constantly

115

:

have a virgin look at your own product.

116

:

Okay.

117

:

And you got to constantly hit

the reset button.

118

:

I don't know anything about this.

119

:

So when I'm like, you know, trying to

install a gateway is the word gateway.

120

:

Okay.

121

:

You know, I'm trying to install a moat.

122

:

What's a moat?

123

:

You know,

124

:

it's really important to me to explain

people that it comes from the word remote.

125

:

You know, so,

you know, you know, stuff like that

126

:

sensor is okay, but payload is not.

127

:

So you constantly

put these glasses on of an end user,

128

:

and you try to

I don't want to say dumbed down.

129

:

That's why we use the word friendly.

130

:

You try to friendly by the entire process

so that the layman can use it.

131

:

Or the professional trade could use it.

132

:

And I would say there are some caveats.

133

:

You know, there's things that,

134

:

you know, your team will tell you,

we can finally find this right now.

135

:

And there are some examples.

136

:

You know, the NFC operation from a phone

137

:

to a moat is very, very difficult.

138

:

So if you can bridge that with a Bluetooth

because the manufacturer doesn't

139

:

want to give you a boolean on the,

you know, on the device,

140

:

then publish a video, you know,

141

:

add a video to to the app and say,

you know,

142

:

literally this is going to be difficult

to turn things on and off.

143

:

Watch this video, fun video

that shows you how to do that.

144

:

Got it.

145

:

And are you using

146

:

a little bit of an unusual question

but normal for today, I guess.

147

:

Are you using AI to do any of that

where you like, hey, just generate

148

:

like a cartoon video of how this works

or you guys aren't aren't doing that yet.

149

:

You're just like, hey, here's my iPhone.

150

:

Yeah, yeah,

we're using AI for much deeper things.

151

:

One of the things with,

you know, IoT deployment

152

:

that users complain about

is the overwhelming amount of data.

153

:

Okay.

154

:

And then you have plumbers

and pump companies and drill companies

155

:

installing meter me at customers,

but they don't want to babysit it.

156

:

Okay.

157

:

So that's where actually AI comes for us.

158

:

We bring in AI.

159

:

We we we nicknamed our,

you know, our AI agent.

160

:

We call her Maggie.

161

:

She's our water magician.

162

:

And she comes in in the role

163

:

that cannot be fulfilled

by anyone in this ecosystem.

164

:

You're not going to have an alarm

165

:

24 seven system like for water systems.

166

:

It's the the economics doesn't work right.

167

:

But now you can.

168

:

So we bring I actually to monitor

169

:

for anomalies things that machine learning

170

:

cannot find things that your threshold

definition couldn't find.

171

:

And we also incorporate

172

:

now in the new version that's coming in

May the actual set up.

173

:

So instead of selecting

I want to fill the tank

174

:

until it reaches, you know, then you have

like a form, you know, until this level

175

:

and then the set the trigger at that level

and the safety,

176

:

you're just going to free

talk to the meter me up and just say,

177

:

I want to fill the upper tank with the,

ravine, you know, lower.

178

:

Well, and then it's going to ask you,

okay, when do you want me to stop

179

:

fueling the tank?

180

:

Oh, when, I guess, I guess 90%. Okay.

181

:

Do you want me to stop pumping from the

well when it's too low?

182

:

Yeah, sure. Or whatever.

183

:

Yeah. So.

184

:

So you're going to have a free talk

with that?

185

:

So that's where we're bringing in AI,

you know, both on the monitoring side

186

:

and on the interaction side

with the installer.

187

:

Oh, that's so awesome.

188

:

I got a million questions.

189

:

I'll start with how do you find customers

or the customers find you.

190

:

Or are you guys putting up billboards

saying like,

191

:

stop losing a billion gallons of water?

192

:

Or like, how do people come and find

either metered meter, me or Lamar?

193

:

Yeah, I don't want to.

194

:

Sounds old fashioned and too naive,

but I've built several businesses

195

:

and I can tell you that the only true

196

:

way to find customers is by word of mouth.

197

:

Everything else

is, you know, icing on the cake.

198

:

The product has to be so good

199

:

that people are just super

excited to talk about, you know?

200

:

I mean, for me, Guy Kawasaki was,

201

:

you know, my age

when he was an evangelist at Apple.

202

:

But the product has to do the, the,

the walking, the product has to do.

203

:

I mean, I need Sheryl Shapley to like,

sit in a table with like,

204

:

you got to watch this meeting and be like,

I can do this and I can do that.

205

:

And that's what sells.

206

:

Everything else is icing on the cake.

207

:

So you can find us on Instagram

and TikTok and,

208

:

you know,

and I publish a few things on LinkedIn,

209

:

and I'm having this podcast

with Nick and it's stuff like this.

210

:

But none of that matters

if the product doesn't sales for itself.

211

:

Is there a way or a method

212

:

that you use

to figure out what a new person might see?

213

:

That is really hard for you to see

because you've been in it so long?

214

:

Yeah, we use SAS services that show you

215

:

what and how people interact with the app.

216

:

Right?

217

:

So Microsoft has it, you know, smartly,

there's there's lots of,

218

:

products out there that let you see.

219

:

And then you actually pretty surprise,

like you're like, oh,

220

:

we we think that our setting up

the alerts is super easy.

221

:

And then you're like, you watch it

like, wait, why did they go back?

222

:

No, they're going forward. You know.

223

:

So as you know, UX designers, you have now

224

:

eyes into

how users interact with your product.

225

:

We're

also like to talk and visit and meet.

226

:

So zoom is a great you know our product

managers get on zoom with people.

227

:

I'm going to meet,

you know, one of our customers twice

228

:

this week, you know, so I, you know,

boots on the ground and watch them.

229

:

We tag along with installers.

230

:

So our product managers will go

and we'll tag along.

231

:

And you're like, oh,

I thought that was simple.

232

:

And you see them

233

:

like struggle with the simplest thing

that you thought that you solved

234

:

and you did it.

235

:

And so you just go back

to the drawing board

236

:

and you just release a better version,

you know, next time.

237

:

And is there a way you internalize

all that in the company that you have?

238

:

I don't know, this.

239

:

It sounds so lame.

240

:

But like weekly stand ups, you're like,

hey, Bill went out and saw

241

:

that this guy tried to put in a gateway

and you know, he's

242

:

trying to plug in the Ethernet

to the wall or whatever it was.

243

:

Have some other way of disseminating

that throughout the company.

244

:

Oh, lots of ways, Nick. Lots of ways.

245

:

So we've established like we

I call it doors.

246

:

There's lots of doors for feedback.

247

:

They all end up in the product

management channel.

248

:

We have a troubleshooting channel where,

you know, people just do that.

249

:

We have a discord channel where

we interact directly with the installers.

250

:

We have shake bugs in the app.

251

:

We have I don't want to say spying,

but like, you know, we have ways to look

252

:

at how users interact with that.

253

:

We have zoom sessions, we have product

254

:

submissions, we've got prioritization,

255

:

the friendly ification

256

:

of what we do is our DNA.

257

:

It's it's embedded

into pretty much the entire life

258

:

cycle, the weekly life

cycle of the company that we have weekly

259

:

meetings, acceleration meetings, friendly

friction meetings, unblocking meetings.

260

:

This is all we do.

261

:

It's all we do.

262

:

Okay.

263

:

Can you give me any by any dimension,

how big is the company?

264

:

It sounds like this is more than just two

people hustling super hard.

265

:

Oh, we're not big, but there are close

to two dozen people on the team.

266

:

Yeah, okay.

267

:

Yeah, and it also sounds unlike

any conversation I've had on the podcast

268

:

where you guys sound

kind of awesomely insane about UX.

269

:

I can't imagine that you're

not paying attention to engineering,

270

:

because if things don't work,

it doesn't matter

271

:

how good your UX is like,

it has to be usable, right?

272

:

Right? Right. For sure.

273

:

How much of a competitive advantage

does it give you to have this

274

:

super focused intensity on UX?

275

:

How much of a competitive advantage

did Apple have,

276

:

you know, having focus on UX versus

Nokia or Nokia?

277

:

I think it's one of those things

that pays the fruits over time.

278

:

Yeah.

279

:

So yes,

you could do a very fast, by the way.

280

:

You know, to to answer your questions.

Have you seen our app.

281

:

I haven't touched yet.

282

:

No. Okay.

283

:

Yeah I think that

when people see me for me

284

:

there's Ha moments like, okay, well,

this isn't like nothing I've seen before.

285

:

This is not just like a dashboard

with some graphs jumping up and down,

286

:

like people have really thought

about intuitive design.

287

:

And so I think it's something

that pays off.

288

:

But to your point,

we're also paying a lot of attention

289

:

to to the back end, the stability of

I mean, you got Dana.

290

:

Yeah, we have Dana. Yeah.

291

:

I mean, we paid our dues to the Laura

gods.

292

:

And that's, you know, that's paying off

after 4 or 5 years into this,

293

:

then you have to have redundancy

on your chirp stack and your app services

294

:

and separate the development

and staging and production environments

295

:

and QA and carry out a mission.

296

:

In fact, I was in a meeting today.

297

:

Nick and one of the engineers

298

:

brought up a whole new backend

way to do our automation.

299

:

Okay, because we do control automation,

we don't just do monitoring.

300

:

And I reminded that engineer, I said, you

301

:

know, despite us not wanting

302

:

to acknowledge that we are

technically a scale, a company,

303

:

and that means that

304

:

everything

new that we deploy does not touch the old.

305

:

We deploy something new.

306

:

This new automation schema.

307

:

That's great.

308

:

It's going to be applied for new systems

that we're bringing on board.

309

:

And an old system

will have to take their time to migrate.

310

:

We're not in this kind of like,

oh, you know,

311

:

just issue a whole new interface

and get users to use it like we are.

312

:

We're mobilizing water.

313

:

We are, giving water for cattle,

314

:

for irrigation, for fire suppression.

315

:

There's no toying with those things.

316

:

So reliability on the back

end and friendly fire

317

:

front end, our, you know, anchors blow it.

318

:

So rad.

319

:

I'm sure someone's going to listen to this

like I want to do that. Same thing.

320

:

This sounds cool.

321

:

Like, what advice would you give someone

who wants to friendly their Lora business?

322

:

I think again

the reset button is really important.

323

:

Like like pick glasses that that you

every time you put on these glasses,

324

:

you look at

325

:

things as if you were seeing it

for the first time.

326

:

And so it's like the The Virgin experience

kind of glasses that you're going

327

:

to put on and see that keep in touch

with your customers all the time.

328

:

They will teach you more than anything.

329

:

And our customers are installers, right.

330

:

And you do

I mean, as it as it pertains to Laura,

331

:

you do have to pay your dues to the

to the Laura Lourdes

332

:

because there's a lot to to shift

when you're shifting from broadband

333

:

connectivity and low latency

to this high latency thing.

334

:

You got to be patient.

335

:

You got to know how to architect the

the backend so that it works with the

336

:

with the advantages

and disadvantages of Laura.

337

:

Before you jump into conclusion

that I can't tell you how many calls

338

:

I've been on, Nick and people say, oh,

we try this with Laura, but it

339

:

just didn't work.

340

:

Yeah, it didn't work because you didn't

pay your dues.

341

:

Yeah, yeah.

342

:

It's easy when you know how it's done,

when you don't. Yeah.

343

:

All right.

344

:

Oh, for thanks so much for carving out

some time to talk to us.

345

:

I know you're super busy.

346

:

Sounds like you're running

this really badass company.

347

:

I'm excited to go

see if I can put meet me on my house,

348

:

which I'm assuming

I can't because we don't have a ranch.

349

:

But it does sound awesome.

350

:

Okay, come on, man, you're welcome.

351

:

Thank you so much.

352

:

That's it for this episode

of The Business of LoRaWAN.

353

:

If you want to go deeper

and actually deploy devices,

354

:

the Meteo Scientific Console

is the fastest way to do that.

355

:

And honestly, it's

also the best way to support the show.

356

:

When you use the console, you're not just

listening, you're participating

357

:

in the same real world LoRaWAN work

we talk about here every week.

358

:

You can get started with the free trial

at Medio Scientific, Aecom.

359

:

Huge thanks to the sponsor of the show,

the Helium Foundation,

360

:

for supporting open LoRaWAN

infrastructure worldwide.

361

:

Check them out at helium Dot Foundation

and hit the show has been useful.

362

:

A quick rating or review on Apple Podcasts

or wherever you listen.

363

:

This really helps

364

:

people find it and helps the show grow

so we can help more people.

365

:

I'm Nik Hawks with MeteoScientific.

366

:

I'll catch you on the next episode.

About the Podcast

Show artwork for The Business of LoRaWAN
The Business of LoRaWAN
Learn From the Pros

About your host

Profile picture for Nik Hawks

Nik Hawks

Incurably curious, to stormy nights and the wine-dark sea!