Episode 17

Business 101 In The World of LoRaWAN - Andy Humphrey

Andy Humphrey, founder of Harmony Analytica and host of The Sprinkler Nerd Show, talks about how LoRaWAN is transforming the irrigation industry with a data-first approach that’s as practical as it is powerful.

With over 500 sensors already in the field, Andy shares how he’s built an IoT irrigation business around the principle of creating clarity—starting with simple deployments and expanding once value is proven.

He breaks down the emerging business model of Sensor as a Service and how a well-placed soil moisture or pressure sensor can uncover hidden problems, provide an ROI, and unlock powerful insights for decision-makers.

His example of using a water meter monitoring system to diagnose a faulty pool fill setup shows just how impactful water meter monitoring can be when paired with the right tech stack.

Andy walks through his real-world strategy of “land and expand,” highlighting how starting with one smart irrigation controller or sensor often leads to broader deployments once trust is built. He also explains the value of knowing your customer deeply enough to build exactly what they need—even if they don’t know what that is yet.

We also dive into Andy’s framework of “IoT for CFOs,” exploring how data from water meter monitoring systems can finally give finance teams visibility into an often-overlooked line item. From diagnosing leaks to optimizing usage, the power of IoT irrigation isn’t theoretical—it’s actionable.

Finally, Andy shows how thinking vertically and designing for real-world use can turn a $5 soil moisture board into a $200 solution by solving the exact problem a customer faces—especially in high-value landscapes.

Links:

Andy Humphrey on LinkedIn

Harmony Analytica

  • 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 on MeteoScientific's

The Business of LoRaWAN

2

:

is someone who's built

more than just a business. He's

3

:

built a way of thinking about problems

that cut straight to the value layer.

4

:

You might know him as the Sprinkler Nerd,

or maybe you caught him

5

:

on Shark Tank pitching the Helix

Eco mower back in the day.

6

:

But behind all that is a guy

who's consistently focused

7

:

on understanding systems,

whether they're water, web, or wireless,

8

:

and then connecting the dots

9

:

between those systems

and the people who need the most.

10

:

Andy Humphrey started out in irrigation

sales, moved into smart irrigation

11

:

systems before IoT was even a buzzword,

and then went full tilt into e-commerce.

12

:

His sprinkler supply store became a seven

figure business, dominating a niche

13

:

that most folks overlook.

14

:

And now he's back to building.

15

:

This time with Harmony Analytica,

a company that blends LoRaWAN

16

:

water sensors and real world ROI.

17

:

What's especially interesting about Andy

is that he didn't come to LoRaWAN

18

:

as a wireless engineer.

19

:

He came in as a seasoned entrepreneur

who knows how to sell.

20

:

And he sees LoRaWAN

not as an end in itself,

21

:

but as a tool for creating clarity,

whether that's showing a property manager

22

:

when a pool isn't refilling

or giving a CFO real time

23

:

insight into water usage

they've been blind to for years.

24

:

In this episode, we get into what

Andy calls sensor as a service

25

:

the power of starting with one small

install and expanding from there,

26

:

and how to think about IoT from the

customer's perspective, not the engineers.

27

:

He's got more than 500 sensors

in the field.

28

:

Plenty of hard won lessons,

from building his own soil moisture probe

29

:

and a refreshingly practical approach

to solving problems.

30

:

Let's dig in.

31

:

Andy, thanks for coming on the show, man.

32

:

My pleasure Nik, so glad to be here, man.

33

:

Yeah, I'm psyched to have you here.

34

:

We first met a couple years ago

with the Gristle King thing

35

:

so totally separate from MeteoScientific.

36

:

And you came in as Sprinkler Nerd there,

and now you're doing some LoRaWAN

37

:

business stuff.

38

:

But really,

I think of you as like a business crusher

39

:

who just applies their focus

to different niches.

40

:

And I thought because from the outside,

41

:

it looks like you really love some things

that are maybe unexpected for a normal

42

:

person is we'd start with asking you,

