Live data from Hacker News

How we were building the wrong product

kilometer.io

21–29 of 29 posts

Re: How we were building the wrong product

#21

Earlier quoted context omitted.

It's the difference between a vitamin and a pain-killer. You want to make pain-killers, because people need them. Vitamins can be helpful. But people don't usually need them.

I would have put money on this example being structured the other way around. People can live with pain; they can't live without vitamins. They only don't need vitamins in the same sense that people don't need oxygen.

Pretty sure that the post you're responding to meant "vitamin supplements."

Re: How we were building the wrong product

#23

Earlier quoted context omitted.

I would have put money on this example being structured the other way around. People can live with pain; they can't live without vitamins. They only don't need vitamins in the same sense that people don't need oxygen.

Pretty sure that the post you're responding to meant "vitamin supplements."

That's it, thanks.

Re: How we were building the wrong product

#25
Yep, users don’t see the value in the product (as shown in the email from the user). “plug&play analytics” does nothing to explain what’s new and why it’s worth my time.

Based on the info from the post, there was no specific need and ideal customer profile in mind for creating this product.

It’s not like an unknown problem, but it’s crazy how often startups have fell in the “do stuff no one needs” and wasted months or years on it. It seems to be one of these things where you need to experience it yourself to understand it.

Re: How we were building the wrong product

#26

Will their next post be "How we were building something that already existed for the last 10 months"? Because this a lot like https://www.geckoboard.com/

Ideas don't have to be original to succeed. Not at all. Having an original idea doesn't even give you a leg up. It's all about execution and having an idea that is at least desirable.

That's what Alex is trying to do. He's trying to find that mix.

Re: How we were building the wrong product

#27

The fact that they feel the need to have mixpanel, segment.io and hotjar on their webpage doesn't exactly show confidence in the product :p Analytics is such a saturated market at this point. It will be interesting to see how things shake out in terms of consolidation / niches / price ranges. It is also interesting to me that they decided to invent yet another format in which customer data must be exposed. Just like…

I saw it mentioned while doing searches a while back and ended up on Quora where a Kilometer rep says in his post:

> our users often call us "Mixpanel on steroids" [1]

I then click through to find ironically, that Kilometer themselves use Mixpanel..

[1]: Screenshot: http://thumbsnap.com/i/kFfmeZEx.png?0310 (from https://www.quora.com/What-are-the-best-Mixpanel-alternative...)

Re: How we were building the wrong product

#28
post #8
post #5

> It took us almost 10 months to put our product in the hands of real users. Almost wondering if I should read the rest of the article at all... How did they expect to build the right product without collaborating with their target customers? Is this a company staffed by psychics? TLDR; Prototype with customers before you build anything.

You make it sound easy and obvious, but the problem is that customers doesn't actually know what they need. They know what they think they want, but they usually want something very much tailored to their business, using their ideas, and their workflows, but at a price of $10/month because it's a SaaS app. Building something that works for many customers means you actually have to come up with a very astute compromis…

We took similar actions at my recently failed startup, which headed on a slow, downward path. I identified an apparent pain in our target market based on past conversations with friends working in that space. My team and I felt we validated the pain because we kept hearing about it in our face-to-face interviews with potential users & buyers. One interviewee even went into mild theatrics half way through his interview, "Stop! This keeps us up at night because we ..." That was just the beginning of his 10 minute proclamation that the problem was worth solving, and that they'd pay a decent amount for the solution. Exactly how he said it.

We developed what we thought and what our potential customers claimed was a solution to an unmitigated problem in a very sensitive financial process. We followed startup advice and made it clear that we would charge for the solution. Fast forward a few months: usage dropped from supercharged to minimal then to nothing. Most of the customers we worked so hard to acquire went back to their old ways. When we did followup calls, their newer recruits were none the wiser that we even built something specifically for them. Clearly, the problem wasn't that important in the grand scheme of things.

Post reply on HN