Corey Knowles

I'm going to build my own Stripe, actually.

Theoretically, you could do that.

But you're probably going to have a lot more bugs than Stripe is going to have, actually.

And so by outsourcing all that stuff that you don't want to handle and saying, Stripe, handle it for me, Stripe focuses on the problem and actually ensures there's less tech debt in that code, actually, just like with Retool.

And our hypothesis is that, and this has been true, I think, over the last seven, eight years for Retool, is a lot of the code that a engineer would write for internal tools were the tech debt really built.

is code that Retool should focus on and we will write it for you and we are fully focused on how do we deliver, laser focused on the best platform for building internal tools on top of.

And so you can eliminate all that debt.

Maybe the last analogy, because I really passionately believe in this, is kind of like BI tooling, where

If you were, if you asked me today to go build a dashboard, let's say of, you know, revenue over time, I would say, oh, I'll use Tableau.

I'll use Metabase.

I'll use Looker.

I'll use something like that.

And the reason I use a tool like that is so I can say, hey, all I have right is the three lines of SQL that are specific to my chart and I'm done.

I don't have to work on the database drivers, the authentication, the authorization, all that crap.

So that's kind of how I think about retools.

I think for that reason, tech debt is not that big of a concern.

But on the second part of your question, I think there are dangers.

I think we should walk in with eyes wide open.

I think the dangers, I would say, are mostly around...

how strong the guardrails are and are people breaking out of the guardrails without the engineers noticing.