what do you love to do?

43

:

I would say that

44

:

I love to play in the sandbox of life.

45

:

Now what does that mean?

46

:

It means I like to play, tinker,

47

:

and part of that is, I guess, first,

48

:

understanding how things work enough

49

:

so that you can connect dots

looking forward.

50

:

All right, so once you know how things

work, then you can say, oh my gosh,

51

:

this might affect said industry

in such a way.

52

:

In ten years.

53

:

And you kind of have this vision.

You can see it.

54

:

You're like, gosh

I know what's going to happen.

55

:

Now we all think we know

what's going to happen.

56

:

So there's some percentage

that it's not going to.

57

:

But if you can see what might happen

based on the tools that are available

58

:

and what you've learned,

then you can start playing in the sandbox

59

:

and trying to create that vision

that you have.

60

:

And so to me, that's what I love to do

have a vision and then go try to build it.

61

:

And that's what you're doing right now

with Harmony Analytica,

62

:

which is this basically, it's

built around the soil moisture sensor.

63

:

You've got the irrigation

kind of sales background,

64

:

and you've got a thing

that I think is really interesting

65

:

for a lot of folks in LoRaWAN,

which is that you come to this from

66

:

this kind of business

first and lots of online sales experience.

67

:

You've had these million dollar,

68

:

multimillion dollar sales years

on the Amazon side or on online side.

69

:

So making the money is not super hard

for you.

70

:

At least that's

how it appears from the outside.

71

:

You never know

what it's like on the inside,

72

:

but putting everything together

so that it's like a unified

73

:

experience is the thing

that I think is really important in the

74

:

on the LoRaWAN side.

75

:

Talk to me about your idea of this sensor

as a service,

76

:

because I think you're going

to crush with it again.

77

:

So this is a bit of a theory

78

:

mixed with playing in the sandbox

to experiment,

79

:

to see if the theory actually

could be proven out.

80

:

One theory would be sensor as a service.

81

:

Now, what's interesting about

that is the service

82

:

would be a subscription.

83

:

Yet at the same time,

we are also in this sort of subscription

84

:

overload economy,

where in some ways it's a barrier

85

:

because users think,

oh my god, another damn subscription.

86

:

Now, man, I don't know.

I got to think about this.

87

:

I really don't want another subscription.

88

:

So I think there is a model

89

:

for sensor as a service.

90

:

I'm not 100% sure yet.

91

:

Exact what that service is.

92

:

And so I think there is something

to be said about deploying devices,

93

:

making happy customers,

and then based on the needs, wants,

94

:

desires of that group of customers,

95

:

then you could layer on the service

part of it

96

:

such that they're happy

because you're building

97

:

something that they want

and they're already in, versus

98

:

having the subscription

be a potential barrier to market.

99

:

And so what I'm trying to do right now

is get as many devices into the field

100

:

and into the hands of customers

as possible, because that's

101

:

also where the learning happens, right?

102

:

And I guess the natural question there is

what what have you learned so far?

103

:

And can you share a little bit

about numbers,

104

:

whether it's uplinks

or sensors in the field or whatever it is.

105

:

Give me some general dimensions of this.

106

:

Yeah.

107

:

We have north of 500 sensors in the field.

108

:

You know, majority of them are soil

moisture sensors.

109

:

Majority of them are sensors

that I'm building.

110

:

But we also have third party devices

in the field.

111

:

We have quite a few weather stations

in the field, different types of weather

112

:

stations in the field, data

loggers in the field that are primarily

113

:

connected to water meters

and pressure transducers.

114

:

So when I look at in my industry,

when I say my industry,

115

:

this would be the irrigation and outdoor

water consumption and indoor water.

116

:

Those would be the primary metrics.

117

:

And as I think about my industry,

where it's been, where it's going,

118

:

I do feel like the next evolution

is the collection of data from sites.

119

:

So as it stands now, there's no data

being collected from outdoor landscapes.

120

:

The only data that might be collected

would be weather that

121

:

