Their frustrations
Understand the specific problem they are experiencing.
Strategy
Identify a real customer problem, develop alongside the people experiencing it, and keep technology and features focused on what they need.
The quick take
A good hardware product idea starts with a specific problem that real people actually have. Technology exists to serve those people.
Identify a few potential customers who already experience the problem you want to solve.
Understand the specific problem they are experiencing.
Learn how they are dealing with the problem today.
Find out what they would actually value in a solution.
Business-to-business products can be particularly attractive because problems are often measurable in wasted labor, lost revenue, or unnecessary expenses.
Show sketches, rough prototypes, and early demonstrations. Observe their reactions and let their needs and preferences help guide the design.
Think about throwing the biggest party at school.
You could spend a fortune on decorations, horses, or even a flying trapeze artist.
But people have incredibly successful parties in literal cornfields or on beaches, with almost nothing except a safe place for everyone to gather.
The people make the party. The attractions don't.
Customer needs guide the direction, while engineering limitations, manufacturing costs, reliability, and supply chain constraints still need to be considered.
Unnecessary features and constantly chasing new ideas can increase costs, create scope creep, and obscure the original problem.
The AVA Labs approach
At AVA Labs, we encourage founders to stay firmly connected to their customers. The most promising products solve meaningful problems for real people.
A good hardware product idea starts with a specific problem that real people actually have.
One of the most expensive mistakes founders make is falling in love with a technology and then searching for a problem it might solve.
That's completely backwards.
Think about throwing the biggest party at school.
You could spend a fortune on decorations, horses, or even a flying trapeze artist.
But people have incredibly successful parties in literal cornfields or on beaches, with almost nothing except a safe place for everyone to gather.
The people make the party. The attractions don't.
Hardware development works the same way.
Technology exists to serve people, not the other way around.
Before investing heavily in development, founders should identify a few potential customers who already experience the problem they're trying to solve.
Understand their frustrations, how they're currently dealing with the problem, and what they'd actually value in a solution.
Then develop alongside those customers.
Show them sketches, rough prototypes, and early demonstrations. Observe their reactions and let their needs and preferences help guide the design.
Of course, engineering limitations, manufacturing costs, reliability, and supply chain constraints still need to be considered.
But the underlying direction should come from the people you're trying to serve, not from whatever technology happens to be interesting.
Without that grounding, development can quickly turn into an expensive art project.
Founders start adding unnecessary features, chasing new ideas, and losing sight of the original problem. Costs increase, scope creeps, and confusion takes over.
At AVA Labs, we encourage founders to stay firmly connected to their customers throughout development.
Business-to-business products can be particularly attractive because the problems are often measurable in wasted labor, lost revenue, or unnecessary expenses.
The most promising hardware products aren't necessarily the most technologically impressive. They're the ones that solve meaningful problems for real people.
The people come first. The technology exists to serve them.