Sign up free

Solution · For small business

Good IT service, sized for a small business.

A small business does not need a large IT department. It needs the one service that earns the money to stay up, someone to call when it does not, and a simple record of what happened — nothing more, and nothing less.

By itserva Editorial Team Updated November 20, 2026 Reviewed by [REVIEWER NAME, CREDENTIAL]

The one critical service named, protected and watched.

A simple agreement that says what good looks like.

Software chosen for a small budget, on published prices.

The problem

Why small business IT feels fragile

Small businesses feel IT problems more sharply than large ones: one outage can stop the whole day, and there is no spare team to absorb it. The fix is focus, not more tools.

No one owns IT

IT is everyone’s second job and no one’s first. When the system fails, the person who fixes it is whoever is free — and the fix is whatever works in the moment, with no record kept.

Every outage stops everything

There is no second site, no failover, no spare. When the till system or the booking system goes down, the business stops earning until it comes back.

Paying for tools nobody uses

Software was bought on a recommendation, used for a month, and forgotten — but the subscription renews every year. A small budget leaks fastest through the subscriptions nobody checks.

Help arrives too late

The support call goes to a queue, the queue goes to a ticket, and the ticket waits. Without an agreed response time, soon means whatever the vendor feels like that day.

The process

Five steps, and the itserva page for each

Five steps, in the order a small business can actually do them.

  1. 01

    Pick the service that matters

    Name the one service the business cannot earn without — the till, the bookings, the email. Everything else can wait; this one gets the attention, the backup and the agreement.

    What is ITSM? guide →

  2. 02

    Agree a simple SLA

    Write down what the service promises: how available it will be, and how fast help arrives when it is not. A short, plain agreement beats a long one nobody reads.

    SLA Template →

  3. 03

    Log incidents in one place

    One record per incident: what happened, who was affected, and what fixed it. The record turns it broke again into a pattern you can see — and a conversation you can have with your supplier.

    Incident Report Template →

  4. 04

    Work out what downtime costs

    Estimate what an hour without the critical service costs in lost sales and wages. The number decides what a backup is worth, and what a faster support contract is worth.

    Downtime Cost Calculator →

  5. 05

    Choose affordable software

    Compare help desk software on price, channels and fit for a small team. The comparison shows what each vendor charges — and marks what it does not publish — so a small budget is spent on facts.

    Best Help Desk Software →

What’s included

Tools, templates and guides for small business

Guide

What is ITSM?

What IT service management covers, who it is for, and where to start.

Template

SLA Template

A service level agreement you can adapt: targets, exclusions and remedies.

Template

Incident Report Template

Record what happened, who was affected, and what was done — in one page.

Tool

Downtime Cost Calculator

Estimate what an hour of downtime costs your organisation.

Product

Service Desk

Log every request and incident in one place, with priority and SLA timers built in.

Comparison

Best Help Desk Software

Help desk software compared on price, channels and fit for small teams.

Measure it

The four numbers worth tracking

Four numbers keep a small business honest about its IT. None of them needs a dashboard — a monthly note is enough.

Downtime cost

What the month’s downtime actually cost in lost sales and wages. It is the number that decides whether the backup, the spare or the better contract is worth it.

Estimate downtime cost →

MTTR

How long it takes, on average, to get the critical service back. A falling number means the record and the routine are working; a rising one means something needs attention.

Calculate your MTTR →

SLA met rate

Whether the agreed target was met this month. One missed month is a conversation; three in a row is a decision about the supplier.

Check your SLA allowance →

Cost per ticket

What each support request costs to resolve. It is the number that shows whether the support contract is good value — or whether the team is paying to fix the same thing repeatedly.

Calculate cost per ticket →

Frequently asked questions

Do we need an SLA if we only have one IT supplier?

Yes — especially then. A short written agreement is what turns “we will get to it soon” into a response time you can hold the supplier to, and it costs nothing to write.

What is the one service we should protect first?

The one the business cannot earn without. For most small businesses that is the till, the booking system or email. Protect that one properly before spending anything on the rest.

How much should a small business spend on IT support?

Start from the downtime cost: what an hour without the critical service loses. If the support contract costs less than one bad outage, it is paying for itself.

Should we buy help desk software?

Only when the requests outgrow email and memory. Until then, one shared log and one report template are enough — and they are free.

Name the service that earns the money.

Run the downtime calculator on that one service, then put the number into the SLA template. A free workspace saves both, so the next supplier conversation starts from facts.

Create a free workspace