I really like what you said, you said it's experimentation is a way to de-risk, you know, web build product build.

That is a big part of how people misunderstand it because most people look at it and think, you know, we're trying to find winning tests. We're trying to find things that win little changes that can make us money. And ostensibly that is what it is, but that's not really the economic benefit of it. The economic benefit of it is that you are going to make better decisions about how to invest in web development. So you know, you have an agency or internal dev team and they've got a queue of stuff that they're doing and that's going to cost money. That's what you're going to spend your retainer on. Are you going to spend the salaries of all these people on? That costs money. And if that list has 10 things in it and you haven't tested them, regardless of what they are, as we know, probably one of those things is worth doing that's going to actually make you money. Some of them will detrimentally impact your revenue and you have no idea which is which. And so you're wasting a ton of money, like you're wasting 90% of that web dev investment. And by experimenting, what happens is A, you only do the things that work. So you've already proven that all of those 10 things will work and will deliver value. But B, experimentation is a much more efficient form of web development. So if you want to build something in production, that might take four days, it could take hours in an experimentation tool. And that's not an agency ripping you off or anything like that. It's basically, there is a lot more process and security and all that sort of stuff that goes with production web development. You don't need to do when you build a test. Obviously, you still need to QA and things like that. You don't go through the same process. And so it's much more efficient. So you're working through those ideas far more efficiently and then not doing the things that don't work. So you're saving just a huge amount of money, resource and everything plus only actually delivering to the website stuff that actually works. So the ROI potential of all that is insane. And you know, it's just frustrating trying to get people to understand that. And again, they just don't view it like that. They view it as like, can we get this button color change to make us some money? And then you get the problem that if they're not finding winning tests, if you go for a month without winning tests, they think, well, this isn't working. So let's not do it. Which again, based on what I was saying is just entirely the wrong way to

look at it.