1. Podcasts
  2. Problem Solvers
  3. What Customers Ask For vs. What They Actually Want
Problem Solvers

5 Oct 2026 · 28m · 13 chapters

Episode artwork

What Customers Ask For vs. What They Actually Want

In short

After product-market fit, how to grow by listening closely to customers, asking “why” behind requests, and using rapid prototyping to turn labor-heavy ideas into scalable services.

Guests

Chad Lawrence, chairman of SimpliSafe; long-time leader who helped pivot from renters to homeowners and later launched ActiveGuard. Hilary Schneider, CEO of SimpliSafe; led the ActiveGuard business evolution and customer-intelligence approach.

Key claims

Customers’ stated wants can be “faster horses”; you must uncover underlying needs (prevention, peace of mind). Product-market fit creates a “pull” for more features, but not every request should be built literally. Scaling requires prototyping, iterating, and reducing cost drivers (AI filtering noise, human review only when needed).

Notable examples

SimpliSafe’s renter thesis failed; homeowners bought the easy DIY install. ActiveGuard: outdoor monitoring with AI plus human intervention; initially unprofitable due to monitoring labor, later improved via efficiency and targeted human review.

Written by AI. May contain mistakes.

Chapters

0:38

Understanding Customer Desires

Exploring the nuances of what customers say they want versus actual needs.

“That often quoted line from, I think it's misquoted actually from Henry Ford, that if you'd asked customers what they wanted, they would have said faster horses.”
1:21

The SimpliSafe Story

A detailed account of SimpliSafe's journey and market challenges.

“There is a story that I have been telling for years that originated on this very podcast with a conversation that I had with the founder of SimpliSafe.”
2:44

Finding Product-Market Fit

Discussion on recognizing and adapting to product-market fit.

“this reflects the challenge of launching a business.”
4:26

Interpreting Customer Feedback

The importance of understanding the motivations behind customer requests.

“And I think it makes me think of two things.”
7:50

ActiveGuard and Customer Needs

Insight into the development of ActiveGuard based on customer needs.

“And you're thinking, I mean, this is like faster horses, right?”
12:21

Navigating Product Launch Challenges

Discussing the complexities of rolling out new products and adapting to market demands.

“I mean, Hillary, what you just described there is really interesting.”
14:01

Exploring the Upside of Machine Learning

Discussing the potential benefits of machine learning and AI in business.

“And so, you know, just from an analytic perspective, I would bucket and say I have different levers I think I can pull.”
14:26

The Importance of Prototyping

Understanding how prototyping can clarify assumptions and drive innovation.

“And no one really knew what the cost drivers would be.”
15:43

Challenges of Rigorous Design in Growth

Discussing why larger companies may overlook rapid prototyping in favor of perfection.

“Now, it wasn't, as Hillary said, it didn't mean it was profitable day one.”
16:49

Balancing Perfection and Rapid Iteration

Exploring how teams can find the right balance between detailed design and quick iterations.

“that happens to teams as they grow and they become these very capable, rigorous teams that develop products, that they want to do that planning and make sure everything's perfect.”
Show all 13 chapters
19:16

Understanding Customer Needs

Learning how to better understand and segment customer needs for product development.

“What is the next series of rough prototypes?”
22:05

Lessons from Historic Brands

Reflecting on how iconic brands can inform current practices in product development.

“And then you need to kind of go back to the same basics that we were talking about at the beginning, which is, all right, they're articulating something here.”
24:18

Creating Long-Term Value in Business

Discussing the importance of ongoing value creation to maintain company success.

“it's really on how do we deliver on that value proposition about being an affordable solution that delivers differentiated protection, which is what makes the company successful.”
A man walking through an airport, asking his phone a question

Ask about this episode

Get the gist, explore an idea or ask about something said.

Claude

On Problem Solvers, what are the key points of this episode?

Searching your listening

Transcript

Automatic transcript. May contain errors.

