 Evan has a question. Our business has some unique requirements that the standard SharePoint features don't fully address. What? Yeah. However, developing custom solutions can be resource-intensive. How do businesses typically balance using out-of-the-box features with the need for custom solutions? What factors should be considered in making this decision? That kind of goes back to what I just said about the other one. You really need to build something new if you can get 80% of what you need out of something that exists and maybe build the other 20. But yeah, it's time or money. You can move with an out-of-the-box solution or 80% and move forward or you have to go back and gather those requirements and figure out what people need. And following up on that, how much money do you have? And how much time do you have? That should answer that question. Maybe you have the resources to do it. Yeah. And there's a lot of plug-and-play solutions out there from third party suppliers. You know, sometimes you can find something that's really simple that will do it for you without having to build a ton of personalized content and start researching and the cost benefit of doing that. What are you trying to do? This is still for the job range. Yeah. I'd also add that from the SharePoint perspective, make sure you're familiar with the roadmap because some things that people are asking for, like as a PM in the SharePoint world, there's a lot of things people are asking for that are on the roadmap and they're in the pipeline, right? They're gonna come. So make sure that you're not spending money building custom solutions when we already have something that's on the way. Neil, you have to share that with us now. She can tell us all the sleep. The roadmap, come on. I'll share the public roadmap. I can give you a link too. You guys are all MVPs. You know where the other roadmap is. But like things like your SharePoint Premium, for example, right? There's a whole ton of features and capabilities and experiences coming on the pipeline with SharePoint Premium that we've never shipped before. So I think whoever asked this question didn't specifically mention what they were looking for. But I think experience, understand the roadmap, understand what it is you're trying to do. And to other folks' comments, right? Third parties provide solutions. There's usually a way to solve a problem without just sitting on the shelf waiting for it or investing like a massive amount of money just to make it happen. There's so many ways. Two minutes, there's multiple ways to skin that cat, as we say, right? Well, we're going back to the first question we addressed, the ROI and figuring that out is what are you trying to do? That sometimes, what's the gap in the functionality? What's the value of buying an off-the-shelf third-party solution today until the features come out in the future with Microsoft? And then other questions, like is, well, if Microsoft, out of the box or with some minor automation, give me 80% of what I need, is that enough of a difference for me and a cost difference? Well, I'm already paying for with Microsoft 365 that it doesn't make sense to go and buy the other things. So what is that value? What is the opportunity cost of not moving forward today with another solution versus waiting for that functionality to be there with Microsoft or going and building that? So there's a lot of those factors that's just back again to that ROI. And once you've defined what you're wanting to do, then you can define what tool makes sense. If you're trying to use Power Apps because you don't like the single column SharePoint form, well, maybe you don't need to go all the way to Power Apps, just throw some JSON in the form and give it a little bit better layout, maybe a little bit of extra functionality. If you don't like the list view, so you're using a Power Apps gallery to make the list view different, again, maybe a little JSON, grab a Chris Kent video, change your list view to look like what you want it to look like, and you've saved yourself a lot of time and a lot of maintenance. And one of the things that hasn't come up as we've been talking about this, and then Neil mentioned being able to look at the roadmap and going out there to see, because I always try to recommend to people if it's coming, maybe don't make it yourself. What I have noticed is over the last year or so, Microsoft has introduced a lot of customer engagement programs that didn't exist in the past. So if you're a business that is trying to make these decisions before, there was a lot of these for these large enterprise businesses, they're building more and more of those programs for smaller medium sized businesses. If you're interested in a specific feature set, reach out to a partner or an MVP, or somebody that you know that might be affiliated with Microsoft and see if potentially there is a customer engagement program that you could participate in, because two things happen. One, you might get the opportunity to use that feature earlier. And second, you can provide feedback that can influence what that feature does or how it goes forward, which means that you're gonna get more out of it and potentially maybe even get to do that for a lot cheaper than it would cost you to build it yourself.