Sagar Batchu

I think one interesting mistake that stands out is a lot of startups that are going through this kind of PMF journey often end up going down a path on products that they decide later that was actually the wrong path. That has happened to us several times. I think with the kind of high autonomy and high sense of experimentation that we have, we will often go down that path.

But I think it's always what's telling about a company is how you recover and how you take the learnings from that. So earlier last year, we actually ended up building kind of addition to our SDK product, which was a Docs product. And Docs is like an important part of any API, right? Every great API is going to have great Docs. But for us at the time, I think it was the wrong place of investment.

But I think it's always what's telling about a company is how you recover and how you take the learnings from that. So earlier last year, we actually ended up building kind of addition to our SDK product, which was a Docs product. And Docs is like an important part of any API, right? Every great API is going to have great Docs. But for us at the time, I think it was the wrong place of investment.

But I think it's always what's telling about a company is how you recover and how you take the learnings from that. So earlier last year, we actually ended up building kind of addition to our SDK product, which was a Docs product. And Docs is like an important part of any API, right? Every great API is going to have great Docs. But for us at the time, I think it was the wrong place of investment.

And we had actually committed a bunch of our customers to launching a Docs product for them. Obviously, when we realized we couldn't make that happen, that was worrying for us. Obviously, the time spent and all of that, but also we had committed to help a number of customers.

And we had actually committed a bunch of our customers to launching a Docs product for them. Obviously, when we realized we couldn't make that happen, that was worrying for us. Obviously, the time spent and all of that, but also we had committed to help a number of customers.

And we had actually committed a bunch of our customers to launching a Docs product for them. Obviously, when we realized we couldn't make that happen, that was worrying for us. Obviously, the time spent and all of that, but also we had committed to help a number of customers.

What we decided at that point was we were going to partner with a company, another company in the space, other companies in the space. And we ended up taking on a bunch of support work to help those customers of ours we had committed to. And we ended up even committing to building an integration with that partner company.

What we decided at that point was we were going to partner with a company, another company in the space, other companies in the space. And we ended up taking on a bunch of support work to help those customers of ours we had committed to. And we ended up even committing to building an integration with that partner company.

What we decided at that point was we were going to partner with a company, another company in the space, other companies in the space. And we ended up taking on a bunch of support work to help those customers of ours we had committed to. And we ended up even committing to building an integration with that partner company.

So our customers would not be left hanging in terms of seeing that vision of an integrated SDK and docs product. So I think we've had several experiences like that, but I think what's... It goes back to our culture on customer centricity. And even in that moment, I think the way we covered was important. I think we haven't left our customers hanging without documentation stories.

So our customers would not be left hanging in terms of seeing that vision of an integrated SDK and docs product. So I think we've had several experiences like that, but I think what's... It goes back to our culture on customer centricity. And even in that moment, I think the way we covered was important. I think we haven't left our customers hanging without documentation stories.

So our customers would not be left hanging in terms of seeing that vision of an integrated SDK and docs product. So I think we've had several experiences like that, but I think what's... It goes back to our culture on customer centricity. And even in that moment, I think the way we covered was important. I think we haven't left our customers hanging without documentation stories.

So I think that's one thing that stands out to me.

So I think that's one thing that stands out to me.

So I think that's one thing that stands out to me.

So we're at that interesting turning point as a company coming out of being a seed company and growing. I think for the product, I think about everything that we've done today is about building APIs. It's about working with your API spec, launching an SDK, distributing to your customers. It's all about build.

So we're at that interesting turning point as a company coming out of being a seed company and growing. I think for the product, I think about everything that we've done today is about building APIs. It's about working with your API spec, launching an SDK, distributing to your customers. It's all about build.

So we're at that interesting turning point as a company coming out of being a seed company and growing. I think for the product, I think about everything that we've done today is about building APIs. It's about working with your API spec, launching an SDK, distributing to your customers. It's all about build.

But when you think about an API and the journey a development team goes on, I think it's really more than that. It's build, it's test, and it's run. Those are three big phases that I see in the API lifecycle today that aren't really serviced by great products. I think there's point solutions and there's... kind of things at the end of the lifecycle and before the lifecycle.