0:00Jason: You know, running a small business, your internet isn't just for email. It's how you process payments, manage your team, and stay connected to customers when it matters most. Whether you've got one location or five, reliable connectivity helps keep your transactions moving, your team connected, and all the tools you rely on within reach. Because when your connection just works, you're not busy troubleshooting. You're focused on your customers and growing your business. AT &T Business can help you stay connected and ready for what's next. Visit att.com slash smallbusiness to learn more. That often quoted line from, I think it's misquoted actually from Henry Ford, that if you'd asked customers what they wanted, they would have said faster horses.

0:48The lesson people often take from that, I think, is the wrong lesson, which is you should not listen to your customers. They don't know what they want. that some visionary has to invent. Whereas I think it's a more nuanced lesson, which is you have to ask why when you're talking to customers.

1:07Jason: Running a business means solving problems. I tell you how the smartest entrepreneurs do it. Hi, I'm Jason Pfeiffer, editor-in-chief of Entrepreneur Magazine, and this is Problem Solvers.

1:21Jason: There is a story that I have been telling for years that originated on this very podcast with a conversation that I had with the founder of SimpliSafe. SimpliSafe, the home security system. So SimpliSafe had started with this thesis, which was that renters don't have home security and they should and they would like it. And the problem is that home security systems at the time were like really hard to install. You had to like bust into walls and stuff and nobody's gonna do that in a rental apartment. And so they created this extremely easy to install. It's actually something that is very familiar to everybody now because it's so industry standard.

2:07Jason: But back then it was like revolutionary that you could just kind of put sensors where they belong. And suddenly your home is secure. And they took it to market. And as it turns out, nobody who was renting an apartment actually bought this thing. But who bought it was homeowners because homeowners actually really wanted something that was easy to install. all. And simply safe, recognize this, and then had to make this decision about whether or not to basically restructure the marketing and the product and everything to address the marketplace that was actually emerging despite itself, despite not actually targeting them and abandon the original concept that turned out to not work.

2:43Jason: And I have told this story so many times because this reflects the challenge of launching a business. You enter a market with an idea of who your market, who your customer is. And then you find out what happens. And then you have to react. And then hopefully you find the glorious product market fit. But okay, what happens after that? That's not a story that I got into in that episode. And this now at the 20th anniversary of Simply Safe is a good time to hear the thoughts of what you do next. What happens when you find that product market fit? What happens once you finally identify who it is that really wants your product and you start to serve them and it starts to work?

3:28Jason: How do you grow that business? How do you think bigger and more expansively? Back on the program, I've got Chad Lawrence, now the chairman of SimpliSafe and Hilary Schneider, who is the CEO of SimpliSafe. Guys, it is so great to have you here on Problem Solvers. Thank you for having me. Thank you. Great to talk to you again, Jason. So let's pick up with that question. And this isn't just a let us tell the whole rest of the history of SimpliSafe, but I really want to hear both of you, great brand builders who have seen this through here, articulate how do you start to think about the business once you've solved that very early problem?

4:10Jason: So maybe, Chad, I kick it to you first because you were there. And then, Hillary, I'd love to hear your thoughts, and we'll start to dig into what entrepreneurs should do once they've planted the flag in the right ground. Well, I guess you frame it very well, and you tell the story very well. And I think it makes me think of two things. First, when you hit product market fit, it feels great. it's characteristic of product market fit that suddenly you feel this pull from the market that everything starts feeling much easier that you're selling the right value proposition to the right customer who wants it and the biggest problem you have is that they want more and it's this great feeling where they're just asking for more and more of you and your biggest problem is how do i start giving them more and more right the second thing more and more even look like?

5:06Jason: Like, you know, what is more and more? You know, for us in those days, it was as we started serving the homeowner and not the renter anymore. These were bigger homes. They wanted more sensors, more coverage, more types of sensors, multiple keypads. We had recently launched our app and they wanted more features in the app and more control of the system, cameras, this pull for delivering more product, more service from you. It's this great feeling and it's a great cycle to be on where the customer starts giving you lots of great feedback that then helps guide where you should be going. Right. And so buried in your answer there, or maybe just the through line in your answer there is once you figure out product market fit, you start to listen really closely to those people.

5:59Because before product market fit, you might be listening to the wrong

