Sagar Batchu

So that was our first product. That was really, we really focused on that API onboarding story. We ended up actually pivoting away from that because we realized to really scale that product, you had to catch companies at the right time. Literally, you had to catch them that week that they were going to launch the API, which is a really tough kind of go-to-market problem to work with.

So that was our first product. That was really, we really focused on that API onboarding story. We ended up actually pivoting away from that because we realized to really scale that product, you had to catch companies at the right time. Literally, you had to catch them that week that they were going to launch the API, which is a really tough kind of go-to-market problem to work with.

So I don't think it was the wrong product, but I think it was the wrong phasing. And so we decided to focus on something that every API out there could benefit from today. And we landed on SDKs as this really important part of the developer journey that most APIs miss.

So I don't think it was the wrong product, but I think it was the wrong phasing. And so we decided to focus on something that every API out there could benefit from today. And we landed on SDKs as this really important part of the developer journey that most APIs miss.

So I don't think it was the wrong product, but I think it was the wrong phasing. And so we decided to focus on something that every API out there could benefit from today. And we landed on SDKs as this really important part of the developer journey that most APIs miss.

The trade-offs we made were twofold. One of the biggest trade-offs is early on, you're trying to get momentum and velocity for yourself in any way possible. You need to find ways to just have a lot of really activity around your product every day. So you start learning about what users are doing.

The trade-offs we made were twofold. One of the biggest trade-offs is early on, you're trying to get momentum and velocity for yourself in any way possible. You need to find ways to just have a lot of really activity around your product every day. So you start learning about what users are doing.

The trade-offs we made were twofold. One of the biggest trade-offs is early on, you're trying to get momentum and velocity for yourself in any way possible. You need to find ways to just have a lot of really activity around your product every day. So you start learning about what users are doing.

So early on, we decided that we were actually going to build it in such a way that the product was self-hostable. In retrospect, that was actually a mistake. I think it wasn't the best decision at the time. Doing that, we incurred a lot more technical debt and we incurred a lot more really just things to do to make the product self-hostable from day one.

So early on, we decided that we were actually going to build it in such a way that the product was self-hostable. In retrospect, that was actually a mistake. I think it wasn't the best decision at the time. Doing that, we incurred a lot more technical debt and we incurred a lot more really just things to do to make the product self-hostable from day one.

So early on, we decided that we were actually going to build it in such a way that the product was self-hostable. In retrospect, that was actually a mistake. I think it wasn't the best decision at the time. Doing that, we incurred a lot more technical debt and we incurred a lot more really just things to do to make the product self-hostable from day one.

I don't think we really optimized for getting it out to as many customers as possible. And so I think that was a pretty hard learning for us was that early on, we really had to optimize for getting it out into the hands of as many customers as quickly as possible. And that's one thing I think most founders will tell you that early on, you're just optimizing for user growth, velocity and feedback.

I don't think we really optimized for getting it out to as many customers as possible. And so I think that was a pretty hard learning for us was that early on, we really had to optimize for getting it out into the hands of as many customers as quickly as possible. And that's one thing I think most founders will tell you that early on, you're just optimizing for user growth, velocity and feedback.

I don't think we really optimized for getting it out to as many customers as possible. And so I think that was a pretty hard learning for us was that early on, we really had to optimize for getting it out into the hands of as many customers as quickly as possible. And that's one thing I think most founders will tell you that early on, you're just optimizing for user growth, velocity and feedback.

So I think that was one trade-off and another one for us. I think another really important learning was that when you're shipping something to your customers, that their end users are going to actually use, you need to really focus on design and design engineering. And this is, again, something that I think we didn't spend enough time on at the time was,

So I think that was one trade-off and another one for us. I think another really important learning was that when you're shipping something to your customers, that their end users are going to actually use, you need to really focus on design and design engineering. And this is, again, something that I think we didn't spend enough time on at the time was,

So I think that was one trade-off and another one for us. I think another really important learning was that when you're shipping something to your customers, that their end users are going to actually use, you need to really focus on design and design engineering. And this is, again, something that I think we didn't spend enough time on at the time was,

Even though we were making portal components that you could theme yourself, it's really important to give users the right hooks into these JS components so they can actually theme it. And we didn't actually spend enough time figuring that out. We ended up, again, having to spend a lot of time with each customer, helping them theme and build these portals for their APIs.

Even though we were making portal components that you could theme yourself, it's really important to give users the right hooks into these JS components so they can actually theme it. And we didn't actually spend enough time figuring that out. We ended up, again, having to spend a lot of time with each customer, helping them theme and build these portals for their APIs.

Even though we were making portal components that you could theme yourself, it's really important to give users the right hooks into these JS components so they can actually theme it. And we didn't actually spend enough time figuring that out. We ended up, again, having to spend a lot of time with each customer, helping them theme and build these portals for their APIs.