 Okay, and what I'm going to provide today is my personal or our personal Dr. Workpress made by someone who was a checklist. Today, we're being called a few times in the last few weeks by people asking us to do the support or hosting or further development of the Workpress site. And the agency did that, but the agency won't provide the most support. So before you should just say yes to such a contract, you might want to ask a few questions. And that's what I'm going to tell you today. So there are two situations you should face to see the most. The first could be the better situation. There's a completely over-precipitation made by the agency or three houses, and they don't do hosting or they do support, so they need another agency to do that, and that's cool because you obviously have to use Workpress in a version in New York City. We talk about everything, but it can still be a major problem, if you ask me. I thought that was very important. And then there's the situation of two, which we're facing currently. We have Workpress information in the version 3.5. Workpress doesn't even exist anymore. But it's four years old, and you might have a chance in that case to just look at the new, but there's a small chance of your customer not paying you 10,000 cents if you need, because it's a very expensive situation. And we also face, and I'll just give you a follow-up on this of course, there's a lot of things you should ask before you take all the support for something you did to yourself. From a project management point of view, first, you surely have to ask the previous three houses or agency, is there any documentation? Do you have PhD doctorial specs? Do you have some kind of PVS which is written on the website? I'm not talking about a grammar book or something. I'm talking about something that's an extensive science. Then, a lot of very important questions, especially if you're a freelancer or an agency who develops things and you don't do the support I count in that it is. Ask your customer if they do changes on their own or if they have to trade for the specific website features. Because I had a case with you where we took over, we didn't ask that. And then we switched that to our hoaxing service, and then we received mailings like four or five times a week for the change in text, for the change in time, to the point at which it came in. If you don't want to do that, you should ask before you take it, before you sign a contract. Ask it so you don't have to do it yourself, and we don't want to do that. And then, of course, you might want to ask them if they did test the software level. Don't ask them if they did test the software. You might want to ask them, how did you test? Did you test the client? Do you have ultimate tests? And they will get the answer, because I had a case where it was majorly profanity when I asked them if they did test the software. Of course they did test the software, but they didn't know if they did test the software. And then there's the technical part. The first thing you should ask about is mostly. Because we are a very special case. We're currently hosting a WordPress course, too, for a third of that's been closed down, and the class is only one until the end of the year. So we have a hundred and twenty WordPress installations that we need to move away from that, from like a closed source mix up of WordPress and other social media stuff. And it's very odd to move to that, because there's a lot of IP access, all we can do already is test for those. And you won't believe me how many agencies did ask something about how they get that stuff out of their infrastructure to their own. Zero questions were asked. Another one very funny case where we didn't hear anything about that page, the whole, and then we used to make a relationship and said, well, we get that site new. We're going to move it to our own servers. Could you please send me a dot and it's not going to be followed by email. And I told them, well, yes, if your email is as long as it allows me to give you 320 gigabytes of data. They told us that we can get a bit of it. We can get a bit of it as well. They were able to move the 320 gigabytes to the server. They had to set up everything new. They had to set up the host to manage the server. They had a lot of storage. If they asked before, they would have known that. They couldn't even have taken a look at the page because we didn't think so. So I don't know why people don't ask this question. Then in some environments, you will have, like, test systems, deployment systems, and data deployments, or any deployments, whatever. If you don't know that stuff, they keep your hands off the process. And in one case, we had a paper on the license keys where the agency paid the licenses, and once we took it over, we had to repaid the license. Of course, in most cases, these are only, like, 50 to 100 dollars. Think about it. And it doesn't cost anything, but... Then, the second thing, if possible, take a good look at the code. I haven't seen some nasty things. A lot of nasty things. Even with the hard installation where we had a workforce for two people in the process, that was newly developed, the work rest of the day, they did everything themselves. They made a child fee from 2014, but there's nothing to see as 2014. But it was still a child fee, and it resulted in the whole spreadsheet page fee for nothing. And then they overrided a lot of centers. They provided only many more. They replaced the whole gallery with short codes. And in the end of the life, 4,000 lines of code that are not maintainable in the next three or four years. So, if you want to be a good developer for your new clients, you might want to look at the code before you and get over it for the development. And of course, in some cases, you can do everything that's that thing. And then what took me a lot of times is some PhD of other frameworks. We have seen, we've got a PhD contest on those YAS, YAS CSS stuff. And you need like Ruby, you need Ruby virtual machines to get that stuff, just to compile your CSS and you need to get some problems if you want to change the code, of course. So, you might want to ask yourself frameworks in use that you don't even know and you might want to rethink if you really want to do that job. So, of course, it's possible you should try to install it locally if your client wants it before you sign a contract. In some cases, it's possible to sign one, but if you aren't sure, you should take over some. There are a lot of questions you can ask. There are a lot more questions you should talk about. So, it greatly depends on the size of the content that you have signed for the code. So, this is just a reminder. So, we won't project. Well, that's about it. Thank you.