Companies / SharkNinja

Company case

SharkNinja

Software-speed scaling on a hardware cost structure

Mockup Prototype Approve-Pivot-Kill Unit economics

SharkNinja launches about 25 new products a year across 38 sub-categories, from vacuum cleaners to LED face masks, and spends 7% of revenue on R&D in an industry where rivals spend 1% or less. In eighteen years it grew from two sub-categories and $250 million to 38 and $6.4 billion. Chapter 13 treats it as the proof that lean methods work in hardware, for a company that stamps, moulds and assembles what it sells.

Each cycle starts with around 65 ideas, of which 40 die. Some are killed after a prototype lands in a consumer's home and the reaction is lukewarm. Some never get that far: the team mocks up the packaging, shows it to consumers, and reads the response before a unit is built. The research team visits hundreds of homes a year and runs no focus groups; it watches people use products and looks for the problems they have stopped noticing. A decade in power tools ended with a decision to walk away; eight years in carpet cleaners ended with a product that took 20% share within months.

The book's favourite SharkNinja story is a scope trap. An engineering team had connected a blender to a phone app. The CEO pressed the button, the blender started, and he asked the obvious question: the blender already has one button, so unless the app can put the bananas in, what is it for? The companion app is one of the most common scope traps in connected hardware.

The takeaway. Kill early and often, test the cheapest artefact that answers the question, and be suspicious of any connected feature that does not remove work from the user.

Where it appears in the book

Paraphrased from Tangibles: How Software Turns Hardware into Platforms (2026). Sources for every figure are on the reference pages.

← All companies

© 2026 Yoel Frischoff / TheRoad. All rights reserved. · About the Book · Press · Teaching · Glossary · References · Privacy · Terms · Accessibility