Olivia Moore

What means something is how an enterprise is going to, what the enterprise is going to do with that.

Like once it gets into the system, how their processes are built, how their humans are going to deal with that.

So all that is really not in the system.

It's more so like in people's brains.

A lot of these contexts is like tribal knowledge, the operator's whole.

And to a certain degree,

they, it's not, it's super fragmented, no?

So actually by doing the work, we're going to learn a lot about this more conversational record or intelligence, but also we're going to start like cleaning the end systems of record just by doing the work very consistently, no?

Yeah, I mean, I think you're, so what you're doing by doing the execution, as I said, is one, creating a better understanding about the relationships of all these different entities.

So you're starting to connect the TMS, the CRM, the ERP, the Snowflake, the Notion page you have, the docs, everything is so disconnected.

You're going to start connecting it, but you're also going to start enriching the relationships of how to deal with those particular records, no?

So I guess the compounding comes from like two angles.

One is having clear or cleaner data sources, like literally the data points is going to make everyone's life easier, but also understanding how to relate those different entities across the business.

So I think it compounds from multiple angles.

Yeah, and I think if you think about it from a context perspective, the FDs are really just seeding this state graph.

If you try to model the business as a world model or a model of the business, you need to seed it somehow.

You can't just put the agent to work from day zero.

But then there's a point where there's a flywheel where the second and third and fifth deployment takes less time.

But I think the FDs are the ones like,

going into the business and starting to see all this context layer and actually leaving it there for like learning and the second and third one.