So building off of what Alex just said, how are you evaluating what AI tools are worth integrating into the practice and then everything else that comes along with it?

Yeah, it's interesting seeing Alex's perspective because he's getting problems after they've been surfaced.

In the CTO role, you're getting thrown solutions, you're getting thrown symptoms.

And so I get like, okay, here's this cool AI tool.

And really the first step that we have to answer internally is what's the problem we're trying to solve? Is it measurable? Alex hit on that.

Can we actually put some metrics to it and measure how it's going to succeed? Are we measuring it now? How are we doing it without AI? Is it something that we can compare before and after? So we have to make sure that we've got the problem defined.

Is there a vendor pitch that really attracted someone but is just a bunch of flash? So number two is how integration ready is it really? Does it connect to Dell Tech? Does it connect to Revit, to Bluebeam even? How can we actually put it into our workflows? And then is the workflow that we, it depends on even something that the pipeline is accessible.

So what does managing what will ultimately be some amount of internal resistance look like through that process? Because as we just mentioned, people have ways they like to work, especially those who have been doing things a certain way for a while.