Video: The Total Economic Impact™ of Cloudflare, 2026: Understand strategies and ROI of IT and security consolidation | Duration: 4540s | Summary: The Total Economic Impact™ of Cloudflare, 2026: Understand strategies and ROI of IT and security consolidation | Chapters: Webinar Introduction (54.14s), Security Breach Statistics (119.725s), Security Breach Challenges (230.375s), Security Platform Adoption (385.74s), Evolving Security Landscape (976.47003s), Platform-Based Security Approach (1067.315s), Economic Impact Analysis (1143.58s), Cloudflare Connectivity Cloud (1666.0901s)
Transcript for "The Total Economic Impact™ of Cloudflare, 2026: Understand strategies and ROI of IT and security consolidation": Hi, everyone. Thanks so much for joining us today for this webinar on the total economic impact of Cloudflare, where we're gonna talk about strategies and ROI of IT and security consolidation. My name's Martin Sanchez. I'm a member of the marketing team here at Cloudflare, and I'm really, really excited and fortunate to be joined by our two featured speakers. The first is Joseph Blankenship, who's a VP and research director at Forrester, and then also Mary Barton, who's a consultant at Forrester who worked on this total economic impact study. Here's what we're going to cover today. We're going to start off with Joseph sharing some recent security trends based on the conversations that he's had with a wide variety of Forrester clients. After that, Mary is going to walk us through some of the results of the total economic impact study of Cloudflare, which will illustrate some of the strategies that organizations are using to deal with those trends and the impact they can see from doing it with Cloudflare. And then finally, I'll end with a bit of the Cloudflare perspective talking about our connectivity platform. So with that, really excited to hand it over to Joseph, who's gonna tell us a little bit about some security trends. Excellent, Martin. Thank you very much for that introduction. And hello, everyone. I'm Joseph Plankenshoev, VP and Research Director for Security and Risk at Forrester. A big part of my job as a research director is to lead one of the analyst teams that's researching security topics, producing our research and working with clients to solve their problems. And one of the things that we do at Forrester, you know, being a very large research firm is wait for it. We do a lot of research. And part of that research is doing surveys out to security professionals just like yourselves. So I'm gonna start this off sharing a little bit of data from our most recent security and risk survey that published in 2025. And then we're going to pivot over into some of the advantages of choosing a security platform or choosing a platform for delivering security use cases. So let's let's dive into a bit of data. Now it will likely not shock anyone who is listening to this webinar to learn that, guess what? People are still having breaches. And what our research shows from our survey respondents is that the mean number of times people are being breached is about 2.8, let's just call it three, three times annually. And you can see that some folks are probably are reporting no breaches, and other folks are actually, reporting 12 to 25 breaches. So what it tells me as a security, professional and researcher is, obviously, this is still a big problem. Data is still being breached. Bad people are still getting into networks. We're still kinda dealing with a lot of the same security problems that we've always had, and now we're trying always trying to find ways to tackle that and try how do we figure out new approaches to solving that? So one of the other questions we ask is, alright, so you're being breached. How is that happening? More often than not, there's some sort of application, being targeted as part of this. So it could be a software supply chain breach. It could be a vulnerability that gets exploited. Obviously, we see tons of that. It could be some sort of a web application exploit. We still see those, happening from time to time. So some of the same things that we've seen for years, other kind of new newer attack methods. Then we also see not only applications being targeted, but also people with things like phishing and social engineering and other sort of human centered breaches that that attackers will take advantage of. So all kinds of things kind of coming at us all at once as security pros, which is why we have this wide variety of tools and techniques that we use to keep attackers at bay, protect our infrastructure and our sensitive data. One of the other questions we ask, we ask a lot of our security decision makers, you know, what are some of the things that are really challenging for you? This is one of my favorite questions in the survey, honestly. It really kind of gives us an idea of what are security leaders struggling with. And, you know, typically, that'll also trans kind of translate into the questions that security leaders are asking us, go through analyst inquiry and guidance sessions. So a little over a quarter of our respondents told us it's the changing and evolving nature of external security threats. Probably no big surprise that it's the external threat environment that is really challenging for us. But we were to dive a little deeper into that data. Some of the other things that come up are internal complexity, just dealing with the internal complexity of our IT environments, our hybrid environments, cloud, on premise data center, all of those kinds of things, as well as dealing with things inside the organization itself. So one of the ways that I talked to security leaders about this when we're kind of discussing these things is, hey, you're very much responsible for keeping all the badness out, keep all the goodness in, and at the same time you're doing that, things are changing internally. We're going and adopting new things like all kinds of AI tools right now. We're still moving things from the cloud out of our traditional data centers to be adopting new technologies, all of those kinds of things. That constant turmoil makes it really difficult for security leaders and security practitioners you know, to do what they're kind of challenged to do. And so that kind of leads us into the next couple of slides here, which is what do we prioritize? How do we actually start doing these things? So one of the other things we ask our security decision makers is, what are your top strategic priorities? What are the big ticket things that you're focused on as a security leader? Should be no surprise that the top thing is improve our ability to detect and respond to threats. So now we're still talking detection and response, not necessarily prevention. We're still kind of in that detection response mode, not necessarily always looking at how do we keep things out. We're also looking at how do we secure our cloud environments. Now, the rank that I've got here on the left, so I think things were ranked one through 25 of the top priorities. And I kind of looked at some of the things that are really important if we're choosing platforms and things like responding and detecting threats came up, cloud security came up, adopting zero trust came up. So you kind of look at some of these things and you say, hey, what are the things that are really impacting our decisions to adopt a platform approach where the platform may provide us some prevention as well as detection and response? Will the platform enable us to do things like implement zero trust and adopt sort of a zero trust approach to prevention? So now looking at some of the strategic priorities, those are the things that are top of mind for security decision makers. How do we consolidate the tech stack, make this a little less complex? Remember that complexity is one of the things that we're really dealing with. And then also, how do we secure people who are working from anywhere? You're still seeing, you know, plenty of people returning to office. That doesn't mean they don't work outside the office, whether it's home, home use, travel, remote locations, all of those things. You've got to be able to secure people wherever they are in in the world. So we go from the strategic kind of the big picture down to the tactical. How do we do these things? Kind of the same thing. It's a one through 25, you know, kind of, you know, check off all the things that you're thinking about. Kind of looked at I kind of honed this in on some of the things that were really important in terms of threat detection and response and prevention. Number one, again, the number one attack vector, applications. So what are the things we want to do? We want to implement application security controls to protect our applications and all of those different capabilities. We want to move things from on premise to the cloud. We find it very difficult sometimes to manage things on premise. This has been ongoing for years, where we've kind of migrated to the cloud, only to do things like management and reporting, but now we're also getting cloud delivered security capabilities. So kind of a big piece there for people as they're choosing new capabilities. Adopting Zero Trust Network Access or ZTNA, so we can secure work from anywhere and also implement a lot of those Zero Trust controls that we talked about, where maybe an attacker cannot get in and then have carte blanche to move around inside of our environment. Then lastly, as we're moving things from on premise to the cloud, we're adopting new capabilities from the cloud that maybe we couldn't have in our traditional on premise approach to security. All right, so as we start talking about security platforms, and I think this is our kind of the latest kind of wave, if you will, of, you know, security procurement. We used to have this phrase we used here at Forrester for a long time and I loved it. It's kind of a play on the on the term defense in-depth. We called it expense in-depth. What expense in-depth means is every time a new thing came up, would go buy something to deal with that, whether it's applications, if it's endpoint, if it's some sort of weird network thing, maybe a DDoS attack, we would have one thing for all of these all of these different, you know, kind of threat vectors or attack vectors or what have you. What that really ended up with is we had this horrible bunch of, you know, different disparate vendor solutions that did not talk to each other. It didn't work with each other. They didn't have a common admin console. They had none of the above. And it made it very difficult for us as security operators to operationalize the stuff and manage it. So one of the things we kinda see when people are adopting platforms is what do they wanna get out of this? Well, they want to have some consistency. They want the implementation work to be done for them. One of the things we've been doing the security thing for a while. One of the things that we used to do is say, hey, we've got this expense and depth sort of approach. It's up to you security people to figure out how to make this stuff work together. So now we're kind of turning the tables on the vendors and saying, hey, vendors, make your stuff work for us. We don't want to do the implementation work. We don't want, you know, the left and the right and all these different capabilities, you know, not really talking to each other. What we really need is a common control plane. We need a common data framework for the way that we're looking at data. We want, you know, really ease we have ease of management, ease of reporting across all of these things. This is kind of what we're looking for and expecting. When we say security platform, what should come at that Shouldn't just be the capabilities themselves, which are obviously crazy important. Are you delivering for the use cases and the outcomes that we're buying the thing from? But you're also making it easy for us to acquire it and manage it and administer it and all of those kinds of things. Are you helping us increase productivity? Alright. So we also kind of ask people, you know, why are you going to the platform? Right? First of all, that ease of integration I talked about, the productivity gains, ease of use, kind of a new one for security people, automation, we want to be able to automate across that technology stack. We want have some streamlined implementations and onboarding experiences. And then kind of lastly, and this is sort of counterintuitive, right? You also think about discounts via bundling. And typically, when we're talking about the platform story, I know Mary is going to dive into a bunch of that stuff for us here in just a minute from the TEI studies that we did, but the discounts are sort of the of the afterthought in a lot of ways, because we're getting all of this other sort of goodness that we're expecting from security platforms. You know, just the ease of being able to set it up, administer it and run it, like we talked about, and then introduce the elements of automation. Now, as we're thinking about implementing and buying security platforms, we also have to think, you know, what are the criteria that we're looking for? You know, so one of the things we're looking for, do you want to have a single user interface across all the solutions? One of the things that used to drive me crazy is when I would see somebody demonstrating a platform and they're, you know, you've got all these different windows open and they're doing different logins. It's not single sign on, it's different logins and different menu structures and all these kinds of things. It's one of the things you're kind of looking for is how easy it's going to be for me to use this thing every day. You want to have the single underlying data model that spans all of the different solutions in the platform, as well as third party integrations are probably never going to get to a completely homogeneous sort of a technology stack. So we want to be able to work with whatever else it is we have in our tech stack. So third party applications, third party capabilities, different cloud environments, etcetera, etcetera. We want to look at our current tools. And this is like one of the things I really love doing with clients when we're working together in guidance sessions, right? And you're talking about making a technology acquisition purchase. Like, that's fantastic. New technology, that's great. What are you currently using for, you know, maybe security operations, detection, response, all of those things? You start looking at it and there's a lot of overlapping capabilities. So one of the things you really want to do as you're going into this kind of a platform discussion is, what are our overlaps? What do we already have? What can we deprecate or maybe get rid of or move off of that's eventually going to save us some headache and probably save us a lot of cost as going forward? Where can we consolidate and do all those things? We want to talk to the vendor. We want to understand their product roadmap. We want to understand how the products got to where they are. Is it a big M and A kind of a strategy that's putting things together? How quickly do those get integrated? Because one of the things that also happens is we're buying a platform and now there's like in the back of our head, we're thinking, is my vendor going to get acquired by somebody and that acquired company is not going to pay attention to this anymore? There's one of it's one of the things you can't really predict that, but we can kind of look at where the company is. Are they mature? Are they delivering the stuff that they kind of they have a track record of delivery, all of those kinds of things. So ask those questions and really get familiar with that vendor. Look at metrics like the integration stats. How quickly can I get up and running for the different capabilities that I'm buying through the platform? What productivity gains should I be expecting? And can I benchmark against those productivity gains? Again, ease of use is a little softer sort of a metric, but that's really looking at your internal workforce and saying, how easy do you find this thing to use? And then kind of look at as you're, you know, doing your implementation strategy, you're kind of thinking long term. Don't think you're going to get to, you know, maybe the end of Q3 and you're going to turn up a brand new platform, multiple capabilities and everything, you know, first first thing in Q1 to be successful. So kind of look at what is your transition plan going to be? As you're kind of deprecating from the current solutions, what are some things you're going to bring up in the platform? Build a roadmap and implementation strategy on how you're going to do those things so it's much smoother and you don't end up with, you know, coverage gaps and that kind of thing. Know, some kind of realistic expectations as well around the complexity of the tools that you're working with. These things are all fairly complex systems. Whenever you have a complex systems, guess what? Things can go wrong. Really kind of plan ahead for that and kind of plan, you know, more of an implementation journey, if you will. So I'm going wrap it up with just a couple of thoughts here. So one of the things that want to leave everyone with is also we are in a period of really accelerated technological change, and that's not just true of security tools. The security space is changing at a really rapid pace in terms of the capabilities we're delivering and the ability to deliver those via kind of more of a platform footprint instead of kind of the best of breed individual product kind of thing we're accustomed to. You're also seeing the business itself adopting AI at a really crazy fast rate. It's up to us as security pros to help the business secure those things as they're rolling out. Big part of that is application security, API security, making sure as we're deploying those things, they cannot be exploited either by internal or external actors. There's been a lot of talk about the quote unquote AI powered threat. I don't know that we've seen a ton of AI powered threats. However, I think it is absolutely one of those things that is on the horizon for us. We're also seeing a lot of automation being added to threats. So think about not only protecting against what we've got now, but is it kind of changing and evolving nature of threats that we talked about before? You have to be ready for external threat environment to start changing very rapidly in terms of approach and capability. And then last, you know, if you're dealing with, you know, the multiple myriad vendors and the implementation challenges and the reporting challenges, you're doing a lot of stuff manually, really start looking at, hey, does it make sense for us to start approaching this from a platform based approach? As you're adopting that platform, make sure whatever you're adopting also maps to your strategic goals for the company, as well as your security program. Look for opportunities to consolidate and deprecate that legacy tech. You know, if you're kind of have things in your environment that are sort of a struggle for you, this is the time to say, is there a better way I can answer that question and maybe move some of those things to a vendor that can help and support me. Lastly, look for the integrated solution where the vendor has already done the work for you. You're not off doing integration stuff, trying to spin it up yourself, learn how to do all that stuff. You're looking for an already integrated set of tools that's delivering a platform and not a portfolio of individual products that you still end up having together. You're looking for a true platform approach to these things. All right. Given that, I'm now going to pass the baton over to my colleague, Mary, and she's going to walk you through this total economic impact or TEI study for Cloudflare. So Mary, please take it away. Thanks, Joseph. Hi, I'm Mary Barton. I'm a consultant at Forrester. And for the past few months, I've been working with Cloudflare to understand the total economic impact the organization might see from deploying Cloudflare to address the issues that we just heard about from Joseph. The TEI is a proven methodology that is repeatable and consistent and it covers the concepts of benefits, costs, flexibility and risks. Forrester conducts hundreds of TEI studies every year and we've been conducting them for over twenty years. The methodology involves due diligence, which begins with us trying to understand the technology as best we can and that within the context of the relevant current demands that organizations seek to address in this investment. For this study, I've been working with Joseph to gain that insight as well as stakeholders from Cloudflare. Next, we interview customers who've deployed the technology and have enough experience with the solution to address the problems that they sought to address and what benefits the solution has brought to their organizations. While Cloudflare introduced us to the customers, they did not participate in the interviews and the customers remain anonymous in the final study. From those conversations that we have with the customers, we construct a representative composite organization and build a financial model that reflects the costs and benefits that the interviewees describe to us. The model is incorporated into a case study that reflects those quantitative benefits as well as the qualitative experiences that those organizations have seen. A brief this presentation is an abridged version of the full study, which you can obtain from Cloudflare. Forrester makes no assumptions as to the return that any other organization might experience, but rather offers a framework that readers can use to evaluate the appropriateness of an investment in Cloudflare. The study is not an endorsement of Cloudflare, but rather an independent study. So let's talk about Cloudflare. We found that the composite organization investment led to an ROI of 227% with a net present value of $21,400,000 In a few minutes, we'll dive down and see how we arrived at those numbers, but first we'll talk a little bit about the people that we interviewed and how we built the composite. As you can see, we spoke with five experienced Cloudflare customers and as you can also see, they represent a range of industries. They are based in Americas and Europe and they have annual revenues ranging from $438,000,000 to $70,000,000,000 So a wide range of enterprise level customers that we spoke to. The prior challenges that drove these interviewees to invest in Cloudflare are really reflective of the challenges that Joseph described for us earlier. And with consolidation of tech stack, improved security and visibility is common themes across those challenges. Because from that customer base, we developed a composite that has 10,000 employees using Cloudflare and an annual revenue of $10,000,000,000 sort of the mid range of the organizations that we interviewed. And based on those interviews, we found that the three year risk adjusted benefits to the organization amounted to $30,800,000 Those included strength in security, increased revenue from reduced downtime, streamlined IT operations, improved access performance, reduced bandwidth and cloud costs from caching efficiencies, and reduced fees from consolidation of that tech stack. The first benefit was strengthened security and this is based largely this analysis is based on the Forrester Research that you heard Joseph speaking about earlier. All of the interviewees reported that with Cloudflare they were able to consolidate their web application firewall, DDoS mitigation, bot management, and zero trust access and email security into a single platform. That significantly reduced the organization's exposure to attacks. Based on that Forrester research that we heard about, the composite saw a 24% reduction in that exposure. For an organization, the size of the composite, the total annual exposure to security breaches prior to deploying Cloudflare was estimated at $4,400,000 and over that three year period that led to a savings of $2,700,000 or reduction in risk of exposure of $2,700,000 The next benefit we saw and quantified was the increased revenue from reduced downtime. Our composite has an online sales component and by saving two fifty hours of downtime through the reduced need for planned downtime for maintenance and responding to outages. Cloudflare's globally resilient cloud architecture provided this two fifty hours of savings. One of our interviewees reported that he had eliminated forty eight hours a month of that type of downtime. Of course, that reduction in downtime not only allowed the company to stay up in running and selling online, but it resulted in streamlined IT operations. This has a qualitative and a quantitative component to it. The planned maintenance windows and DNS related outages being freed up allowed IT resources to focus on strategic initiatives and innovation. One interviewee reporting that the IT engineers were very happy to have their weekends back and moreover in their day to day work to be able to focus on strategic work instead of firefighting. The improved access performance was another key result from moving from customers who replaced their VPN solutions with Cloudflare Zero Trust Network Access and Device Client reported the improvements in connection speed and reliability. End user satisfaction increased, employees gained faster access to applications without the latency and instability associated with that prior architecture. The composite saw a 90% reduction in tickets, and one customer reported that even from the office, connections through Cloudflare were two and a half times faster. The benefits for that composite amounted to a risk adjusted three year benefit of $5,200,000 The reduced bandwidth and cloud costs from the caching efficiencies. Finally, have two benefits here, this one and the next, that are cost savings from infrastructure and consolidation. Cloudflare's caching efficiencies resulted in reduced demands for the origin servers and a 50% reduction in cloud egress consumption for the composite. That led to a savings of about $430,000 a year. Lastly, we had reduced fees. Customers reported that Cloudflare's consolidation of multiple security and performance services led to a 20% reduction in fees paid for those services. For the composite, that saved them another $1,800,000 risk adjusted over the three year period. To calculate the ROI, Forrester balanced those $30,800,000 in benefits against a three year risk adjusted cost from licensing and support fees, implementation, deployment, and maintenance of $9,400,000 over the three year period, resulting in, as we said earlier, a 227% return on investment. So you can read more about the Forrester methodology and see the detailed analysis of Cloudflare in the full report available from Cloudflare. Thanks so much to the audience for your time, and thanks, Martin, for having us as your guest today. And now I'll turn it over to you. Thanks so much, Mary. And also, thank you again, Joseph, for sharing all those stats. Really, I just learned a lot from hearing that. So hopefully when everyone else has learned something too. I want to wrap up quickly by sharing the Cloudflare perspective on this. Obviously, a lot of the statistics and findings and quotes that Mary shared from the study, I think, tell the story better than I could ultimately. I do want to highlight a few things. There's obviously a wide variety of different benefits that study covers, and we feel that we can do all of that with our connectivity cloud. For us, that's our unified platform of connectivity, security, developer services powered by our programmable global network. Connectivity cloud is our word for it. Frankly, we don't really particularly care what people would call it. A lot of our customers don't even call it that. But the point is that we're able to unify a bunch of these disparate security, connectivity, and developer services on that single platform. And based on various aspects of its architecture, it's able to deliver a lot of that simplicity of integration, ease of use, kind of the benefits of having single models that Joseph was talking about in his discussion on choosing security platforms. I just wanted to share a bit of detail on some of those things. Obviously, like I said, just based on the variety of use cases and benefits that the study found, there's a ton of different services that we unite on our connectivity cloud platform. Don't worry, I'm not going to read every single one of these things here. That would take way too long. But just the point is that we really are able to combine a kind of unprecedented amount of these different services in a single place, unlocking a whole ton of efficiency and innovation for security teams across a variety of use cases, business models, and industries. And really how we're able to get some of that or all of that efficiency, all of that ease of use, ease of integration is via a few key elements of our architecture. If you follow along, some of these will resonate with some of the quotes and the examples that Mary was giving. The first one is really fact that all of these services that we're delivering on our platform are all built on a single cloud network within a single control pin that operates at global scale. When I say global, I really do mean global. As you can see here, the network spans over three thirty cities in over 125 countries. It has over practically, I should say, four fifty terabytes per second of network capacity and growing. You know, that number changes every quarter, so watch this space. Another thing that's growing rapidly is, the amount of cities that we're able to run AI inference from. I'll talk more about that in a sec. And then because of just the massive scale of that network, we're able to serve over 20% of the total web properties, including over 80% of the top 50 generative AI companies, helping them block. And again, at last count, an average of around two thirty four billion cyber attacks every single day. That's another number that I would encourage you to watch because it keeps going up. But it's not just about global scale. It's not just about size. What we really try to do is to have and have tried to do is design that network in such a way that enables really strong resilience, that enables organizations to negate the need for that network downtime, that network maintenance that Mary was talking about. And really how we do that is with, you know, kind of a vanishingly few, exceptions. Every Comprehensive service is built to be able to run on any server in every data center in that entire network that I talked about. So that means that no matter where you are on Earth, no matter where your customers are on Earth, where your users are on Earth, CloudFare systems are running close to them. So they have a faster experience using them, minimizing latency in a variety of use cases. It means that if, you know, you have, you know, a few data centers in our network go down, there's a bunch of other ones nearby that will automatically pick up the load, whether that's enforcing policies, whether that's caching content, delivering content, whether that's running serverless code, again, whole variety of use cases. AI, I think, is one of those vanishingly few use cases because, again, we can only quote unquote run inference from around two ten cities, like I said, but that number was 190 a few months ago. So again, watch this space. But again, scale is great. Resiliency and uptime is great, but we've talked about ease of use. We've been talking about switching costs when it comes to adopting new platforms. And here's where I think some of our specific capabilities really start to shine and enable some of the outcomes that Mary was talking about. There's a lot of different ways that you can program and customize all of those different services that I was just talking about and really allowing organizations with a variety of unique needs, whether that's regulatory or policy based or region based to enable to get some of these outcomes that Mary was talking about. When we let you do that is by letting you customize cloud for services with serverless code that runs everywhere or anywhere on our network. We have a developer platform and a lot of organizations use that to actually run entire web applications, the backend and frontend, the storage, etcetera. But another thing that you can do with that developer platform is kind of build your own security tools essentially, which really helps with a lot of those kind of edge cases that can otherwise scuttle consolidation, security modernization projects. We also let you keep your existing IP range, which is, again, just kind of like an ease of implementation thing. Then also letting you limit data processing and logging and customer data, metadata storage to certain countries and regions, which is really, really helpful when it comes to regulatory compliance, data privacy regulations, like the GDPR and things like that. I wish I had time to talk about every single one of these things in extensive detail because there's some really cool use cases that come out of it. But overall, the idea is that we have designed our platform to be able to make it be really easily customizable and programmable. So no matter what your need is, you can still start using everything and testing everything quickly, which, as Joseph said, such an important benefit. And then finally, kind of a frequently talked about, but sometimes underrated thing when it comes to ease of use is just like how many windows you have to use, like Joseph was talking about. And again, Cloudflare lets you use everything via a really simple unified either a user interface, that kind of single window, single pane of glass experience, or you can even integrate Cloudflare services very directly into your existing code production pipeline via our Terraform integrations and other single API across all services. So again, I wish I could talk about this for an entire webinar if we have the time, but allowing you to do things like automate certain web security protections whenever your developers publish a new feature or a new webpage or automatically implementing new policies for certain internal SASE and zero trust use cases. The list kind of goes on and on, but being able to do all of this, managing web security or managing all sorts of security rather, drawing on that single base of threat intelligence based on the over 20% of all web properties and being able to have all of that at your fingertips via a single UI or API, just again, unlocks a ton of power. Again, a lot of great stories we could tell. One I wanna just talk about quickly is Canva, which is a super popular online design platform. I think at last count, there's like, you know, 260,000,000 people using their services. So very, very large enterprise delivering very user experience intensive services at global scale. And they have really gone offline on our connectivity pad using all of the use cases that Mary covered and more. So they are using us to deliver both their applications secure to deliver their web application to secure it from wide variety of threats, and they're able to have really fast and reliable experiences across that two sixty million large user base. They also use us to secure certain aspects of their workforce. Again, speaking to some of those breach risk reduction and access performance use cases that Mary was talking about. So they use us to secure application access and public internet access across more than 5,000 users and contractors. And then finally, using us to actually build features to test them, to even run AI inference at the network edge, which is really important for them as they try and keep their user experience fresh and performant and innovative. So just again, one example of how all of these super wide variety of use cases and services can come together for in a single platform for a really demanding company. That's all the time we have for we we have time for, I think. So again, I just wanna thank Joseph, thank Mary both so much, Mary, for your work on this study, Joe, and then for walking through it for us, Joseph, sharing all those insights. Again, hopefully everyone has learned a bunch. I've learned a ton and will be following up with the study so you can all learn more about these outcomes and how you can gain similar ones for your organization. Thanks so much everyone and have a good day.