HITT- A Connectivity Carol: Navigating Networks Past, Present, and Future- 12.16.25

This HITT presents a ‘Connectivity Carol’ framework to help technology advisors understand and guide their customers through network evolution. The Telarus advanced networking team explores three phases: networks past (legacy systems like MPLS and point-to-point connections), networks present (complexity from multiple security solutions, IoT explosion, and dashboard fatigue), and networks future (AI-driven automation, consumption-based services, and edge computing). The session emphasizes that the enterprise network market is projected to grow from $124 billion to nearly $200 billion, driven by AI, cloud adoption, and distributed workforces. Key themes include helping customers transition from inefficient legacy infrastructure, addressing current complexity challenges through consolidation, and preparing for future trends like private cellular networks and AI operations. The team provides practical advice for technology advisors on identifying customer pain points and positioning network modernization opportunities.

Transcript is auto-generated.

Our HITT series today, is with Graeme, Josh, Brinton, and Jason of all of the Telarus advanced networking team in some form or fashion. And you can see from Graeme’s, decked out appearance, they are dressed for success, and they’re going to present you guys for the next little bit with a connectivity, Carol.

Yeah. Thanks, Jen, and good morning, everybody. Thank you so much for being here. I think as Jen said, fifteen thousand of you tuned in over the course of this year.

Thank you so much. We appreciate you guys joining us for these calls. We really you know, we do it for you. This is these are topics based on what you wanna hear, and we’re so glad that you guys take the time out of your day to join us.

This is my favorite time of the year by far. The holiday season is so great. There’s so many awesome things about it, including the great stories and movies that happen over the holidays, movies like elf, home alone, all these great ones. One of the classics, of course, is a Christmas Carol, and there’s been many versions of it.

Go ahead and drop in the chat what your favorite version of the Christmas Carol is. Mine, I love the Scrooge version with Bill Murray, and then, of course, the, classic Disney Christmas Carol. But we’re gonna do our own version of the Christmas Carol here today to wrap up the year. We’re gonna do a connectivity Carol where we’re gonna walk through the ghosts of network past, network present, and network future to help you with some new tools and techniques that you can use in twenty twenty six to help grow your network business.

So let’s go ahead and kick over to the next slide there, Chandler.

Again, you know, usually, when you look at your base of customers, you’re gonna find they’re gonna fall into one of these categories. Right? You’ve got a group of customers that are probably, what I’ll call, living in the past. Right?

They’ve got old network gear. They’ve got legacy stuff happening, and we wanna help them make that transition. Second category, we’ve got folks that have advanced some stuff. They’ve maybe modernized a little bit, but they’re struggling with all of the things that come with that, all the different elements, all the different aspects.

And we’re gonna talk a little bit about sales, tools and techniques that you can use to talk to them. And then, of course, we’re gonna give you a little bit of a glimpse of what we think is coming down the rail, what we’re gonna see as we start to round out the year of twenty twenty six and into twenty seven and beyond. We’re gonna talk a little bit about where we see this going. So buckle up.

It’s gonna be a fun time, a connectivity, Carol, networks past, present, and future. So next slide, Chandler. First off, why do we care about this? Right?

Who cares if people have got old network gear, if they’ve got old stuff going? Well, we all care because there’s a huge opportunity there for us in the form of revenue. As you guys know, we’re all in this business to make money, and this is a huge opportunity. The enterprise network landscape is experiencing a ton of growth.

A lot of that is due to AI and some other things happening, but the market is projected to surge from approximately a hundred and twenty four billion, already a huge number, to almost two hundred billion by twenty twenty three, representing a compound annual growth rate of over nine percent. So we’re seeing a lot of things that are driving that. Right? I talked about AI.

That’s a huge part of it. But also things like cloud and SaaS adoption, the distributed workforce that we all know and love so well. A lot of us have made a lot of money over that on that over the last couple of years. And then, of course, things like IoT devices and mobility devices that are just exploding on the network.

For technology advisers, understanding what’s going on with all these different dynamics and being able to communicate that to your customers is going to be critical to helping them make the changes they need to make in the upcoming years to be ready to compete. So let’s go ahead and move on to the next slide.

