Webinar · 25 minutes · Published August 2025 · Presented by Joel Sosebee, Director of Client Success at AT-NET Services
This webinar is for business leaders whose IT support, internal or outsourced, feels stuck in a cycle of tickets and firefighting with no real strategy behind it. Joel Sosebee of AT-NET Services looks at what reactive IT costs a business and why many of those costs are easy to miss.
Joel walks through the problems reactive support creates, the hidden costs behind it, and the proactive process AT-NET uses: technology standards, baseline security controls, continuous monitoring and a dedicated strategy role. He closes with questions to ask about your current IT relationship and answers attendee questions on cost, timing and first steps.
What this webinar covers
- Why “ticket tennis,” the endless back and forth between users and support, keeps a business stuck in reactive mode.
- The hidden costs of reactive IT: lost productivity, delayed projects and missed deadlines, lower customer satisfaction, employee turnover and the long-term cost of patchwork fixes.
- What changes with a proactive model: technology aligned to standards, a dedicated resource for proactive maintenance, root-cause fixes and a plan for cybersecurity.
- How AT-NET keeps proactive work separate from its service desk, with roles for standards alignment, managed cybersecurity and a strategy officer who builds a technology roadmap.
- Questions leaders can use to assess their current IT relationship and their team’s readiness for a cyber event.
- Live Q&A on telling a reactive vendor from a strategic partner, how cost compares, how soon results appear and what the first step is.
Chapters
- 0:00 Welcome and agenda
- 1:58 Ticket tennis and the problems reactive IT creates
- 3:29 The hidden costs of reactive IT
- 5:17 What proactive IT looks like
- 7:10 AT-NET’s proactive process
- 10:40 How proactive and reactive teams are organized
- 12:10 Results of a proactive approach
- 14:50 How to assess your current IT relationship
- 17:37 Q&A: choosing a partner, cost, timing and first steps
Key takeaways
- Proactive IT needs a dedicated owner. Joel’s point is that service technicians handling reactive tickets cannot also deliver proactive work; someone has to stand over it with metrics for success and accountability, as you would for any new initiative.
- Standardize first. Aligning your technology to industry best practices and security frameworks, even if you are not subject to compliance, is what makes results consistent and performance predictable.
- Security tools are only part of the answer. Joel stresses that only a portion of baseline security controls are products; the rest is people and process, backed by continuous monitoring for anomalous activity so threats are detected early.
- Plan for a cyber event before it happens. An incident response plan with clear assignments, practiced through regular tabletop exercises, works much like a fire drill for your team.
- When evaluating a provider, ask how they deliver proactivity: how many dedicated resources they have for it, what the model looks like, how they have done it successfully and how long they have been doing it.
Is your IT support stuck in firefighting mode? A short conversation can show whether a more proactive, strategy-led model would help your business. Learn more about AT-NET’s managed IT services or vCIO services for IT strategy and planning, or talk with the AT-NET team.
Transcript
Read the full transcript
0:00 Joel: All right, thanks everybody for joining our webinar today on reactive IT. My name is Joel Sosebee. I’m the Director of Client Success for AT-NET Services. We are a managed IT solution provider in the Southeast, and we work with small and medium businesses. We want to specifically zero in on reactive IT today because when we meet with business leaders each week, we hear two things from them consistently that are problematic within their business. The IT relationships that they have are too reactive, and again, that’s whether they have an internal team or whether they’re partnering with an external organization. They’re too reactive in nature, and there’s no real strategy that’s being delivered in their business. So those are the reasons why we wanted to focus in on this today, and the alternative to a reactive-based IT model in your business.
0:55 A couple little housekeeping items before we get going. If you could mute yourself for the duration of the call, feel free to submit any questions in chat along the way. We’ll get to those at the end, and then you can unmute yourself and come on live if you’ve got any questions that way.
1:18 All right, here’s our agenda for today. We’re going to go through what the problem is at large with reactive IT, what problems that causes within the organization, and then zeroing in on some of the hidden costs, the things that not everybody thinks about when it comes to reactivity and what that represents in your organization; what a proactive IT difference could look like; how the proactive process is delivered specifically by the model that we’ve designed; some of the results that you can expect in your business from a different approach; how you can practically get started along these lines; and then last but certainly not least, give you a chance to ask some questions.
1:58 All right, so let’s talk about the first thing. This is something that we talk about very often in our business, something called ticket tennis. Literally, it’s that endless back and forth between users and support. This is something, again, that we hear from people that we talk with, prospective clients: just that routine. We even call it the reactive spiral of death in our business, because it doesn’t lend itself to anything that’s valuable for the business overall, except for a particular user at any given point in time getting support. But nothing really changes.
2:36 Reactive IT results in unplanned downtime for the organization, disrupting revenue, product and/or service delivery, depending on your business. Those things can be very, very costly, and we’ll talk about some of those costs in a minute. Lack of standards leads to inconsistent results; we’ll talk about what the alternative to that is. Firefighting, preventing any kind of strategic improvement in the organization. If you’re fighting fires, you’re definitely not being strategic. Reactivity increases risk to cyber attacks. That’s one of the things that, if you’re not specifically thinking about it, or you have a partner that’s helping you think through those things, you’re not thinking about reactivity in those terms. But it really increases the likelihood and the probability that you’ll have a cyber attack, and it will be more devastating in your business if you have a reactive model.
3:29 Let’s talk about some of the hidden costs. Lost productivity across the workforce is probably number one. You think about your largest expense in your budget: it’s your people. And so lost productivity is something that happens when you have a reactive service model, which is very costly for a business. Delayed projects and missed deadlines can result from reactivity and things that don’t work as they should. Lower overall customer satisfaction scores in your business. And something that we’ve heard from people that we’ve met with is having turnover within their business, and not all of the cause, but some of the cause, was technology not working well in their organization. If they can’t do their job, they’re going to have more and more frustrations, and potentially lead to some turnover.
4:19 Long-term costs are very high in this type of model, based on patchwork fixes is what I’ve got there, but any kind of band-aid, treating symptoms versus getting to the root cause of an issue. And over the last five years, as cyber events have gone up, we get calls routinely for incident response from people who aren’t even our clients. People will call in and ask us to help them through cyber events in their business. And there’s two things that we know from dealing with each one of those things. One, they’re far more costly than any organization thinks at the time. When you consider forensics and legal and lost productivity and potential loss of clients, all those things are very, very costly for an organization. And regardless of what type of business you’re in or the business plans that you’ve set for your business for this year, it has the potential of derailing those business plans.
5:17 So let’s talk about the alternative to that, because there is an alternative. We’ve been successfully delivering on this model for, we’re approaching 14 years in it. But let’s talk about what proactivity would look like in your business. The graphic that I’ve got there is more the care and feeding versus the firefighting model. What that represents in your organization is an alignment of the technology to standards. We’ll talk about specifically how we deliver that, but standardizing the technology that you own and employ within your organization. If you think back to what I said a minute ago, the overall cost of having reactivity in your organization is inconsistent results. Getting consistent results when you standardize the technology is the alternative to that.
6:00 A dedicated resource that’s focused on proactive maintenance and optimization; again, we’ll talk about how we deliver that. Eliminating those recurring issues before they have an impact on the business: proactivity will allow you to do that because you’re focused on the underlying root causes versus those symptoms. Predictable performance and outcomes is the benefit of standardization as well as proactivity, as a part of that: just making sure that we do have a predictable outcome for the way that technology should be run. Freeing up your team to focus on those core business activities, the reason why you hired them in the first place, not to manage your technology, but to do their particular task and carry out your mission. And then a proactive approach lends itself to a plan for cybersecurity and the journey that that is. And then also, not if something happens in your business, but something happens in your business along the way of cyber: having an effective plan that your team can socialize, and you know who’s doing what and how that will work according to the way that you need it handled.
7:10 So, let’s talk about our proactive process. I’m going to go through this; it will be just some verbiage on the screen, and then I’ve got a graphic to support that. But I just want to give you an idea of how we approach this. One is, you can’t deliver proactivity if you don’t have someone dedicated for proactivity. You think about in your organization, if you want to move the needle on either a new product, a new service, or a different way of doing things within your business, you would hire somebody to stand over that. They would have metrics for success and then also accountability. The same is true in this case with proactivity. You can’t do that from reactive-based service technicians.
7:56 We have a process called the standardization and alignment of technology. So we align the standards, the technology that you have, against industry best practices, our years of experience since 1999, and then largely based on security frameworks. Even if you’re not subject to compliance, there’s still standards that organizations ought to adhere to to drive down risk. All those things are measured on an ongoing basis and aligned to those standards so that we can build a process for how we can help your organization get better. And so those continuous reviews are important in order to do that.
8:33 The implementation of baseline security controls: baseline security controls are necessary to drive down a lot of the risk. But when we see other organizations out there and how they’re doing cybersecurity, almost everybody we talk to says that they’re fine when it comes to their cyber risk. But when we pull back the curtains and look at what’s going on under the surface, there’s some tools, and even though the tools have been upgraded, tools are 25% of what you need when it comes to cyber. So you need baseline security controls, and only a portion of those are products. The rest is people and process, and that’s what helps you reduce that risk for cyber attacks. If everybody was fine, a small and medium business wouldn’t be compromised every 39 seconds.
9:22 Once those security controls and those baselines are implemented, then we can pivot to continuous monitoring for anomalous activity on systems at large: what looks like a threat, and alerting on that threat so we can take immediate action. Again, think that the early detection is what we want to put in place so we can minimize the impact to the organization. That’s what we’re talking about here. And then having a dedicated, in our business we call it a chief strategy officer or strategy officer, that’s dedicated to providing that element of strategy. So when we hear business leaders saying there’s no strategy, it’s typically because whatever they’re doing, again, whether it’s an internal process for IT or external, there’s no one that’s standing over providing thought leadership to the organization that’s focused on those business outcomes that are necessary. And with that strategic planning, we’re able to build a technology roadmap to align the technology that you run today, and the technology as it changes over the course of time, with those business goals, to make sure the technology is right-sized but it’s also optimized, and that new and emerging technologies are considered when it comes to your business goals.
10:40 So this is what that looks like graphically. These are all the functional areas, save for professional services, and everybody would have some element of delivering projects in business. But if you look at the bottom diamonds there on the reactive side, again, functional areas that we also have in our business, the centralized services down here really represent delivering tools, standing over those tools, making sure that they’re operating the way that they should be in the organization. And then you’ve got the backstop over here of a service desk. So, not unlike anybody else, we want to make sure that when our clients have issues, we’ve got great support for them to back them up. But what’s moving the needle forward on businesses are these proactive elements that I’ve outlined on the slide before. And you notice these are a different color, and that’s really to indicate that they don’t get involved with these reactive things down here. So the alignment: we’re focused on aligning the technology to standards. Our managed cybersecurity team is implementing the framework that’s based on the chief strategy officer, when he’s talking to clients and assessing their level of risk for the technologies that they operate, and based on the current tactics, techniques and procedures of the threat actors. And then we have a separate team that can implement those changes and manage those things on an ongoing basis.
12:10 So, results of proactive IT. This is a really, really big one when you think back to what I mentioned a minute ago on the decrease in overall efficiency of your workforce. With a proactive approach, you get rid of those issues that are super consistent and not diagnosed at a root cause level. You see a significant increase in workforce productivity. That might not be 30% in your case, but we’ve seen up to a 30% increase in workforce productivity. Significant reduction in downtime: when you’re proactive, you can plan around things. You can put contingencies in place. And don’t just think cyber when you think downtime. There’s lots of things that can introduce risk for downtime in an organization, and those are all things that we help our clients manage. Any kind of downtime is costly for the provider that you’re using, so us or someone else, an internal team, and your organization at large. And so you want to minimize those downtime events.
13:12 Better cost predictability for IT expenses. So when you have proactivity, you have a strategic plan, you have an IT roadmap. All those expenses, anything that needs to change, investments that you need to make in your organization that are going to have a financial impact, those are identified and put on the roadmap so that you can budget and plan for those types of things. Things that come up in your business that are unplanned, because you’ve dealt with them before in a variety of ways in your business, I’m sure they’re always the most costly, and you have to make quick decisions you’re not necessarily prepared for. So we want to help prepare organizations for those types of things.
13:52 Higher employee satisfaction with IT. If you think about the way we all do business nowadays, we’re all very technology dependent. The technology needs to work so we can do our job day-to-day, which will lead to higher employee satisfaction overall. It should yield a better quality customer experience when the technology works right. As I mentioned a minute ago, you’ve got a mission in your business. You’re delivering a product or a service, and you want that to be a quality experience for your customers. Technology is an enabler to help you do that. And then reducing risk for cyber attacks by up to 95%. We know that that’s mathematically possible because of the security controls that we put in place. You can’t get to 100, and you can’t get to 100 because there’s always some reason that the technology will fail. And that’s why the early detection to minimize impact is really, really critical in there.
14:50 So let’s talk about how you would get started, and it really starts by assessing your current IT relationship. Just think for a second about how things work day-to-day from an IT perspective. If you’re in a leadership role, what do you consistently hear from your teammates? Is everything going great? Is there room for improvement? Are you consistently hearing about the same kind of things? Are issues going unresolved for long periods of time? That’s a good indication that things are reactive in your business when it comes to technology and technology management. Do you meet with someone other than an engineer or an account rep regularly? You should. People that you’re working with should have somebody who’s, again, not an engineer pulled off a service desk or an account rep. We have account reps in our business and they do a great job, but we don’t put them in charge of thought leadership. That’s not what we want them to do, to help an organization strategically plan for things.
15:48 How well does your current partner know your business? Do they educate you on current technologies and things to consider in your business? If the answer to the previous question was no, probably a good reason why they’re not educating you on those current technologies. But a valuable partnership should be giving you things to consider in your business that could potentially help, not just trying to sell you things, but to get you to think about doing things in a different way.
16:20 How well is your team prepared to deal with a cyber event? This is a really good indication of whether you’re in pretty good shape when it comes to cyber or you’ve got a long way to go. If you’ve got a plan, that would be the first part: what we call an incident response plan, something that would have a series of assignments for teammates and a process that you would undergo in your organization if and when something happens on the cyber side. It’s sort of a process; you think back to the elementary fire drill that we were all subject to. Same kind of thing. What would you do, not if but when something happens, and can you follow along those set of instructions and processes? And if you don’t have that, then you’re likely not doing tabletops routinely to figure out what that would look like and make sure that you’ve got everything planned for.
17:20 And we’d be remiss if we didn’t ask: after you evaluate the relationships that you’ve got right now, do you need a better IT partner? Is that where you are right now? Is now the appropriate time to consider doing something different?
17:37 Joel: All right. At this time, I’ll open it up to any kind of questions that you all have. And Austin, I don’t know if we’ve got any submitted via the chat, but if anybody wants to ask any questions, happy to answer any questions for you that I can.
17:55 Austin (moderator): Yeah, we do have one from chat. The question is, when you are evaluating a change, how do you discern between a reactive vendor and the strategic partner model that you were talking about?
18:15 Joel: How do you evaluate it, or…?
18:17 Austin: Yeah. How would you discern, when you’re looking at making a change and you’re meeting with somebody, what would you look at to determine whether they’re going to be a reactive partner or a strategic partner?
18:31 Joel: Well, I would look at how many dedicated resources they have for proactivity. That’s probably the first place to start: how many people outside of that model that I showed everybody graphically. If everybody’s in that reactive space, you can’t really expect better results. There needs to be a dedicated person that’s in charge of just carrying out that mission on the proactivity side, and so that’d be a good place to start. And I’ve given people practical ways to evaluate what they’re doing right now. But yeah, that’s what I would do. Specifically, how do you deliver proactivity would be a question that I would ask any prospective partner. How are you delivering that? How have you done that successfully? What’s the model like? How long have you been doing it? Those are some questions that you can ask them and get a sense for if it’s good intentions, because good intentions won’t get you there. We’ve seen that. Very rarely do you see somebody change their business model, which is what would be required if you don’t have something like this in place. Good question, though. Any other questions?
19:42 Austin: Yeah. I’ve got a couple more here. As far as cost goes, does proactive IT cost more than traditional support?
19:52 Joel: I’d say overall the answer is no, just because of all the costs, like we went through some of the hidden costs. Typically on your line item as a budget, if you just look at it and what you’re spending on it, people typically zero in on what I’m paying a managed service provider, what I’m paying Microsoft, all those things. A relationship like this is very, very different from your traditional reactive service model. So I would say sometimes, because when we’re talking to people, what we’re trying to evaluate is: do you need better results, would you be willing to invest a little bit more money if that were required, and is now the right time to make a change? Those are the three questions that we are trying to figure out when we’re meeting somebody for the first time. And so in that, a lot of times we do tell people, “Hey, look, this might be a little bit more expensive.” In the long term, it’s significantly less expensive. When you think about all those soft costs, and you think about the implication that poor technology and poor technology management has on your mission at large and on your clients, it’s significantly less expensive. Good question.
21:02 Austin: Okay. Well, along those same lines then, if you’re making the change to proactive IT, how quickly can you expect to see the results you’re talking about?
21:12 Joel: Well, I think you can see results in as little as 30 days. I don’t think you’re at the point where you’ve recognized or realized all the change at that point. But one of the things that we do when we’re going through the onboarding process with a new client is we’re really looking for what are those recurring issues that you’ve been dealing with for 12 months or more, and the things that your team is frustrated with daily. And we have a process for taking down those things to start with. So if we can eliminate a lot of those things that are causing reactivity and begin to focus on some of the other elements, over that 60- to 90-day period, things really, really settle down dramatically. But people see results in as little as 30 days, for sure. Good question.
22:06 Austin: The last one I’ve got here is, if you’re looking to make a change to proactive IT services, what’s the first step to take?
22:17 Joel: Well, I think I would start with the last thing that I laid out: do you need a change? Not everybody that we meet with needs a change. Not everybody out there is doing a bad job. We know that the vast majority of people are set up to deliver on the reactive model. We’re in a peer group that’s nationwide, and within that we talk about what they’re seeing in their markets, and we know as many as 95% of people are simply delivering on this. It’s really a 12- to 15-year-old IT services model. But consider some of those things, and that’ll really expose if you’ve got things that you need to consider. And so the next step would be, and we make this very easy for people, it’s just a conversation. Let’s sit down and talk about what you’re thinking about the IT services that you’re receiving, how your technology is today, what, if anything, needs to change going forward. And we evaluate whether or not a change would help you in those areas, whether potentially a change to us would help you in those areas. And then last, but certainly not least, does it make sense? Based on the things that you’ve got to take down with your business goals for this year, is now the right time to make a change? And if all those things line up, then we talk about what that would look like and help them have a sense for what it’s going to look like when we take over support, and what it looks like as we work with them strategically and proactively in some of those areas that I’ve outlined. So yeah, it just starts with a simple conversation. We normally ask people that we’re talking to, prospects, 15 or 20 minutes just to gauge what makes sense to have another conversation. So that’s the way we lay it out. Good question. Any other questions?
24:06 Austin: That’s all I’ve got.
24:08 Joel: Okay. All right, good deal. I put my contact information up there, so feel free, if there’s something that you have a question about that we covered today but maybe didn’t get to, or you’ve got questions that you didn’t get a chance to ask, or you’ve got a teammate that watches the recording of this and they’ve got questions, feel free to reach out to me. Happy to field any questions or have a conversation at your convenience. But otherwise, I appreciate everybody for joining our webinar. We’re going to do these monthly, so hope to see you on a future webinar. Thanks again. Have a great day.
This summary and transcript were prepared from the webinar recording with AI assistance. The transcript is lightly edited from YouTube’s automatic captions for readability. More episodes and webinars: The CyberCast by AT-NET.