 Hi Victor. Hi Christian, how are you doing? I'm doing well, thank you. It's great to talk to you again and I appreciate this additional time for our conversation. I thought we had a very positive conversation last time. You had mentioned that you really like GitLab, but that your official tool is Atlassian. So I wanted to maybe answer some of the questions that you had regarding what that means, thinking about GitLab for the organization. Yeah, you know, you and I, our conversation was really good and I got really excited and jazzed up about GitLab again. You know, as you know, I'm a big user and believer of what you guys have as a company and GitLab itself. I just, you know, it's hard for me to bring in, when we already have Atlassian as our standard, you know, in that sense, what do you have to help me show that your tool is better, that I can take in and have those conversations with my management? I definitely recognize and understand the concern, particularly when you have that corporate standard. For what it's worth, and you may know this already, but GitLab integrates strongly with Atlassian tool sets. We know that you may be using as an organization the Atlassian stack for a number of years, with assisting data and business processes, and we want to make it seamlessly to work with with GitLab. So as an example, one of our integration points is that to integrate with JIRA issues, to describe that feature in a little bit of detail, that integration allows you to integrate a single repository in GitLab with all the JIRA projects in a single JIRA instance. What that means for you is that as your developers are working in that repository, those commits going into that GitLab project are going to have links referencing back the JIRA issues. So from a project management perspective in JIRA, you have full visibility into the work that is being done by the developing teams within your JIRA issue, linking back to the GitLab project. That's awesome. So I came to you around being more of a code repository, an SCM tool, because we do have some issues around, and I would love to know more, but knowing that you integrate with JIRA, and it sounds like a very strong integration, that's fantastic. If we aren't ready to go all in, is that going to be an issue? Can we start small? What would be your suggestions on how we put the processes and how we get started? Certainly starts more, and that integration that I mentioned is a starting step. Once again, with everything that you have already invested in JIRA, you don't have to go all in. We aim to make it easier. The JIRA issues is one of those examples, but we provide you not only that integration to the boards, I mean to the issues themselves, but as you progress into taking it further and using a single platform, you're going to find features like, for example, our issue boards in GitLab that are analogous and quite flexible, perhaps even more so than in Atlassian, where you are able to configure the workforce for your individual teams working that repository, whether it's a single team with a single process or a number of teams using different processes each within that same project. Our implementation services team is also ready to assist, understanding that there are workflows, there are practices that the teams are used to in your case. Our implementation services team are there to not only help you with say a configuration of that integration, that repository, but also ensuring best practices and enabling the teams to work seamlessly within the tool sets. That'd be great, because my concern is if I'm able to get the green light and bring you guys in, that it's going to be looked upon as just another tool set and it's going to be quite honestly disruptive. So whether the process installed tools and features is something that I can sell into my organization, it's just, I'm not sure, will it be a disruptive situation? It's obviously a good point to bring up as well, that disruption. And to that end, we also aim to make it complex. You mentioned starting slowly first, implementation services can help you get started there. In the end, though, thinking about Atlassian or thinking about Gizla, rather, as another tool, I would also like to ask your team members, your developing groups, how would they feel about maybe bringing in a tool set that enables the transition to a single platform that is already fully integrated versus having to maintain different systems, different configurations, different upgrades for all the different parts of that system. And Gizla provides you that single installation, single upgrade, plus the services to help your teams get up to speak quickly. That'd be great. And would we still get to use you as our essay or will I be working directly with the implementation specialist or is there a team? I'm always available to you as the essay, but we do have a submission that implementation team. As a matter of fact, they're peers of my immediate customer success group. So we work close together, hand in hand. They know our initial conversations. They know any practices or initial advice we've provided to you. And they will run with that and also expand upon that and always expand upon that best practices. Great. Well, thanks, Victor. I appreciate you taking time to answer some of my concerns and provide even more great information that I can take back with to my management. I would love for next step to be that you and maybe your sales team can have a conversation. I can set up a meeting with my management and some of the development teams to get a little bit more and ask more questions if possible. But I think this is a great start. I will facilitate that. And until our next touch point, if you have any more questions or concerns, please let me know. I'll be happy to assist. Awesome. Thanks, Victor. Thanks, Kristen. Bye-bye.