6:02Jason: people or you're listening to everybody and you're trying to figure out some kind of signal in noise. And I remember, Chad, our original conversation was really oriented around what do you do once you've discovered that maybe your original thesis is incorrect? I mean, you had to make this hard decision about whether or not to abandon this idea that you felt very confident about that renters were the ones who were going to want to buy this product and instead pivot towards somebody else. But now, once you're listening really close, I suppose another problem develops, which is just because you found the right ICP, right, ideal customer profile, doesn't mean that everything that they tell you should be built into the product.

6:45Jason: People have lots of thoughts and not all of them should be followed. You know, I think, and that is the second part that this framing makes me think of is it makes me think of that often quoted line from I think it's misquoted actually from Henry Ford that if he'd asked customers what they wanted they would have said faster horses. It's attributed to him. I'm not sure if it's true or not but the lesson people often take from that I think is the wrong lesson which is you should not listen to your customers. They don't know what they want. Some visionary has to invent the future for their customers.

7:24Whereas I think it's a more nuanced lesson, which is you have to ask why when you're talking to customers. And they will tell you all sorts of great things. There'll be all this signal in the noise of what they're telling you. But you have to ask why again and again to really understand what the deep need is. And that may lead you in a totally different direction, but it is still really from deeply understand your customers. And I'll tell you, in our more recent company history, this played out exactly that way, where we heard from our customers again and again that they wanted cameras, more cameras, outdoor cameras, more outdoor cameras, more outdoor cameras.

8:07And you're thinking, I mean, this is like faster horses, right? I want more and more horses. And what came to us from really asking why of those customers was what they really wanted was prevention. that it's great to have a camera outside your house to know what's going on, but what they really wanted, what they were searching for, was to stop crime before it happens outside your house. And this led us to develop our latest revolution of our service. It's outdoor monitoring, active guard service that actually monitors the outside of your home, both with AI and then elevated to human reps who intervene on your behalf.

8:44But that came from hearing those customers say they wanted outdoor cameras, but it's not horses. They wanted something else, right? They wanted prevention.

8:55Jason: Yeah. So fact check is you are correct. Henry Ford did not say that. It just got popularly attributed to him. It's not clear if anybody said that. Although, fun fact, just a thing that I happen to know, which is that in the early days of cars, people would stand on the sidewalk and they would yell, get a horse! And Henry Ford thought that was funny. And so he would start yelling that at cars too. Anyway, so Hillary, maybe this is an interesting place for you to pick up on this thread to pick up on because what Chad is talking about is a really important nuance, which is that customers might say the thing that they want, but what they're actually doing here is this interesting mentally complex thing, which is that they are telling you a product that they want because they're kind of taking the leap of what they think would solve a underlying problem that they actually have.

9:48Jason: And so your job is not to fulfill the random solution that they've come up with, but rather to best understand the motivation and the ultimate benefit that they're seeking. It sounds spot on. And in the case of ActiveGuard, which Chad and team really originated and got launched, I think it was about two years ago, a year and a half ago. The thing that's really interesting about it is I think what the customers were really saying is what they want is peace of mind around the safety of those they love. And so the home is a metaphor and our vision is every home secure, but the home is really a metaphor for all the things that live within that home.

10:33And yes, people don't want their crown jewel stolen, but they really want is nothing happening to those they love the most. And so as Chad and team launched the service to begin with, you can imagine that if I'm a monitoring team and I'm, I have 24 seven to monitor the outside of a home that it took a lot of time on our monitoring teams. And so when we first launched it, it wasn't very profitable at all because we had to spend so much on the monitoring. And then what happens is you start to recognize there's certain kinds of cases that happen over and over again. And if it's a dog or it's a flag flapping in the wind, we don't need to have a human look at that because we can use AI and machine learning to factor out that noise.

11:20And so what's happened over the time since we've launched it is the monitoring has gotten a lot smarter and so it means that the human in the loop, our American trained team, is actually looking at the cameras at the times that it's most important to really look at and that they're able to prevent crimes. And if you look at our latest advertising campaign, you'll actually see live footage of crimes that we prevented. And there's nothing that tells the story like seeing what can happen and what you prevented for someone. And so it kind of takes the business metaphor and puts it on its head, which is in the past, security was really around intrusion monitoring.

