Yeah

... well, do I turn it on for this one and not for this one, and is this one gonna overwrite what occurs here? And how do I like manage or govern, you know, what is going-- like is, is all this going into the same LLM? Do I have to go and maintain that? How do I make sure that somebody doesn't post like a Social Security number into the wrong place that goes and- So if I'm sat in IT and I say, "Hey, I want the marketing ops person to be able to have autonomy or control over building agents," do I want them to go and do it in a third-party application that requires additional governance, or would I rather have a consistent way that all these executions occur in one place?

Mm-hmm.

And I think one of the key components or challenges about a lot of these agent solutions is they rely on well-built-out integrations, and they rely on well-built-out, uh, integrations that can carry out action.

And I think over time, we'll see the AI get better at carrying some of that out on its behalf, you know, and building these, uh, uh, building connectivity itself.

But we're a ways away from that right now.

So I feel like there's gonna be a lot of kind of turnover in a lot of software stacks, experimentation with new applications, trying to find quite what fits.