(upbeat music) >> Okay, we're back. We're here in the main stage in Cloud City. I'm John Furrier and Dave Vellante. Normally, we're over there on theCUBE set, but here we've got a special presentation. We'll talk about Totogi and the new CEO of Totogi is Danielle, who is also the CEO of TelcoDR, Digital Revolution. Great to see you. And of course, Robin Langley, we interviewed you in theCUBE, CTO of Totogi. This is a main stage conversation because this is the big news. >> Yeah. >> You guys launched there with a hundred million dollar investment. We covered that news a couple weeks ago and you as the CEO. What's the story. Tell us what is happening with Totogi? Why such a big focus? What's the big push? >> Yeah, I'm really excited about Totogi because I really think this team is working to build public cloud tools for Telco the right way. It's everything I've been talking about. I talked about it yesterday in my keynote and this is really the execution of that vision. So, I'm super excited about that. A couple of days ago, Rob and I were talking about the charging system, but there's another product that Totogi introduced to the world and that's the webscale BSS system. So I think we're going to talk about that today. It's going to be great. >> Let's get into actually the charging system, which was great processing here. What is this focus? What is BSS about with cloud? How does the public cloud innovation change the game with this? >> Well, a little bit like charging. I mean, there are maybe, you know, a hundred plus BSS systems out there, why does the world need yet another BSS? And I think one thing is we're coupling up with public cloud, which gives it that webscale element. Right? We can have a platform. Never do another upgrade again, which I think is really exciting. But I think the really key thing that we're working on is we're building on top of an open API standard. And a lot of vendors talk about their APIs, why is this different? These are standards developed by TM forum, right? It's an independent body in our industry. They've been working on these, sorry, open APIs, and all the different vendors signed a manifesto that say, "I pledge. I pledge to support the open API", but if you look at the leaderboard and everyone is Sub10, Sub5, right? And so it's kind of like, going through the actions and not falling, you know, saying it, but not following it up and we're doing it. >> Wow, so... >> Yeah. >> Dave: Robin, you guys just popped up on the leaderboard. You went from a standing start to, I think more than 10. >> Yeah. >> I don't think that's ever been done before, has it? >> No, so we were out there. We published 12 APIs and we've got a quote from, you know, TM forums saying, essentially I've never seen anyone move so fast and to publish. And it's our intent to publish, you know, 50 plus, all of their APIs by the end of the year. >> So, how were you able to do that? I mean, like, were you holding them back? Just kind of dumping them on one day? This is the nature of the new business, isn't it? >> Yeah, absolutely and then you think about BSS. It's just, you know, been known for years to be a spaghetti of, you know, applications, you know, disparate data, data being duplicated, systems not talking to each other, lots of different interface types. And it was crying out to be just, you know, sold properly in the cloud. And the public cloud is perfect for this. You know, we can build a model and start, rather than looking at the applications first, you know, let's look at the model, the unified model and build on those open APIs and then start to, you know, allow people to come in and create an ecosystem of applications all using that same model. >> If you don't mind me asking you, if you can explain. 'Cause we talked before we weren't on camera, but we talked about the cloud and you were explaining to me how this is perfect for the challenges that you guys are trying to solve. What about the public cloud dynamic or innovation component that you guys are leveraging? Take us through a little bit on that, because I think that's a big story here that's under the covers is... >> Yeah. >> What you're capable of doing here. Do you mind explaining? >> Yeah, no, absolutely. So the cloud gives us this true scalability across everything. You know, we can scale to billions of records. So we can hook in, you know, to suck in data from, you know, our on-premise systems anywhere. We have, you know, a product called Devflow, so we used to do that. And it can really allow us to bring that data in, scale-out, use standard term cloud innovations, like Lambda functions and AWS, you know, DynamoDB, and present that, you know, through that open API. So we can use, you know graphQL, you know, present that with rest on top. And so you can then build on top of that. You can take any low code, no code application building tool you like, put that on top and then start building your own ecosystem. You can build inventory systems, CRM, anything you like. >> Well one thing that's really interesting about these projects is they usually take months, years to deploy, right? And what we're doing is we're providing, almost BSS as a service, right? It's an API layer that anyone can go to. Maybe you need to use it for five minutes, five months, five years, right? With the open standard and your own developers can learn how to use this text stack and code to it doesn't require us. And so we're really trying to get away from being an SI, you know, systems integrator or heavy services revenue, and instead build the product that enables the telcos to use their own people, to build the applications that they, they know what they want, and so, here you go. >> It's a platform. >> Yeah. >> It's a platform. >> So, how do you connect to systems on the ground? Like what's the modern approach to doing that? >> Yeah, go for it. >> Yeah so, telcos have, you know, a huge amount of data on premise. They have difficulties you can get to it. So, as I mentioned before, we had this Devflows product and it has connectors. We have like 30 plus connectors to all the standard sort of, billing systems, CRM systems, you know, we can hook into things like Salesforce. And we can create either, you know, couple of a real-time interface in there, or we can start to suck data into the cloud and then make it available. So, if they want to start with a nice, easy step and just build slowly, we can just hook in and pull that information out. If there may be, you know, an attribute that you want to, you know, use in some of that application, you can easily get to it. And then, you know, over time you start to build your data into the cloud and then you've got the scale, you know, and all the innovations of that brings with it. >> So is Devflow an on-ramp, if you will, for the public cloud, is that the way you were thinking about it? >> Yeah. >> Yeah. Yeah, I mean, I call it the slurper. (group chuckles) Right. I mean, these telcos have, like Robin was saying, spaghetti systems that have been, you know, customized and connected and integrated. I mean, it is a jungle out there of data. They're not going to be able to move this in one step. We just think of like a pile of spaghetti, like the whole bowl. >> Overcooked spaghetti. >> Right overcooked, the whole bowl comes out and it's really hard to just pull out one noodle and the rest is there and what are you going to do? And so the slurper, right, Devflows, allows you to select which data you want to pull out. It could be one time, you could have it sync. You don't have to do the whole thing and it doesn't disrupt the production environment that's on-premise. But now you're starting to move your data into the public cloud and then like Robin was saying, you can throw it up against quick sites. You can throw it up against different Amazon services. You can create new applications. And so it's not this like, you know, big bang kind of approach. You can start to do it in pieces and I think that's what the industry needs. >> I'm talking about this the other day, when we're talk about charging. What a lot of vendors will do is they'll put a wrapper around it, containerize it and then shove it into the public cloud and say, "Okay". >> Check mark. >> Yeah a checkbox. And it affects how they price, if they price the same way. But we talked a lot about pricing the other day, really pricing like cloud, consumption pricing. How are you pricing in this case? >> Same with the charging system. The BSS system is paid by the use, paid by the API call. So, really excited to introduce yet, again, a free tier. We think we're doing 500 million API calls per month for free. We think this is great for a smaller telco where like, you're experimenting and just getting to know the system and before you like, go all in and buy. And I think that API pricing is going to go right at the heart of some of these vendors that love to charge by the subscriber or a perpetual license agreement, right? They're not quite moving as a service. And so, yeah. >> Are you saying, they're going to be disruptive in the pricing in terms of lower cost or more, consumable. >> And I think it's also an easier on ramp, right? It's easier to start paying by the use and experimenting. And it's really easy, just like I was talking about with charging, where you're going to get the same great product that you would sell to a tier one at a price that you can afford. And now those smaller two or three guys aren't having to make a trade off between great technology, but I'm paying through the nose or sacrifice on the tech, but I can afford it. And so, I think you're going to see this ecosystem of people starting to learn how to code and think in this way. Telcos have already decided that they want to adopt the TM forum, open APIs. They're on all the RFPs. Do you support it? Everyone says they support it, but we don't see anyone really doing it. They're not on the leaderboard. >> And there's transparency, because you're pricing by API call, right? Versus the spaghetti, you guys call it, the hairball of what am I paying for? >> Right, you're getting, all of this. It's by the subscriber. It's millions and millions of dollars. Oh, and you know, you're going to need to buy a bunch of consulting revenue to make it all work and talk to each other. Pay up, right? And that's what we're living in today. And I'm taking us to the, you know, public cloud future by the API. >> This is the big cloud revolution. It's unbundling has been a really big part of the consumption of technology paid by the usage, get in, get some value, get some data, understand what it is, double down on it, iterate. >> Put it up with different services that are available that we don't have, but Amazon uses, right? They have call centers up there, they have ML that you may want to use like, start using it, start coding, start learning about the AWS tech stack. >> So is it available now? >> Yeah. >> Yeah. No, it's available now. We've already published the swagger for the BSS APIs. So, you know, they can come on board, they can go to access to all the API straight away and start using it. They can load up their favorite REST clients and then start developing. >> So you got a dozen APIs today. Where are we headed? What can we expect? >> All by the end of the year. There's over 50 APIs. You know, the number one guy on the board is at like 22, 21, 22 APIs covered. We'll be 50 plus by the end of the year. And we're just going to blow doors. >> The API economy has come to telco. >> Yeah, I mean, it's really BSS' Lego pieces, right. Assembling these different components and really opening it up. And I think there's been a lot of power by the vendors to keep it locked down, keep it close. Yes, we have an API, but you got to use our people to do it. Here's the hundreds of thousands or millions of dollars that you're going to pay us and keep us in business, and fat and happy, and I'm coming right in on the low end. Right, dropping that price, opening it up. I think telcos are going to love it. >> Well, Mike, you said too, you'll allow the smaller telcos to have the same, actually, better capabilities than the larger telcos, right? Maybe the stack's not as mature or whatever, but they'll get there and they'll get there with a simpler, easier to understand pricing model and way, way faster. >> Yeah. >> All right and that's where the disruption comes. >> And I Think this is where AWS has really done well as a hyper scaler against their competition, is that they've really gotten to market very quickly with their services. Maybe they're not perfect, but they ship 'em. And they get them out there and they get people using them. They use them internally and they get them out. And I think this is where maybe some of the other hyperscalers, they hold them back and they wait until they're a little bit more mature. And AWS is one because they've been fast. And I want to sort of copy that feat. >> I think your idea of subscriber love in your keynote, and I think applies here because Amazon web services has done such a great job of working backwards from the customer. So they'd ship it fast on used cases that they know have been proven through customer interactions. >> Yep. >> They don't just make up new features. And then they iterate. They go, "Okay". >> Start simple, grow on that, learn from the market. What are people using? What are they not using? Iterate, iterate, iterate. >> Okay, so with that in mind, working backwards from your customer, how do you see the feature set evolving for this functionality? How do you see it evolving as a product? >> Yeah, I mean, I think all of the BSS systems today have been designed with manual people on the other side of the screen, right? And we've seen chat bots take off, we've seen, you know, using chat as support. I think we need to start getting into more automation right? Which is really going to change up telco, right? They have thousands of customer support agents and you're like, "Dude, I just want a SIM, that's all I need". >> Yeah. >> Just like, where do I push a button and send an Uber to my house and drop it off or eSim. And so, speeding up business, empowering the subscriber. We know how to interact, we just went through COVID where we learned about different apps that overnight, you can like order all of your groceries and order all of your food and there it is, and it was contactless and... >> It's funny, you said future of work, which we love that term, "work". Workloads, work force, you got all these kind of new dynamics going on with cloud enablement and the changes is radical. And the value is there. There's value opportunities. >> I mean like, you know, where are the ARVR applications, right? Where your agent pops. I saw the demo. There's a strife in Austin and they're going to kill me 'cause I can't remember their name. But they had a little on your mobile phone, a little holographic customer support. Like, "How can I help you"? Right. And I'm like, "Where's that", like, imagine you're like, ATT, you're not like on the phone for like an hour and a half trying to like, figure out what's wrong. And it's like, you know, it knows what's wrong. It understands my needs and so, no one's working on that. We're still working on, keyboards. >> Right, that and chat bot is a great example because it's all AI, and where's the best AI? It's in the cloud because that's where the data is. That's where the best of modeling has been. (chuckles) >> I think your point, it's the scale of data. >> Absolutely. >> And machine learning and AI needs a lot of data points to get really good. I mean, I'm old, I'm 50. I graduated in 1993. I took an AI class from Niels Nielsen, like the godfather of AI, right? Okay, like that AI, even 10 years ago AI, it's just moving so quickly and it's now super affordable. >> Well, I really want to thank you guys for coming up and sharing that knowledge and insight, congratulations on the product and open APIs. Love open API's open source with some new revolution. Danielle and Robin. Thank you so much. >> Thanks so much. >> Thank you. >> Thank you. >> Congratulations. Thank you everyone for coming. (crowd applauding) (people whooping) Okay, back to you in the studio at Cloud City.