12:05We're going to let you know when somebody breaks the barrier of your window or enters a door. And in this case, we're saying, no, no, no, we're going to get it before it even gets into your house. And so if you think about peace of mind, it's the ultimate peace of mind.

12:20Jason: How do you guys think internally about rolling out a product like that that originally doesn't financially scale? I mean, Hillary, what you just described there is really interesting. The original version of a product like this is very labor intensive. It's costly. And the reason that it ultimately makes business sense is because you're able to find all of these efficiencies in it that make it better. but you might not know exactly what that's going to look like at the beginning, or maybe even if it's possible technologically to get there. I mean, there's a lot of stories that I hear like this, right?

12:56Jason: Which is like, we rolled out this thing, and then because of machine learning and AI, it became a lot more efficient. But like, okay, what if it didn't do that? What if it actually wasn't able to become more efficient? Or maybe you rolled it out a few years ago before AI and machine learning was as good as it is now, or maybe you didn't even know that that was going to be possible. So I'm curious if you could take us inside the kind of thinking for rolling out a big product like that, that you know is addressing a need. It is coming out of consumer research. So you understand that there's value there.

13:28Jason: But you have to plot out over a course of time exactly how this thing is going to go from not making financial sense at the very beginning to making financial sense. Yeah, so I'm going to hand it back over to Chad in a second because he was really here when it first launched and he can talk about that in more detail. But you are making bets on these things and you can have hypotheses, which is that, you know, over time, technology costs are going to come down because that's a curve we've seen. I may not be able to exactly predict each element, but I can know that over time that cost is going to come down.

14:00I know that with machine learning and AI, I'm going to be able to get some upside. But how much is that upside? And so, you know, just from an analytic perspective, I would bucket and say I have different levers I think I can pull. I'm not exactly sure how much each lever is going to contribute, but I believe I have enough levers here that if we rapidly iterate, we can get to a better mousetrap. But, Chad, back to you. Yeah, that is well said. And if I think about this specific case, what became pretty clear from when we first heard the customer need to then first envisioning the solution to trying to figure out how if it could be feasible and profitable, we realized we had this wide range of assumptions.

14:50And no one really knew what the cost drivers would be. There were orders of magnitude differences in people's intuitions around what would happen. And so pretty quickly what we realized was we had to start prototyping, which is often a really important step to go through. I think it's one of these things as companies start getting bigger, they often start planning things so deeply they forget to prototype. And we try to be really careful about that and look for these opportunities where if we're diving headlong into some big, long project, have we prototyped that enough? Have we figured everything out?

15:28Have we tried the rapid iteration cycles? And that was one of the big unlocks here was the rapid prototyping that we did revealed that some of our assumptions were wrong and helped us get to a clear understanding of how we would get there. Now, it wasn't, as Hillary said, it didn't mean it was profitable day one. It's just the early iteration cycles could show you this curve we were going down, even from the very beginning. and then you take a bet that you can project that forward and you can continue to do that and so in this case it played out that way.

16:00Jason: Can you dig in a little bit more on that prototyping insight because that's really interesting so as a company grows what's the reason that you think people don't prototype? You're at scale and so your teams are used to dealing with problems that need to be designed very well. The engineering solutions, the product surface is going to be covered, it's going to be consumed by so many people that it draws teams into thinking things through very well, which is good. You want that. You do want your products when they launch to have been rigorously engineered and every eventuality thought through. But you don't want to apply that necessity to the very beginning of a project when you need to learn faster.

16:45And so I think it's a natural effect that happens to teams as they grow and they become these very capable, rigorous teams that develop products, that they want to do that planning and make sure everything's perfect. But you don't want it to be perfect at the start. You actually want some rough edges. You want the first thing you put in front of a customer, you actually, sometimes you want it to look a little ugly so that the customer doesn't feel too bad in telling you what's wrong with it. If it looks perfect, they might feel like they'd insult you. So you want to put some of those rough things in front of customers.

17:17You want to try things very fast. And sometimes it takes a reminder to a team to go through that phase and not plan everything out from the start. Right. Because it's an interesting

