Santiago Suárez

But he was like, you're all idiots.

We're going to build a monorepo.

And the monorepo gives you, obviously, you know, for folks who don't know what the monorepo is, it basically means all your code is in a single repository.

So for agents to read it,

it's a lot easier than if you have multiple code bases in many parts of the org.

They also have some extreme economic advantages because there's very little duplication.

You reuse components almost automatically.

We have 60 product engineers supporting a gigantic product surface.

So Monorepo was kind of a canonical decision, one that allowed us to drive AI.

And the second one is,

You know, we built a company using an event sourcing architecture, which means that every single event that happens at this company gets logged.

And events are anything from we texted you to you add something to our shopping cart, to your bureau score, to your financial, everything.

You know, we generate over 10, what is it?

Over 10 million events per day.

So those two things were there.

critically, these event architectures we use Kafka for ours are brutal to query.

So that's why most people end up moving away from this.

And again, four years ago, no, five years ago now, we partnered with Databricks.

So what that means is you, in real time, are able to ingest these events and

showcased them in vector form for LLMs, SQL form for classical machine learning models, obviously tabular forms for still the humans we've got, because we do have some humans.