mostly isn't coming from a local weather

stations

122

:

just coming from a broadcast service,

and then maybe some water consumption.

123

:

But water consumption

is probably only 5% of projects

124

:

have a flow meter or water

meter dedicated to the irrigation system.

125

:

Currently, pressure is not being monitored

or reported at all on an irrigation

126

:

system, and soil moisture again,

is probably less than 1%

127

:

of all irrigation

systems have a soil moisture sensor.

128

:

I would have thought we'd be

there'd be way more penetration.

129

:

It seems like it's super obvious

that you need those things.

130

:

But of course,

131

:

I mean, I guess I'm a nerd, so it's like,

yeah, that's the first move for me.

132

:

But it sounds like

in the land of irrigation,

133

:

the first move is not being a nerd.

134

:

And there's something to be said

about the technology

135

:

that is required to make it possible

136

:

has been available,

but not in a place that's affordable

137

:

to the everyday person

company, service provider.

138

:

But it's getting there.

139

:

We're much closer

now than ever before. So.

140

:

So even if we went back ten years ago,

there really wasn't,

141

:

well, maybe ten,

maybe LoRaWAN is ten years old.

142

:

Is that about right?

143

:

2000m 2009.

144

:

So yeah.

145

:

Well, but in terms of like having devices

that are.

146

:

Yeah, out there in the world. Sure.

147

:

And and the full stack

if you will, maybe:

148

:

So so what we can do now

wasn't possible before

149

:

unless you had big pockets and,

150

:

and you were much more of an engineer,

sophisticated user.

151

:

So you see immediately

the market was only going

152

:

to be a 1% of 1% of 1%

that would deploy it.

153

:

But as things become more readily

available and the technology evolves, now,

154

:

we can get it further down the funnel

to to more of the everyday person.

155

:

And I think that's

as we go forward into the future

156

:

that'll that'll move down market, down

market, down market even more.

157

:

So that I think that's one of the reasons

why none of this technology

158

:

was really deployed into the irrigation,

is because it was just too, too costly.

159

:

There was really no ROI.

160

:

It wasn't worth somebody's time

except for those few edge cases.

161

:

Right.

162

:

And now for 200 bucks,

you can put a wireless pressure transducer

163

:

on an irrigation system and monitor

the pressure remotely.

164

:

I mean, that's pretty amazing.

165

:

And I guess, I mean, I'm

not an irrigation guy.

166

:

What what is that change for

someone who's in that business?

167

:

Like, why do I care about pressure?

168

:

I'm assuming there's some really obvious

things, but, well, every irrigation

169

:

system has a preferred

operating like performance spec.

170

:

So a sprinkler is designed to operate

at a certain pressure.

171

:

And if the pressure, let's say,

is much lower,

172

:

your distribution uniformity is affected.

173

:

So you're no longer

applying an even amount of water

174

:

and you can use it

for diagnostic purposes.

175

:

And what's interesting about pressure

is it's not constant like the city.

176

:

If it's city water,

177

:

there's a time in the day

where the city has the highest pressure,

178

:

and then it slowly goes down and down

and down throughout the day,

179

:

and then it ramps back up.

180

:

And oftentimes the city is very cyclical,

181

:

like every day

the pressure ramps up at the same time.

182

:

And so one of the things

that's interesting is let's say

183

:

an irrigation contractor

is installing a system for the first time.

184

:

They should take a pressure reading.

185

:

I would say that let's say half do not,

which they should,

186

:

but if they're there at the site

and they take a pressure

187

:

reading and it's 1 p.m.,

that might not actually be the pressure

188

:

when the system

is running at four in the morning,

189

:

but there really hasn't

been a good way for someone to say,

190

:

let's put a pressure transducer on here

and let's just

191

:

monitor it for a couple days

so we can get an idea for what

192

:

the pressure looks like

at this price object.

193

:

And we can document that.

194

:

And then if there's ever an issue

sometime in the future, we know what our,

195

:

you know, sort of baseline metrics were

when we first put this in super smart.

