Konrad Niemiec

Are we solving the problem of a product manager or a customer success person or a sales person or an ops person making a change to software safely? Like what problems are we actually solving with this tool and who needs this the most? And who is that initial user base? That was our biggest mistake was we were really focused on the solution instead of the problems that we were solving.

Are we solving the problem of a product manager or a customer success person or a sales person or an ops person making a change to software safely? Like what problems are we actually solving with this tool and who needs this the most? And who is that initial user base? That was our biggest mistake was we were really focused on the solution instead of the problems that we were solving.

Are we solving the problem of a product manager or a customer success person or a sales person or an ops person making a change to software safely? Like what problems are we actually solving with this tool and who needs this the most? And who is that initial user base? That was our biggest mistake was we were really focused on the solution instead of the problems that we were solving.

I think frankly, the feature flagging space solves a ton of different problems and even just listing them out takes a while. But once we made that shift, I think that was when we were really focused on our second version of the product.

I think frankly, the feature flagging space solves a ton of different problems and even just listing them out takes a while. But once we made that shift, I think that was when we were really focused on our second version of the product.

I think frankly, the feature flagging space solves a ton of different problems and even just listing them out takes a while. But once we made that shift, I think that was when we were really focused on our second version of the product.

We focused on simplicity and easy to debug and great developer experience, which we were focused on the whole time, but really through the lens of simplicity, because one thing we realized is we built a product that was a great solution, but it was actually very complicated and hard to get started. I think that was our biggest mistake with the first MVP.

We focused on simplicity and easy to debug and great developer experience, which we were focused on the whole time, but really through the lens of simplicity, because one thing we realized is we built a product that was a great solution, but it was actually very complicated and hard to get started. I think that was our biggest mistake with the first MVP.

We focused on simplicity and easy to debug and great developer experience, which we were focused on the whole time, but really through the lens of simplicity, because one thing we realized is we built a product that was a great solution, but it was actually very complicated and hard to get started. I think that was our biggest mistake with the first MVP.

An approach in general, I think, which led to a very complicated product that was tough to onboard to and tough to use. So we're really excited to hopefully have people see that it's very straightforward to get started with Leko and they can feel that benefit right away.

An approach in general, I think, which led to a very complicated product that was tough to onboard to and tough to use. So we're really excited to hopefully have people see that it's very straightforward to get started with Leko and they can feel that benefit right away.

An approach in general, I think, which led to a very complicated product that was tough to onboard to and tough to use. So we're really excited to hopefully have people see that it's very straightforward to get started with Leko and they can feel that benefit right away.

The future, maybe in the medium term, I'm super excited about. After we launch our free forever tier, we're looking forward to launching our team plan later this year. And with that, we're going to take a bunch of our learnings from some of our early guide customers and really help businesses organize the configuration of their product at a high level.

The future, maybe in the medium term, I'm super excited about. After we launch our free forever tier, we're looking forward to launching our team plan later this year. And with that, we're going to take a bunch of our learnings from some of our early guide customers and really help businesses organize the configuration of their product at a high level.

The future, maybe in the medium term, I'm super excited about. After we launch our free forever tier, we're looking forward to launching our team plan later this year. And with that, we're going to take a bunch of our learnings from some of our early guide customers and really help businesses organize the configuration of their product at a high level.

So right now with this launch, we're focused on the developer tool and obviously handing off control of software to other teammates across the business. But how can we actually use this to define the high level configuration of our product? What are the allowable configurations? Is it having these five features and a limit of 10,000 reads a month? Is that the team plan?

So right now with this launch, we're focused on the developer tool and obviously handing off control of software to other teammates across the business. But how can we actually use this to define the high level configuration of our product? What are the allowable configurations? Is it having these five features and a limit of 10,000 reads a month? Is that the team plan?

So right now with this launch, we're focused on the developer tool and obviously handing off control of software to other teammates across the business. But how can we actually use this to define the high level configuration of our product? What are the allowable configurations? Is it having these five features and a limit of 10,000 reads a month? Is that the team plan?

And then the enterprise plan has a scalable one. You can basically use Lecko to define that at a high level. And what that lets you do is it lets teams understand avoid untested code slipping to customers. You can really scope down what you can test and integration test. And we think it'll really have benefits across the business all the way to kind of retention and revenue and things like that.

And then the enterprise plan has a scalable one. You can basically use Lecko to define that at a high level. And what that lets you do is it lets teams understand avoid untested code slipping to customers. You can really scope down what you can test and integration test. And we think it'll really have benefits across the business all the way to kind of retention and revenue and things like that.