Again, we’re gonna talk about the connectivity, Carol. We’re gonna basically break down where your customers are. Each one of your customers fits into one of these categories, we believe. Either they’re dealing with past architecture, as I said, they’re struggling with what’s going on today, and then we wanna give you, of course, some tips and tricks as to how you can help them take the next step into the future.

So without further ado, let’s go ahead and dive in, and I’d like to invite our first guest onto the call. Chandler, you can move to the next slide. Playing the role of the ghost of the network past. It’s our man, Josh Hazelhorst.

Haas, welcome to the call, the ghost of network past. Now a lot of people think we chose you for this role because, of course, you’re the seasoned veteran on the team. Right?

Discrimination, Graeme, and you know it.

You got a little bit of the gray of the beard. Yep. No. But the reality is these are the kind of conversations you have every day. Right? You help a lot of tech advisers guide their customers through this exact transition. So why don’t you talk a little bit about how some of these conversations start, kind of a lot the environments that you find yourself being introduced into, and how you kinda help them make that transition.

Yeah. And and you mentioned transition, right, is is we work on a lot of projects that they’re still not transitioning.

They’re still international or global in scale. They still have islands of tech teams where I’ve got, you know, a network team, a cybersecurity team, an applications team, and they’re they’re completely disjointed.

But there’s still request for I need, you know, point to points and I need MPLS and I need, you know, hub and spoke solutions. And and that’s not wrong depending on the use case. Right?

So we started getting crazy advanced in doing things over software like d m v p n to connect locations to locations and multisite to multisite. Again, it’s still not wrong. So if you have customers that that are doing this request, again, it’s not wrong. But what we have to do is we have to ask the questions, right, of how are you connecting, where are you connecting, why are you connecting, where are the workloads, where are the users, where are the remote users, how are we doing remote access.

If we don’t ask all those questions, we don’t understand the whole game. And a lot of times, Graeme, the customer don’t always understand the whole game because you’re talking to the network guy. But then the cybersecurity guy is talking about doing things like SD WAN and next gen firewalls and IP sec tunnels, and they’re not talking the same language. So we kinda have to come bring in and and talk the same language.

But, again, if they’re still talking legacy, it’s okay. It’s not incorrect. It just depends on that specific use case. Right?

Yeah. And and a lot of times, we’re not talking about a full, you you know, lift and shift or a full rip and replace. There are certain things we can do to help them meet the needs of today’s, user, right, with some of the stuff they have in place previously. And and it’s really just like you said, it’s not wrong what they’ve got, and they probably set things up the way they did for a reason that was, you know, pertinent at the time.

But the reality is a lot of things have changed. Right? Things like the distributed workforce, a lot of this stuff where you can’t just have everything at your headquarters locked down anymore. There’s a lot of different things that are changing.

So let’s go ahead and move to the next slide there, Chandler. Talk a little bit, Josh, about some of the challenges these older users are having with the environment of today.

Yeah. I’ll talk to you on a specific one I’m working on right now, and I don’t know how I don’t wanna say be discriminate, but I don’t know how the the age of our of our listeners are.

But I have a city in Texas right now. They’re asking to decommission spurs. Now the people that are running the project don’t even know what those things are. Like, they don’t even really have IT staff. The the IT staff retired a hundred and twenty seven years ago. Right? But they have these locations that need to connect back to the main location.

It’s kind of a hub and spoke if you think about it in today’s world, but back then, it it it was the way you did it. That was best practice on how to connect city buildings to city buildings to, you know, the the HQ building.

But the problem is what? I have I have no visibility in transport. I don’t know about anybody up down. I don’t know if there’s any trouble unless somebody calls me and tells me that that that they’re not getting interwebs.

Right? So how do I troubleshoot anything? Like, everything is guessing at that point in time. Even if we shut down some Spurs, now we say, okay.

Bring in some Internet connections at those local locations. Let them have local Internet breakout. The person I’m talking to has no idea what I just said. So sometimes we gotta oversimplify and say, listen.

It’s inefficient. We’re not gonna fix your network issue. We’re gonna fix your inefficiency issue. I have no visibility.

