Transcript for "Best Practices for Device Lifecycle Management":
Hello, everybody. Thank you so much for being here. I'm gonna give everybody another second or two to find their way into the room. But in the meantime, I will introduce myself. My name is Michael. If you have never been to one of our webinars before, it's very nice to meet you. I run content for Rippling IT. So great to have you here as always, whether you're new or returning. Another thing we like to do while we're waiting, I like to get things started with a just with a quick poll to to get everybody warmed up. So I'm gonna share that real quick here if I can find it. Nope. You got it. Cool. So today, since we are talking device life cycle management, we're gonna start by asking everyone about their current process for device deployment. And I'm just gonna run through this real quick. How would you describe your current device deployment process? Process? Whether it's fully automated, zero touch deployment, which is what we love to see, or partially automated with some manual config required, mostly manual. I'm seeing a lot of those come in right now, you know, where IT kinda needs to be involved with every device before deployment, or are you completely manual and really individual setup bespoke for each device? So, please feel free to to share there. I see some responses coming through, so that's great. There will be a couple more polls as we go along today, so just keep an eye out for those and and weigh in. So as I said, today, we will be talking about best practices for device life cycle management. And we will be doing that with our product lead for IBM here at Rippling IT, Pablo Hernandez, as well as our excellent IT community manager, Carter Francis. Tons of experience between the two of them. A lot of expertise. I know you'll you'll enjoy what they have to say today. So, since they're on top of all the details today, I am responsible for a couple quick housekeeping items before we get started. So number one, you'll be getting this full recording on demand. So you can watch it later for back to anything you heard. Keep an eye on your inbox for that. We will send it along. Number two, kind of as we've noted with the polling, please feel free to use the chat as well. I see some people already doing that, which is great. Continue to do that. Use that and the q and a fields while we're on today if you have anything you wanna ask. We will try and get to everything we can during the session. Anything that we miss live, we will follow-up later by email. You may be sensing a theme there. Finally, there is a bunch of related content that we've attached to this session in Goldcast. You'll find links there to read some of the free guides we've published, read more about very exciting new feature that we've launched this week in device buyback, which we'll talk about a little today. You can register for future webinars, etcetera. Lots of good stuff there. So that is under the docs section of your side panel that you see next to poll and q and a. Please take a look. Check out whatever catches your eye. But, with that, I will go ahead and, welcome in Pablo and Carter, and I will see you guys at the end of the talk today. So I'll be in the chat in the meantime, and I hope you guys enjoy. Alright. Welcome, everyone. Today, we're going to get tactical about device life cycle management. So how do we go from we think we know where laptops are to every device, every stage along the way, fully managed. Howdy, Pablo. You wanna give a quick hello to everybody? Hey, Carter. Hey, folks. Today's goal is very practical. It's about the exact policies, the processes, and handoffs that make zero touch deployment, clean off boarding, and compliant disposal work at scale. Right on. Well, we're gonna start with, like, what the must have stages of a device life cycle look like. So maybe let's map the terrain. What stages, Pablo, actually matter here? Yeah. So it's, if you look up the entire process, a durable model is plan, procure, provision, operate, refresh, recover, and finally retire and dispose your devices. So you're not just tracking hardware, you're managing risk, cost, and compliance as one system, and treat each stage as a measurable process with owners and SLAs. For example, things like time to device, first day readiness, retrieval success rate, and whatnot. Right on. Well, I guess, kinda makes sense to start from the beginning. Right? Like, how do I make sure I'm getting a good price on procurement? I know that in my experience buying devices, like, there's so many vendor options and stuff. It can definitely feel like a guessing game. Like, how does how can IT teams that we're we're, you know, in front of make sure that they're not overpaying for devices? I mean, the first thing I always tell people is, you gotta protect your budget. So buying from authorized resellers and comparing their prices to MSRP, which these, manufacturers suggested with your price before committing is really important. And with authorized resellers, you can be sure that you're getting genuine hardware, valid warranties, eligibility programs like Apple Business Manager or Windows Central, versus gray market or consumer channels, which often don't qualify for those. And the second thing is maintaining a standardized catalog of preapproved SKUs. So you can benchmark pricing regularly and avoid one off prices. IT assets cost cost analytics or even basic monthly price audits can show whether vendors are creeping above market level. Yeah. I think, I think for sure, like, a standardized catalog. I I remember being in scenarios where I didn't have that or, like, before I kinda realized that was, like, good practice and, like, supporting all these different kinds of machines can, like, get pretty crazy pretty quick. Exactly. I think you have, like, your engineering computer, your non engineering computer, your finance, PC, that can really help. Yeah. I think that's important, you know, to to call out that Rippling's device management integrates directly with our device store. So in that kind of scenario, you you know, we are an authorized reseller. We're a top 10 Apple reseller. So, you know, you're always gonna see current MSRP prices. You're always gonna see live inventory, so you'll know what's actually there and what's not. Makes it easier to to support a, you know, a a business that operates in many different places, maybe. Yeah. And and not only will you see the MSRP, you will also see the discount that you're getting on MSRP, which, cannot up to a lot money. Nice. Awesome. Well, what, what does good zero touch look like? I know that is a concept that gets kinda thrown out a lot. And for people who haven't experienced it, what is the actual bar? What it what does it look like, and what does it feel like when it's operating right? Yeah. Good question. So I think for Apple devices, it's using Apple business manager with automated automated device enrollment. So that Macs, iOS, iPads, auto enroll on the first boot into your MDM. They receive profiles, apps, and security baselines. And so the end user unboxes, signs in, and the device configures itself. No IT imaging or anything like that. For Windows, we use a process so that the new devices automatically enrolled in MDM and receive policies accordingly. It removes the manual build steps and keeps swift, down from day one. Yeah. No more, you know, setting up dozens of machines in a basement, like, imaging them or going one by one. Right? Yeah. Yeah. We Rippling uses, device management in this in this scenario to orchestrate those flows across both Apple and Windows in one platform. I know in my experience, that's pretty unique. I've often had, like, multiple MDMs that I'm trying to support, in those scenarios. So definitely a nice thing to call out. Awesome. Well, which day one policies should be universally enforced is kind of our next topic. Breeds, you know, that goes into the MDM world there. And I think a lot of folks I just talked to our our product managers offer, a week ago about kind of, like, hesitations sometimes behind, decisions for rolling out MDM. And I think that it kinda bleeds into the way people set that up for the first time. They people can get overwhelmed by the possibilities of, like, exactly what do you need to configure on an MDM versus what you want to configure. So I I like to call out that you you can always start with things as simple as you want and then work your way to, like, beefier compliance goals if that's your goal. So if there's, like, six baseline things that I consider table stakes, and whether or not you're going for those specific compliance goals, I think these things that I'm gonna list through are they're all super easy to roll out with Rippling. Full disk encryption by default, we escrow FileVault and BitLocker keys and, escrow this the key in the in the platform. So, like, you never have to write that down. You don't have to worry about it getting lost in a spreadsheet somewhere. It's not gonna be in multiple tools. So if someone, you know, does have any problems with with that, you you know exactly where to go for it. Second, I think OS updates, and, like, channels and deadlines there, like, you might need a different OS update cadence for your IT or security team versus all of your sales org or the broader org. So you can set up as many different policies for OS updates as you need to get really specific about when those are gonna happen. Third, I think making sure your firewall settings are the way you want them to be is really important. It kinda goes missed by some in a modern in a modern scenario just because it doesn't get talked about it as much as it used to, I feel like. Four, I think all your apps, your baseline apps, your most important things like your EDR, your antivirus, like your VPN, if you have a company VPN, even, like, the browser that you want people to use. Like, most people should be locking computers down, so not everybody's an admin, in my opinion. And if you roll out all the apps automatically using MDM, you don't have to worry about that otherwise. Five is screen lock and password standards. Those things seem kind of like, you know, entry level, but every compliance goal and any kind of IT shop is gonna need those to be to be set up properly. And then finally, something that's kinda more modern that's that's really normal to roll out is, like, blocking your USB and peripherals that you don't need to trust. So you can block, like, mounting, a USB key, for example. So these are rules that you need to establish and maintain, because your security configuration with monitoring and remediation in place is something that needs to you know, this needs to be in place. When MDM rolls these policies out, those policies happen at at an MDM protocol level, so the baseline of your computer is functioning with all of these in mind. And then like I mentioned, like, how you might have different OS update cadence for, like, your IT crew, in Ripley, and that's really easy because everything about our MDM uses attribute based policies. So think, like, your department or your role or your location can determine exactly what gets rolled out. So you can roll out different software for your engineers versus other people in your organization. And then finally, we do have some templated policies for, like, SOC two and NIST and CIS compliance. So for things like password and OS updates, those are made extremely straightforward. You just pick the right one, and you're all ready to go. Yeah. I mean, I think that all of that used to be done manually. It it really simplifies a lot. Yeah. Yeah. There's a time saver here that's that's in modern MDM that's, like, life changing. Well, what about, like, scale? What do you think about, like, keeping visibility as your fleet scales? I mean, devices scatter across countries if you open a new office suddenly, like, how do we avoid losing track of inventory? Yeah. Opening new offices or just having remote workers in Costa Rica and then someone else in Dubai. Right? Yeah. And I think the important thing, the trick here is to have a single system of record and not have different systems for people and then devices and then policies. Or, like, if if you have that all centralized, that gives you real time compliance status. It's like encryption, OS, EDR. I create assignment and chain of custody, who has which device when and then knowing that at all times. And through inventory, like, what's active, what's in transit, warehouse, archive. The key is life cycle wide control and governance. Operationally, that means that your MDM and inventory live in one data graph fed by HR events and logistics updates, not like loose CSVs and spreadsheets all over the place. Yeah. If you suddenly have, like like and Rippling is pretty unique from that perspective. I mean, you have your inventory and your device management and your identity world all feeding, you know, it's all from the same place. So, like, suddenly, your identities and policies and physical stock your physical stock is all something that you can build in a single report and keep shared out with the right people. Yep. Awesome. Well, what do we think about the right way to operationalize global shipping then, and retrieval of those devices? I mean, what pro what processes reduce, like, someone never sending you back a laptop at the end of their time with you. Right? Yeah. I think, like I mean, we we said this before, but, again, for procurement, standardizing your SKUs is really important. Mhmm. We've been in house of device store. We are a top 10 Apple reseller. So you can preset what approved devices you want for each, for different roles, for HR managers to use so that they can buy the right device for their new hires, and then use ABM and autopilot enrollment by default. Then with shipping, use drop shipping and pre with pre assignment, so that you have you can avoid having to ship those devices to IT first. And then at the time of offboarding, let HR offboarding you, like, kick off MDM actions, like locking device, wipe, and then automate the retrieval with sending, like, retrieval kit, each of scheduling and device status updates, all tied to the device record. And lastly, in chain of custody, we wanna track the device when the device is in transit, inventory or killed, or if you are redeploying it or reselling it. Yeah. I think I think those I think you hit it on the head you hit it on the head there. Like, offboarding can be, like, the most painful part of your week every week. Or if you have everything on lock, like, you can schedule those locks and wipes. And so even if I'm out of the office, like, the IT task of locking a computer for someone who leaves the company is gonna happen automatically. Automatically ship someone a return box with a label pre address so they can just instantly drop that laptop in there and ship it back to you. Like, that device goes back to the Ripley warehouses. They get cleaned up, and then they get labeled for you to either redeploy or you can actually sell them back now. We have new buyback options all in one record. Yeah. What about, like, setting the right inventory levels, like, either being overstocked or understocked, you know, is a waste of money or time depending. What do you think the best way to, like, size your inventory kind of anticipating your your staffing looks like? Yeah. I mean, it's a classic inventory management problem. And I think you need to treat it like any other supply chain problem. You start with how much how many devices are we using? Are we going through every month? And what's the lead time? How long does it take to to get the devices? So what you should do is, like, follow these steps. Cal first, like, calculate how many high new hires and replacements you're going through on average per month. And if you have estimates, it's even better for the future. And then multiply that by the vendor lift time, how long is this device device gonna take to arrive from the time I place the order. So that allows you to make sure that you have enough inventory for for your normal operations. But then the abnormal things happen, so you wanna add a safety stock buffer based on your SLAs or first day readiness. So if you wanna make sure that 90 or 99% of your new hires have a device on day one, then you wanna add that safety stock there to make sure that even if the abnormal happens, you still have devices. And so, for example, if you onboard 20 people a month and lead time is two weeks, keep 25 to 30 devices ready to redeploy, on hand. And then track aging inventory to avoid depreciation losses, so that, I mean, you'll not only buy devices for your new hires. Right? You need to buy to replace, aging inventory. So you need to make sure that you're doing that both because your employees want to have the best, devices that allow them to work, but also because you wanna be able to sell those before they depreciate and they're worth nothing. Yeah. For sure. I think that's what makes our new, like, buyback stuff so cool, like, in inventory management now. It shows you real time levels across your warehouses, what you have. Right? But you can also see, like, if they're ready if they're ready to be deployed or if they're at a level you think you should you should sell back at that point or not. I feel like that visibility gets so lost. It's one of the first things you might not have if you're, like, kinda piecemealing all your systems together. So it really lets you, like, forecast purchases and plan further out than you would otherwise. Yeah. And, we're doing interesting things there, and and more things coming up that will be announced soon. That will make this really exciting. Yeah. I think in the spirit of that off boarding conversation, retrieval rates, as as I mentioned, can be, like, super commonly a pain point, especially if you've got everybody remote. You know, you might not be getting things back in time or getting things back at all. Any any tips for, like, making sure those devices get back in to IT's hands? Yeah. I mean, we do this thousands of times per month. And, and really what we've learned is the number one thing that you should do is make the recovery process automatic and painless for departing employees. That is the number one thing. And for that, the three principles you follow are, first, triggering retrieval the moment that HR initiates off boarding. Don't wait for a ticket. Don't let that get lost in width. So if you can automate the request, which you can do with replaying that, signifies things a lot. The second thing is communicate very clearly. Send branded trackable return instructions with the only prepaid labels and, or scheduled pickups so that the employee doesn't need to coordinate shipping or do anything like that. And the last thing is remember to escalate automatically. Right? Like, set those reminders. Mhmm. A few gentle reminders. It's usually just a matter of, like, bringing this back to their attention of, hey. We're we're, tracking this return. It hasn't arrived. Can you please make sure you ship your device? That really is, like, 95% of what's gonna make with you all very successful. Yeah. In companies that pair both are part of HR and IT, in their same workflow, we'll typically see their recovery rates jump to above ninety five percent. Yeah. I totally I totally feel the pain of, like, before I realized you should be sending, like, pre, you know, the boxes with shipping labels in them and how easy that really is. I've had to, like, you know, either I had a an old device. It's been with Ripley in a few years now. So, like, whenever I had a device upgrade and I had to return my old device, it's just so dumb easy to, like, drop that in the box and then drop it off at a place everything else is, like, already taken care of with those boxes. And I feel like that along with, like, locking and wiping computers and making it so easy like that, it's hard to, like, say, no. I'm gonna, like, hold on to this computer and make that an issue for yourself. Right? I feel like, you know, with returned hardware logging into your inventory management, you always know where it is, keeping the security and the asset value tracked. I just think that's that's some cool stuff. And with us integrating now with over 70 HRIS providers, things like Workday and BambooHR, you can, like, use those HR platforms if you need and still have all this automation happening with, with Rippling and the inventory side of things. What about, getting into kind of the the more fun stuff, the new stuff that we're talking about with device buybacks? Like, what about, like, refresh cycles versus, like, a total cost? I mean, how do you decide if you're replacing a device too early or, like, you know, is it is it more complicated to run into a device starting to fail if you if you use it for too long out in the field? Yeah. I mean, buying new devices is expensive. But you know what's also expensive? Having an employee with a device that fails, losing their information, not being able to work for a few days. So you really need to take both things into account. My recommendation is use a risk and value based triggers. So what that means is essentially, think about the risk. Right? Like, part of the risk of some having someone working in an unsupported OS, with repeatedly EDR alerts, with battery health issues? Think about productivity when you're defining this model. Like, what are the slowdown metrics of someone working with an old device? What are the number of help desk incidents are gonna be raised? Yeah. But and then on the other side, think about the financials. Think about, like, what's the residual value gonna be if I sell this device now? What's the remaining depreciation? At the end of the day, you wanna put those two things into balance and find where there's, like, an optimal point where it's okay. After I start seeing this kind of indicators based on tickets, on company and employee, you have complaints, things like that, and based on, like, the market value, when is it optimal for you to start to start, to to implement that policy to refresh those devices. Yeah. I think having a view into the health of the device when it gets back into our inventory warehouses and, like, that device and its status is recorded. You both know how old it is and what it's, you know, potentially worth in a resale moment. It really kinda makes your aging inventory look different, in my opinion. Like, it's no longer a bunch of nameless computers in your shelf that if you don't have, like, a junior IT admin to, like, go in and, like, take stock of or, like, remember if that device even turns on after you got it back a few months ago. Like, that stuff making you have a different perspective on whether you're gonna redeploy or sell back a device is, like, game changing from that perspective, I think. Absolutely. What about, like, table stakes compliance for disposal? Like, if you're not gonna resell a device and you're gonna, like, dispose of a device fully, what's non negotiable in in that kind of situation? Yeah. And I think for even, like, both cases where you're either selling it or destroying it, you need to think about, how to make that securely. Right? You should always follow, NIST has specific guidelines, like NIST SP 888, that indicates how you should, securely either destroy a device that's completely useless or, the waste to the data ratio. Right? Like, we know that just deleting data doesn't guarantee that that cannot be recovered and accessed later again. So there are specific guidelines there. And depending on that, situation of the device, you can do, you wanna make sure that you're compliant. If you're working with a third party vendor that's gonna either buy back your device or recycle them, make sure that you request that they provide the certificate that allows you to see it was the the data was destroyed anyways in a way that's compliant for that. You all know that if you're doing stuff too, but even if you're not, it's really important to to know that that data is secure. And just keep those divide keep those certificates, and keep those records. Our buyback process allows you to do that, allows you to always get, a certificate for that and download them straight from the platform. So I I I think it's really important to to make sure that you're closing the loop in the right way. Yeah. And like you said, it's not like I'm going to dive into my email to go find that in in a rippling scenario, you're actually gonna have it in the platform. Right? Like, those those certificates are automatically generated. Right? Yeah. Yeah. So that simplifies things a lot, at that end of cycle. Super cool. Well, should we resell, redeploy, recycle, retire devices? Those are kind of the three things we just we just talked about. How do you how do you pick? Like, do you have any kind of, like, guidance for, like, what the actual, like, scenario is where we say this is a good one, we need to redeploy it? I mean, for sure, the least expensive option is always gonna be to redeploy. Right? As long as the device, a, it matches your your meets your baseline requirements. So for example, you say, like, oh, it meets the year, it meets the, battery health, the, like, condition of the device. It's not broken. The screen works. If you have a device that's still under your guidelines usable, then you should definitely redeploy. If it's not, then you should resell in a way that's safe and that you can get this kind of certificate that we were talking about earlier. Make sure it's unenrolled from NDM, things like that. She don't wanna sell a device that no one will be able to use. No one's gonna buy that. But if you do that, then you like, that's into that gets into file a lot using we think. Restarting you at least make some money back, and you're getting bills device in a secure way. And you should only recycle really when both both those options are not available. Mhmm. So you at least get a certificate, and you're responsible getting rid of of that device. I think that being easy is such it's something that until you've gone through it and, like, had to line up with a vendor to, like, securely destroy a bunch of computers, and like you said, like, go through the hassle of making sure you get those those certificates of destruction. Like, until you've done that and it not go well, it's so hard to, like, really get that across that it is such a time suck. And if you're trying to get, like, finance information by a specific time or, like, just leadership in general needs to know where you're at with your budget, like, how many computers do we actually need, it's just such a different view of your entire inventory, than, like, working with third party resellers or bringing a whole another organization in just to do those things. Right? Absolutely. Yeah. What about this is kinda on the, MDM side of things. But if we talk about, like, configurations and making things making sure things are continuously compliant, rather than, like, you know, back in the day where you'd be, like, whack a mole and, like, having to go to someone's desk. I mean, our MDM side of things really make sure that, like, you know how a device stands now and, like, how to how to enact some changes. Like, are there any kind of things you would make sure to implement? Yeah. I mean, I think, like, you need to treat secure configuration not as a document, but as a process where there is detection and there's response. Right? The CIS controls are, like, con offer establishing and maintaining both secure configuration with monitoring and remediation. So you can implement inside continuous checks where is encryption of, if they are missing, always behind, the most recent value, or most in most recent version. Are you doing automated remediation or grinding workflows? Is, are there exception windows with owners and, you know, review dates, report on compliance is, like, percentage of team and risk tier. But having that process where it's it's as automated as possible and it's triggering when when something is wrong, that will really help you, maintain that compliance. I think it's an interesting thing to call out, like, Rippling's workflow studio in that component. Things that in the past where I've worked with multiple MDMs, you know, one for my Windows world and one for my Mac world, and and I have a separate identity platform maybe. Like, making sure that, like, you can auto notify or, like, let people know about changes, like, is is such a different scenario where maybe anytime an encryption status changes on a machine, that should generate a Slack message to the IT channel, or it should send an email to your help desk. Right? Gives you, like, at a glance audit proof, along with keeping all those reports built up. Yeah. And it's a very flexible tool, so you can really, like, set up anything that you want. We hear, people ask about BYOD a lot. I'm of the mindset that, you know, it should kind of be a last resort for an organization. I think, like, enter you know, computers are not that expensive, anymore in the grand scheme of things. And if you're hiring someone who needs a company computer, I feel like it just eliminates so much hassle, to to not have BYOD and, like, not worry about anything touching a personal computer. But if you do have to do BYOD, do you do you have anything to, like, talk about there? Yeah. I mean, there's there's different scenarios. Right? There's companies who, like, allow just just to bring your mobile phone. Mhmm. And, overall, I think regardless of the type of device, you wanna make sure that you scope it tightly, like, you have always minimums, screen lock, encryption where possible, selective white for corporate data. But at the same time, you wanna avoid the equipping corporate requirements that's, like, turn BYOD into, like, corporate owned with extra steps. So we map the baseline to CIS configuration principles, which will limit what you truly enforce on personal devices. And I think that's the best scenario for to make that work. Yeah. And I like, in a rippling in a rippling world, that's where you'd leverage those attribute based policies. Right? Like, you could have a custom field that says, like, this person has a BYOD device and treat them differently in the MDM management because of that. Right? Yeah. Yeah. Absolutely. Cool. Well, what about metrics then that matter for both IT and finance? We talked a little bit about, like, you know, the idea of making sure you're aligned when you're selling back devices and stuff like that. But what does a good scorecard for that look like? Yeah. So, like, we think about the entire, life cycle that we talked about earlier. The first thing is, like, time to device and first day readiness. Are you are you actually deploying usable devices? Mhmm. Second is the policy compliance rate. There are some basic adherence to that. What's the baseline adherence to that? Mhmm. Then retrieval also says rate when someone leaves when you have or when the device is is, no longer usable, as well as the days to retrieval. Then you jump to, the aging of the unassigned inventory. What is the value of that working capital? Is that beyond the what you consider, like, the least think of having those devices still redeployed. And if you're never gonna redeploy those devices, then they're just, like, losing money by sitting there. Right? So on assignment metering is an important metric to keep in mind when you're warehousing devices. Yes. The difference in a buyback is gonna be, like, $400 or, like, $75. And you're, like, all you did was wait, you know, six or twelve months longer, and it never got used. Like, what are you doing? Yeah. Yeah. For a device. A lot of money for a device that wasn't used by anyone. Exactly. And I guess the last thing that I would bring up is days to credit and then, money that you get from a recovered device. Make sure you're getting competitive offers. Like, we we actually compete different vendors to make sure that we offer our best best price. But you can always, like, see what the market value are is of of those devices and make sure you're getting a fair deal. I agree. Well, this one kinda, like, point to conversation, like, why build this then, this MDM and an inventory together versus, you know, some people like to like to to have the mantra of connect all the best of breed, applications or systems together and kinda maintain that. Like, what what's your what's your perspective from someone who's actually in the background building all this for Rippling? Yeah. I I I really think, like, the wins are in the handoffs. Like, when HR offboards someone and then has to handoff to, someone in IT where who, like, uses MDM to lock or wipe a device, who then has to hand off to logistics and, someone who's gonna, like, retrieve the device, collect it, store it, who then has to let finance know, like, all those handles are an opportunity for things to go wrong, for data to go missing, for devices to go missing. So, like, it the fact that you can have all that together, it really simplifies and prevents those those errors. The like, you avoid delays, you avoid mismatches. And, you know, ISO life cycle guidance and the CIS's guidance, they both, recommend, like, maintain and monitor. So I you should always keep tracking. You should know where your devices are and more importantly, your data at all times. And having those integrated really simplifies that and make sure that that's that's happening at all times. You know, you have the same graph, the same data graph with all the information collected in one place. Same people, same devices, same policy, all of that really tied in. So I think that's what, like, inventory management and device management are native peers. I think when a when a org gets to a certain size, it's like, if you don't have all that with, like, a true source of truth and, like, you're talking about handoffs, that is, like, the first thing to go out the window when an org starts to get, like, bigger than its processes are really ready for. I think, like, I I'd be I'd be so curious if people on this call, like, I bet everyone has experienced not being told about someone off boarding at some point or not being told about a new hire that started to happen last minute. Right? And that stuff is so painful, and it doesn't it doesn't need to be, which is pretty cool. Yeah. Yeah. Well, Pablo, I I know we're we've kinda come up on time a little bit, but thanks so much for the blueprint from first boot to certified destruction. It's been a pleasure talking to you. Thanks, Andrew. And, you know, like, I always say, like, very few people got into IT because they wanted to ship devices. They love shipping devices. And we do that, and we love it. So if that's something we can help, you know, like shipping devices, securing, warehousing, sale back, destruction, providing those certificates. That's what we do. And by integrating, like, with MDM and and IBM, I think we we have the opportunity to do really cool stuff that brands really, really, it really wow's clients. So, yeah, I'm happy I'm happy to help and happy to to have more conversations like this. Awesome. Well, thanks for joining us, everybody. Be sure to schedule a demo. If you haven't seen Rippling in action or haven't seen Rippling in action lately, it's it's quite the beast. Check it out. See how it can automate your full device life cycle from top to bottom. Cheers. Have a great rest of your day. Thank you. Bye. Alrighty. Thank you very much to everyone who came out today to watch and engage. We went over a ton of stuff there. So I hope you all took something took something useful away from this. And, yes, we will we will get to the raffle which came up earlier. So, but quickly before we do that, I would just like to preview another very exciting session that we have coming up in a few weeks time as we will be off webinar duty, next week, the week of Thanksgiving. Frankly, we think you should be off duty too. So enjoy the holiday. But, once we're back, December, same time, same place on Wednesday, we'll have the head of Rippling IT, our fearless leader, Anik, talking with the head of our IT solutions consulting team, Todd, for a fittingly year end conversation. We're gonna go over all the launches we put out in 2025 to really up level the Rippling IT product suite, and then we'll kind of reflect on the lessons learned there, some trends in the industry, and and how that all is informing our road map for 2026. So that should be a really cool session, for you all to come and watch, and we we definitely hope to see you there. While we have everyone now, as Carter mentioned, and you should be able to see this survey up right now, if you haven't seen Rippling IT in action yourself or you just haven't seen it in a while, The product has changed for the better in a lot of ways in the last year. That is much of what Anik and Todd will be talking about in a couple weeks, actually, but we can also talk about it a little today. So, the first five attendees today to book and attend a live demo of Rippling IT will win a Lego Technic Mercedes f one set, perfect for all of the aspiring Lewis Hamiltons in the room. So please take us up on that. And the reason we would like you to do that is not purely self serving for what it's worth. I hope you, have gotten that sense from listening to Pablo and Carter just now, but it it's because we genuinely believe that we are rethinking IT operations in a way that can be really liberating for IT teams, especially those that that are buried in slogs of manual busy work or, you know, siloed point solutions that just don't really talk to each other and and work with each other well. So here at Rippling IT, we generally organize all of our offerings into into three core pillars, two of which we talked about today. The third of which is this top one, identity and access. And what we've been talking about, is we have a very wide range of tooling to help solve many of the problems that land on an IT team's desk on a daily basis. And one of those, which you heard a bit about earlier, I'll just draw a firmer line under today, is device disposal. Old laptops piling up in storage was a really consistent problem. We heard about from so many customers and even from our own internal folks who have had to deal with this themselves, that we wanted to do something about it. And device buyback is our way of doing that. So we've had we've had beta customers, as you can see on this slide, pay for their entire Rippling subscription, for an entire company just by reselling devices that were sitting around gathering dust. And we believe that's a really powerful offering for any number of other organizations out there, which is why we're so excited to take that live. So, it is really part of our overall approach to product and underlying philosophy of end to end native automation, which is why buyback is so exciting. It kind of closes the loop on, device life cycle management. And, like, around here, we are very intentional about the fact that we are not a platform in name only. We're not a bunch of acquired software kind of stacked up in a trench coat is the joke we always make. That is not us. Everything is natively built, which you heard Carter ask Pablo about. And it's natively built. It's natively integrated, all centering on, you know, what is really the central core of Rippling as a company, what we call the employee graph. You probably heard Pablo make reference to that. We talk about it frequently because it's so important to what we do. All of our components are built on your employees' data, whether that's their role, their office location, who their manager is, what have you. And that gives us a unified data architecture to draw from in automating all manner of daily IT work, whether that's, like, team specific app access or location specific security policies. Like, the flexibility is is really powerful because there's a lot of data to draw from. And, like, especially these days, as more and more organizations are implementing AI tools, We are of the firm opinion that those tools are not effective, absent, robust sets of data. And that is what we really give you across your IT infrastructure. So that all said, I will not let us escape today without getting down to the real business of, who won today's gift card raffle. So we do have a winner to announce for that, and that is William Voyak from Modern Campus. My heartfelt congrats to you, William. We will, get in touch with you about that. And, yeah, you know, honestly, that seems like about as good a place as any to wrap up for the day. So, let me just thank everyone again for for joining us today, for for getting involved. I know we have some outstanding questions that are left in q and a. We will follow-up on those, I promise. So in the meantime, enjoy your Thanksgivings. We hope to see you again very soon in December. And, till then, take care. Be well. See you guys.