DLM with in-house IT: why nobody on your team gets replaced

By Arjun Mehta, Device Operations Lead, Sirius Star, Last updated 17 May 2026

Last quarter we audited a 280-person Andheri pharma exporter whose IT manager spent his Saturday morning reimaging six laptops by hand. His MD wanted to roll out DLM with in-house IT support. The MD’s exact question was, “If we bring Sirius Star in, what happens to Rakesh?” That fear runs every conversation we have with mid-size Indian companies. It’s also wrong, but you can’t tell people their fear is wrong, you have to show them.

On this page

• What “we already have an IT guy” actually means
• What your IT guy does well, and what DLM should not touch
• What DLM handles that a single IT manager cannot reasonably do alone
• The two-roles split: who owns what when DLM is in place
• Five signs your IT setup is under-resourced, not over-staffed
• How to introduce DLM with in-house IT without making anyone feel sidelined
• When DLM with in-house IT is the wrong call
• Frequently asked questions

Here is how to bring DLM with in-house IT into a 150 to 500 person company in approx 6 to 8 weeks, get the CFO an opex line that beats CapEx, and keep your IT manager fully employed, even if he’s been there 9 years and is loyal to the MD. The DLM with in-house IT model is the one we have run for approx 30 mid-size Indian companies in the last 24 months, and the pattern is consistent enough to write down.

What “we already have an IT guy” actually means

We hear this sentence at least four times a month in vendor calls when DLM with in-house IT comes up. It almost never means what it sounds like.

What it usually means is one of three things. There is an IT manager with one or two helpdesk juniors, and the manager is the bottleneck for every new joiner laptop, every refresh, every device disposal, every DPDP destruction certificate, every Saturday firefighting call. The team is competent. It is also approx 40 percent overloaded on a normal week and 90 percent overloaded during audit season. The second meaning: there is an IT manager who handles infrastructure (firewalls, switches, Wi-Fi, server room) and a junior who runs the helpdesk ticket queue. Devices fall into a no-man’s-land. Asset tags drift, refresh dates slip, MRs in tier-2 cities wait two weeks for a replacement Galaxy Tab. The third meaning, the rarest, is one IT person doing everything alone. That person has a notebook with serial numbers, a folder of warranty PDFs on a shared drive, and a deep belief that nobody else should touch the fleet.

In every one of these three patterns, “we already have an IT guy” is true. None of those three patterns are reasons not to bring in DLM. They are reasons to bring it in carefully.

What your IT guy does well, and what DLM should not touch

The in-house IT manager is, in our experience, the single best person in the company at five things. He knows which sales head must never get a Lenovo because of an old screen issue. He knows the SAP FA module’s asset tag format and the GST input credit pattern for IT capex. He knows which of the 280 employees will call the MD directly when their email breaks. He knows the office network’s quirks (which AP drops at 4pm on Fridays, which printer needs power-cycling at 9am). He is the human institutional memory of every IT decision in the last 7 to 10 years.

None of that is replaceable by DLM. None of it should be.

A vendor who tells you they will absorb all of this is selling you a fantasy. The correct DLM with in-house IT contract specifies what the vendor does (a long list) and what the in-house IT team continues to own (the strategic stuff). The boundary is what protects the IT manager’s job and what makes the contract sustainable past month 6. DLM with in-house IT done well looks like a senior IT manager owning architecture while a partner owns logistics.

What DLM handles that a single IT manager cannot reasonably do alone

This is the part that gets glossed over in vendor decks for DLM with in-house IT. Below is the actual list, in order of how much pain it removes for the IT manager.

DLM with in-house IT works because the in-house team keeps the institutional knowledge while the partner absorbs the volume work. Here is what that looks like in practice.