I can’t see. I can’t road map. I can’t troubleshoot. I can’t help my end users.

We’re gonna fix that. We’re not gonna sell you anything.

We’re not gonna tell you names and acronyms. We’re just gonna fix the problem, and the problem was it’s inefficient.

But then it goes back to accounts payable in these people, especially in cities, government, schools, or whatever.

The AP department just pays invoices, Graeme. They don’t know what they’re paying for. They don’t care what they’re paying for. Their their their whole job is to collect the invoice, pay the invoice, get it out. Right?

Well, that cost is consistent and constant. Is there a better way? We hear our our our TAs out there all the time saying, hey. We can save you cost.

Yeah. Well, maybe. But the the AP people have no idea what that even means. Right?

Well, what it means is let’s decommission some of this stuff. Let’s get it a little bit more elegant and simplified, and the byproduct is gonna be cost cutting.

Yeah. I love that concept in the middle of the slide here, this idea of cost without agility. Right? Like, a lot of these companies will just continue paying these invoices because they always have, but what they’re paying for, they could just be doing something different that’s gonna give them so much more flexibility and helping them kinda walk through that. You know, it’s not always about saving money. It’s just about doing things better and easier, and to your point, Josh, more efficiently. So, Chandler, let’s go to the next slide here.

So how to spot some customers in the past, Josh? Couple of quick keywords, couple of things that you maybe would hear from your customers to sort of signal our TAs out there that, hey. This is maybe somebody that’s got some antiquated architecture or or needs some help kinda making that transition.

Yeah. If say say I’m working for a with with a with a global operator. I got got locations in in United Kingdom. I got some in Australia.

I got some in the US, and I’m on, you know, private line circuits. I already know they’re in multiple MPLS worlds. They got MPLS over at Verizon in Europe. They got MPLS with AT and T in the United States.

How do I see it all? How do I manage it all in one simple interface so I can properly troubleshoot my locations? Like, I can’t. I already know you can’t. You can’t you can’t bind Verizon’s MPLS with AT and T’s MPLS and manage in a central plan. I already know this. They may not know that e yet, but there is a simpler way to do it.

Guys that say, I’m the Internet drain. Everything comes back to me at h at headquarters, and then I am Internet out for all of my locations.

Why are you backhauling and hairpinning all of that traffic back to a central point creating latency and then letting me get Internet out from you, why don’t you just let me connect locally? Just just give me local Internet breakout so I don’t have to come all the way back to you to get to Salesforce, for example. So those kind of questions, we already know that it’s kind of a legacy I wouldn’t say legacy routing. It’s just a legacy way of thinking of this is what we’ve always done. This is what we thought is is the is the reason, and there’s just there’s just such an easier way.

And that’s a key. Not necessarily a better way, just an easier way. Right? Kinda simplifying things, making it easier. So, Josh, thank you so much. We’ll we’ll have you back here in just a couple of minutes. But now we’re gonna go ahead and make a transition.

Please welcome to the call. Playing the role of the ghost of network present, it’s our man, Britton Gunderson. Gundy, welcome to the call, man. Again, this is the kind of thing that you talk about all the time. Is our is Britton with us?

Graeme. Hey.

There you are. How’s going? And I love the hat. You’ve got the hat on just like me. Appreciate it.

I was trying to join in.

Yeah, man. Representing the ghost of network present. This idea, like, what and, again, you have a lot of these conversations all the time every day. Right? More pass, more tools, more devices, but more complexity and not a lot of clarity. So, Chandler, if you wanna go ahead and kick it to the next slide. Britton, talk through a little bit of what you see some of the challenges RTA’s customers are having when they’re dealing with today’s networks.

Well and you you said it perfectly, complexity.

So complexity is everywhere in the organizations that we deal with, which is an opportunity for us. You know, one of the things that transitioned from that past to present is a diversity in transport. Now we have access to all types of Internet connectivity. However, there’s challenges of tying those together efficiently. Seeing the the details, the the, portal, the information, the analytics on those has now become difficult. Security sprawl. So organizations have almost gone from, you know, only security at the edge to now security everywhere that has led to point solutions.

