Eilon Reshef: evaluation

Transcript context

…What are the percentage of success rate you have with new products because you would think this approach is the best way to consistently build products people will end up buying and using. Is it like 100% of the time you end up building things that people will buy and use, is it something below that? What do you find? I think it does increase significantly the utility of the products, I would say very close to 100% of the features we build end up being used by a significant number of people. We don't charge for all of them, for most of them we don't charge, which doesn't mean other things couldn't happen, maybe people use it, but the value is not huge. So, it's like yeah, design partner like it, but it ends up being applicable to a smaller fragment or segment of our customer base than what we had hoped. It may be they're not as willing to pay for it, although that's a little bit of a different process, like real product launch. It could be the quality is not good enough because we're focusing on, is it providing value, is it understandable versus did you find a bug when you used, I don't know, Safari, on this kind of computer. Because we're not building the design partner program to solve for this, maybe we should, but we are not doing it right now. But generally speaking, I would say better than that, more than 95% of the capabilities we build are being used in a very significant way. Which I think is probably higher than most companies. And this feels like a cheat code of how to build new product lines, expand a product expansion, TAM expansion, like ways to add new ways to charge your existing customers, and it feels like a cheat code basically, just tell us what you need, we'll work with you and build it and we'll sell it to you and it'll be great.…

Stored transcript either side of the excerpt. The highlighted words are the published quote; the surrounding text is unedited source, never generated.