 So let's talk about what that means. So you're talking about if something critical or disaster occurred, you're talking about not losing a day's worth of data, but maybe 15 minutes. Maximum. Big, big, big difference. Maximum. And there are paths. There's a disruption to the business. That's potentially hundreds of thousands or millions of dollars or more. Absolutely. And our client base is in the legal industry. They're in the financial services industry. We call them risk intolerant. I like to also call them high value content creators. If you have a lawyer making a very nice salary for every hour that he works, it's very important that he keep working. Because for every minute that he's not, and especially for every minute that email is down, he's not producing in the way that he should. Dave, we've got two minutes. I wanted to get one question in from my standpoint, then Dave's going to get one last question in. You guys are in the business cloud service provider business. And a lot of your vendors that support you have to have the cutting edge technology. Dave and I talked about cloud service for us being a key integral part of this new architecture. But what do they got to do to be successful? What do you say to the folks that are trying to interface with you and get you new technology? What are the key things that you need to run your business going forward? Not today, but with virtualization, it's going to enable a whole new set of requirements. What do you demand from the falcon stores of the world and other vendors? What do they got to continue to do or do differently? I think the biggest change is something that we have to push all our vendors very hard on. And you can call it whatever you like, on-demand business model, SPLA model, SPLA model. They have to be able to allow us to consume their services in an on-demand model as well. And we've had to fight that a lot over the last couple of years to reach that with all of our vendors. That's changing. It's changing very quickly. Additionally, we need rapid, agile development iteration cycles. I can't come to a vendor and say, this doesn't work right. And the guy will have that fixed six or eight months from now. No, it's got to be two weeks, four weeks, because you've got to match the speed of the market. And no one is going to sit around and wait for you to change a piece of code six months from now. No one. You'll move on.