Four metrics tell you everything about an MSP device-lifecycle service: two are operational levers, two are commercial outcomes. Track them monthly, broken down by customer and by leasing partner, and you can see at a glance whether the service is running cleanly and whether it is growing and earning. This is the deep dive on each — how to measure it, what to compare against, and what target to aim for.
Key takeaways
- Non-compliance rate is the single most telling operational number — it drives late fees, forced extensions, buyouts, and reclaims downstream.
- Track labour per exchange not as minutes saved per device, but as how many customers one coordinator can carry before you must hire.
- In one validated Nordic case, automation pulled non-compliance from ~50% toward 10–15% and lifted lifecycle service margin to 78–85%.
How do you measure non-compliance rate?
Non-compliance rate is the share of device exchanges that fail or are not returned on time, expressed as a percentage of total exchanges in the period. Count an exchange as non-compliant if the device misses its contracted return window, comes back damaged beyond normal wear, or is never returned at all.
It is the master operational metric because almost everything costly flows from it: late returns become extra billing, missed windows become forced extensions, and unreturned units become residual buyouts — followed by reclaims when those penalties land on the customer's invoice. In one validated Nordic case — a 1,200-user construction company with laptops scattered across sites nationwide — the manual non-compliance rate sat around 50%. With automated notifications and self-service returns, comparable operations bring this toward 10–15%. Treat these figures as a directional reference from a single case, not an industry survey.
What is labour per exchange and why track it?
Labour per exchange is coordinator hours spent per device exchange, measured all-in across ordering, tracking, chasing, and return handling. In the same Nordic case the figure ran around 0.375 hours per exchange manually versus roughly 0.25 with automation.
The minutes saved on one device are not the point. The point is the ceiling those minutes impose. When every exchange depends on manual coordinator effort, one team's capacity caps how many customers you can serve. Pull the per-exchange cost down and automate the chasing, and the same headcount absorbs roughly three times the lifecycle customers. So track this metric as a capacity question — how many customers can each coordinator carry before you have to hire — not as a stopwatch number.
What is lifecycle coverage and why does it matter?
Lifecycle coverage is the percentage of your customers actually receiving lifecycle services. This is the growth metric, and it is where most MSPs quietly stall.
Most plateau around 20% coverage, because manual processes cap how many customers one team can serve. The constraint is rarely demand — customers want the service — it is that reactive coordination does not scale. Automating the workflow is what makes 60% coverage reachable without proportional headcount. If coverage is flat while your customer base grows, the lifecycle service is being rationed by capacity, not chosen by customers.
How do you calculate lifecycle service margin?
Lifecycle service margin is the gross margin on the lifecycle service line once it is productised and priced as a standalone service, rather than bundled invisibly into another contract and priced at nothing.
Run reactively and bundled, lifecycle is a cost centre — in the Nordic case it ran at a net loss before productisation. Run as an automated, standalone service at a per-user price (€3.90 per user per month in that case), it reaches 78–85% gross margin — well above the 7–15% an MSP typically earns on general managed services. Calculate it as (lifecycle revenue − fully-loaded lifecycle cost) ÷ lifecycle revenue, and watch it move as automation strips out coordinator effort.
How often should you review these, and who else cares?
Review all four monthly, split by customer and by leasing partner — partner-level splits reveal which contracts generate the most non-compliance. The first two metrics tell you whether the service runs cleanly; the last two tell you whether it grows and earns.
These numbers are also evidence. Enterprise procurement managers increasingly ask for them in RFP qualification, and the same documented non-compliance rate and systematic process are what an ISO 27001, SOC 2, or NIS2 review expects to see — proof that your MSP manages device lifecycle deliberately, not reactively. Tracked consistently, the metrics that run the service also pass the audit that wins the next one.
For the full operational picture — the six lifecycle stages, how penalties accrue, and where the margin leaks — see the pillar guide: The Complete Guide to MSP Asset Lifecycle Management.
See how Apila Asset automates device lifecycle
A lifecycle layer above Intune and your ITSM — automated EOL workflows built for Nordic MSPs running multi-leasing environments.
Explore the platform