17:32Jason: incentive issue, isn't it? You've got people whose jobs are to rigorously design things, to perfect things. And it's not always somebody's job to kind of make the fast, ugly prototype thing. And so in a way, what you need to do is take this process that everyone feels invested in and almost push back against it for the benefit of the slower moving. no, slower moving isn't the right word, for the part of the process that isn't as sleek and exciting. Yeah, I think that's right. I mean, you want to have a phase where you will throw things away. And if your team is designing it to have the perfect scalability right from the start, they're going to feel really attached to how well developed that solution is.

18:39With a prototype, when you hand it over to the team to make it perfect, you kind of want them to say, this is what you built? This is crap. This is terrible. And that's kind of what you want because that was doing that fast work. You don't want to be too attached to it. You want to be willing to say, that was totally wrong. That was totally wrong. Ooh, here's something. Okay, let's go build that. Mm-hmm.

19:02Jason: Mm-hmm. Hilary, I'm curious your perspective coming into a company like this. It's gone through so much of this growth, so much of this innovation. It's been a market leader. How do you think about where a company like this goes next? What is the next series of rough prototypes? What is the next series of understanding an even deeper need or concern that your customer has that they might not be articulating in quite the clearest way? Yeah, I think it goes back to almost where we started, Jason, which is who's your target customer? And, you know, right now we have a customer that we really like that we have developed this broad based system for.

19:44But as we've added more cameras, more sensors and more intelligence, it's become a more expensive system. And so the question then becomes, okay, can we introduce a value solution that isn't targeting the exact same customers? So maybe I don't want full intrusion plus outdoor monitoring plus fire plus water. All I really care about is I want a camera. And can we offer a camera that can give you that active guard kind of service without having you buy everything else that we're selling today? And there's a risk aversion in companies. It's the innovator's dilemma of if I launch a new service and I'm charging less for it, am I going to lose my customers because they're going to swap into the lower priced product?

20:40And so that's where the prototype comes into it. into play again. And you have to say, can we serve two customer groups that have a similar need, but maybe different financial constraints? And how would I approach that in a way to broaden the number of customers I can reach with a really differentiated set of experiences?

21:03Jason: That requires a level of really nuanced understanding of your customer and how to segment them. How do you suggest entrepreneurs approach that? It's really listening to your customer in every single way possible. So, you know, the best intelligence, some of the best intelligence we get is actually through our customer support teams, whether they're the monitoring teams or they're the teams who are taking the technical support calls or the questions about how do I use my system or how do I change something. Now with these large language models, we can upload all the transcripts that we get from our customers and we can start understanding them in much more detailed ways to be able to say what are their pain points and how many customers is this a pain point for and what would a solve look like and does that have sufficient value for them?

22:02Jason: That's really interesting. So you're able to see across so many different conversations what people are looking for. And then you need to kind of go back to the same basics that we were talking about at the beginning, which is, all right, they're articulating something here. And maybe we don't need to treat them like product developers, but what is the underlying thing that's driving them? And one final thing that I wanted to pull on that, Hilary, you just said, which reminded me. this feels appropriate because this conversation here is coming out of an old episode that I always reference, and now I'm going to reference another episode in this one, which is that I had a conversation a long time ago with Richard Dixon, who at the time, he's now the CEO of Gap, but at the time he was president of Mattel, and he had been brought back to revive Barbie because sales of Barbie had been declining.

22:55Jason: And I asked him, well, how do you even start on a project like that? And his answer, very similar to your answer, was you go back to the fundamentals of what made this company great in the first place? What was the point of it and why did people like it at first? What worked? It's interesting to think about, and I'd love to just hear both of your reflections on this as a final point. It's interesting to think about the question of that with SimpliSafe because if you go back to the really early days, the answer was this is a company that's here to help renters who are underserved in the home security market.

23:32Jason: But actually, what you found out was that the company's real purpose, or at least correct me if I'm wrong, I didn't build Sibley Safe, but it was to make home security as easy and affordable as possible. That seems to be the thing that actually drove it in the very beginning. And you don't want to, it's easy to lose sight of that as a company tries to build and build and build and add and add and add and add, right? Absolutely. And so it really comes back to, I think, Chad set up a really clear mission here, which is every home secure. And I think the added insight we have right now, it's not just the home, but the home's a metaphor for those you love.

