Managed IT Support NZ: Compare Proposals Clearly

Use one comparison sheet, not a stack of sales brochures

Managed IT support proposals can use similar labels while covering different work. For an Auckland or wider New Zealand business comparing providers, the useful question is not simply “Does this include support?” It is “Who handles this task, under what conditions, and what evidence will show it was done?”

Start a worksheet with one row per business requirement and one column per proposal. Add separate columns for exclusions, unanswered questions and the document that supports each answer. Mark an item “not confirmed” when a proposal is silent; do not assume it is included or excluded.

Bestcomm’s managed IT service overview describes its service scope. This article focuses on the comparison worksheet you can take into a scoping conversation, rather than prescribing a package or promising an outcome.

Row group 1: people, devices and applications

List the broad categories of people and technology that need support. Avoid putting passwords, security codes or sensitive incident details into a sales enquiry.

For each proposal, ask:

• Which user groups, locations and devices are covered?
• Which applications are supported, and which remain with another supplier?
• Who approves new accounts and changes to access?
• Who handles starters, role changes and leavers?
• Which inventory records will you receive, and who keeps them current?
• Are equipment repairs, replacements and software licences included or separately charged?

Describe the business requirement before comparing the proposed tool. A remote-working team might need clear ownership of device and access issues; a particular monitoring product is not, by itself, evidence that those responsibilities are covered.

If you already have an internal IT person, record the boundary between their role and the provider’s role. Co-managed arrangements need an agreed division of work rather than duplicated assumptions.

Row group 2: support hours and escalation

Give response targets, resolution targets and service hours separate rows. Acknowledging a request is not the same as restoring the affected service.

Ask the provider to explain:

• How staff request help and what information to include.
• How priority is assigned and who can escalate a request.
• Which hours and locations the agreement covers.
• How response and resolution commitments are defined and measured.
• What happens when another supplier controls the affected system.
• What after-hours work costs and how it is authorised.

Do not assign your own response-time figure to a provider. Use its written proposal and clarify ambiguous wording.

Bestcomm’s separate network emergency response service covers Greater Auckland fibre and network incidents within its stated scope. It is not a promise of nationwide attendance or general 24/7 managed IT help-desk cover. Confirm managed-support hours in the relevant agreement.

Row group 3: maintenance, backup and security responsibilities

Keep these responsibilities separate even if a provider bundles them commercially. Ask what is monitored, who reviews alerts and which actions are included. For updates, ask how changes are assessed, scheduled and reported rather than assuming every update is applied immediately.

For backup and recovery, record the systems covered, agreed recovery expectations, retention arrangements, restore-test evidence and the person responsible for resolving gaps. Ask what the latest test actually demonstrated. A backup dashboard label is not the same as evidence that every required system has been restored successfully.

For security, identify the controls and services included, exclusions and escalation responsibilities. Ask the provider to explain which approach fits your business and why. This worksheet does not select a compliance framework or determine your legal obligations; discuss sector-specific or contractual questions with the relevant advisers.

Row group 4: onboarding, change and exit

Ask for the proposed handover steps, dependencies and deliverables. Record who supplies documentation, approves access and agrees the priorities. Detailed access should be handled through an agreed secure process, not pasted into a general enquiry.

Compare how each provider handles project work such as an office move or migration. Is it included, capped or separately scoped? Who approves a variation and how will you receive its price and timing implications?

For exit arrangements, ask what documentation and business data you receive, how access is handed over, what assistance is available and which notice periods or charges apply. Use the actual contract terms rather than assuming all providers follow one model.

Compare the price only after the scope is clear

Record the pricing basis, NZD currency, GST treatment, minimum commitments and separately charged items. Ask about hardware, licences, travel, onboarding, project work and third-party charges. Do not treat a missing line item as free.

Review the unanswered questions before ranking proposals. If a critical responsibility is unclear, request a written clarification and update the comparison sheet with its date and source. The objective is a decision you can explain, not a score inflated by a long feature list.

To discuss your requirements, contact Bestcomm with approximate user and device counts, locations, main applications and the problems you want to address. Do not include credentials or sensitive incident information. Scope, support hours, delivery arrangements and pricing need to be agreed for your business.

Cover image is illustrative; it does not depict a documented customer engagement.