Return on investment
See what your app estate really takes to run.
Count the hours you get back.
Drop your Intune apps export below. We match it against the Devicie catalog in your browser, show you where coverage and currency stand, and count the hours automated packaging, patching and provisioning return to your team each year.
How does the ROI work?
Export your Intune app list. Drop it in below. In a few seconds you'll see how much of your estate Devicie already packages and keeps current, which apps have no match yet, and how many hours a year automated packaging, patching and provisioning give back to your team.
Nothing is uploaded. The matching runs in your browser, against a catalog snapshot that ships with the page. We don't ask for your email.
- Coverage. Every app in your export, matched by name to the Devicie catalog. Every version of one product folds into a single row, because Devicie takes the product and brings the estate to the catalog release.
- Gaps. The apps with no catalog match — your bespoke packaging candidates. Devicie packages these for customers at no extra charge.
- Hours. Packaging, patch chasing and Autopilot provisioning, counted separately with your own assumptions. Change any of them and the total updates.
How the numbers are built
Every assumption is editable and every calculation is shown. If a number looks wrong for your team, change it — the point is the arithmetic, not our defaults.
Matching. Every name in your export is parsed for version, architecture and language, then matched to the Devicie catalog by name. All versions of one application fold into one row. OS-native apps, printer queues, drivers and scripts are set aside, so coverage is measured against applicable apps only — not padded with things nobody packages. Matching is deterministic and the same input always produces the same result.
Packaging hours. Matched apps × updates a year × hours per update. The defaults are 4 updates a year and 4 hours per update. Those are Devicie's own working figures from packaging at scale, not an industry benchmark — treat them as a starting point and put your own in.
Patch chasing. Your own figure for hours a month spent chasing outdated apps flagged by security scans and vulnerability reports, annualized.
Autopilot provisioning. Devices provisioned a year × technician hours per build. Shown separately, because it's device work rather than app work.
The three lines measure separate work and don't overlap. Audit preparation, migration effort, and the cost of incidents from software left unpatched are all excluded — so a full accounting comes out higher than what you see here.
What this is not. It's a labour estimate, not a quote, and it does not include what Devicie costs. It answers one question: how many hours is this work taking you now.
Questions people ask
Where do I get the export?
In Intune: Apps → All apps → Export. You'll get a CSV. That's the file. If you can't get to it right now, the tool's own Try sample data button runs the whole thing on a realistic 55-row estate so you can see the output first.
Does my application list leave my browser?
No. The catalog and the matching engine are part of the page, so matching happens on your machine. We record anonymous aggregate usage — a coverage percentage and a size band — so we know the tool is being used. Never your application names, never your file.
Why does one app show several versions?
Because that's usually what an export looks like: three versions of Chrome across three rings. Devicie manages the product, not the version, so all of them fold into a single row carrying the catalog release. The bold version is what the catalog ships; the range beneath it is what we found in your estate.
What happens to the apps with no catalog match?
They're your bespoke packaging candidates. Devicie packages line-of-business and in-house applications into the catalog for customers at no extra charge, and keeps them current after that. Three unmatched apps is a short conversation, not a blocker.
We already pay for Intune. Why would we pay for this?
Intune is where policy lives. It doesn't package your apps, chase versions, or notice when a configuration you set six months ago has drifted. That work is done by people, and the hours above are what it costs. Devicie automates the doing — automated baseline deployment, hourly drift detection and remediation, and a maintained app catalog on top of the Intune you already own.
Are these numbers a quote?
No. They're a labour estimate built from your export and your assumptions, and they exclude audit preparation, migration effort and incident cost. For a measured picture of your tenant rather than an estimate, request an Intune Health Assessment — read-only, no agent, results back in 48 hours.
App currency is one signal. There are others.
The same drift shows up in configuration, compliance and enrolment. An Intune Health Assessment reads all of it: your tenant scored against the CIS benchmark, app coverage measured against this catalog, and a prioritised list of what to close first. Read-only, no agent, back in 48 hours.
Related reading
How the work gets automated
- Trusted application patching at scale
- Application management best practices
- Best practices for efficient patch management
Why estates drift
- The problem with device management is that it never stays managed
- The myth of the golden tenant: why IT teams need automation, not templates