Build vs. buy
The build is only the first cost
Your team can build automation for Intune. The investment continues every time an application changes, a script needs maintenance or a new configuration requirement needs testing. Compare Devicie with the full responsibility of running that system over time: the work, the people who own it and the results the business needs.
After the first run
Plan beyond the first successful run
A script that packages an application solves a useful problem. Operating the process means keeping it useful through subsequent releases, changed installers, deployment exceptions and staff transitions.
The same applies to configuration. Establishing a configuration creates a continuing need to maintain the agreed settings and evaluate improvements as Intune and security guidance change.
These responsibilities belong in the decision to build or buy. Someone needs the time, knowledge and authority to carry them.
Recurring work
Compare the recurring responsibilities
Your team retains the decisions about business requirements, priorities, rollout and exceptions. The comparison is how much recurring preparation and maintenance each approach leaves with that team.
| Responsibility | What an internal approach needs | Devicie provides |
|---|---|---|
| Supported application updates | Release monitoring, package preparation and maintenance of the automation | Maintained catalog packages for supported applications |
| Applications outside the catalog | Installer knowledge, package preparation and a repeatable next-version process | Submitted-installer packaging, a reviewed workflow and reuse of previous setup where applicable |
| Agreed configuration | A defined desired state, drift handling and an intentional-change process | Correction of managed-policy drift with readable notifications |
| Configuration improvements | Evaluation and testing as platform capabilities and security guidance change | Specialist development and testing of Devicie configurations |
| Review and follow-up | Useful data, maintained reporting and ownership of exceptions | Reported application results and supported device information |
People dependency
Identify the expertise needed to keep it running
Who understands the automation? Who tests a change when its owner is away? Who can explain a result to security, support or a new administrator?
An internal system needs documentation, access management, testing and a handover plan. Buying a product also requires vendor review and an internal owner.
Devicie gives your team maintained product capabilities to use. Include the ongoing work your team retains when assessing that change in responsibility.
Cost comparison
Compare costs over the same timeframe
Use your actual application set and policy scope. Separate the value of time released from cash savings: freeing an administrator to work on other priorities does not automatically reduce payroll.
For Devicie, include
- The subscription
- Onboarding effort
- Any retained tools
- The customer work that remains
For the internal approach, include
- The initial build
- Maintenance
- Testing
- Infrastructure
- Reporting upkeep
- Staff handover
Evaluation worksheet
Test the next version
Evaluate a subsequent release as well as the initial deployment: who updates the package, checks retained configuration, tests changes and handles exceptions? Use a representative catalog application, one of your own installers and a supported managed policy. Carry each through a change after the initial setup. Record who detects the new release, prepares the package, tests it, handles the policy edit and investigates exceptions. Record elapsed time separately from hands-on work. This is an evaluation worksheet, not a claim of measured savings. Populate it from the same scope and observation period on both sides.
Initial setup and prerequisites
Record the actual work.
Customer actions for the next application release
Record the actions and time.
Policy correction and intentional change
Record the process and time.
Remaining maintenance and dependencies
Identify the owner and ongoing cost.
Where each fits
Where each approach makes sense
Use demonstrated coverage, remaining effort and total cost to decide.
An internal approach
An internal approach can fit when your requirements are narrow, your automation is maintained and its ongoing ownership is an intentional investment.
Devicie
Devicie is worth evaluating when recurring application and configuration work competes with other priorities, or when maintaining the tools behind that work creates a dependency you want to reduce.
See the consolidation business case →Questions we get asked
Can we keep automation we already use?
Evaluate it workload by workload. Agree which applications and policies Devicie will manage and how retained automation will operate without conflicting changes.
Does buying remove all internal responsibility?
No. Your team still owns requirements, deployment decisions, business acceptance and exceptions. Define those responsibilities during evaluation.
How do we evaluate continuing value?
Repeat the review over time: maintained applications, managed-policy corrections, reported results, customer effort and unresolved work. Use the same scope and measures at renewal.
Compare a month of recurring work
Bring the applications, policies and scripts your team maintains. Walk through what Devicie can take on and build a comparison around the work that remains.