First, new joiner Day 1 readiness. The HR team gives notice on a Friday. By Monday at 9am the joiner needs a laptop with the SAP client, the OneDrive sync set up, the email configured, the corporate Wi-Fi profile pushed, the antivirus active, and the MDM agent enrolled. With an in-house team of one manager and two juniors, this is realistically a 3 to 5 day cycle. With DLM with in-house IT, the device is pre-imaged, pre-tagged, pre-enrolled, and shipped to the joiner’s desk. Day 1 ready. The juniors are freed to handle the strategic backlog they have not touched in months.

Second, pan-India warranty escalation across tier-1 and tier-2 cities. When a Galaxy Tab dies in Indore at 3pm on a Tuesday and the field MR is mid-call with a doctor, the in-house IT manager is on WhatsApp coordinating with Samsung Authorized Service Centre Indore, FedEx for the replacement unit, and the MR’s regional sales head. A national DLM with in-house IT setup, run by a partner with channel relationships in 27,000+ pincodes, does this same job in 1 to 2 days with a documented escalation matrix, while the in-house manager focuses on the strategic project he has been deferring.

Third, EOL disposal with DPDP-compliant destruction certificates. India’s DPDP Act treats device disposal as a data-processing event. Every laptop that leaves the building must have its drives wiped to a documented standard, and a destruction certificate must be archived for audit. Doing this in-house means one of the juniors spends an afternoon every quarter running DBAN or a similar tool and filing PDFs in a Drive folder. Doing it via DLM with in-house IT oversight means the certificates are NIST 800-88 grade, audit-ready, and indexed by serial number. When the regulator asks, you have an answer in 90 seconds, not 4 hours.

Fourth, predictable per-device opex instead of unpredictable CapEx peaks. The CFO sees an opex line that scales linearly with headcount. The IT manager stops being the person who has to justify a Rs.18 lakh laptop refresh request in Q3 when capex is frozen. The math is paisa-vasool for a 200+ device fleet, and we have laid the model out in detail in our laptop TCO over 4 years breakdown and in the DaaS cost per device India post, so we will not re-do it here. The CFO conversation about DLM with in-house IT becomes a 15-minute exchange instead of a 90-minute defence.

Fifth, residual value and refresh cycle discipline. In-house teams almost always hold on to laptops too long because nobody owns the “when to replace” decision. By month 36, a laptop that was a paisa-vasool buy at month 1 is now consuming approx 18 hours of helpdesk time per quarter in productivity tickets, fan replacements, and battery swaps. DLM contracts specify the refresh cycle in the contract. The buy-back value at month 36 is built in. The decision gets made on schedule, not on whoever screams loudest.

It [stops the helpdesk firefight] so you can [redirect your IT team to strategic work] which means [your IT manager finally gets to lead the AI rollout instead of reimaging a sales lead’s laptop on a Saturday].

The two-roles split: who owns what when DLM is in place

This table is the single most useful artefact in a DLM with in-house IT contract negotiation. We give it to every prospect before pricing comes up, because the contract is the boundary.

Notice the bottom half of the right column says “out of scope, hands-off”. That is the contract working. A DLM partner that drifts into application rollouts, security policy, or vendor selection is overreaching and should be pushed back. A good DLM partner stays in their lane.

Five signs your IT setup is under-resourced, not over-staffed

This is the section the IT manager often skips because it is uncomfortable. It is also the section the CEO needs to read.

1. New joiner laptops are taking more than 2 working days from HR notice to desk-ready. The fix is not “hire another junior.” The fix is to take the imaging and dispatch off the IT team’s plate.
2. The IT manager is the SPOC for warranty escalation in cities the IT manager has never visited. He is co-ordinating Indore from Andheri at 7pm. That is a logistics job, not an IT job.
3. Asset tags are reconciled to SAP FA quarterly or worse. The team is busy enough that this slips. By month 9 the spreadsheet drifts. By the time it matters (audit), nobody trusts the numbers.
4. The disposal process for retired laptops is “the juniors will handle it next week” for 4 quarters running. The DPDP-grade destruction certificates do not exist. The CFO does not know this until the audit.
5. The IT manager has not taken more than 3 consecutive days off in 18 months. Every time he tries, he gets pulled back for a sales lead’s broken VPN. This is the loudest signal of an under-resourced setup. It is also the one the IT manager will deny the longest.

