Your IT team already knows what application packaging involves: turning installers into standardised MSI, MSIX, or Intune Win32 packages ready for deployment. But with Windows 10 support now ended and Windows 11/Intune migrations accelerating, many teams are finding their current packaging model can’t keep pace. This guide gives you a genuinely neutral, data-backed framework covering cost, speed, control, and risk, so you can decide with confidence whether in-house, outsourced, or a hybrid approach fits your organisation in 2026.
Key takeaways
- Application packaging converts a software installer into a standardised, deployment-ready format (such as MSI, MSIX, or Intune Win32) for tools like SCCM/MECM or Microsoft Intune.
- Outsourced application packaging typically works on a per-app or fixed-price model and suits variable workloads, backlog clearance, and organisations lacking in-house specialists. It provides immediate scalability and access to deep expertise.
- In-house packaging suits organisations with high, constant volumes of applications and a need for minute-by-minute control over the packaging process.
- Windows 10 reached end of support on 14 October 2025, which is driving a surge in Windows 11 and Intune migration projects and, with them, packaging demand.
- Many organisations adopt a hybrid model, outsourcing complex projects and backlogs while managing simple, routine updates internally.
- Outsourcing converts fixed packaging costs (salaries, training, software licences) into a predictable variable operating expense billed per application.
- Neither model is universally better. The right choice depends on application volume, backlog size, in-house expertise, and strategic migration timelines.
What is application packaging in IT?
Application packaging is the process of preparing a software installer into a standardised, deployment-ready format, such as MSI, MSIX, or Intune Win32, for centralised distribution through tools like SCCM/MECM or Microsoft Intune. A packaging engineer takes a raw installer, often messy or interactive, and repackages it so it can install silently, consistently, and without user intervention across hundreds or thousands of devices.
Modern packaging work spans several formats. MSI remains the long-standing Windows installer standard, while MSIX is Microsoft’s newer, more secure containerised format built for modern app delivery. Intune Win32 wraps traditional installers for cloud-based deployment through Microsoft Intune, and App-V, Microsoft’s older application virtualisation technology, is being phased out in favour of MSIX and native Intune delivery. If you want a deeper technical grounding in these formats, Application Packaging 101 covers the fundamentals in more depth.
Why the in-house vs outsourced decision matters now
The in-house versus outsourced decision matters now because Windows 10 reached its official end of support on 14 October 2025, and Microsoft no longer provides software updates, security fixes, or technical assistance for Windows 10 PCs. Microsoft no longer provides software updates, security fixes, or technical assistance to Windows 10 PCs. That deadline has triggered a wave of Windows 11 and Intune migration projects across UK organisations, and every migrated device needs its applications repackaged and validated for the new platform.
The scale of the remaining migration is significant. A nationally representative Which? survey found that based on a survey carried out in September 2025, Which? estimates that 21 million people still own and use a laptop or computer running Windows 10 in the UK. Many of those devices sit inside businesses and public sector bodies still working through their upgrade backlog.
Migration speed is also slower than the last cycle. Windows 11 migration has taken four years to reach 50% adoption, compared to three years for Windows 10 to reach the same milestone (Source: Omdia, 2025). That slower curve means packaging teams face sustained demand well into 2026 and 2027, not a short-term spike. For a deeper look at how SCCM and Intune fit into this migration wave, see SCCM vs Intune for application deployment in 2026.
What is in-house application packaging?
In-house application packaging is when an organisation employs its own dedicated packaging engineers, typically within the Desktop Engineering or End User Computing function, to build, test, and maintain application packages internally. A typical in-house team includes one to three packaging specialists, often supported by testing and change-management staff, using tools such as Advanced Installer or the SCCM/MECM console itself.
The main advantage of in-house packaging is direct control. Your team sits inside the same change-management process as the rest of IT, can prioritise urgent business requests immediately, and builds deep institutional knowledge of your specific application estate. This suits organisations running application packaging at enterprise scale with a steady, predictable volume of work.
The trade-off is cost rigidity. Salaries, training, software licensing, and cover for annual leave or sickness are fixed costs regardless of how many packages you actually need in a given month. Skilled packaging engineers are also in short supply across the UK, meaning recruitment and retention carry real risk, particularly during a migration surge when demand for these skills spikes across the whole market.
What is outsourced application packaging?
Outsourced application packaging involves a specialist third-party provider handling packaging on a per-application or fixed-price basis, converting fixed internal costs into predictable variable expenses. Engagement models vary: some providers charge per package, others offer a fixed monthly fee for a set volume, and delivery can be fully remote, on-site, or a blend of both depending on your security and access requirements.
The financial case for outsourcing centres on converting fixed costs into variable ones. One UK Government department client reported saving an average of £9,300 per month using Alkane Solutions’ fixed-price application packaging service (vendor-reported client testimonial, Alkane Solutions, 2026). Vendor-reported figures from Camwood similarly claim that managed packaging services can deliver a 92% reduction in time per application and a 12x increase in output for a 20-person team, though this specific claim is vendor marketing and hasn’t been independently audited.
In-house vs outsourced: side-by-side comparison
The comparison below sets out how in-house and outsourced packaging perform across the five factors IT decision-makers weigh most heavily: cost, speed, control, expertise, and risk.
| Dimension | In-House Packaging | Outsourced Packaging |
| Cost / TCO | Fixed costs: salaries, training, software licences, cover for absence | Variable, per-app or fixed-price billing; no recruitment or training overhead |
| Speed & scalability | Limited by team headcount; struggles with sudden backlog spikes | Scales up quickly for migration projects and backlog clearance |
| Control & customisation | Full, immediate control over priorities and process | Governed by SLA; less minute-by-minute flexibility |
| Expertise & compliance | Deep knowledge of your estate, but narrower skill breadth | Broad, current expertise across MSIX, Intune, SCCM, and compliance standards |
| Risk & dependency | Key-person risk if staff leave; skills shortage risk | Vendor dependency; mitigated by documentation and warranty terms |
This table format is designed to answer “is it cheaper to outsource application packaging or do it in-house?” directly: outsourcing usually wins on pure TCO for variable workloads, while in-house wins on control for high, constant volumes.
Is a hybrid model the best of both worlds?
A hybrid packaging model, outsourcing complex projects and backlog clearance while retaining routine updates in-house, is considered the most effective approach for many organisations. This structure lets a small internal team handle day-to-day requests and urgent fixes, while a specialist provider absorbs the unpredictable, high-volume work that comes with a migration project or a long-neglected backlog.
In practice, this usually means keeping straightforward version updates and low-risk repackaging in-house, where speed of turnaround matters most, and sending complex MSIX conversions, legacy App-V retirements, and large-scale SCCM-to-Intune migration batches to an outsourced partner. Based on analysis of the providers and case studies referenced in this guide, the organisations reporting the strongest cost outcomes are almost always the ones using outsourcing for surge capacity rather than as a full replacement for internal capability. This mirrors guidance in the application delivery decision matrix, which frames packaging decisions around workload type rather than a single universal answer.
Can a provider handle packaging for both SCCM and Intune?
Yes, most established UK packaging providers support both SCCM/MECM and Microsoft Intune, since the two platforms often run in parallel during a phased migration. A competent provider will package once and validate deployment across both channels where needed, reducing duplicate work for your team.
Can outsourcing accelerate an Intune or SCCM migration project?
Yes, outsourcing can significantly accelerate migration timelines because providers can flex capacity up quickly without the recruitment lead time internal hiring requires. This matters directly for the current Windows 11 wave, where the migration curve is already running slower than the previous Windows 10 rollout.
Can companies use both in-house and outsourced packaging?
Yes, this is exactly what the hybrid model describes, and it’s increasingly the default recommendation across the industry rather than a compromise. Running both models simultaneously lets organisations match resourcing to workload type instead of forcing every package through one fixed process.
What happens to legacy App-V packages as support ends?
Legacy App-V packages typically need to be converted to MSIX or repackaged as native Intune Win32 apps, since App-V is being phased out in favour of newer formats. Organisations with large App-V estates often find this conversion work is exactly the kind of one-off, specialist-heavy project best suited to an outsourced provider.
What’s next: how to decide for your organisation
Deciding between in-house, outsourced, or hybrid packaging comes down to auditing your current backlog, team capacity, and migration timeline before committing budget. Start with a practical checklist:
- Count your current application backlog and estimate how many packages need Windows 11 or Intune readiness work.
- Assess your internal team’s capacity against that backlog, including planned leave and any recruitment gaps.
- Compare the fixed cost of hiring or expanding your internal team against a fixed-price or per-app outsourced quote.
- Identify which application types are routine (candidates for in-house) versus complex or legacy (candidates for outsourcing).
- Request a scoped quote from at least one specialist provider, such as those referenced in the problem with application compatibility tools, to benchmark against your internal cost model.
Conclusion
Neither in-house nor outsourced application packaging is universally better. The right model depends on your application volume, backlog size, in-house skill availability, and how urgently your Windows 11/Intune migration needs to move. For most mid-to-large UK organisations facing the 2026 migration wave, a hybrid approach, keeping routine work in-house and outsourcing backlog and complex conversions, offers the most defensible business case. Start by auditing your backlog this month, then request a fixed-price quote to compare against your internal cost baseline.