24:16And so now as we look at our mission, it's really on how do we deliver on that value proposition about being an affordable solution that delivers differentiated protection, which is what makes the company successful. Chad, final thought here.

24:37Jason: What would you advise founders to do to keep an eye on what makes their company great as that company changes? I'll make a shocking statement here that the companies that become the most valuable over the long term are the ones that create the most value. In the short run, you can become a valuable company by capturing some value or moving some numbers around. But if you're really going to be a valuable company over the long term, it comes down to value creation. And there's really two ways to create value. You either make something better that is worth more and customers are more willing to pay for, or you take cost out of the system somewhere.

25:26You make it more efficient, lower cost. And you can choose what to do with that value you create. Maybe you give some of that value to your customers and you give them a great deal. It's at a low price for a great value and you grow faster. Maybe you capture some of that value and you have to pay amazing engineers to keep making great products. So you have to charge an appropriate amount for it. But ultimately, what it comes down to is creating a lot of value. So the two things that I think we've talked about today are differentiating your offering by either creating a more affordable solution, taking costs out of the equation.

26:05That was really the original SimpliSafe story in a lot of ways. people weren't searching for a DIY home security system. They were searching for an accessible, affordable, easy home security system. DIY, doing it yourself, was a way to enable that. Fundamentally, it took a lot of cost out of it. And that became a great value for customers. And that's one of the reasons we've done so well. One of the things we've done most recently is actually to create a lot of value on the other end by creating this service that actually protects you before anything bad happens. by intervening when people are outside your home before they've even come to the door.

26:42That's something that people are even willing to pay more for. And again, we won't charge all the way up to that. We want to give those customers a lot of that value so that they benefit from it. But that's where the value, that's where you create a valuable company from, is pushing on those ends and not being complacent about that. I think it's easy to think once you've found product market fit that you're done. but you're not. You have to keep looking for ways to create more and more value.

27:11Jason: Well, Henry Ford didn't say exactly that, but I'm sure he thought exactly that. Chad, Hillary, it's so great to have you. Chad, to have you back on the show. Hillary, to meet you. And congratulations on hitting the 20-year mark at Simply Safe. And we'll talk 20 years from now. And I'm sure there'll be a lot more of the journey to review. Really appreciate your time. Looking forward to it. Thanks. Thank you.

27:37Oh, yes.

From the publisher

 SimpliSafe was built for renters. Renters didn't buy it. Homeowners did. Jason has told that story for years, because it's a perfect lesson in how founders get their customer wrong. But he never asked the obvious follow-up: once you finally find the right customer, then what? Now, 20 years in, SimpliSafe founder Chad Laurans and CEO Hilary Schneider reveal what comes after product-market fit, and why customers asking for "more cameras" didn't actually want more cameras.

This episode of Problem Solvers is presented by AT&T Business. To learn more about how the right connectivity can help support your business as it grows, visit att.com/smallbusiness.

Jason wants to help solve your impossible problem! Click the link below to sign up:

https://entm.ag/levelup2026

0:00 The "faster horses" myth

0:29 Welcome to Problem Solvers

0:46 The SimpliSafe origin story: renters vs. homeowners

2:21 What happens after product-market fit?

2:55 Meet the guests

3:47 What product-market fit actually feels like

5:11 Should you build everything customers ask for?

6:11 Why you have to keep asking "why"

7:14 From "more cameras" to crime prevention

8:17 Fact check: Henry Ford never said it

9:22 What customers really want: peace of mind

10:02 Making a costly service profitable with AI

11:44 Launching a product that doesn't scale yet

13:48 Why big companies forget to prototype

16:51 Build things you're willing to throw away

18:26 What's next for SimpliSafe

19:48 The innovator's dilemma of a cheaper product

20:31 Mining customer support calls for insight

21:52 Go back to what made you great

23:22 The mission: every home secure

23:57 Long-term value comes from creating value

26:33 Wrap-up
Learn more about your ad choices. Visit megaphone.fm/adchoices

More from Problem Solvers

All episodes