Do you need managed IT support or help when things break?

Buy defined responsibility

Managed support can make sense when the business needs ongoing maintenance, account administration, monitoring and a reliable fault process. Ad hoc support can suit a simple environment with an internal owner and tolerable interruptions. Neither label proves quality. The important question is who is responsible for each task and what evidence shows it is being done.

Do not assume a monthly per-user fee includes every device, cloud service or security control. Equally, do not assume an hourly technician is cheaper if nobody handles updates, backups or departures between visits. Compare the operating model the business needs, including what the owner or office manager would otherwise have to coordinate.

Make a responsibility matrix

List endpoints, accounts, software, network, internet, backups, recovery testing, security alerts, printers and specialist systems. For each, identify the responsible party, included work, frequency where applicable and escalation path. Mark exclusions and dependencies. A task with two vaguely responsible suppliers can be as problematic as a task with none.

Ask who approves changes and extra spending. Define how new staff are onboarded and departing staff are removed. Australian small-business cyber guidance recommends practical controls such as MFA, updates and backups, but a supplier contract must still say who configures and maintains them. Buying support does not transfer every business decision or obligation to the provider.

Understand response and resolution

A response target describes when someone acknowledges or begins handling a problem. It is not the same as a guaranteed restoration time. Ask how severity is defined, which hours apply, whether on-site attendance is included and what happens outside those hours. Check the escalation process for a trading outage.

Use realistic scenarios in the sales discussion: the owner cannot sign in, a laptop is stolen, the network fails at 4 pm, or a critical application is down but supplied by another vendor. Ask the provider to walk through ownership and charges. A useful answer identifies limitations rather than promising that every incident is covered and resolved immediately.

Compare complete costs

Request the user or device count, minimum monthly fee, onboarding, software licences, projects, site visits, travel, after-hours work and exit costs. Confirm whether backup storage and security products are included or separately billed. Normalise the GST basis and compare the same scope over a defined period.

For an illustrative ten-person business, A$110 per user per month is A$13,200 annually excluding GST. That may be economical if it includes valuable ongoing work and reduces coordination and disruption. It may be poor value if it mostly covers a small number of basic tickets and leaves critical responsibilities undefined. Compare with a realistic ad hoc budget plus the internal time needed to own maintenance, rather than assuming one model wins universally.

Preserve business ownership and exit

Keep domains, core tenants and recovery under business control. Give the provider appropriate delegated access and document how it is revoked. Require useful records of equipment, configuration, licences and unresolved issues. Ask for the process and cost of changing providers before signing, not after the relationship deteriorates.

Check whether a long agreement bundles finance, licences or commitments that survive service cancellation. Get appropriate advice on material contract terms. A low initial fee can conceal onboarding charges, automatic renewal or expensive exclusions. A provider who makes the environment understandable and transferable may offer better long-term value than one whose price is attractive only while the business cannot leave.

Keep a practical decision record

Have the provider walk through a sample monthly report before signing. Ask how you will know that agreed maintenance occurred, which risks remain and what decisions need your approval. Keep the reporting proportionate to the business; a short actionable account is better than pages of unexplained alerts. Record who at your business reviews it and can authorise remediation. If important risks are repeatedly left unresolved because nobody owns the decision, the problem is not solved by adding more monitoring or increasing the number of tickets reported.

Make performance review practical

Agree a short recurring report: important incidents, maintenance completed, unresolved risks, backup or recovery results and upcoming decisions. Avoid a dashboard full of technical counts with no action for the owner. Ask which issues need business approval and which the provider is already handling.

Use the quote comparison tool and contract checklist to compare proposals. Start with a written service scope, named contacts and a review date. The useful outcome is clear responsibility and dependable operation at an acceptable total cost. A managed-service label and a low cost per user are insufficient evidence on their own.