196

:

I mean, that's exactly

the kind of thinking and investigation

197

:

I expect from you. So well done.

That's rad.

198

:

I can totally see how that would be.

199

:

Also, a part of the sales pitch

where you come in and you say, hey, you've

200

:

you've never seen this information before,

we're going to show this to you.

201

:

And maybe that's

something that you do for free.

202

:

Maybe that's something you charge

an initial consulting piece for.

203

:

And in fact, this idea of IoT for CFOs

came directly from you.

204

:

You're the one who told me about that.

205

:

Can you walk me through your sales

pitch for.

206

:

Maybe we actually, we start with, like,

how do you find new customers?

207

:

Then we'll walk through

a pitch conversation.

208

:

So certainly

209

:

somebody could run a Google search

and come across something and inquire.

210

:

But there's also the who do you know

who's in your who's in your network?

211

:

Who can you talk to you

about opportunities

212

:

that they've never thought of before.

213

:

And then they start

looking at their clients and so on.

214

:

And so I think that word of mouth,

but just your network

215

:

and sort of talking about opportunities

that are now available

216

:

that maybe weren't available before

and trying to expose problems

217

:

really like this technology is no good

unless it's

218

:

providing some inherent benefit

which could be

219

:

or should be solving someone's problem

or pain points so that they have an ROI.

220

:

An ROI on the investment.

221

:

And that could be to save energy costs,

or it could be to fix problems in systems,

222

:

you know, find leaks

that were not surfacing

223

:

before because you can sometimes

you see a leak if it's going to drain.

224

:

Okay. So it's the relationship piece.

225

:

And we were talking a little bit

about this idea

226

:

of a lot of the technology

that we're using in LoRaWAN is open.

227

:

It's not like LoRaWAN is my secret

and I'm not sharing with anyone.

228

:

Everybody kind of understands it.

229

:

I think your secret sauce is,

A, you're a willing to work

230

:

as hard or harder than anyone

and B, you've got this ability

231

:

to put all of these ideas together

and actually execute on it.

232

:

And those two things are very simple,

but it's

233

:

I think the saying is, this shit

ain't complicated. It's just hard.

234

:

And you're good at this. Personally.

235

:

It's it's not complicated.

236

:

And it reminds me if I were trying

to find something parallel to use

237

:

as a parallel example, I might use

238

:

the internet as a parallel example,

meaning let's say a website.

239

:

So in 1998, or you could probably even say

240

:

2002 and earlier,

building a website was very difficult.

241

:

Yeah, not for someone who was skilled

or schooled in that,

242

:

but for the everyday person

it was difficult.

243

:

And then as it evolved,

it became easier and easier

244

:

and easier for someone to stand up

a content website, an e-commerce website.

245

:

And that I feel like is very similar

to what we're seeing with the IoT

246

:

industry, is you don't have to be an IoT

engineer anymore.

247

:

There are tools and sort of built

for you, done for you solutions

248

:

that you can put together to build a tech

stack that works for you, you know?

249

:

And my tech stack might be different

than someone else's tech stack.

250

:

But finding the tools that are available,

putting them together in a unique

251

:

way, sort of is the differentiator beyond

252

:

sort of saying, I've got something

that's patented, proprietary, yada yada.

253

:

I'm not sure.

254

:

I'm not so sure

that that's really the case anymore.

255

:

No, it's putting together a tech stack,

finding a vertical and applying it. Yep.

256

:

Very straightforward stuff

that requires a little bit of imagination,

257

:

but nothing beyond

what the normal person can do.

258

:

And you're

certainly exceptionally good at this.

259

:

Okay, so the way you're finding

new customers is through relationships.

260

:

You're a total hustler.

I see you go to the conferences.

261

:

I see you coming back.

262

:

I listen to your podcast

and you're talking about,

263

:

you know, hey, shout out to Billy

and Jimmy and Tommy and Sammy, like,

264

:

you're really good about making sure

all of those relationships are out there

265

:

when you meet a customer

