What information is needed for a managed IT services pricing estimate?

A reliable managed IT services pricing estimate is based on a clearly defined service scope, an accurate picture of the technology environment and the level of operational responsibility expected from the provider. The most useful information is specific, current and separated into what must be included from what may be needed later.

Start by describing the organisation’s operating model. Explain whether staff work from one office, several premises, remotely or through a mixture of these arrangements. Note any sites that depend on shared systems, site-to-site connectivity or centralised access. The estimate may also need to account for different user roles, such as office staff, managers, field workers, administrators and users who require access to sensitive information. Role-based detail is more useful than a total user count alone because different groups may need different devices, applications and support boundaries.

An asset schedule helps turn general information into a workable scope. This can include:

• Desktop computers, laptops, tablets, mobile devices, servers and network equipment
• Virtual machines, cloud resources and hosted applications
• Printers, scanners, telephony equipment and other connected business devices
• Operating systems, software subscriptions, business applications and licensing arrangements
• Equipment that is owned, leased, shared or approaching replacement

Where exact details are not available, indicate that clearly rather than presenting an assumption as fact. An approximate inventory can support an initial budgetary estimate, but a more complete record is normally needed before a final proposal is agreed. Device age, configuration and ownership can affect whether the requirement is ongoing management, remedial work, replacement planning or a separate project.

Explain the boundaries of the service you are considering. For example, distinguish between routine management of the existing environment and one-off work such as a migration, office move, server replacement, network redesign or application implementation. Also clarify whether the provider is expected to manage all technology or only selected elements. A partial arrangement might cover user support and endpoint management while another supplier, internal employee or specialist application provider retains responsibility for other systems.

Support arrangements should be described in operational terms rather than only as a general request for “IT support”. Useful information includes the preferred contact routes, who is authorised to raise requests, how requests are prioritised and which types of issue should be escalated to a third party. State whether support is intended for employees, customers, contractors or other external users. If certain systems are business-critical, identify the consequences of an outage so that their management and escalation requirements can be considered properly.

Existing documentation can materially improve the estimate. Relevant records may include network diagrams, asset registers, supplier details, licence schedules, domain and hosting information, backup records, user lists and administrative ownership details. The provider may also need to review configuration information or conduct a technical assessment to validate what has been supplied. This is particularly important where infrastructure has developed over time and no single document reflects the current environment.

Security information should be factual and specific. Disclose known security controls, recent incidents, outstanding recommendations, privileged-access arrangements, remote-access methods and any systems containing confidential or regulated information. Identify whether the organisation needs assistance with policy management, security monitoring, staff awareness, vulnerability management or incident preparation. These requirements can represent a different level of service from general technical support and should be priced as part of the intended scope rather than assumed to be included.

Compliance and contractual obligations should be identified with their practical implications. This may include requirements from clients, regulators, insurers or internal governance policies. Rather than naming a standard without context, explain what evidence, controls, reporting or access restrictions are required. The estimate can then distinguish between maintaining an existing control and carrying out work to achieve it.

It is also useful to provide commercial information that affects the shape of the service:

• The preferred billing structure and whether licensing, connectivity or third-party charges should be included
• Any existing supplier contracts, renewal dates or termination constraints
• Whether projects and hardware procurement should be quoted separately
• The expected approval process and the people who will assess the proposal
• Any procurement, insurance or data-processing documentation required before work begins

Ask the provider to show the assumptions behind the estimate. A transparent estimate should make clear which users, assets, sites and services have been counted, what is excluded, which items are provisional and whether taxes or third-party charges are treated separately. It should also identify any information that still needs verification. This makes competing options easier to compare and reduces the risk of choosing a lower apparent cost that covers a narrower scope.

For a growing organisation, provide a planning view rather than treating the current environment as fixed. Include known office changes, recruitment plans, acquisitions, new applications, infrastructure replacement and changes to working practices. The purpose is not to predict every future requirement, but to show which parts of the service may need to scale or be reviewed. S2 Technology Group can use this type of information when discussing a managed IT services scope for a small or medium-sized organisation, with the final estimate based on the environment and responsibilities actually agreed.

Before requesting the estimate, compile a short information pack containing the asset schedule, site and user summary, current supplier list, key systems, known issues, security and compliance requirements, desired service boundaries and planned changes. Supplying this in a consistent format gives the provider a stronger basis for assessing the work and gives the organisation a clearer basis for evaluating the resulting proposal.