 in the platform technology or the product technology world, more often than not, you're gonna see people use the word assessment. We deliberately use the word discovery because discovery for us means, let's find out what we don't know before we make decisions. And what we find is that people come to us and they ask the question, what tool should I be using? And we kind of go back and say, that's the wrong question. The question is, what is it are you trying to accomplish? And what questions should you be asking? And what is it that we don't know? And so we are more often than not recommending rather than an implementation project or a design project or a build, we're saying, let's do a discovery. Now, it's important to understand that discovery is not something new. It's something that you actually have to do no matter what you're going to do. But by splitting that out as a separate project, you're basically saving yourself from the things you don't know. So at the end of the day, while it might seem like it's something new or something additional, it's actually the first phase of any project and by making it a separate project, you're accomplishing two things. One, you're mitigating risk and two, in the long run, you're lowering costs, which are absolutely two goals that I think every project should and probably does have. So a discovery is basically where you're doing all of that exploration of what are the actual problems we're trying to solve? What are the business needs? What are the gaps? What are the risks? What will it take to actually implement this? What do we need to design? Do we need to do a technical proof of concept before we implement anything? And all of that, which can represent anywhere between 40 to 60% of the actual cost of the project, will actually, on the other end,