And again, at least in the situations I've seen with GRC teams, they tend to be smaller, but now really be able to force multiply.

So I think GRC engineering is that force multiplier, but it's really just APIs going into your GRC and you still have to understand what good looks like.

So if you're getting the data from whatever integration you're doing, you still have to understand what good looks like in your environment.

So it's not this binary.

And I think that the GRC professional in that situation becomes even more important because as the risk advisor to say, yeah, this is the information we're getting.

It looks okay, but it's not comprehensive or here's the gap that we're seeing.

So I think in some ways it's really great because it allows them to be a little bit more technical because they're learning APIs and they're pulling in the integrations and they're understanding the software that gives us the information or the software that we're testing.

So I guess in the way you teach GRC now to folks, how have you seen that education evolve?