Most Canadian IT teams can produce their device hardware spend and their wireless bill in minutes. Almost none can produce the third number, which is what it costs the organisation to manage the fleet rather than to own it.
That third number is the only one your management model changes. Hardware costs what hardware costs. Airtime costs what airtime costs. The cost of running the fleet is where a well-organised operation and a barely-coping one separate.
This guide is about where that cost actually sits, why it behaves the way it does, and why the obvious places to look are usually the wrong ones.
What it costs to manage mobile devices in-house
There is no reliable single figure, and the reason there is not is the most useful thing in this guide. What it costs to manage a mobile device fleet in-house is determined far less by how many devices you own than by how many device models, management platforms, and carrier accounts your team is holding together.
Two fleets of identical size can carry very different management costs. The variable is complexity, not scale.
So rather than open with a benchmark that will not match your fleet, this guide covers where device management cost actually sits, why the obvious places to look are usually the wrong ones, and how to work out your own figure at the end.
About the numbers in this guide. Where a figure comes from published research it is linked inline at the point of the claim. Where a figure comes from our own modelling it is labelled as illustrative and the assumptions behind it are shown, so you can replace them with your own. We have kept modelled figures out of the headline claims deliberately, because a benchmark built on somebody else’s assumptions is worse than no benchmark at all.
Why device budgets only show two of the three costs
Every device budget we review has the same shape. Hardware is there, airtime is there, and the cost of managing the fleet is scattered across headcount, ticket queues, and lines nobody has reconciled.
That matters because the three costs behave completely differently. Two of them are fixed by the fact that you operate a fleet at all. The third is fixed by how you operate it.
Most cost-of-ownership models present one total, and that is why they rarely survive a conversation with a CFO. You are buying devices whether you manage them yourself or not. Rolling hardware refresh into a “cost of in-house management” figure inflates the number and invites the obvious objection, which is that the spend is not going anywhere.
Separating the two changes the question. It stops being how much you spend on devices and becomes how much you spend holding the fleet together, and that second figure is the one a decision can move.
Why break/fix is the loudest device cost and not the biggest
Break/fix is the loudest cost in device management and nowhere near the largest. It is also the reason most teams misdiagnose where their time is going.
A broken scanner generates a ticket, a phone call from a site manager, and a visible queue. Enrollment, policy chasing, carrier line administration, and asset reconciliation generate none of that. They are quiet, they are continuous, and they consume multiples of the time that break/fix does.
The arithmetic is not close, and it holds under any assumption you care to make. Take a modelled fleet of 1,000 devices at a 7% annual failure rate, which produces 70 incidents in a year. At VDC Research’s published benchmark of roughly 70 minutes of IT time per incident, that is 82 hours. Two weeks of one person’s year.
The 7% failure rate there is our assumption rather than a published figure, so push it as hard as you like. At 30% you reach 350 hours, still under a quarter of one full-time role. VDC’s rugged-specific support figure is lower again, at 26 minutes per incident, which cuts the number further. No failure rate turns break/fix into three people’s work.
Yet a Vanson Bourne survey of IT decision-makers found that 34% of IT operations time goes to device management. On a team of 10 that is more than three full-time roles. Both findings are correct. The attribution is what gets it wrong.
The quiet costs are where the time goes.
- Enrollment and re-enrollment. Every new hire, every replacement, every platform migration.
- Policy management. Pushing a change, then chasing the 40 devices that never checked in.
- OS version drift. Multiple device generations, each with a different support window and update path.
- Carrier line administration. Adds, moves, changes, suspensions, and the SIM ordered for a driver who left before the start date.
- Asset reconciliation. A spreadsheet that was accurate the day it was built.
In theory a fleet inventory records what you own. In practice, on nearly every fleet we take on, the first job is finding out what is actually in the field, because the spreadsheet and the carrier bill disagree and neither matches the MDM console.
Teams optimise the cost they can hear. If break/fix were the cost, one more technician would fix it. It is not, so it does not.
Device management cost scales with complexity, not fleet size
Device management cost scales with surface area rather than device count. Surface area means the number of distinct things your team is holding together, and it is the single most reliable predictor of what a fleet costs to run.
A fleet of 800 devices running three device models across two MDM platforms and three carrier accounts costs more to administer than a fleet of 3,000 running one model, one platform, and one account. We see this consistently, and it is the reason headcount planning based on device count keeps coming up short.
Each additional element multiplies rather than adds. A second MDM platform does not double the policy work, it doubles the policy work and then adds reconciliation between the two, plus a second set of OS support windows, plus staff who have to be current on both.
Score your own fleet against the drivers that expand surface area.
- More than three device models in active use
- More than one MDM or UEM platform, such as SOTI MobiControl running alongside an inherited deployment
- More than one carrier account or rate card
- More than 20 sites
- No automated asset reconciliation, which in most fleets means a spreadsheet
- Any acquisition absorbed in the last 24 months
Four or more of those and you are running an expensive fleet regardless of how many devices you own. This is also why acquisitions hurt so much more than growth does. Adding 400 devices of the same model to an existing fleet barely moves the administrative load. Inheriting 400 devices with their own platform, their own carrier agreement, and their own support history moves it a great deal.
Where mobile device costs are decided versus where they are paid
Device cost is decided at sourcing and staging, and paid eighteen months later at break/fix, carrier billing, and disposal. The gap between those two moments is why cost problems resist fixing.
The decisions that set your cost are all early ones. Which device model, and how many models you are prepared to run. Which warranty tier. Whether devices arrive staged and enrolled or get configured on site. Whether the asset record is created at receiving or reconstructed later. Whether the carrier line is provisioned against a named asset or against nothing in particular.
None of those decisions produce a visible cost when they are made. All of them produce one later.
A device that arrives unstaged costs a technician an hour at deployment and then costs again at every OS update, because it was never enrolled properly. A device with no asset record generates a carrier line that survives the device. A fleet with four models in it generates a spare pool four times more complicated than it needs to be, for as long as those models are in service.
The practical consequence is that the point of pain is almost never the point of repair. Teams under cost pressure attack break/fix turnaround, carrier invoices, and repair spend, because that is where the pain presents. Those are symptoms of decisions made at sourcing and staging, and they cannot be resolved downstream of them.
The mobile device costs that never appear on a line item
The most expensive device costs share one property, which is that nothing in your general ledger tracks them. Costs without an owner and without a line item never get managed, and they compound quietly for years.
Three of them matter.
Compliance exposure. A retired handheld is not an empty device. It holds personal information about the worker who carried it, customer addresses and delivery signatures, route and location history, and in a regulated carrier, electronic logging records. Certified disposal with documented chain of custody typically runs $15 to $25 per device in our experience. The average Canadian data breach now costs $7.11 million according to IBM’s 2026 report, and for operations touching Quebec, Law 25 carries penal fines of up to $25 million or 4% of worldwide turnover.
Delayed IT projects. Every hour spent administering devices is an hour not spent on the work the business is waiting for. This is the cost that resonates with operations leaders and the C-suite, because they are the ones explaining why a strategic project slipped.
Workaround debt. The subject of the next section, and the one nobody prices at all.
What we find with all three is not negligence. Nobody owns the step. Devices come off the road and land in a box at a terminal, because the person who can authorise the wipe is not the person holding the box, and no process connects them. Secure Decommissioning is largely a matter of building that connection.
How workaround debt compounds device downtime costs
Workaround debt is the operational cost that accumulates when frontline teams stop trusting their devices. It outlasts the device failure that caused it, and it never appears on any cost line.
When a scanner is unreliable, people adapt. Paper forms get printed. Personal phones get used for photos of delivery paperwork. Verbal confirmations replace captured signatures. Each of those is a rational individual response to an unreliable tool, and each one is a data gap, a compliance exposure, and a hole in operational visibility.
The debt is that they persist. Replacing the scanner does not retire the paper form, because the paper form now has its own process, its own habit, and its own quiet supporters. We regularly find workarounds still running years after the hardware problem that created them was solved.
This is also why downtime costs are systematically underestimated. The narrow calculation counts the hours a device was unavailable. VDC puts frontline productivity loss at 74 minutes per device failure, which for a 1,000-device fleet works out to a figure small enough to make the whole downtime argument look weak.
The wider picture is different. SOTI’s Road Ahead research, which includes a 300-respondent Canadian sample, put total device-related downtime at 13 hours per person per month across transportation and logistics workers. That figure captures application crashes, connectivity gaps, and battery fade alongside hardware failure, which is closer to what frontline teams actually experience and closer to what generates workarounds.
The two figures measure different things and we would not add them together. The point is that the number on your ticket queue is the floor, not the cost.
Why standardization projects stall in understaffed IT teams
The project that would reduce your device cost requires exactly the capacity your device cost is consuming. This is the consolidation trap, and it is the honest answer to why most teams already know what the fix is and have not done it.
Standardising a fleet is well-understood work. Retire the older device generations, consolidate onto one management platform, reconcile the carrier accounts into one structure, rebuild the asset register properly. The outcome is a smaller administrative surface area and a materially lower cost to run.
It is also a project. It needs staging capacity, technician hours, and a period where someone is doing the consolidation instead of the daily administration. Run our own model over a 1,200-device fleet carrying two absorbed acquisitions and the gap between a high-complexity and a standardised profile comes out near $294,000 a year. That is a modelled figure on the assumptions set out later in this guide rather than a benchmark, but the direction is the point, and none of it arrives until the project completes.
The team that needs it most is the team least able to run it, because it is fully occupied administering the complexity the project would remove. Every peak season, every new site, and every acquisition pushes the project back another quarter.
Recognising the trap matters more than the arithmetic around it. A fleet stuck in it will not consolidate through better prioritisation or one additional hire. It consolidates when someone absorbs the project work from outside the team, which is a structural change rather than an incremental one.
Four stages of device fleet cost maturity
Fleet cost maturity moves through four recognisable stages, and each one is defined by what is true about the fleet rather than by what it spends.
Most Canadian fleets we assess sit between reactive and tracked, and almost all of them believe they are further along than they are. The test is simple. If your asset register, your carrier invoice, and your MDM console disagree about how many devices you have, you are at stage one regardless of what else is in place.
Why device fleet management can cost more in Canada
Benchmarking against US figures or a global vendor’s model understates your position. Three structural factors add cost here that do not exist in the same form south of the border.
- Carrier structure. The Canadian wireless market is concentrated, and each national carrier runs multiple sub-brands with different plan architectures. Enterprise agreements mean custom rate cards and pooled commitments that shift at every renewal, and the administrative burden scales with the number of agreements you hold rather than the number of devices. The CCTS, Canada’s telecom ombudsman, accepted a record 23,647 complaints in its 2024 to 2025 reporting year, with billing the largest issue category at 46%. That is the consumer side, where plans are simple and there is an ombudsman to escalate to. Enterprise accounts have thousands of line items and neither.
- Regulatory surface. A team managing procurement, deployment, support, and disposal across provinces works inside at least five distinct regulatory domains. PIPEDA federally, Law 25 in Quebec, provincial health information legislation where clinical data is in scope, three separate e-waste frameworks in Ontario, Quebec, and British Columbia, and the federal electronic logging device mandate for regulated carriers. Bill 96 adds French-language interface obligations for Quebec operations.
- Geography and climate. A fleet spanning 7,000 kilometres includes sites where a replacement device takes days rather than hours. Devices run at minus 25 degrees in reefer trailers and cold-chain warehouses and at plus 40 on a summer loading dock. Zebra TC series and Honeywell CT series hardware handles that. Consumer-grade hardware does not, and even rugged devices show accelerated wear, which means the failure rate you should plan around sits at the upper end of published benchmarks rather than the middle.
How to compare in-house device cost to a managed quote
A per-device managed price is not comparable to your internal cost unless the scope matches, and it usually does not. Most disappointing managed mobility engagements start with a comparison that was never like for like.
Before you can compare anything you need your own internal figure, and it takes three lines rather than a full costing exercise.
Every figure in the third column is illustrative. The devices-per-FTE ratio, the loaded FTE cost, the line rate, the waste rate, and the failure rate are all assumptions we chose to demonstrate the method, and all five should be replaced with your own numbers. The 74 minutes is the only published input, and it comes from VDC Research.
Two of those inputs move the answer far more than the rest. Your devices-per-FTE ratio and your wireless waste rate together account for almost the entire figure, which is worth knowing before you spend time refining anything else.
Once you have your own number, work through the scope line by line before drawing any conclusion.
If a quote lands below your internal cost and the scope matches, the decision is clear on cost alone. If it lands above, the question becomes what the difference buys. Turnaround times you cannot currently hit, staging capacity you do not have, and the ability to escape the consolidation trap. That is a legitimate answer and a better conversation than a rate comparison.
How we think about device cost at PiiComm
We are Canada’s largest pure-play managed mobility services provider, with 500,000+ assets under management and operations running since 2007. Managed mobility is all we do.
The reason we publish the framing rather than a savings claim is that the framing is the part that transfers. Whether you work with us or not, splitting run-rate from addressable cost, recognising that break/fix is the loud cost rather than the big one, and measuring surface area instead of device count will change how you plan your fleet.
Where we tend to be useful is the consolidation trap. The project that reduces your cost needs capacity your team does not have, so we absorb it. Canadian technicians in our own facilities handle the staging, the platform consolidation, the carrier reconciliation, and the certified decommissioning, and the fleet comes out with fewer models, one platform, and a reconciled line inventory. Our technicians are our employees, our facilities are here, and the decisions about your fleet are made in Canada.
On wireless specifically, the reason waste persists is not that it is hard to find. Finding it means reading every line of every invoice against an inventory nobody has time to maintain, which is a parsing problem. That is why we built ClearSight TEMs AI. Upload your Canadian carrier invoices and it reads them, reconciles them against your fleet, and shows you where the spend is going in minutes rather than weeks.
If any of this sounds like your fleet, start with the wireless line. It is the fastest thing to verify and it usually tells you a lot about the rest. Upload a single month of invoices to ClearSight and see what comes back.
If you would rather work through the whole picture with someone, talk to our team and bring your fleet count.
Frequently Asked Questions
What does it cost to manage a mobile device in-house?
There is no reliable published benchmark, because the cost is driven by administrative complexity rather than by fleet size. Three components make up the figure, which are IT labour, recoverable wireless spend, and downtime productivity loss. Together they form what we call addressable cost. Hardware refresh and airtime sit outside it because you pay those regardless of who manages the fleet. Two fleets of identical size can differ substantially on the addressable figure depending on how many device models, management platforms, and carrier accounts they carry.
What is the difference between run-rate and addressable device cost?
Run-rate cost is what the fleet costs to own and operate correctly, covering hardware refresh, wireless service, and compliant decommissioning. Addressable cost is what your management model costs, covering IT labour, recoverable wireless spend, and downtime. Only addressable cost changes based on how you run the fleet, which is why keeping the two separate is what makes a cost case survive a finance review.
How many mobile devices can one IT employee manage?
One full-time employee typically covers between 150 and 600 devices, based on the Canadian fleets PiiComm manages, where the role includes enrollment, policy management, carrier administration, staging, break/fix, and asset reconciliation. Fleets with a single device model, one management platform, and one carrier account sit at the top of that range. Fleets carrying multiple device generations, platforms, and carrier agreements, typically following an acquisition, sit at the bottom.
Is managed mobility cheaper than managing devices in-house?
Not always, and it depends on how much administrative complexity your fleet carries. A fleet running one device model, one management platform, and one reconciled carrier account is already inexpensive to administer, and the cost case for change is weak. A fleet carrying multiple device generations and inherited carrier agreements is expensive to administer, and that cost does not respond to adding headcount.
What percentage of enterprise wireless spend is wasted?
Gartner as put average enterprise wireless overspend at 15%. In our own audit work we see higher figures where line inventories have not been reconciled, particularly in the first year or two after an acquisition. The waste concentrates in four places, which are zero-use and orphaned lines, plan and usage mismatch, cancellations that were requested but never completed, and features enabled at provisioning that nobody turned off. All four are process gaps rather than pricing problems.
Why does device management cost more after an acquisition?
Because device management cost scales with administrative surface area rather than device count. An acquisition adds devices along with a second management platform, a separate carrier agreement, additional device models, and a support history nobody documented. Each of those multiplies the administrative load rather than adding to it, which is why absorbing 400 devices through acquisition costs far more to run than adding 400 devices of an existing model.
What does device management cost for a transportation and logistics fleet?
Transportation and logistics fleets sit at the expensive end of the range for three reasons. Failure rates run high because devices operate in reefer trailers and on outdoor docks, sites are dispersed so replacement logistics take days rather than hours, and sector consolidation leaves many fleets carrying multiple device generations and carrier agreements inherited through acquisition.
What is the difference between device lifecycle management and MDM?
MDM is a software platform that enforces policy, pushes applications, and monitors compliance on devices already in the field. Device lifecycle management is the operational system around it, covering sourcing, staging, deployment, break/fix, spare pool management, and certified decommissioning. MDM is one input into the labour cost of running a fleet.