Alex Wiltschko

you know, AI agentic, like, you know, kind of tool calls, like search and like research about the company, like synthesize, like yeah, exactly.

Um, yeah.

And like, you know, we do all that stuff, but to me, like the more interesting, you know, kind of disruptions underneath that are like one, like, you know, are people, do people even want to come into your interface anymore?

And this is, yeah, that's what I was going to ask.

Yeah, I think it's like, I think the right move is like hybrid headless, right?

I think the whole, look, if you wanted just like a backend database, you could use like Postgres, like Supabase, right?

And there's like PHP, my admin equivalents, like modern day ones, right?

Like Prisma has its own version of it.

that are OK or they're good.

But I think what most people actually want, especially in a business context, is you want the database, but you want to have proper permissioning.

You want to have proper collaboration.

And most importantly, you don't want to exclusively interface with the data through an agent.

You want to do that a lot of the time.

But it's really helpful to actually go in and see the actual data.

I think of it as the equivalent of, even though agentically you can generate all your code, and you should as a frontier developer, does that mean you never want to inspect any lines of code ever?

No.

You still want to see a diff of all the actual code files change, whether that's in your IDE or in GitHub or whatever.

And so I think the equivalent here is, like, you want to be able to drop down into a really nice interface.

And we've done some work around, like, kind of figuring out what's the best blend of the two, right?

So, like, with ChatGPT, for instance, we have kind of a first-class integration where you can go in through ChatGPT and, like, interact with your data and your table and say, like, hey, pull me, like, all the customers that are, like, waiting for an outreach from me.