What should hosted desktop service pricing include?

Hosted desktop service pricing should provide a complete, itemised view of the service rather than a single per-user figure. A useful quotation explains what each user licence includes, which technical resources are provided, how the service is supported, what is charged separately and how costs change as the organisation grows or its requirements change.

The pricing model should state whether charges are calculated per user, per desktop, per device, by consumption or through a combination of these methods. It should also explain whether users are assigned dedicated or shared resources, and whether different user profiles are priced differently. A basic office user, a power user running demanding software and an administrator may not require the same specification. Without this information, two apparently similar quotations may provide materially different services.

• the monthly or annual charge for each user type;
• the technical specification assigned to each hosted desktop;
• the minimum number of users or desktops covered by the agreement;
• the billing frequency and payment terms;
• whether prices are stated inclusive or exclusive of VAT; and
• any minimum contract period, renewal arrangements or annual price reviews.

Included service components should be defined in practical terms. For example, the quotation should identify whether the fee covers the hosted desktop environment itself, the operating system, standard applications, user profile management and administration. Software licensing needs particular attention because some applications are licensed per user, while others are licensed per device or require a separate agreement. The customer should be able to see which licences are supplied as part of the service and which must be purchased or retained independently.

Pricing should also describe the boundaries of technical support. This includes how users raise issues, which parts of the hosted environment are covered, whether support for business applications is included and where responsibility passes to the customer or a software supplier. If support is divided into standard and additional services, the quotation should explain the difference and identify how separately chargeable work is authorised. Vague wording such as “full support” makes the total cost difficult to assess.

One-off charges should be separated from recurring charges. These may include initial design, environment configuration, user onboarding, data transfer, application packaging, testing and administrator training. The quotation should say whether these activities are included, priced as fixed fees or billed according to time spent. If migration work depends on the condition or quantity of existing data, the assumptions behind the estimate should be recorded so that changes do not come as a surprise.

Usage and capacity assumptions are another important part of the price. Storage, data transfer, processing capacity and additional resources may be subject to limits or variable charges. The provider should state what happens when those limits are reached, how additional capacity is requested and whether it is billed retrospectively or from the date of change. It is also useful to clarify whether inactive users, archived accounts or temporary accounts remain chargeable.

A complete price should explain how changes are handled. Ask how new users, leavers, role changes and temporary increases in capacity are billed, including whether charges are prorated. The agreement should specify who can approve changes, when they take effect and whether removing a user also removes their data or simply stops their access. These details affect the real cost of a hosted desktop service over time more than the initial quotation alone.

Resilience and data protection provisions should be described sufficiently for the customer to understand what is being purchased. Pricing documentation should identify the included backup scope, retention arrangements, restoration process and any charges for recovery or additional retention. It should distinguish between a copy used for operational recovery and an independently protected backup, as these are not necessarily the same service.

The quotation should record the service commitments that relate to the hosted platform, including planned maintenance arrangements, incident handling, service reporting and any agreed targets. These commitments should be matched to the price and defined in measurable terms where applicable. If a particular level of service is available only at an additional cost, that option should be shown separately rather than assumed to be included.

Exit costs and ownership should be addressed before an organisation signs. Pricing information should explain how data is returned, in what format, how long access is provided for transfer, and whether assistance with migration to another environment is chargeable. It should also clarify ownership of customer data, configurations, licences and any documentation created during the service. A low monthly price may be less attractive if the agreement contains unclear termination or extraction charges.

For a meaningful comparison, request a total-cost schedule covering the initial implementation, recurring service, foreseeable changes and termination. Check the assumptions behind each line, confirm that all required applications and user types are represented, and ask for exclusions to be stated explicitly. The best pricing document is not necessarily the shortest or the lowest headline figure; it is the one that allows the organisation to understand what it receives, what it may need to add and how the cost will behave as its hosted desktop service develops.