Basically firewall to the outside, firewall for segmentation internally, how do you secure your users internally. This has created portal sprawl. Now you have analytics, data, reporting that basically sits everywhere.

Also, IoT explosion. So from an Internet perspective, seventy percent of the Internet traffic is generated by mobile devices. So that’s like that’s a tremendous amount of network that wasn’t there in the past.

So now we have new challenges of tying these together, making sure that we can see visibly what’s happening inside the network, and kind of keep our arms around it. It’s it’s really a challenge. IoT just alone is going, fourteen percent growth year over year, and we’re gonna see above twenty billion devices deployed, globally.

Yeah. It’s crazy numbers. And one of the things, Britton, you and I shared on the virtual ascend we did a couple of weeks ago was this idea of devices. Right?

You know, employees today, the average employee has three devices. The expectation is that’s gonna increase up to close to fifteen by twenty thirty. Who knows if we get there? But the fact of the matter is we’re moving to an environment where there’s more, not less.

And every single one of those devices we add adds complexity.

Yeah. We’ve gone from the state of implementing these different technologies. Now we just have technology sprawl just over from the transport perspective, security perspective, devices, getting our arms wrapped around it. And, really, the challenge is there’s there’s a four million four million gap talent, for security that we need to still fill, and that’s globally. So we’re being asked to do more with less with the people that we have, and, we you know, we’re helping our our IT directors get through their their dates.

Yeah. I mean, there’s just so much going on here in complexity. And, Chandler, if you wanna go ahead and move us to the next slide.

Again, you know, this idea of complexity. Complexity is the new holiday traffic jam. Right? Anybody who tried to go to the malls during the holidays, you know what I’m talking about here. But, Britton, talk through some of the customer pain points. Again, some of the keywords that you’re listening to when you’re having conversations with TAs and their customers, things that you key in on, things like dashboard, those kind of things that sort of lead you to believe, hey. Maybe we’re dealing with an environment here that’s, you know, that’s that’s overly complex, and we can bring some simplicity.

Yeah. I think this first bullet dashboard fatigue, really to me, it’s an analytics fatigue because now you have all of these point solutions where you have to log in, to determine what’s happening from a security perspective. Well, how do you how do you look and step back and see that whole user experience, what that path for that user to get to that SaaS application? How do you troubleshoot? Well, you’ve you have to swivel chair from one device to the next, from one portal to the next, and it’s really difficult. So the IT skill set is is growing. Also, is a enormous gap there.

But it’s it’s difficult to to translate skills from one platform to the next and really do it efficiently.

The other the other element is, you know, from a troubleshooting perspective and inconsistent cloud performance, you know, really determining what the challenge is. Is this an application issue? Is this an Internet routing problem?

You know, really kind of coming back to just making a good experience for, the clients. We have the technologies, but it’s just not integrated fully integrated altogether. Well and and also with that that, integration and multiple platforms, this does innately create security gaps. If you have different systems and more complexity, you’re automatically going to have more patching, more management, more things to manage, and just keep your arms around, and complexity does create security gaps.

And last, again, skill sort shortage. This is this is truly a a problem that we all have to deal with and help our our our friends on the IT, side deal with because people are being asked from the security side to help manage network, and network folks are obviously being asked to manage security services. So simplifying, unifying the platform, aligning this with the business. You know, one one concept that’s brought up here is NAS. So NAS has been something that has been mature on the WAN side, but we’re starting to see that on the WAN side being much more functional and easier to use on on the network LAN side of the services that we sell. So it’s a bright future, but currently, lots of complexity, lots of sprawl, device, portals, analytics, reporting. It’s it’s a lot to take in.

Yeah. And I think, you know, there’s opportunities there, which is the key. Right? When you hear about complexity, when you hear issues, you know, I’m never having issues accessing a certain app or we’re having issues with all these devices.

There’s opportunity there for us to come in and help, and some of those consolidation opportunities you can see on the slide here. But, obviously, that is not an exhaustive list. We’ve got a lot more going on. Thanks, Gundy.

