Why IT Leaders Are Switching to Device as a Service for Laptops and Devices | Episode 5
The IT Director's PodcastShow Notes
In this episode of the IT Directors Podcast, we break down why device as a service is poised to become one of the most important strategies IT device procurement, repair, and management.Jay and Michael sit down with Stan Sargent, founder and CEO of Clear Winds Technologies, to discuss how rising hardware costs, supply chain disruptions, and global tariffs are forcing companies to rethink how they purchase and manage devices.From Chromebooks and laptops to desktops and tablets, the traditional model of buying and maintaining devices internally is becoming harder to sustain. Many organizations underestimate the true cost of managing IT devices, including repairs, security updates, asset tracking, and the hidden labor costs involved in break-fix support.That’s where device as a service comes in.Instead of large capital purchases and unpredictable repair costs, device as a service allows organizations to move device management into a predictable operational model with fixed costs over a period of time, lifecycle management, and built-in support.In this episode, we discuss:• What device as a service actually means for IT leaders• Why hardware pricing is increasing across the industry• How tariffs, memory shortages, and chip demand are affecting device costs• The hidden costs of repairing and managing devices internally• How device as a service simplifies asset management and lifecycle planning• Why more organizations are moving toward DaaS to stabilize IT budgetsIf your organization manages laptops, Chromebooks, or end-user devices, this episode will help you understand why device as a service is becoming a critical strategy for the future of IT.Check out the show notes here: https://www.clearwinds.net/device-as-a-service-solutions/
More from The IT Director's Podcast
Cybersecurity horror stories are real, and one spoofed email led to a $750,000 wire that was gone in about 60 seconds. In this episode of The IT Directors Podcast, Clear Winds CEO Stan Sargent shares the cybersecurity horror stories he has seen firsthand, and what IT directors can do before it happens to them. Jay and Michael sit down with Stan Sargent, CEO of Clear Winds Technologies, to walk through real cybersecurity horror stories. They cover a phishing click that led to ransomware months later, and backups that were encrypted along with everything else. This is a practical conversation for business owners, IT leaders, and technology professionals who want to understand how attacks actually unfold and what to do about them.
Most IT pros hit the same wall when they start trying to figure out how to become an IT director (or how to become an IT manager first): you've got the hard skills, you know the tech, but nobody ever taught you the other side of the job — the people, communication, and leadership skills that actually get you promoted, and keep you there once you land it.
Many IT directors eventually hit the same wall: you're great at the technical side, but no one taught you the actual IT director skills — the political, cultural, and leadership moves — that determine whether you thrive in the role or just survive it.In this episode, Jay and Michael sit down to answer 5 real questions sent in by listeners and viewers — the kind of questions that rarely get addressed in technical training but come up constantly for anyone leading an IT department. Jay draws on 25 years of experience as IT Director and COO at Birmingham City Schools, including a story involving a $21 million grant, Tim Cook, and a decision that almost went the other way.This is a practical, no-BS conversation for IT directors, CIOs, and anyone trying to lead a technology team while also navigating executive politics, retention, and burnout.🚀 In this episode:0:00 Intro1:48 How to get a seat at the executive table instead of just being "the IT guy"9:56 How to say no to a CEO's pet project without losing political capital16:52 How to manage a high performer who refuses to document anything19:17 How to retain great engineers when you can't compete on salary22:57 How do you actually unplug when you're the only one who understands the IT infrastructure29:24 BloopersIf you've ever felt stuck outside the room where decisions get made, or been the only one holding the keys to the kingdom — this episode is for you.
Every IT team gets the same call: "the system is down." It's a description, not a problem — and the engineers who can tell the difference are the ones who keep systems running. In this episode, Jay and Michael welcome back fan favorite Rick Goudeau, employee number two at Clear Winds and a database specialist with over 50 years in technology dating back to the 1970s. Rick has spent his career on Oracle E-Business Suite upgrades, disaster database recoveries, and the kind of thorny problems that don't show up in vendor documentation. In "Tales From the Old Timer," he breaks down the specific behaviors that made him effective — thinking like a diagnostician, working methodically, staying relentlessly curious — and why mentoring the next generation is the part that lasts. This is a practical, no-BS conversation for IT directors, CIOs, DBAs, systems engineers, and anyone responsible for building a team that can troubleshoot without them in the room. 🚀 In this episode: - Why "the software doesn't work" is a description, not a problem — and how to get to the real issue - The Sherlock Holmes principle Rick has used for 50 years: eliminate the impossible, and notice the dog that didn't bark - Why being methodical doesn't mean being slow — and how documenting 200-300 step Oracle upgrades pays off years later - Why roughly 60-70% of IT problems are understanding issues, not technical ones - The WordPress fix that worked — and why the right engineer refused to stop at "it works now" - How an AI model change quietly slowed down a working application, and what that reveals about AI as a starting point vs. an ending point - Recovering a production database that was accidentally deleted — and the mentoring moment that came out of it - The reboot that didn't come back up, and why staying calm in front of the person shadowing you matters more than the fix - Why mentoring has to be organic, not something you do because you're a director or manager - The intern who bought Rick a mug 40 years ago — and why he's still using it - Rick's parents, two walls of books, and the reason he was never allowed to say "I'm bored" - Why the goal is building people who can pass you, not people who need you If you've ever been the only person who knew how to bring the system back up — this episode is for you. 👀 Check out the show notes: https://www.clearwinds.net/it-team-me...
Every network team is being told the same thing right now: automate faster or fall behind on AI. But the engineers actually getting it right aren't the ones automating everything — they're the ones who know exactly where automation can break things .In this episode, Jay and Michael sit down with Russ White, He has decades of experience building and designing large-scale networks for companies like Cisco, LinkedIn, and Juniper and holds the distinction of earning the very first Cisco Certified Design Expert (CCDE) certification in 2007. In addition, he hosts his own podcast, The Hedge. Russ White breaks down the real trade-offs of network automation, why AI should validate systems rather than build them, and whether AI will ever fully replace human judgment in network design. This is a practical, no-BS conversation for IT directors, CIOs, network engineers, and anyone leading AI or automation adoption inside an organization where one bad automated decision can take down the network. 🚀 In this episode: - Why "a fool with a bad tool is worse than a fool without a tool at all" - The hidden trade-off automation always brings: speed vs. brittleness - Why most automation failures come down to culture, not tools - How to shift a team's mindset from "build the runbook" to "hunt for new failure modes" - Why relying on AI to build systems — instead of validate them — is backwards - The Stanley Milgram experiment and what it reveals about blind trust in AI - What part of network engineering will always require humans, even in 2036 - Why humans' lack of self-discipline is the real AI risk, not the technology itself - What cloud, ATM, and expert systems can teach us about the current AI hype cycle - How Russ White's PhD in Philosophy shaped the way he approaches network design If you've ever been told to "automate everything" while still being the one responsible for the network staying up — this episode is for you. 👀 Check out the show notes: https://www.clearwinds.net/russ-white-will-ai-replace-network-engineers-2026/ 👀 Check out Russ White's podcast, The Hedge!: https://open.spotify.com/show/0LJ1ejpJIrnYeNJXYpWVe6 🔔 Subscribe to The IT Director's Podcast: Weekly insights on AI, cybersecurity, business IT strategy, business technology, automation, and more. 📲 Follow The IT Directors Podcast: LinkedIn: https://www.linkedin.com/company/clear-winds-technologies/ Instagram: https://www.instagram.com/theitdirectorspodcast/ Facebook: https://www.facebook.com/theitdirectorspodcast/ X: https://x.com/itdirectorspod YouTube: https://www.youtube.com/channel/UCj0XUY76X-5heKedsqHAEjQApple Podcasts: https://podcasts.apple.com/us/podcast/the-it-directors-podcast/id1868490062