and you're going in.

266

:

I thought,

this is one of the coolest things you've

267

:

described to me in our past conversations

is you'll start with just one thing.

268

:

Can you walk me through in general

without giving away your secret sauce?

269

:

Though?

270

:

I don't think it matters because I don't

think I was going to work as hard as you.

271

:

What that pitch looks like when you're

first talking to a potential customer.

272

:

It is interesting

because if we're not careful

273

:

and this is probably just business

sort of business sales 101 is if you throw

274

:

a bunch of stuff out there, we might know

exactly what we're talking about.

275

:

But the customer

then is just full of confusion.

276

:

Yeah.

277

:

If you say, here's what we can do,

and there's ten things like okay,

278

:

so to me it's really about trying

to understand the customer.

279

:

Where are they?

What problem can they solve.

280

:

And if it's not soil moisture sensor,

then I might not mention that

281

:

because maybe it's

282

:

water consumption

that matters more to them.

283

:

So if I try to focus in on one aspect

284

:

and if you can like to use

a silly analogy,

285

:

like land and expand land with one thing,

and then start going sideways

286

:

and introducing like another technology

and another type of a sensor,

287

:

I feel like is a better approach

than throwing everything out there

288

:

and then expecting the customer

to pick one.

289

:

Yeah, hoping they decide for themselves

all the stuff that you know.

290

:

Okay.

291

:

And here be a good example

using soil moisture sensor as a starter.

292

:

So I don't I don't think you would care

if I mentioned name names Isaac

293

:

Carter

Carter Irrigation Solutions in Florida.

294

:

And he started using some soil

moisture sensors.

295

:

And then he, you know, once

you have a relationship with someone,

296

:

you really to me,

I want to be their problem solver.

297

:

If you if you have a problem on the site,

just come to me

298

:

and we'll see what we can do

to figure this out.

299

:

Well,

one of his customers has a swimming pool.

300

:

Of course it's Florida.

301

:

They have a swimming pool and

they were having trouble with the company.

302

:

Who maintains the swimming pool

with the level

303

:

control,

like the automatic fill swimming pool.

304

:

Okay, the pool service

company said everything is fine.

305

:

But the homeowner saying, I really don't

think this thing is running.

306

:

It's not working, you know?

307

:

And I said, all right, Isaac, let's just

put water meter on here with a data logger

308

:

and we can create some charts

and really see what's going on here.

309

:

So we did that

310

:

and I started watching it immediately

because it's interesting to me.

311

:

And I want to make sure that technology

is working correctly.

312

:

And we're not registering any water.

313

:

So no water.

314

:

A couple days

go by, week goes by two weeks go by.

315

:

And I'm like, you know,

there's got to be evaporation.

316

:

Like,

this swimming pool should be filling.

317

:

And there was no water usage.

318

:

And then I started to get worried

because I'm thinking,

319

:

okay,

maybe my technology is not working here.

320

:

Yeah, maybe there's something stuck in the

water meter and it's just not reporting.

321

:

So Isaac went out there.

322

:

I said, just turn the thing on manually,

turns it on.

323

:

Okay, we got some water usage.

324

:

It's not the IoT sensor. Right.

325

:

So now they had real data.

326

:

The homeowner had actual data

that they could go to their swimming pool

327

:

service provider and say, hey, I,

we started recording the consumption

328

:

and there's no water

coming through the fill.

329

:

Then the company came out

and they realized at the level of

330

:

the fill was not accurate.

331

:

You know, because a pool fill is

basically just a toilet float.

332

:

They had to adjust the toilet float.

333

:

So that it would fill automatically.

334

:

And it was very hard for the homeowner

to say to the service provider, there's

335

:

something wrong, because a lot of times

service providers don't trust homeowners.

336

:

Yeah,

it's like being on the phone with AT&T.

337

:

They don't think, you know, you're doing.

Yeah, they put in the water meter.

338

:

We tracked it online

and they were able to solve that problem.

339

:

The other part I’ll layer on here is