(gentle music) >> Okay, thank you Adam. Thank you everyone for joining us on the main stage here, folks watching, appreciate it. I'm John Furrier, Dave Vellante co-hosts of theCube. We're here in the main stage to talk to the two main players of Totogi, Danielle Royston, CEO as of today, the big news. Congratulations. >> Danielle: Yeah. Thank you. >> And Robin Langdon the CTO, Totogi. >> Robin: Thanks. So big news, CEO news today and $100 million investment. Every wants to know where's all the action? Why is this so popular right now? (Danielle chuckles) What's going on? Give us the quick update. >> Yeah, I met the Totogi guys and they have this great product I was really excited about. They're focused purely on telco software and bringing, coupling that with the Public Cloud, which is everything that I talk about, what I've been about for so long. And I really wanted to give them enough funding so they could focus on building great products. A lot of times, telcos, startups, you know they try to get a quick win. They kind of chase the big guys and I really wanted to make sure they were focused on building a great product. #2, I really wanted to show the industry, they had the funding they needed to be a real player. This wasn't like $5 million or a couple million dollars, so that was really important. And then #3, I want to make sure that we could hire great talent and you need money for compensation. And so $100 million it is. >> $100 million is a lot of fresh fat financing as they say. I got to ask you, what's different? Because I've been researching on the refactoring aspect of with the Cloud, obviously public cloud with AWS, a big deal. What's different about the charging aspect of this? >> Yeah I mean, charging hasn't been exciting, maybe ever. I mean, it's kind of like this really sort of sleepy area, but I think what the Totogi guys are doing is they're really coupling the idea of charging and network data to bring hyper-personalization to subscribers. And I think that's where it changes from being a charging engine to become an engagement engine. Telcos know more about us than Google, which is kind of crazy to think about it. They know when we wake up, they know what apps we use. If we call or text, if we game or stream and it's time to start using that data to drive a better experience to us. And I think to Totogi is enabling that. I'm super excited to do that. >> So Robin, I wonder if you could talk about that a little bit. I mean, maybe we get into the plumbing and I don't want to go too deep in it, but I think it's important because we've seen this movie before where people take their on-prem stacks, they wrap it in containers and they shove it into the Public Cloud and they say, "Hey, we're cloud too." If reading a press release, you guys are taking advantage of things like Amazon Nitro of course, but also Graviton and Graviton2 and eventually 3, which is the underlying capabilities, give you a cloud native advantage. Can you explain that a little bit? >> Yeah, absolutely. I mean, we wanted to build this in the Cloud using all of those great cloud innovations. So Graviton2, DynamoDB and using their infrastructure, just allowing us to be able to scale out. These all available to us to use and essentially free for us to use. And it's great, so as you say, we're not shoehorning something in that's decade's old technology, wrapping it in some kind of container and pushing it in. Which is just then, you just can't use any of those great innovations. >> And you've selected DynamoDB as the database. Okay, that's fine. We don't have to get so much into why, but maybe you could explain the advantage because I saw some benchmark numbers which were, like an order of magnitude greater than the competition, like share with us, why? How you were able to get there? And maybe share those numbers. >> Yeah, no, we do. So we just launched our benchmark. So, a million transactions per second. So we just blew away everyone else out there. And that's really because we could take advantage of all that great AWS technology in there and the database side we're using DynamoDB, where we had a huge debate about using what kind of database to go and use? There's a lot of people out there probably get very religious about the kind of database technology that you should be using. And whether it should it be SQL in-memory object database type technology, but really a single table design, gives you that true scalability. You can just horizontally scale that easily, across the whole planet. >> You know, Danielle. Again, I said that we've seen this movie before. There are a lot of parallels in telco with the enterprise. And if you look at enterprise SAS pricing, a lot of it is very static, kind of lock you in, per seat pricing, kind of an old model. And you're seeing a lot of the modern SAS companies who are emerging with a consumption pricing models. How are you guys thinking about pricing? >> Yeah, I don't know of any other company in telco that's starting to price by usage. And that is a very standard offering with the cloud providers, right? Google we know, Amazon, all those guys have a price by the API, price by the transaction. So we're really excited to offer that to telcos. They've been asking for it for awhile, right? Pay for what you need, when you need it, by the use. And so we're really excited to offer that, but I think what's really cool is the idea of a free tier, right? And so I think it's smaller telcos have a trade-off to make, whether, am I going to buy the best technology and pay through the nose and maybe at an unaffordable level, or do I compromise and buy something more affordable, but not as great. And what's so great about Totogi, it's the same product just priced for what you need. And so I think a CSP it'll, below 250,000 subscribers should be able to use the Totogi absolutely for free. And that is, and it's the same product that the big guy would get. So it's not a junior version or scaled back. And so I think that's really exciting. I think we're the only ones that do it. So here we go. >> Love the freemium model. So Robin, maybe you could explain why that's so much, so important in the charging space, because you've got a lot of different options that you want to configure for the consumer. >> Yeah. >> Maybe you could talk about sort of how the old world does that, the old guard and how long it takes and how you're approaching this. >> Yeah so it's, I mean traditionally, charging design, there's as you say, there's lots of different pricing leavers you want to be able to move and change to charge different people. And these systems, even if they say they're configurable, if they normally turn into an IT project where it takes weeks, months, even years to build out the system, you know, marketing can't just go in there and configure the dials and push out your new plans and tariffs. They have to go and create a requirement specification. They hand it down to IT. Those guys go and create a big change project. And by the time they're finished, the market's moved on. They're on to their next plan, their next tariff to go and build. So we wanted to create something that was truly configurable from a marketing standpoint. You know, user-friendly, they can go in there, configure it and be live in minutes, not even days or weeks. >> No, IT necessary. >> Robin: No IT necessary. >> So you know, I've been thinking about, John and I talk about this all the time, It's that there's a data play here. And what I think you're doing is actually building a data product. I think there's a new metric emerging in the industry, which is how long does it take me to go from idea to monetization with a data product. And that's what this is. This is a data product >> Yeah. >> for your customers. >> Absolutely, what Robin was talking about is totally the way the industry works. It's weeks before you have an idea and get it out to the market. And like Robin was mentioning, the market's changed by the time you get it out there, the data's stale. And so we researched every single plan in the world from every single CSP. There is about 30,000 plans in the world, right? The bigger you are, the more plans you have. On average, a tier one telco has 40 to 50 plans. And so how many offers, I mean think about, that's how many phones to buy, plans to buy. And so we're like, let's get some insight on the plans. Let's drive it into a standardization, right? Let's make them, which ones work, which ones don't. And that's, I think you're right. I think it's a data play and putting the power back into the marketer's hands and not with IT. >> So there's a lot of data on-prem. Explain why I can't do this with my on-prem data. >> Oh, well today that, I mean, sorry if you want to jump in. Feel free to jump in, right. But today, the products are designed in a way where they're, perpetually licensed, by the subscriber, rigid systems, not API based. I mean, there might be an API, but you got to pay through the nose to use it or you got to use the provider's people to code against it. They're inflexible. They were written when voice was the primary revenue driver, not data, right? And so they've been shoehorned, right? Like Robin was saying, shoehorned to be able to move into the world that we are now. I mean, when the iPhone came about that introduced apps and data went through the roof and the systems were written for voice, not written for data. >> And that's a good point, if you think about the telco industry, it seems like it could be a glacier that just needs to just break and just like, just get modern because we all have phones. We have apps. We can delete them. And the billing plans, like either nonexistent or it has to be all free. >> Well I mean, I'll ask you. Do you know what your billing plan is? Do you know how much data you use on a monthly basis? No one knows. >> I have no clue. >> A lot. >> No one. And so what you do is you buy unlimited. >> Dave: Right. >> You overpay. And so what we're seeing in the plans is that if you actually knew how much you used, you would be able to maybe pay less, which I remember the telcos are not excited to hear that message, but it's a win for the subscriber. And if you could >> I mean it's only >> accurately predict that. >> get lower and lower. I having a conversation last night at dinner with industry analysts, we're talking about a vehicle e-commerce, commerce in your car as you're driving. You can get that kind of with a 5G. The trend is transactions everywhere, ad-hoc, ephemeral... >> Yeah. >> The new apps are going to demand this kind of subscriber billing. >> Yeah >> Do people get this? Are you guys the only ones kind of like on this? >> No I think people have been talking about it for years. I think there's vendors out there that have been trying to offer this idea of like, build your own plan and all that other stuff but I think it's more than just minutes, text and data. It's starting to really understand what subscribers are using, right? Are you a football fan? Are you a golf fan? Are you a shopper? Are you a concert goer? And couple that with how you use your phone and putting out offers that are really exciting to subscribers so that we love our telco. Like we should be loving our telco. And I don't... I don't know that people talk >> They saved us >> about loving their telco. >> from the pandemic >> They saved us during the pandemic. The internet didn't crash, we got our zoom meetings. We got everything going on. What's the technical issue on solving these problems? Is it just legacy? Is it just mindset? Robin, what's your take on that? >> I'll keep talking as long as Robin will let me. (Daniel laughing) >> So the big technical issues, you're trying to build in this flexibility so that you can have, we don't know what people are going to configure in the future. It's minutes and text messages are given away for free. They're unlimited. Data is where it's at, about charging for apps and about using all that data in the network the telcos have, which is extremely valuable and there's a wealth of information in there that can be used to be monetized and push that out. And they need a charging system on top that can manage that and we have the flexibility that you don't have to go off and then start creating programs and IT projects that are going to do that. >> Well it's funny Danielle, you say that the telcos might not like that, right? 'Cause you might pay less. But in fact, that is the kind of on-prem mindset because when you have a fixed resource, you say, okay, don't use too much because we have to buy more. Or you overbuy to your point. The cloud mindset is, I'll try it. I'll try some more, I'll try some more. I'm aligning it with business value. Oh, I'm making money. Oh, great. I'm going to keep buying more. And it's very clear. It's transparent where the business value is. So my question is when you think about your charging engine and all this data conversation, is there more than just a charging engine in this platform? >> Well, I think just going back to what Robin was talking about. I think what Totogi is doing differently is by building it on the Public Cloud gives you virtually unlimited resources, right? In a couple of different directions, certainly hardware and capacity and scalability and all those other things, right? But also as Amazon is putting out more and more product, when you build it in this new way, you can take advantage of these new services very, very easily. And that is a different mindset. It's a different way to deploy applications. And I think that's what makes Totogi really different. You couldn't build Totogi on-premise because you need the infinite scalability. You need the machine learning, you need the AI of Amazon, which they have been investing in for decades, if they now charge you by the API call. And you get to use it like you were saying. Just give it a try, don't like it, stop. And it's just a completely different way of thinking, yeah. >> If I have to ask you a question about the Public Cloud, because the theme here in Cloud City is the Public Cloud is driving innovation, which is also includes disruption. And the new brands are coming in, old brands are either reinventing themselves or falling away. What is the Public Cloud truly enabling? Is it the scale? Is it the data? Is it the refactoring capability? What is the real driver of the Public Cloud innovation? >> I think the insight that CSPs are going to have is what Jamie Dimon had in banking. Like I think he was pretty famously saying, "I'm never going to use the Public Cloud. Our data is too precious, you know, regulations and all that stuff." But I think the insight they're going to have, and I hopefully, I do a keynote and I mentioned this, which is feature velocity. The ability to put out features in a day or two. Our feature velocity in telco is months. Months, months. >> Seriously? >> Yeah, sometimes years. It's just so slow between big iterations of new capability and to be able to put out new features in minutes or days and be able to outmaneuver your competition is unheard of. So the CSPs that starts to get this, it's going to be a real big get, and then they're going to start to.. (Danielle makes swishing sound) >> We just interviewed (Dave speaking indistinctly) a venture capitalist, Dave and I last month. And he's a big investor in Snowflake, on the big deals. He said that the new strategy that's working is you go to be agile with feature acceleration. We just talked about this at lunch and you get data. And you can dismantle the bad features quickly and double down >> Yup. >> on the winners. >> Ones that are working. So what used to be feature creep now is a benefit if you play it right? >> Danielle: It's feature experimentation. >> That's essentially what you- >> It's experimentation, right? And you're like, that one worked, this one didn't, kill that one, double down on this one, go faster and faster and so feature experimentation, which you can't do in telco, because every time we ask for a feature from your current vendor, it's hundreds of thousands, if not millions of dollars. So you don't experiment. And so yeah- >> You can make features disposable. >> Correct. And I think that we just discovered that on this stage just now. (group chuckling) >> Hey look at this. Digital revolution, DR. Telco DR. >> Yeah. >> Great to have you guys. >> This is super awesome. Thanks so much. >> You guys are amazing. Congratulations. And we're looking forward to the more innovation stories again, get out there, get the momentum. Great stuff. >> Danielle: It's going to be great. >> And awesome. >> Feature experimentation. >> Yeah. >> Hashtag. >> And Dave and I are going to head back over to our Cube set here, here on the main stage. We'll toss it back to the Adam in the studio. Adam, back to you and take it from here.