Sagar Batchu

So this was everything from a DSL that we use internally to define and build APIs, infrastructure components like sidecars for authentication, a lot of tools to actually make the development and deployment of the APIs easy for every developer at the company.

When I left LiveRamp, I realized that this was a pattern that was happening across the industry at any company of scale, and even small startups. But the truth is not every company has the enduring time, talent, the kind of willpower to actually invest in great APIs. But not investing in great APIs means that you're really restricting your customers from getting the best of you.

When I left LiveRamp, I realized that this was a pattern that was happening across the industry at any company of scale, and even small startups. But the truth is not every company has the enduring time, talent, the kind of willpower to actually invest in great APIs. But not investing in great APIs means that you're really restricting your customers from getting the best of you.

When I left LiveRamp, I realized that this was a pattern that was happening across the industry at any company of scale, and even small startups. But the truth is not every company has the enduring time, talent, the kind of willpower to actually invest in great APIs. But not investing in great APIs means that you're really restricting your customers from getting the best of you.

I started to dabble in that. and really talk to users, work with developers in the space, it all started to revolve around OpenAPI, which is this kind of core description language for REST APIs. So that's where Speakeasy started. And through that process of iteration, we've now gotten to where we are, which is this growing platform of tools that help companies build and ship great APIs.

I started to dabble in that. and really talk to users, work with developers in the space, it all started to revolve around OpenAPI, which is this kind of core description language for REST APIs. So that's where Speakeasy started. And through that process of iteration, we've now gotten to where we are, which is this growing platform of tools that help companies build and ship great APIs.

I started to dabble in that. and really talk to users, work with developers in the space, it all started to revolve around OpenAPI, which is this kind of core description language for REST APIs. So that's where Speakeasy started. And through that process of iteration, we've now gotten to where we are, which is this growing platform of tools that help companies build and ship great APIs.

You're absolutely right. When we started, one of the core problems that we were working with was this idea that a lot of our customers were spending a lot of time, a lot of support time onboarding users onto the API. Like the table stakes for what they were providing the users was just the classic three pane documentation site.

You're absolutely right. When we started, one of the core problems that we were working with was this idea that a lot of our customers were spending a lot of time, a lot of support time onboarding users onto the API. Like the table stakes for what they were providing the users was just the classic three pane documentation site.

You're absolutely right. When we started, one of the core problems that we were working with was this idea that a lot of our customers were spending a lot of time, a lot of support time onboarding users onto the API. Like the table stakes for what they were providing the users was just the classic three pane documentation site.

Now, this is the classic left hand view, middle view, right hand view you've probably seen for a lot of API docs. And that just wasn't enough. That, to me, felt like the lazy thing to do, throw up a Swagger doc site and send it to your customer.

Now, this is the classic left hand view, middle view, right hand view you've probably seen for a lot of API docs. And that just wasn't enough. That, to me, felt like the lazy thing to do, throw up a Swagger doc site and send it to your customer.

Now, this is the classic left hand view, middle view, right hand view you've probably seen for a lot of API docs. And that just wasn't enough. That, to me, felt like the lazy thing to do, throw up a Swagger doc site and send it to your customer.

We actually started to innovate around a set of React and developer portal components that would allow you to stitch together a really interactive and guided onboarding experience.

We actually started to innovate around a set of React and developer portal components that would allow you to stitch together a really interactive and guided onboarding experience.

We actually started to innovate around a set of React and developer portal components that would allow you to stitch together a really interactive and guided onboarding experience.

So you can, if any of you have used like the Stripe API or GitHub's API or some of the other great APIs out there, you'll see that as part of that first step of onboarding you to the API, they have a beautiful portal where you can immediately get your API key. You can understand your usage. You can basically walk through all the elements of the API in a very guided and beautiful UX.

So you can, if any of you have used like the Stripe API or GitHub's API or some of the other great APIs out there, you'll see that as part of that first step of onboarding you to the API, they have a beautiful portal where you can immediately get your API key. You can understand your usage. You can basically walk through all the elements of the API in a very guided and beautiful UX.

So you can, if any of you have used like the Stripe API or GitHub's API or some of the other great APIs out there, you'll see that as part of that first step of onboarding you to the API, they have a beautiful portal where you can immediately get your API key. You can understand your usage. You can basically walk through all the elements of the API in a very guided and beautiful UX.

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.