this house was three houses away

340

:

from another house

that has some soil moisture sensors,

341

:

and Wi-Fi to our little IoT gateway

wasn't good at this house,

342

:

but come to find out, the LoRaWAN sensor

343

:

we are using

was able to pick up the gateway.

344

:

You know, at the house three,

you know, three houses away.

345

:

So it was just a great,

great mix of technology on this project.

346

:

Nice. And so you'll start with one sensor.

347

:

You'll expand it out to more

if that's appropriate.

348

:

And then walk me through this IoT

for CFOs idea,

349

:

because I think it's such a neat way

to think about the world, and especially

350

:

as we enable more and more people

with all the technology out there, from

351

:

AI to dashboards to just making anything

that you can articulate possible.

352

:

How do you think about this IoT

for CFOs thing?

353

:

Yeah. So I will say this is it a theory.

354

:

So let's just say there's a 50% chance

that it's a good theory,

355

:

and there's a 50% chance

that it's not a good theory.

356

:

Your theory is that historically,

357

:

you know, CFOs look at profit and losses,

and they and they look at budgets

358

:

and oftentimes

let's just take a use case of water.

359

:

You know, there's been a water bill

360

:

that's been paid every months,

every month for years and years and years.

361

:

And it's just a line item.

362

:

And it probably gets signed off.

363

:

And you know,

364

:

there's going to be some projects,

some companies have facilities manager.

365

:

So the CFO might go

to the facilities manager, and they may

366

:

or may not have an explanation

for what the water bill is.

367

:

But beyond that, there isn't much data

that a CFO can

368

:

look at to explain the

the line item for water.

369

:

And oftentimes on buildings

indoors and outdoors, there's one

370

:

water meter that goes into a building.

371

:

And then after that,

nobody really knows where it goes per se.

372

:

Right?

373

:

Like use 600,000 gallons,

figure it out. Yeah.

374

:

And so if they wanted to reduce it,

they don't necessarily know if they can

375

:

because they don't really know

where it's going.

376

:

And things are getting better.

377

:

But also historically there was just one

read at the end of the month

378

:

that says, here's

what you used at the end of the month.

379

:

So they don't know if it was

all the water was used on one day

380

:

because it was a ginormous leak. Right.

381

:

And they don't have the the visibility

into the timeliness of the data.

382

:

So, you know, daily

383

:

consumption is better than weekly,

which is better than monthly.

384

:

But the closer you can get to the

385

:

to the sample period,

the more you can find anomalies.

386

:

So if a building is

387

:

let's just say, for instance,

they're running 60 gallons

388

:

a minute all throughout the building,

389

:

but all of a sudden they're running

150 gallons for a couple hours.

390

:

Then you can start to ask questions, why?

391

:

Why did our consumption

spike during this period?

392

:

Or maybe it's spikes during this period

every Monday, Wednesday, Friday?

393

:

Okay, what could be going on here.

394

:

And you can try to look for for Pat urns.

395

:

And I guess I'll add that

into the conversation here,

396

:

is that I'm really finding that

the data is more useful

397

:

when looking at it over time than it is

any single one point in time.

398

:

So it's it's almost like looking

at the trends and finding that

399

:

pattern recognition that has value,

but not what is the soil moisture.

400

:

Right now isn't as powerful

as let's look at what it is

401

:

now compared to the last seven days.

402

:

So you kind of need something

to compare it against.

403

:

Oh, that's rad.

404

:

And you're bringing that to people

who are naturally numbers

405

:

nerds with CFOs and saying,

let me just basically pull

406

:

the curtain back

from what's happening in your business.

407

:

You can make whatever decision you want,

like it's your business.

408

:

I will just enable you to

to remove that blocking layer

409

:

from the data, because the data exists

whether you retrack it or not.

410

:

Right? Right.

411

:

So maybe the facilities manager's job

is to make sure the facility is working

412

:

like everything's connected, plumbed,

so that the data can be delivered

413

:

to the CFO. Yep.