We’ll have you back here in just a couple minutes to talk on, but let’s make a transition here. Next slide, Chandler.

Let’s talk a little bit about where we think we’re going here. And to join us as the ghost of the network future, it’s Telarus’ principal solution architect, mister Jason Kaufman, looking very festive in his Christmas outfit. Jason, welcome to the call. Let’s talk a little bit about where we see some of this going. And I think, obviously, there’s a few things that we’re starting to get a taste of already, but we can also start to maybe extrapolate that a little bit and see, hey. Where are we going with some of this stuff? So, Jason, welcome to the call, my man.

Thanks for having me, Graham. Yeah. I I tried to dress to impress here. I got the the the tie and the sparkle knits and all this stuff. Just wanted to keep the thunder going.

That’s it, man. I love it. It’s a good look. It’s a good look.

So let’s talk about where you think we’re going here, Jason. Obviously, you have a lot of conversations with TAs and their customers about, you know, strategy. Right? Like, that sort of next step in the evolution of where we’re going with our network services. And, of course, you’ve got the of the view of the whole technology stack as our principal solution architect here. So talk through a little bit about some of the stuff you’re trying to prepare customers for as we move into the next few years.

Yeah. It’s it’s all about enablement. So it’s enabling the users, enabling the technology, and enabling the past, like, the connectivity on, you know, not only just AI driven technology, but then also how is it being monitored, how is it being consumption based to where you’re using and procuring what you need when you need it? Everybody’s getting used to the cloud infrastructure space to where you’re getting resources as you need them.

You’re paying for them at the hour that you need them, and then you’re turning them off when you don’t. A lot of the conversations around connectivity is, hey. I want to procure connectivity when I need it, and then I wanna give it back when I don’t need it, but I only wanna pay for what my usage is. So it’s no longer trying to subscribe to, hey.

We need to subscribe to ten gig pipes because we need that ten gigs for five minutes out of the day. No. It’s only subscribing to what you need, and then you’re bursting and taking the additional, you know, delta when you need it and then allowing somebody else to use it, you know, when they need it. So a lot of the company a lot of the conversations we’re having is not only building the capacity to withstand all these different usage structures and using it for all these different, you know, all these different customers and what they need it for, but only allowing them to, you know, procure it when they need it and giving them access to it at those times.

So what I mean by that is, you know, let’s say you have a massive migration or data backup or something like that, and you’re only doing it after hours. After hours is traditionally from electricity, from resource consumption, from anything like that. It’s generally been a lower cost time to use different resources. So how do we do that from a connectivity stance?

Hey. We’re gonna do our backup strategy around three AM or something. Maybe we can use a cheaper transport during that time, take it, and then give it back to allow somebody else to use it outside of that time frame. So it’s using it when you need it, but then also using that AI intelligence to say, hey.

It’s gonna be up when I need it, and it’s gonna have that self healing characteristic to say, hey. Automation’s gonna figure out there’s an issue, whether it’s performance, it’s it’s downtime, it is whatever whatever degradation is gonna is being read, but it’s automatically gonna heal it when somebody needs it. So you have it. You have you know it’s robust, and you have what you need when you need it.

Yeah. I love that. And and I think, Chandler, if you wanna move to the next slide here, there’s a couple of fundamental forces that we find that are really kinda putting a huge impact on this. And, obviously, behind the scenes on all of this is AI.

Right? AI is a huge initiative that a lot of companies have. It’s a big part of it, but it’s not the only thing that’s going on in the network space. These three things here, I think, are are are ones that we’ve identified as trends that you can talk to your customers about.

The device explosion, Britton and I talked a little bit about that. Edge computing, all of these things being done at the edge, Kaufman, instead of being done within, you know, the corporate structure. And then, of course, you talked on it a little bit with this as a service, you know, disposition that a lot of cuss customers have where they wanna buy things as they need it, use it as they need it, and not pay for stuff they’re not using. So talk a little bit about how you’re incorporating these things into your conversations.

Yeah. It’s minimizing the latency to get to those resources. So as you were saying, how quick how quickly can we get that user to access whatever they need to access to do their day? So, you know, we’ve seen on the news right now how China’s pumping out the six g technology, multiple hundred gigabits per second at a mobile device wherever they’re going.

