Compare Managed IT Quotes Without Comparing Different Services

01

1. Give Each Provider The Same Starting Brief

A per-device quote and a per-user quote can cover different estates. One person may use a desktop and a laptop; another may only need access to a shared workstation. A server, network appliance or cloud tenant may have its own charge. Before asking for a price, describe what needs support and ask how each item is counted.

Use approximate numbers for the first conversation, then confirm the inventory before the agreement. Include remote staff, shared devices and anything that cannot be unavailable during normal trading. State which applications another supplier supports, rather than assuming the IT provider can fix every specialist system.

If the list is uncertain, use a small-business IT asset register to organise it. An inventory is more useful than guessing that two packages labelled “complete support” mean the same thing.

Give every shortlisted provider these six items:

• Staff, business-owned devices and locations, including shared and remote use.
• Main systems: email, files, accounting, booking, job management and any servers.
• The work that stops when a device, internet connection or account fails.
• Current support arrangements and recurring issues, without confidential records.
• The working hours and onsite circumstances the business needs covered.
• Expected changes, such as another employee, an office move or a planned migration.

02

2. Use A Written Proposal Comparison Worksheet

Copy the following rows into your own comparison document. Add one column for each provider. Record a written answer or mark the item “not confirmed”; a blank is not evidence that a service is included. Keep sensitive account details in your private records, not in the comparison you send to multiple suppliers.

Request a redacted example report or a walkthrough of the support process where available. Do not ask a provider to expose another customer's records. If a proposal makes an assurance about a specific control, ask what evidence would demonstrate it for your own systems.

03

3. Separate Monitoring, Response And Resolution

“Monitoring included” does not explain what happens when a backup fails at night or a workstation stops reporting. Ask whether the service creates an alert only, includes investigation during agreed hours, or includes defined remediation. Identify the customer contact and escalation route if the next action requires a licence, replacement part or another vendor.

A response target also needs a definition. An automated ticket acknowledgement, a person reviewing the issue, the start of investigation and restoration of the affected service are different milestones. Ask which one the provider measures, when the clock runs, how priority is set and what happens outside the stated support hours. Do not assume a quick acknowledgement guarantees a quick repair.

These are comparison examples, not promised incidents or response times. Ask each provider to describe the included action, extra-cost boundary and customer responsibility for the same situations. A clear answer is more useful than an unsupported “we handle everything”.

Test the proposed scope against three ordinary situations:

• One employee cannot open email. Who handles the request, and is account administration included?
• The office internet connection fails. Who checks the local network, contacts the internet supplier and arranges a visit if needed?
• A backup job reports failure. Who investigates, what is escalated and is a recovery test separate work?

04

4. Check Security, Backup And Business Control

An IT provider may need powerful access to operate your systems. Ask how that access is authorised, protected and removed, and what evidence of provider activity is available. Australia's ASD guidance for organisations engaging a managed service provider supports clear security expectations, limited access and an agreed incident-notification process. These are questions to scope with a provider, not instructions to change your live access settings yourself.

Ask which data is actually backed up. Files on a workstation, a server, email and cloud applications may use different arrangements. Establish who responds to failed jobs and who is responsible for a restore test. If recovery work is separately scoped, show that boundary in the comparison rather than treating it as missing or automatically included. Our backup restore testing guide explains the separate recovery questions.

Keep ownership and administration distinct. A provider can administer a business-controlled tenant or domain without becoming the owner of the business's records. Confirm who holds subscriptions, which documented recovery and handover arrangements exist, and how access would be transferred to another authorised administrator. Do not move live accounts simply to make quotes easier to compare.

For security evidence, ASD's questions to ask managed service providers cover secure administration, monitoring, assessment and incident readiness. Ask proportionate questions for your environment; do not present a tool list or a general statement of compliance as proof of every promised outcome.

05

5. Compare The Full Cost Of The Same Scope

Break the proposal into a recurring baseline and variable work. The baseline may contain device management and agreed support, while licences, onboarding, onsite labour, replacement hardware and projects are itemised separately. Neither approach is automatically better: the important point is knowing what you will approve and pay for.

Build a comparison for the same period using this structure: recurring service fees, recurring licences, agreed setup work and the same clearly labelled optional scenarios. Do not turn hypothetical visits or repairs into a predicted annual bill. Ask how adding a user or device changes the fee, whether a billing minimum applies, and when price or scope can be reviewed. Confirm tax treatment before comparing totals.

Ultra IT's Managed IT Core starts from $239 per month for a monitoring and maintenance baseline covering up to five eligible devices. It is a starting point, not a quote for every team or a promise of unlimited onsite work. Support labour, Microsoft 365, security, backup and third-party licences are scoped separately unless the written plan expressly includes them. Covered devices, tasks, additional services and response arrangements are confirmed in that scope. Use the Managed IT service page for the current offering rather than assuming this checklist replaces a proposal.

The UK's NCSC guide to choosing an MSP also distinguishes responsibilities, service levels, backup arrangements and regular review. Its UK-specific certification and example timing recommendations are not presented here as Australian requirements or Ultra IT commitments.

06

6. Close The Gaps Before You Choose

Once the rows are filled in, compare the unresolved items first. A cheap proposal with an undefined backup response or account handover is not yet comparable to one that spells out those responsibilities. Equally, a larger package may include services your team does not need. Ask whether a smaller, clearly defined baseline meets the actual operating requirement.

Choose on the practical scope, accessible support process, understandable evidence and commercial fit. Technical scope discussion does not replace reviewing the agreement itself; obtain appropriate advice if its legal terms need interpretation. Keep the final clarification with the accepted proposal, so the owner and provider refer to the same document later.

Before the final decision, ask these four closing questions:

• Which worksheet items are still unconfirmed, and who will clarify them?
• Which existing problems need separately approved setup or remediation work?
• What will the first service review show, and which person in the business will attend?
• How will the scope change when the team, devices or key applications change?