We don't start with a clever idea. We start with a product that already sells — and the same frustration turning up in its reviews, month after month.
Most product ideas begin in the wrong place: someone has a flash of inspiration and works backwards, trying to convince the world it needed the thing all along. It's a slow, expensive way to be wrong. The market has to be taught the problem exists before it will consider the solution, and most of the time it never does.
We work the other way around. Before we design anything, we look for a product that people are already buying — and paying attention to what they complain about once they own it. That's the brief. Not our imagination; their frustration.
Why existing demand beats a good idea
A product that already sells has answered the hardest question for us: do people want this and will they pay for it? That question has killed more good ideas than bad execution ever has. When we find a category with steady sales, we're no longer guessing about demand — we're free to spend our attention on something far more useful: what's still wrong with it.
And there's almost always something wrong. Look at the one- and two-star reviews of any established product and you'll usually find the same handful of complaints repeated in a hundred different voices. A strap that cuts off circulation. A part that fails after a year. A material that doesn't survive an Australian summer. Those repeated complaints are the most honest product brief you'll ever read, and it's sitting in public, for free.
A complaint has to be specific enough to build from
Not every gripe is useful. "I didn't like it" tells us nothing. What we're hunting for is a complaint that's specific, repeated, and fixable — the kind where you can already picture the change that would solve it. When the same functional failure shows up again and again, and one practical change would resolve most of it, you're no longer looking at a review. You're looking at a specification.
The test we apply is simple: could a single, well-chosen change solve roughly eighty per cent of the important complaints? If yes, and if that change can be delivered through better supplier selection, materials, or quality control rather than expensive new engineering, we're interested. If the only real fix is exotic and costly, the opportunity usually isn't worth it, however loud the complaints are.
We don't invent problems
The discipline that keeps this honest is refusing to invent problems customers aren't actually reporting. It's tempting to add a feature because it sounds clever, or to talk yourself into a complaint that isn't really there. We try hard not to. The problem statement has to come from real evidence — reviews, conversations, the things people say when they think no one in the industry is listening. If the frustration isn't real and repeated, there's no brief.
That's why we spend so much time inside communities rather than in front of whiteboards. The people who live with a product every day already know exactly what's wrong with it. Our job isn't to be cleverer than them. It's to listen closely, notice the pattern, and turn it into something better made.
The complaints are the brief. Everything we build starts with a frustration someone assumed was just how it is — and the quiet belief that it doesn't have to be.