Transcript: Dedy Kredo | Qodo | Takhles Episode: How Do You Launch Fast in a Changing World?
Host: Eyal David · Guest: Dedy Kredo · Back to episode
· Updated:
A Takhles cut from the conversation with Dedy Kredo of Qodo: how to launch fast when the world changes every few weeks. Dedy explains why you need a strong insight and a big bet (for Qodo: the early realization that the enterprise needs processes, best practices and ownership of AI-generated code), how to balance value today against where the models are heading, and how a pre-release customers can roll back from helps you move fast without breaking them.
In this episode
- In a GenAI startup the game is win big or fail big: you need a strong point of view, an insight people aren't paying attention to today, and to go with it through a big bet.
- The sweet spot is usually a few months ahead: don't sink the bulk of your effort into something that will be obsolete in two months, but don't build too far out either.
- As a startup you don't have the luxury of waiting a year or two; you have to build things that deliver value today.
- Qodo's big bet: while everyone was excited about a prompt that generates code, they understood early that the enterprise needs processes, per-team best practices and developer ownership of AI-generated code.
- One way to move fast: a pre-release (beta/alpha) customers can switch to and easily roll back from to the stable release.
Taking bets: how it differs from classic product
Eyal David: [00:00] Taking bets, let's say, that's now so different from classic product management, or even from starting a classic business, right? Where you take a bigger percentage and now start casting lines, basically.
Win big or fail big: a strong point of view and a big bet
Dedy Kredo: [00:13] Yes, it's basically, it's kind of, it's basically either win big or fail big. Yes, you, you, you basically have to have some point of view. I started talking about this a bit earlier, you need some strong point of view, where you know how to say okay, I believe I have some insight here, that it's something people don't pay enough attention to today, and that this is where it's heading. Our example, say, was in the worlds where all the excitement was around wow, I give a prompt and it generates code for me, suddenly I have a working website, and that's amazing. Yes, it really is amazing. Yes, but we understood relatively early that for it to work in the enterprise you need other processes, you need to be able to define best practices per team, per organization. You need to have definitions of what you're willing to deviate on and what you're not willing to deviate on. You basically need to have the ability to, to let developers take ownership of AI-generated code, which by the way is an unsolved problem, even the UX of this thing, how it's going to happen. You need to have some strong insight that you believe in, you need to go with it, and you really need to make a big bet in order to do this. Another area that's very interesting to think about is basically, you, if you're building a product that's GenAI first, you constantly need to think about where this is heading. Meaning, what the models will be able to do a month from today, three months from today, a year from today. It's very hard to predict. And you need to have some point of view on this, and you need to find this balance between, on one hand, as a startup you have to build things that deliver value today. You don't, you don't have the luxury to wait to build something for another year or two, and you need to find this sweet spot. I think this sweet spot is usually some few months ahead. Meaning, you don't want to invest the bulk of your effort in something that will be obsolete in two more months, right? And on the other hand, you, if you build too far out, it doesn't, it just doesn't work in the startup world. So finding this balance is, is, is, is hard.
Innovation on steroids and pre-releases
Eyal David: [02:23] It's hard, and it's even harder, I think, because the expectation now is also for much higher-quality products, right? And what you're describing is let's run as fast as possible, build something, not that it's scrappy, but that it delivers enough value and looks normal enough if it has some kind of interface, or that its results are good enough. Combining all that, like, it's innovation on steroids, I really don't know. The whole company has to rally behind it, that's how it sounds.
Dedy Kredo: [02:23] Yes, yes, totally. It's some kind of mode where on one hand you move very fast, and on the other hand you, you create some, some kind of mode. You, say, for example, just an example of what we're doing now: we're putting out a pre-release. Meaning, it's a kind of, like, you can think of it as a beta or alpha that we're already releasing, and customers can, say, switch to it and use it. We know it'll be a bit more fragile, more brittle, and they can go back, switch and go back to the stable release.
Eyal David: [03:18] That was a Takhles episode from Product Builder. Want to hear the full conversation? Look for it in the feed, and don't forget to follow us.