And now we’re talking about companies like T Mobile that are offsetting, and there’s other companies doing this as well, offsetting the cellular technology with satellite, with partnership with Starlink. So you’re enabling that person wherever they’re at have access to company data or personal data or whatever it is. And then now we’re also taking those resources from the cloud infrastructure, from the on premise infrastructure, putting it on the edge to where it’s the first pop of wherever that ISP is. So now you’re minimizing the distance it takes to travel there.

So that all ultimately, you’re gonna give that better experience and quicker access to data so that person’s not gonna have to wait for the sign on times. You know, everybody always translates this to AOL startup message. Like, you know, having to having to go through those seven or eight different steps before you can actually get into what you need to do. Now imagine having no matter what you need to have access to, you have it to where where you where you need it to be, and then just building out all that infrastructure to make it quicker.

You know, the quicker you have access to stuff, the more technology you can get access to. You have to have that foundational role of, hey. I need to be able to con to get to something and connect to it as quick as possible and where I needed to in order to have access to it. So the quicker they can get connectivity options to wherever the person’s located, the more access they could do and the more technology you can give them access to.

I know that’s kinda like one of those things, like, you’re looking at the hundred things of sales that you you know that you didn’t know type of thing, it’s one of those things. Connectivity is the bare bow the bare bones to everything. In order to give somebody access to things, you need to, you know, build it to them.

Yeah. As Sherif said in the comments here, I think it’s a great know, connect networking is the new big oil. Right? It’s the thing that’s behind the scenes on everything we do, every single piece of technology you sell to your customers.

Behind the scenes, there’s a network that drives that and makes that possible. And anytime somebody’s making a change, there’s an opportunity to talk through a network refresh. So let’s bring the whole crew back on here, Hass and Brinton, as we move to the next slide there, Chandler, sort of you know, let’s talk through a couple of questions that we ask, couple of things that we say, couple of technologies maybe that we’ve got our eyes on here over the next couple of months, couple of years. You know, I know private cellular, private network, private cellular network is a big one that we’re seeing more and more of.

Guys, what else have you got your, your eyes on for, for our TAs here to keep keep in their, you know, view?

For for me, Graham, it’s a you know, and I lean on Britton and Kaufman all the time. Right? But it’s not only I I love that term that network is a new oil, but it’s not just about buying more bandwidth or more and more pipe or whatever. It’s it’s about how does this application need to behave for that end user experience, one, to have a hundred percent user adoption rate, and two, so I as the network administrator don’t get calls. So it’s not just about throwing pipe at it, but it’s about how that pipe needs to behave for that specific application.

And and I’ll give you an example. I’m working one right now at a at a New Zealand. They bought a contact center platform. They got all the pipe in the world, but everybody in New Zealand is transporting to US West to connect to the contact center host.

And the CFO doesn’t know anything about IT or tech or whatever. So why is this always so slow? Well, you and I and us, we can figure this out immediately. Well, why are you sending traffic all the way to US West when you need the traffic in Australia?

Well, that’s just how it was designed. We bought a bunch of bandwidth and that’s how it works. It it doesn’t have to be. So we, as advisers, need to say, how does that end user need to feel and behave on that application?

Where does that host need to reside? How does it need to perform and behave? It’s not about just throwing bandwidth out of it. It’s about throwing bandwidth out of but where is it connecting and why?

Yeah. Gundy, Kaufman, anything you guys wanna add here?

I I think, you know, Jason hit it. The the network is being treated differently. I think we have the the skill gap that we have is created, because these folks have traditionally dealt with AWS, Azure, the the, cloud models, and they expect that in all areas of their their network. There’s more and more conversations that I’m dealing with system admins instead of network admins that really want to consume just on a a consumption model. And legacy telecom processes and things like that, it’s it’s difficult. It’s difficult to transition from this, you know, build it after an order has been placed type of mentality to consume on demand. So that that’s one thing that I’m seeing recently in the last two years is many more discussions around that type of consumption model.

