Chris Pedregal

Is this like an unsolved open problem where you need to do some exploration? first and then figure out what the right solution is. For the one where you know what you need to build, at least from our experience, it's the basic advice that everyone hears, which is build the minimal thing as quickly as possible.

Is this like an unsolved open problem where you need to do some exploration? first and then figure out what the right solution is. For the one where you know what you need to build, at least from our experience, it's the basic advice that everyone hears, which is build the minimal thing as quickly as possible.

Give yourself deadlines where you will ship it to real humans, maybe not to everybody, to real people, and then try to increase the shipping iteration speed as quickly as possible. I think we've gotten in trouble before and it's easy to, is you don't know what mode you're in and you use that philosophy to the open-ended problem.

Give yourself deadlines where you will ship it to real humans, maybe not to everybody, to real people, and then try to increase the shipping iteration speed as quickly as possible. I think we've gotten in trouble before and it's easy to, is you don't know what mode you're in and you use that philosophy to the open-ended problem.

And then what ends up happening is you end up shipping something crappy to people and you ticked it off. You're like, oh, we shipped it in two weeks. This is great. But actually you didn't actually solve the problem to be solved. The thing you did was you shipped as opposed to figure out what is a great solution for people and do that.

And then what ends up happening is you end up shipping something crappy to people and you ticked it off. You're like, oh, we shipped it in two weeks. This is great. But actually you didn't actually solve the problem to be solved. The thing you did was you shipped as opposed to figure out what is a great solution for people and do that.

And interestingly, I'd say that is extra important in this space because there's so much pressure to move quickly that every now and then taking the extra time to think about how to do this is really important. A good example is we were working on Granola for a year before we launched. And we're so late to the AI note-taking game already. We were seven years late when we founded Granola.

And interestingly, I'd say that is extra important in this space because there's so much pressure to move quickly that every now and then taking the extra time to think about how to do this is really important. A good example is we were working on Granola for a year before we launched. And we're so late to the AI note-taking game already. We were seven years late when we founded Granola.

We didn't launch for a year. You know how I talked about that interaction, like we completely changed the core interaction of the product. If we had launched that publicly, we never would have been able to switch it. There's no way because users would have learned a new behavior. Users would have said, oh, this is cool.

We didn't launch for a year. You know how I talked about that interaction, like we completely changed the core interaction of the product. If we had launched that publicly, we never would have been able to switch it. There's no way because users would have learned a new behavior. Users would have said, oh, this is cool.

The ones who we would have retained would have liked it, but we wouldn't have retained that many users. That would have been it. I think that's very important to kind of protect your ability to change direction with the product until you have a lot of confidence that you're in the right direction. And how do you manage that while also moving in a really quickly in a fast moving space?

The ones who we would have retained would have liked it, but we wouldn't have retained that many users. That would have been it. I think that's very important to kind of protect your ability to change direction with the product until you have a lot of confidence that you're in the right direction. And how do you manage that while also moving in a really quickly in a fast moving space?

I ask myself if we're doing this correctly every day. Sam and I, when we started playing with LLMs, we became convinced that all the tools for work that we use are gonna be rebuilt or reinvented on top of LLMs. And we became convinced that there's gonna be like this new class of software

I ask myself if we're doing this correctly every day. Sam and I, when we started playing with LLMs, we became convinced that all the tools for work that we use are gonna be rebuilt or reinvented on top of LLMs. And we became convinced that there's gonna be like this new class of software

In the same way that if you were a developer, you probably spend all day in Cursor or Visual Studio, like some IDE. We think that there's gonna be a new class of software, it doesn't have a name yet, where people like you and I will spend all day in and we do our work in.

In the same way that if you were a developer, you probably spend all day in Cursor or Visual Studio, like some IDE. We think that there's gonna be a new class of software, it doesn't have a name yet, where people like you and I will spend all day in and we do our work in.

Folks whose jobs revolve around people and communication and projects and meetings and all that, there's gonna be a new workspace for those folks And that's what we set out to build from day one. And that's exactly what we're setting out to build now.

Folks whose jobs revolve around people and communication and projects and meetings and all that, there's gonna be a new workspace for those folks And that's what we set out to build from day one. And that's exactly what we're setting out to build now.

I think the interesting question for us is, it's really important if you're not an open AI or an anthropic, that you are really, really good at a use case today. You can't just be building a fantastic product in the future. You need to be damn useful at a very specific thing today. And every step along the way, you need to be super useful to people.

I think the interesting question for us is, it's really important if you're not an open AI or an anthropic, that you are really, really good at a use case today. You can't just be building a fantastic product in the future. You need to be damn useful at a very specific thing today. And every step along the way, you need to be super useful to people.