levelpartner.ai
Scaling and operations

IT operational efficiency: a practical guide

IT operational efficiency in a company of 10 to 250 people is mostly about licences and access, not servers. The money and time leak through software seats nobody uses, accounts that stay open after people leave, onboarding that takes a week to set up a laptop, and three systems doing the same job. This article answers a practical question for an owner or operations lead without a large IT department: where does IT waste actually sit in a firm your size, and how do you remove it without hiring an IT manager?

Where the waste sits

Large organisations worry about data centres, networks and infrastructure costs. Most firms of 10 to 250 people run on cloud software and have very little infrastructure left to optimise. Their IT inefficiency sits in five places.

  • Licences: paid seats for people who left, people who never log in, or tools that were replaced but never cancelled.
  • Access: new starters waiting days for accounts, leavers keeping access for weeks, and nobody sure who can see what.
  • Duplicate systems: two or three tools doing the same job because different teams chose them.
  • Support: small problems handled by whoever is nearest, with no record, so the same problem is solved repeatedly.
  • Data ownership: customer and company data scattered across personal accounts and tools nobody administers.

None of these needs specialist infrastructure skills. They need an owner, a register and a few procedures.

Start with a licence audit

The licence audit is the quickest win and it usually pays for the effort many times over.

List every software subscription the company pays for, from the finance records rather than from memory. For each, record the monthly cost, the number of paid seats, the number of active users in the last 60 days, the business owner, the renewal date and the notice period.

Then compare paid seats with active users. The gap is usually larger than anyone expects.

Illustration: a licence audit at a 70-person consultancy

Suppose finance records show 34 subscriptions costing an illustrative 9,800 pounds a month. Say comparing paid seats with users active in the last 60 days turns up 61 unused seats across 12 tools, worth 1,450 pounds a month, plus four replaced tools still billing 620 pounds a month. Removing both would come to 2,070 pounds a month, or about 24,800 pounds a year, before any consolidation. Your own audit will produce your own figures.

Repeat the audit every six months. Seats accumulate again quickly, especially when new starters are given everything by default.

Onboarding and offboarding as procedures

Joiners and leavers are where access goes wrong. A new starter who waits three days for accounts loses three days of productive time. A leaver who keeps access to the CRM and shared drives for a month is a security and data protection problem.

Write two short procedures.

The joiner procedure lists, by role, every account a new starter needs, who creates it, and the deadline: everything ready before their first morning. It should include equipment, email, the main business platform, any role-specific tools, and the security setup such as two-factor authentication.

The leaver procedure lists every account to remove, who removes it, and the deadline: same day as the last working day. It also covers transferring ownership of files, client records and open tasks, and recovering equipment.

Tie both procedures to the HR process so IT is triggered automatically when someone is hired or resigns. On the levelpartner.ai platform, user access is managed in one place within Settings, and a workflow's Assign User action can move a leaver's contacts to a named colleague, which makes the leaver step for customer data quick.

Reduce the number of systems

Every system you run needs licences, access management, training, support and someone who understands it. Five systems that share customer data also need integrations, which break quietly.

Look at the overlap the audit reveals. Firms often run a separate CRM, email tool, booking tool, form builder, SMS app and invoicing system, each holding a copy of customer data. Consolidating those onto one platform reduces licences, access points and integrations in one move.

Keep specialist systems where they do a job a general platform should not: accounting, regulated case management, design software. The aim is fewer systems overall, not one system for everything. For a broader look at this, our guide to digital operations management covers how to decide what to consolidate.

Handle support with a record

In most firms this size, IT support is informal. Someone has a problem, asks the person who is good with computers, and it gets fixed. Nobody records it.

The cost is invisible but real. The same problems recur. The informal helper loses hours every week from their actual job. Nobody knows which systems cause the most trouble.

A simple fix: one route for IT requests, such as a shared form or a dedicated inbox, and a basic log of what was raised and how it was solved. After three months, the log shows which problems recur and which tools generate the most friction. Those become candidates for training, a procedure or replacement. The sample standard operating procedure shows a format for writing the fixes down.

Own your data

Customer and company data should sit in systems the company administers, not in personal accounts. The test is simple: if any one person left tomorrow, could the company still access every client record, file and conversation that person handled?

If the answer is no for any system, fix it before anything else. Move shared work onto company accounts, set the company as owner of every subscription, and keep administrator access with at least two people.

The mistake most IT efficiency advice makes

Most writing on IT operational efficiency is aimed at IT departments in large organisations: infrastructure automation, cloud cost optimisation, service management frameworks and monitoring. It assumes a team of IT staff whose time is the main cost.

In a firm of 60 people with no IT department, that advice does not apply. The cost is in licences you pay for and do not use, and in the productive time of non-IT staff lost to access problems and repeated small issues. Fix those and the IT bill and the friction both fall.

The trade-off

Tighter access control and a single request route add a little friction. Staff can no longer sign up for a tool on a company card and share it with their team without approval. Some will see that as bureaucracy.

You also need someone to own all of this, usually an operations lead spending a few hours a month, or an external IT provider on a small retainer. That is a cost, but much smaller than the waste it removes.

Illustration: an estate agency and the leaver who kept access

Picture a four-branch estate agency where an audit shows a negotiator who left five months ago can still open the property management system and a shared drive of vendor details. With no leaver procedure, there would be no reason to think they are the only one. A same-day leaver step tied to HR, plus one full access review, would close the gap before anything went wrong, which is the only good time to close it.

A quarterly IT routine

Once the basics exist, a short quarterly routine keeps IT efficient.

  • Check paid seats against active users and remove the gap.
  • Review renewals in the next quarter and decide on each.
  • Confirm every leaver from the past quarter has no remaining access.
  • Read the support log and pick the top recurring problem to fix.

To turn those fixes into habits, see our guide to SOP training. For giving an assistant their own access instead of shared passwords, read the SOP for a virtual assistant.

Frequently asked questions

What is IT operational efficiency for a small company?

It means getting the software, access and support the business needs at the lowest cost and friction. For most firms of 10 to 250 people it comes down to licences, access control, the number of systems and how support requests are handled.

How often should we audit software licences?

Every six months. Unused seats build up quickly as people join, leave and change roles, and many subscriptions renew automatically. Link each audit to the renewal dates coming up.

Do we need an IT manager?

Not usually below about 100 staff. An operations lead with a few hours a month, supported by an external IT provider for technical issues, covers most needs if the procedures and registers exist.

What is the quickest IT saving?

Removing unused licence seats and cancelling tools that were replaced but never stopped. A licence audit usually finds both within a day or two of work.