Now I’d say the the biggest one I’m seeing is a big push for AI ops, That self healing characteristics to where what Hoff was saying, that IT guy is not getting those calls after hours. The MSP is not getting calls after hours. The connectivity provider, the aggregator, whoever’s providing the service. You know, making sure that it can detect when an issue or potentially before an issue is occurring and then remediate it and make that user experience all positive no matter what’s going on under the hood.

So we’re seeing that with, like, network as a service companies that bring in, like, the Juniper, the Meraki to where you could as soon as you plug something in, you could physically see how it’s connected, where there’s a potential issue. You know, they could track it down super quickly to where that IT person has the root cause analysis at the snap of a finger. So think of not only getting that telemetry on the discovery side when you’re troubleshooting, but also having the system to say, you know what? We already have a playbook for all this stuff.

We’re gonna handle ninety nine percent of the stuff autonomously, and we’re only gonna need barely minimum human interaction. So a lot of the international companies that we’re looking for and that that we’re, you know, consulting with today, they’re asking for these types of things. How do I scale, and how do I have something that I don’t wanna deal with? How do I have it autonomous to where we can focus on business strategy and other things?

Yeah. So I think the AI ops is gonna be a massive push moving forward.

Yeah. I agree with I agree with Kaufman. That’s kinda why we work as a team to figure these out and ask these why questions. But I don’t wanna be the party pooper and and and burst the the balloons here. But when I roll out a application, it’s not magic. It’s not floating in the cloud. That application resides somewhere physically.

And if I have hundreds, if not thousands of applications in my organization, how do I know where that application physically lives? By implementing AIOps, I don’t have to know. I don’t have to worry about it. I’m going to automatically connect to that nearest host. Right? And that is super, super important.

Yeah. So, Chandler, let’s go ahead. Skip the next slide. Let’s just move to that that yeah.

Let’s move to this one here. So, you know, folks, you’re on the call here. Hopefully, this has been very helpful for you as we start to go in there. Obviously, that act of sort of classifying where you think your customers might be, that’s what we’re asking you to do here for the next step.

If you think these tools and these conversations are gonna be useful for you with your customer base, go ahead and take a look at your customers. Be like, hey. Where do they sit in this in this reality? Right?

Are they dealing in the past? Are they kinda struggling with the challenges of the present? Or are they ready for a conversation about where we’re going here and what’s next? So once you’ve done that, sit down with them.

You’ve classified them and help them with a plan. Right? How do we get you to the next phase? Ideally, we want them all in that sort of sitting on the edge of the present, looking to the future.

Right? And we wanna be there to help them do that. So, hopefully, you guys have found this of value and, always, of course, know that we’re here to help. Next slide, Chandler.

So, again, we’re here to help you guys with these conversations. As I mentioned on the call, both Josh, Britton, and, of course, Jason have these conversations all the time. Feel free to bring them in if you have conversations. Hey, Josh.

I feel like I’ve got somebody who’s maybe dealing with some legacy stuff here. I’d like to tee up on a call. Gunderson, hey. These guys are going on, and, obviously, all three of these guys can handle, you know, all the topics we’ve got.

Our team is here to help you folks. We hope this has been good. Remember, the best way to predict the future is to help your customers build it, and the Telarus team is here to help you do it. Guys, thanks again for tuning in all this year.

Jen, I’m gonna hand things back off to you.

Maybe we got a little couple minutes for q and a. I’m not sure if we do, but if so, all all of us are here to do that.

There haven’t been as many questions today. There’s been a lot of comments and saying, yeah. What what Graham said, what Brinton said, all that kind of thing. But I haven’t seen a lot of questions. So we can pause just for a second and see if anybody’s got any questions for this team before we move along.

But it looks like Yeah.

And if not, of course, if you have something that comes up in a in a minute, all of us will stick around and kinda put stuff in the chat here. So I know we’ve got a full agenda today, so we’re happy to kinda handle questions that way. Let’s do that. And before we turn off, just wanna again, so many great names in the chat. I really appreciate the contributions of the folks week in, week out, every time I’m on here, contributing with conversation and questions.

Hope you guys have a very happy holiday season, and, we’ll see you in the New Year.