Frequently Asked Questions

Find answers to common questions about our application packaging services, processes, and solutions.

FAQS

Find answers to common questions about our application packaging services and solutions.

We offer a transparent fixed-cost, pay-per-application pricing model, allowing you to accurately budget for your application packaging requirements without unexpected costs or hidden fees.

Our pay-per-app approach provides:
  • Predictable budgeting and cost control
  • No long-term commitments
  • Easy scaling based on demand
  • Clear visibility into project costs
  • Reduced administrative overhead

No. We support organizations of all sizes, from single application packaging requests to large-scale enterprise migration and modernization projects.

We package a wide range of applications, including:
  • MSI
  • MSIX
  • App-V
  • Numecent Cloudpaging
  • Intune Win32 applications
  • PSADT Scripted packages
  • Mac Packages
  • Legacy and custom business applications

Depending on the project requirements, we utilize industry-leading tools such as:
  • AdminStudio InstallShield
  • Advanced Installer
  • Master Packager
  • PACE Suite
  • PSADT
  • Orca
  • MSIX Packaging Tool
  • Numecent CloudPager

Our packaging services support:
  • Microsoft Intune
  • Microsoft Configuration Manager (SCCM/MECM)
  • LanDesk
  • Azure Virtual Desktop (AVD)
  • Windows 365
  • Citrix
  • VMware Horizon

Yes. Every package undergoes installation, functionality, and uninstallation testing to ensure it meets enterprise deployment standards.

Applications requiring custom scripting, middleware integration, extensive customization, or virtualization are assessed individually. We provide a clear fixed-price quote before work begins.

Yes. Applications are typically categorized as Standard, Medium, or Complex based on factors such as installation requirements, custom configurations, dependencies, virtualization needs, and testing effort.

Standard applications are typically delivered within agreed service levels. Delivery timelines depend on application complexity, dependencies, and testing requirements.

Turnaround times depend on application complexity. Standard applications can often be completed within 1–3 business days, while more complex packages may require additional time for testing and validation.

Absolutely. Our APP Packagers team can scale to support application rationalization, Windows migration projects, Intune migrations, cloud transformation initiatives, and ongoing BAU packaging requirements.

We support enterprise projects involving hundreds or thousands of applications and can scale our resources to meet project timelines and business requirements.

We offer flexible engagement models, including:
  • Pay-per-app packaging
  • Fixed monthly packaging services
  • Dedicated packaging resources
  • Managed application packaging services

No. We believe in transparent pricing. All costs are agreed upfront, giving you complete visibility and control over your application packaging budget.

All packaging, testing, documentation, and agreed deliverables are included in the quoted cost.

Yes. We offer discounted pricing for large application portfolios, migration projects, and ongoing packaging engagements.

Absolutely. Our pay-per-app model allows you to submit packaging requests as needed without maintaining dedicated packaging resources.

Our service typically includes:
  • Package creation and customization
  • Silent installation configuration
  • Installation and uninstallation testing
  • Upgrade and patch validation
  • Deployment readiness testing
  • Packaging documentation

We offer post-delivery support to address packaging-related issues and can provide ongoing maintenance services through flexible support agreements.

We provide an unlimited package warranty for the supported version of the application. If any packaging-related issues are identified after delivery, our team will investigate and remediate them at no additional cost.

The package warranty remains in effect for the lifetime of the packaged application version. As long as the application version remains supported and unchanged, we will address packaging-related defects and deployment issues covered under the warranty.

Our warranty applies to the specific version that was packaged and delivered. If a vendor releases a new application version, it is treated as a new packaging request and will require packaging, testing, and validation for that version.

Warranty support ends when:
  • The packaged application version is retired or reaches end-of-life.
  • The application is upgraded to a newer version.
  • Changes are made to the original application source, installation media, or packaging requirements.
  • The application is no longer supported by the software vendor.

The warranty covers packaging-related issues, including:
  • Installation failures
  • Uninstallation issues
  • Detection rule problems
  • Packaging configuration defects
  • Deployment-related packaging errors
  • Packaging-related application launch issues

Minor packaging corrections and defect fixes are covered under the warranty. However, vendor-released application upgrades, feature changes, or new application versions are considered new packaging requests.

  • Peace of mind with ongoing packaging support
  • No unexpected remediation costs
  • Reduced operational risk
  • Improved deployment reliability
  • Long-term value from every packaged application

Yes. Application dependencies are treated as separate packaging requests when they are not already available within your environment/standard build.

Dependencies may include components such as:
  • Microsoft Visual C++ Redistributables (VC++)
  • SQL Server components and database prerequisites
  • Microsoft Office Add-ins and integrations
  • .NET Framework and .NET Runtime packages
  • Java Runtime Environment (JRE/JDK)
  • Browser extensions and plugins
  • Middleware and third-party libraries
  • Driver packages and supporting software
Each dependency requires its own packaging, testing, validation, and deployment preparation, and is therefore priced separately.

If a dependency has already been packaged and approved for deployment within your environment, it can typically be reused across multiple applications without requiring additional packaging effort, helping to reduce overall costs.

Dependency packaging costs are based on the complexity of the application, installation requirements, testing effort, and deployment methodology. We will identify all known dependencies during the application assessment phase and provide transparent pricing before work begins.

As part of our packaging techreview process, we analyze application prerequisites and dependencies to ensure successful deployment. Any additional dependencies discovered during assessment will be communicated and approved before packaging proceeds.

Any dependency package created by our team is covered by the same Unlimited Package Warranty as the primary application package, for the lifetime of the packaged version or until the version is retired, upgraded, or modified.

A pay-per-app model helps organizations:
  • Reduce staffing costs
  • Eliminate recruitment and training expenses
  • Scale resources up or down as needed
  • Access experienced packaging specialists
  • Improve budget predictability

Our fixed-cost, pay-per-application model provides predictable budgeting, faster turnaround times, and access to expert packaging resources without the expense of hiring dedicated contractors. This allows your organization to scale packaging efforts efficiently while maintaining complete control over costs.

  • Fixed-cost, pay-per-application pricing
  • Unlimited Package Warranty
  • Enterprise-grade quality assurance
  • Fast turnaround times
  • Experienced packaging specialists
  • Support for Intune, SCCM, Citrix, VMware, and AVD
  • Flexible managed service options
  • Scalable support for projects of any size or complexity

Still Have Questions?

Our Team Is Here To Help You.

FAQ