414

:

But the CFO, it may not be him or her.

415

:

Could be their team.

416

:

It could be data analysts,

whatever that might look like.

417

:

Could look at it

418

:

and decide what to do with it,

and then send back that information

419

:

to the facilities manager, say, hey,

here's what I think we could do.

420

:

Yeah. Super cool.

421

:

Dig it dude.

422

:

And then you've recently developed

this soil moisture sensor on your own.

423

:

That's kind of this complete

package piece.

424

:

You put a whole podcast out there

on how you did it, going into,

425

:

I would say, pretty decent detail

so that anyone could more or less

426

:

replicate what you did,

which I thought was super cool of you.

427

:

Was there any lessons learned there?

428

:

If you're going to compress all that

into someone building a business

429

:

and LoRaWAN, as we wrap this thing up

where you're like, hey,

430

:

this is what I learned,

and this is really what I would recommend

431

:

you do if you're thinking about building

432

:

a business connected

to or reliant on more wind and sensors,

433

:

I do think that it has a lot

to do with the who.

434

:

Who is the customer?

435

:

And you could take something

436

:

simple like a temperature

and humidity sensor, let's say,

437

:

and you could take the same board

inside the product

438

:

and it's measuring temperature

and humidity.

439

:

You know, that's a commodity, right?

440

:

A LoRaWAN temperature humidity sensor for

all intents and purposes is a commodity.

441

:

However, if you think about the who

442

:

who is using it,

why do they want to use it?

443

:

And then you can design with that in mind.

444

:

Maybe it needs to be waterproof.

445

:

Maybe it needs to be one inch by one inch.

446

:

Maybe it needs to be installed

in the full sun

447

:

and it needs, you know, ventilation,

448

:

you know, what is the application

and who's going to use it.

449

:

And then you can start to get creative

450

:

with designs it

so that it meets their needs.

451

:

And maybe it becomes a $200 temperature

and humidity sensor.

452

:

Yet you can buy over-the-counter

453

:

LoRaWAN temperature and humidity sensor

for probably less than $5.

454

:

Like just a board like, right?

455

:

They're not expensive.

456

:

But then when you figure out

457

:

what the use cases and who needs it,

then you can design it for them.

458

:

Got it to the total

add customizing as a value add.

459

:

Absolutely. Yeah.

460

:

And I think that that's a lot like

461

:

the internet,

meaning a website is just a website.

462

:

But you got to think

with the user in mind, what do they want

463

:

to achieve from it.

464

:

And you know, soil moisture sensors

are a great example because the use case

465

:

that I'm building for is primarily

466

:

high value landscape assets.

467

:

And it's not every yard,

every home in America

468

:

because that ends up

becoming much of a commodity. Yep.

469

:

But it's also turf.

470

:

Grass is a big you,

you know, big, big market.

471

:

And so the sensor that I designed is fully

electrically potted, sealed.

472

:

You could throw it in a pond

and then pull it out two weeks later

473

:

and it's still going to work.

474

:

You can't replace the batteries,

but that's by intent

475

:

because it needs to be installed

in really harsh environments

476

:

where you have to make sure

477

:

it's not going to have any water

intrusion.

478

:

Dang.

479

:

So yeah, throw in a pond is that's a

that's a pretty good sales pitch is like,

480

:

yeah, you could drop this in a pond,

come back in two weeks, it'll still work.

481

:

Just stick in the ground.

So we got you. Yeah.

482

:

And if you can get 3 to 5 years out of a

out of a battery

483

:

or out of a out of a sensor,

and it's affordable to me, that outweighs

484

:

expensive, you know, but something

that you can own longer, you know.

485

:

So that's I guess.

486

:

Yeah.

487

:

The side that I fall on, it's part of the

problem is making something affordable.

488

:

Right.

489

:

That's part of the problem

I'm trying to solve is make it affordable.

490

:

Yeah. And you're very practical.

491

:

I think this is maybe the the last

takeaway piece is in a business sense,

492

:

and I've got another partner like this

who is very practical as well

493

:

in another business.

494

:

And you got to be careful

what you're optimizing for.

495

:

And I think you know what you're very good

at figuring out what to optimize for.

496

:

Like optimize

for some nerdy technical thing.

497

:

And you're like,

no, no, no, it's what the customer wants.

498

:

That's all that matters.

499

:

And you're serving the customer.

500

:

You're not serving your own

kind of technological wishes.

501

:

That might be the fun part

to start playing around with,

502

:

but at the end of the day, you're

delivering something to the customer.

503

:

They're giving you value in return.

504

:

Like what they want

is what matters. Absolutely.

505

:

And there is something to be said about

506

:

customers sometimes

don't know what they want, right?

507

:

You don't know.

508

:

But if you can try your best

to get into the shoes of the customer,

509

:

and you might be able to show them

what they want and what they need.

510

:

If you can be your own customer,

you don't necessarily have to ask them

511

:

what features do you want?

Because they might not know.

512

:

But if you know what it's like to be them,

you can design

513

:

for that kind of like a few steps

ahead of them per se.

514

:

Yeah, I love it, I love it,

I like getting into their shoes

515

:

and being the customer

before the customer.

516

:

As a customer, I'm super smart.

517

:

Yeah.

518

:

And again, I think that all of this

technology is best applied to verticals.

519

:

And so if anybody's listening to this,

it's like they need to think about LoRaWAN

520

:

and IoT through their vertical

and then design for for their vertical.

521

:

Dig it.

522

:

Andy,

thanks so much for making the time today.

523

:

Super cool to get to pick your brain

a little bit always.

524

:

It's always worth it

for me to get on the phone or listen to

525

:

and and listen to what you're saying

526

:

is such a great way to look at the world

through a business lens.

527

:

Thank you man. Yeah, man. Thanks so much.

528

:

That's it for

529

:

this episode of The Business of LoRaWAN.

530

:

I built this for you.

531

:

The one person in about 100,000

who actually has an interest

532

:

in how this tiny little slice of the world

works.

533

:

Of course,

this isn't just about you and me.

534

:

It's about everyone in LoRaWAN

535

:

and how we can work together

to make an exceptional thing.

536

:

LoRaWAN is a dispersed community

with little pockets of knowledge,

537

:

all around the world,

and most of them don't

538

:

talk to each other as much as I'd like.

539

:

So the first and best thing

we can do to make this show better

540

:

is to get more guests

on who I don't even know exist.

541

:

I want to talk to strangers.

542

:

Strangers Who are your friends.

543

:

Please

introduce me to the most rad LoRaWANeer

544

:

you know, or point to my way, or reach out

and give me a name.

545

:

When it comes to running down

LoRaWAN guests, I can track a falcon

546

:

on a cloudy day if you can remember

metsci.show, you can find me.

547

:

That's metsci.show metsci.show

548

:

Okay, so sharing knowledge

by getting great guests on is the first

549

:

and by far the most important thing

we can do to make this better.

550

:

The next best thing for the show to do

is the usual stuff.

551

:

Subscribe to the show, give it a review,

share it in your corner of the world

552

:

again, that's that sideshow.

553

:

Finally, if you want to support the show

financially, you can do that over

554

:

at support.metsci.show You'll see options

there for one time donations.

555

:

If you really like this show,

as well as an ongoing subscription option.

556

:

If you think the show is worth supporting

for the long term.

557

:

If you want to try LoRaWAN for yourself,

sign up for MeteoScientific account

558

:

at console.meteoscientific.com and

get your first 400 data credits for free.

559

:

That's enough to run a sensor for

about a year if you're firing every hour.

560

:

The show is supported by a grant

from the Helium Foundation

561

:

and produced by Gristle King, Inc..

562

:

I'm Nik Hawks,

I'll see you on the next show.

Next Episode All Episodes Previous Episode

About the Podcast

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

Listen for free

About your host

Profile picture for Nik Hawks

Nik Hawks

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