Sagar Batchu

And I think in the SDK product is super important because an SDK at the end of the day is a representation of your product and your engineering brand. A great SDK looks great to customers. A bad SDK looks like you're not investing in maintenance and engineering.

And I think in the SDK product is super important because an SDK at the end of the day is a representation of your product and your engineering brand. A great SDK looks great to customers. A bad SDK looks like you're not investing in maintenance and engineering.

And I think in the SDK product is super important because an SDK at the end of the day is a representation of your product and your engineering brand. A great SDK looks great to customers. A bad SDK looks like you're not investing in maintenance and engineering.

It's only been a little under two years and it's already a pretty long journey. I think one thing that stands out, I think to me that Speakeasy has done really well is building our customer relationships. I think a lot of developer products have great products. At the end of the day, these teams are all like great builders and the ideas are amazing.

It's only been a little under two years and it's already a pretty long journey. I think one thing that stands out, I think to me that Speakeasy has done really well is building our customer relationships. I think a lot of developer products have great products. At the end of the day, these teams are all like great builders and the ideas are amazing.

It's only been a little under two years and it's already a pretty long journey. I think one thing that stands out, I think to me that Speakeasy has done really well is building our customer relationships. I think a lot of developer products have great products. At the end of the day, these teams are all like great builders and the ideas are amazing.

But I think building a kind of company, culture and organization that really prides itself with respect to how it handles its customers, I think is somewhat underrated in developer tooling. I think what I'm most proud of is just the customer relationships, the level of support kind of care that we're able to give our customers.

But I think building a kind of company, culture and organization that really prides itself with respect to how it handles its customers, I think is somewhat underrated in developer tooling. I think what I'm most proud of is just the customer relationships, the level of support kind of care that we're able to give our customers.

But I think building a kind of company, culture and organization that really prides itself with respect to how it handles its customers, I think is somewhat underrated in developer tooling. I think what I'm most proud of is just the customer relationships, the level of support kind of care that we're able to give our customers.

I think our median response time is something like 2.4 minutes or something, even as we scale. And it's just, for me, to every person developing actively on the product, to those doing sales, product marketing, I think we really care about making our customers successful. It goes hand in hand with our product, right?

I think our median response time is something like 2.4 minutes or something, even as we scale. And it's just, for me, to every person developing actively on the product, to those doing sales, product marketing, I think we really care about making our customers successful. It goes hand in hand with our product, right?

I think our median response time is something like 2.4 minutes or something, even as we scale. And it's just, for me, to every person developing actively on the product, to those doing sales, product marketing, I think we really care about making our customers successful. It goes hand in hand with our product, right?

We're this kind of embedded product that, you know, when we launch with a customer, they're often like doing an SDK API launch. And so we're part of that launch and we're part of helping them boost their end users.

We're this kind of embedded product that, you know, when we launch with a customer, they're often like doing an SDK API launch. And so we're part of that launch and we're part of helping them boost their end users.

We're this kind of embedded product that, you know, when we launch with a customer, they're often like doing an SDK API launch. And so we're part of that launch and we're part of helping them boost their end users.

So there's a lot of craft and care that goes on the product, but there's also a lot of craft and care that goes into learning support and just being there for our customers, making sure they're successful with their end users.

So there's a lot of craft and care that goes on the product, but there's also a lot of craft and care that goes into learning support and just being there for our customers, making sure they're successful with their end users.

So there's a lot of craft and care that goes on the product, but there's also a lot of craft and care that goes into learning support and just being there for our customers, making sure they're successful with their end users.

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.

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.