If any 3 of these 5 are true, the company is not over-staffed in IT. It is under-resourced. DLM with in-house IT adds capacity, not headcount. That is the single sentence the CEO needs to internalise before any pricing conversation.

How to introduce DLM with in-house IT without making anyone feel sidelined

This is where most internal politics fail. We have watched approximately 30 DLM proposals stall at this step, not because the math was wrong, but because the IT manager felt like he was being told he was the problem. Here is the script that works, and the lazy assumption it pushes back against.

Most companies treat the conversation as “vendor in, IT person out.” That framing is wrong, and frankly, lazy. The IT manager is not the problem. The work he is buried under is the problem. The vendor’s job is not to replace the manager, it is to remove the work that should never have been on the manager’s plate in the first place. The CFOs who frame it as a headcount-reduction conversation get the worst contracts and the highest churn. The CFOs who frame it as “Rakesh gets to lead AI rollout and DLM handles the device firefight” get sustainable contracts and IT teams that stay 5 to 7 years.

Rakesh, our 280-person Andheri pharma exporter’s IT manager, faced this exact framing in February when the MD first brought up DLM with in-house IT. The MD was leaning towards the model. The CFO was framing it as cost reduction. Rakesh’s two juniors had heard the rumour and were updating their LinkedIn. We sat down with all four of them, walked through the two-roles table above, and the conversation pivoted in approx 40 minutes. Rakesh’s job was not to defend the helpdesk queue. His job was to figure out what the company’s IT should look like in 3 years, and the DLM contract bought him 14 hours a week to do that work. His juniors got reassigned to a SAP-to-Power-BI migration project that had been sitting in his backlog for 16 months. The MD signed the DLM contract on a Tuesday. Rakesh was promoted to IT Head 5 months later. The two juniors are still there.

The trick is sequencing. Talk to the IT manager first, not the CFO. Ask him what he would do with 14 hours a week back. Listen. Then bring the CFO in with that vision in hand, not as a cost-cutting pitch. DLM with in-house IT is sold to the IT manager first; the CFO is the second meeting, not the first.

If your IT manager’s answer to “what would you do with 14 hours a week back” is a long pause and a shrug, you have a different problem. That is a hiring problem, not a DLM problem. DLM cannot fix a disengaged IT lead.

When DLM with in-house IT is the wrong call

We owe you the negative case. DLM with in-house IT is not always right. Three scenarios where we tell prospects to wait.

You have fewer than 50 devices. The per-device economics do not work below approx 50 active devices. Below that, the in-house IT manager handles the volume comfortably with a Saturday or two a quarter. Below 30 devices, the right answer is to outsource imaging only and keep everything else in-house.

You are about to be acquired or are doing the acquiring. M&A activity disrupts every IT contract within 12 months. Sign the DLM contract after the integration plan is final, not during the diligence phase.

Your IT manager is leaving in the next 90 days and you have no successor identified. DLM with in-house IT assumes there is an in-house IT manager on the other side of the contract to own the boundary. If the manager is leaving, hire the successor first, then bring in DLM with that person’s input on the contract. Doing it the other way creates a vacuum the DLM vendor inevitably fills, which is when DLM starts looking like outsourcing rather than augmentation. That is a different product. We do not sell it.

For everyone else with 100+ devices and at least one IT person, DLM with in-house IT is the model. You can read the broader Device Lifecycle Management framework on our service page, or skip straight to a free audit at the bottom of this post. The DLM with in-house IT contract template we use is built around the table above, and it is the document we walk through line by line in the first scoping call.

Arjun’s take

