Eran Zinman

After 14 or 15 months, I didn't raise any money. I just felt I wasn't ready. And eventually it was a big failure. I ran out of money, personal money, and ran out of energy. I remember thinking to myself after I closed that company, I wasted all my resources, you know, personal, financial. I'm at point zero. I must have learned something. I didn't spend all that time without learning anything.

After a lot of processing, I realized that I've learned that the reason I failed in that company is that I was afraid to fail. It might sound weird, but I was so afraid of negative feedback from customers. I was afraid people are going to write about me on TechCrunch or on a blog post. I thought people are going to be critical of my product. I don't know. I was just afraid.

After a lot of processing, I realized that I've learned that the reason I failed in that company is that I was afraid to fail. It might sound weird, but I was so afraid of negative feedback from customers. I was afraid people are going to write about me on TechCrunch or on a blog post. I thought people are going to be critical of my product. I don't know. I was just afraid.

After a lot of processing, I realized that I've learned that the reason I failed in that company is that I was afraid to fail. It might sound weird, but I was so afraid of negative feedback from customers. I was afraid people are going to write about me on TechCrunch or on a blog post. I thought people are going to be critical of my product. I don't know. I was just afraid.

And I swore to myself that when I build my next company, I'm going to fail. I'm going to fail often. I'm going to be happy about failures because I want to learn as quickly as I can. and improve and get actual feedback from users.

And I swore to myself that when I build my next company, I'm going to fail. I'm going to fail often. I'm going to be happy about failures because I want to learn as quickly as I can. and improve and get actual feedback from users.

And I swore to myself that when I build my next company, I'm going to fail. I'm going to fail often. I'm going to be happy about failures because I want to learn as quickly as I can. and improve and get actual feedback from users.

Because after 14 months working on that product, people gave me feedback that if I've shown them like a mock-up or like an early version, I would get the same feedback and I would be in a totally different place today. And we keep that DNA up until today on Monday. We fail, we tell people, try it out. A, B test. Get feedback from customers. Just learn.

Because after 14 months working on that product, people gave me feedback that if I've shown them like a mock-up or like an early version, I would get the same feedback and I would be in a totally different place today. And we keep that DNA up until today on Monday. We fail, we tell people, try it out. A, B test. Get feedback from customers. Just learn.

Because after 14 months working on that product, people gave me feedback that if I've shown them like a mock-up or like an early version, I would get the same feedback and I would be in a totally different place today. And we keep that DNA up until today on Monday. We fail, we tell people, try it out. A, B test. Get feedback from customers. Just learn.

And it's a big part of our DNA today as a company.

And it's a big part of our DNA today as a company.

And it's a big part of our DNA today as a company.

Growing up, writing code, I was always this smart kid in school, in uni. When you build an actual product that people need to use, nobody cares about your achievement or knowledge or how much you know about anything. It's all about the product. Is it good enough? Do people really want it? It's not about an exam. It's not about somebody saying great job.

Growing up, writing code, I was always this smart kid in school, in uni. When you build an actual product that people need to use, nobody cares about your achievement or knowledge or how much you know about anything. It's all about the product. Is it good enough? Do people really want it? It's not about an exam. It's not about somebody saying great job.

Growing up, writing code, I was always this smart kid in school, in uni. When you build an actual product that people need to use, nobody cares about your achievement or knowledge or how much you know about anything. It's all about the product. Is it good enough? Do people really want it? It's not about an exam. It's not about somebody saying great job.

It's about actually succeeding in the real life. And I think I was not ready for that. I tried to not fail. I wanted everybody to clap and say, this is an amazing product. And this is not the way you build things. You need to get feedback. You need to get people involved, get their opinions.

It's about actually succeeding in the real life. And I think I was not ready for that. I tried to not fail. I wanted everybody to clap and say, this is an amazing product. And this is not the way you build things. You need to get feedback. You need to get people involved, get their opinions.

It's about actually succeeding in the real life. And I think I was not ready for that. I tried to not fail. I wanted everybody to clap and say, this is an amazing product. And this is not the way you build things. You need to get feedback. You need to get people involved, get their opinions.

Oh, yeah.