I have had this exact conversation with 12 IT managers in the last 6 months, and the pattern is the same every time. The manager is wary in the first call, asks pointed questions about scope creep in the second call, and by the third call he is the one helping draft the responsibility table. The shift happens when he sees the two-roles split written down. It is the boundary that makes the relationship work, not the pricing. Honestly, the DLM contract is paisa-vasool for any company with 100+ devices and a single overworked IT manager, but the contract has to recieve the same scrutiny the IT manager would give to any other vendor, line by line, not on someone else’s word. DLM with in-house IT works because the boundary is written down.

Frequently asked questions

Will DLM replace my IT team?

No. DLM with in-house IT augments your team, it does not replace it. The DLM with in-house IT contract partner takes over imaging, asset tagging, warranty escalation, DOA replacement, and EOL disposal. Your in-house team continues to own strategy, security policy, application rollouts, and vendor selection. The two-roles split is written into the contract.

What if my IT manager pushes back on the DLM proposal?

Talk to him first, before the CFO. Ask what he would do with 14 hours a week back. If the answer is a strategic project he has been deferring, you have a DLM use case. If the answer is a shrug, you have a hiring problem instead. DLM does not fix a disengaged IT lead.

Will Sirius Star talk to our SAP FA module?

Yes. The DLM with in-house IT model assumes your team owns SAP. We post a monthly reconciliation file in your asset tag schema, mapped to the SAP FA serial number convention. Your team validates and posts the entry. We do not write directly to SAP.

What happens to our two helpdesk juniors?

In approx 18 of the last 20 DLM with in-house IT deployments we have run, the juniors got reassigned to higher-value work the IT manager had been deferring. SAP migrations, Power BI dashboards, M365 rollouts, security policy updates. The DLM with in-house IT partner absorbs the imaging and dispatch work, not the strategic work. The juniors are the cheapest people on your IT team to lose, but they are also the easiest to redeploy when DLM removes the firefighting.

How fast can DLM with in-house IT be rolled out?

Approx 6 to 8 weeks for a 150 to 500 person fleet running DLM with in-house IT. Week 1 to 2 is contract and image specification. Week 3 to 4 is pilot deployment on 20 to 30 devices with one location. Week 5 to 6 is national rollout including tier-2 city escalation matrix. Week 7 to 8 is asset tag reconciliation and CFO dashboard handover. Audit-ready by month 3.

By the way, did you know we offer a parallel quote on your current device fleet at no charge? You send us a list of serial numbers, refresh dates, and current monthly support cost. We come back inside 5 working days with a per-device DLM cost and a side-by-side comparison. No commitment, no sales pressure, no Sunday WhatsApp from us. Reply “PARALLEL” on WhatsApp to claim it.

Free device audit: DLM with in-house IT for Indian companies

Free device audit. If we don’t find at least Rs.4 lakh of recoverable savings over 36 months on a 150+ device fleet, the audit is yours free and we do not chase you.

200+ businesses trust Sirius Star with their DLM. Response within 4 hours. We sit down with your IT manager first, not your CFO, because DLM with in-house IT only works when the IT manager owns the scope conversation.

Get my free device audit on WhatsApp

Audit includes: per-device 36-month TCO, the two-roles responsibility split tailored to your team, refresh cycle assessment for your current fleet, DPDP disposal readiness check, and a CFO-ready opex vs CapEx model for DLM with in-house IT. Plus the parallel quote if you want it.

Talk to our team directly

P.S. The two-roles split table from this article is also available as a one-page PDF we have shared with approx 40 IT managers in the last 6 months. It is the document we put on the table in the first DLM scoping meeting. Reply “SPLIT” on WhatsApp and we will send it. It includes the full responsibility split, contract clause templates for scope-creep prevention, and the 5-signs checklist you can run against your own setup before any vendor call.

About the author

Arjun Mehta is Device Operations Lead at Sirius Star Enterprise Technologies, where he runs Device Lifecycle Management programmes for mid-size Indian companies across pharma, BFSI, manufacturing and ITES. He has led approx 30 DLM deployments in the last 24 months, including the national insurer 2,500-device DaaS rollout, and works out of Vashi, Navi Mumbai.

Profile: /author/arjun-mehta/