Flamingo Raises $4.5M Seed Round

Skip to content

IT metrics that matter: KPIs for MSPs and in-house teams

Best Practices
MSP
IT Operations
Conrad LunderstedtConrad Lunderstedt
October 6, 2026
247 views
IT metrics that matter: KPIs for MSPs and in-house teams

Covers IT department KPIs mapped to business objectives, KPI examples for each IT staff role, how many IT staff per employee, endpoint management KPIs, what MSP clients want reported, and the metrics that get gamed with the number that exposes each.


IT metrics are the numbers an IT department or MSP counts from its own systems, such as response time, patch compliance and the date of the last restore test, to see whether IT is doing its job. Every RMM and PSA ships a dashboard with forty of them, and nobody reads forty tiles, so the numbers stop changing decisions and start decorating a login page. This guide picks the IT metrics and KPIs worth tracking for an in-house team and for an MSP reporting to clients, and shows where each one is measured, and where it gets gamed.

TL;DR

  • Metric vs KPI. A metric is any number a system can count; a KPI adds an owner, a target and a decision that changes when the number crosses the target.
  • Four layers. Track the service desk, uptime, security and what the business sees, at five to ten KPIs per function.
  • For IT departments. Tie each KPI to an objective the business funds, such as hours lost waiting on IT or patch compliance inside 14 days, and review it monthly with the budget owner.
  • For MSPs. Track the same numbers per client, then translate them into outcomes: hours lost, exceptions named and restore test dates.
  • Start with three. First response time by priority, patch compliance with exceptions named, and the date of the last restore test.

What IT metrics are (and which ones are KPIs)

A metric is any number you can count from a system: tickets opened, minutes to first reply, endpoints missing a patch. A KPI is a metric with three things bolted on: an owner, a target, and a decision that changes when the number crosses the target. Ticket volume is a metric. Tickets per user per month for one client, trending up for a quarter, with a review booked when it passes 1.5, is a KPI.

Two more distinctions save arguments later. Leading metrics predict pain: patch lag, backlog growth, reopen rate. Lagging metrics record it: outages, churn, breach count. And an SLA is a promise built on a metric, so measure the metric for a quarter before you sign the promise. The post on what an SLA is covers how the promise gets written.

For an IT department, KPIs sit at two levels. Function metrics, like the service desk and patching numbers below, are what the team watches each week. Department KPIs sit above them and track the objectives the business pays IT to meet, such as keeping people working and proving recovery works, and they are the numbers that go to whoever owns the IT budget. An MSP runs the same two levels per client: technicians watch the function metrics, and the client review covers the outcomes.

One rule from NinjaOne's IT KPI guide (updated July 2026) holds up in practice: five to ten KPIs per function. Past that, people watch the dashboard instead of the fleet. The rest of this post sorts the candidates into four layers: service desk, uptime, security, and what the business sees, then maps them to department objectives and staff KPIs.

Service desk metrics

The desk produces the most numbers and the most arguments about them. Start with the ones that describe what a user feels:

  • First response time: minutes from ticket creation to a human reply, measured per priority, never as one blended average.
  • Resolution time: creation to confirmed fix, again per priority.
  • First-tier resolution rate: the share of tickets closed by the first tier without escalation. One r/msp owner prefers it over first-contact resolution for a plain reason: a second call is fine, an escalation costs a senior tech's hour.
  • Reopen rate: tickets reopened within seven days of closure. It is the check on resolution time, because a fast close that comes back was not a fix.
  • Backlog trend: open minus closed over a rolling seven days. Negative is good, positive for three days in a row means the queue is winning.
  • CSAT: a one-tap rating at closure, read next to its response rate, since a 4.9 from six people says less than a 4.4 from sixty.
  • Tickets per user per month: the demand number, and the first thing to compare across clients or departments.

MSPs add one more: reactive hours per endpoint per month, which ties desk time to what each client pays for. A client at 0.4 hours per endpoint and a client at 1.6 are not the same account, whatever the contract says. The help desk KPIs section of our help desk guide covers the formulas in more detail.

Uptime and reliability metrics

Availability is a percentage per service per month, measured where the users are. A synthetic check that logs into the app every five minutes counts; the server's own uptime counter does not, because a server can be up while the service behind it is dead. The arithmetic matters when you write the target: 99.9% allows about 43 minutes of downtime a month, 99.5% allows about 3.6 hours.

Behind availability sit the repair metrics. Mean time to resolve, by priority, tells you how long an outage lasts once someone is working it. Mean time between failures on a device class tells you when hardware is aging out. Both need an incident record with real timestamps, which is what the incident management process exists to produce.

Two more belong on every scorecard because they predict the outage rather than report it. Patch compliance is the share of endpoints on the current patch level inside the agreed window, with the exceptions named. Backup health is two numbers: backup job success rate, and the date of the last successful restore test. The second one is a date, not a percentage, on purpose. Uptime Institute's 2026 outage analysis (May 2026) found 57% of respondents saying their most recent major outage cost more than $100,000, and one in five over $1 million. A restore test date is the cheapest insurance on that list. Our guide to IT infrastructure monitoring covers where the availability and repair numbers come from.

Security metrics

Security metrics come in two kinds: coverage and time. Coverage numbers answer "how much of the estate is protected": MFA coverage on accounts, endpoint agent coverage, disk encryption coverage. Each is a percentage of in-scope devices or accounts, and each is only useful with the exceptions listed by name. "97% MFA" hides three service accounts with domain admin rights.

Time numbers answer "how fast do we close the gap". Time to patch a known-exploited vulnerability is the one to start with. CISA's Binding Operational Directive 26-04, which replaced BOD 22-01 in June 2026, sets a remediation due date for each entry in the Known Exploited Vulnerabilities catalog, three or 14 days for every entry added since then; borrow that clock even if the directive does not apply to you. Verizon's 2026 Data Breach Investigations Report (May 2026) found that 31% of breaches started with an exploited vulnerability, ahead of stolen credentials for the first time, and that only 26% of the known exploited vulnerabilities in CISA's catalog had been fully remediated across the organizations studied, which is the reason that clock matters. Add open vulnerabilities older than 30 days, and mean time to detect, the dwell-time number that threat hunting is meant to shrink.

Then the people numbers: phishing simulation click rate and, more useful, report rate. A team that reports the phish inside five minutes has a working control; a team that never clicks may just have a good spam filter. The post on security awareness training explains why the report rate is the one to track.

Last, the noise number. Alerts per technician per day, and the share that led to an action, tells you whether the security stack is producing signal. Tuning starts from that ratio, which the alert fatigue post walks through.

Endpoint management KPIs

The endpoint fleet is where coverage numbers drift first, so it earns a short list of its own:

  • Check-in rate: the share of managed devices that reported in over the last seven days. A device that has gone quiet is a device nobody is patching.
  • Patch compliance inside the agreed window, split between the operating system and third-party applications.
  • Time to deploy a critical or KEV-listed patch, from release to installed on the last device.
  • Encryption and endpoint agent coverage, with the exceptions named.
  • Devices on an operating system past its end of support, such as Windows 10 machines without Extended Security Updates after October 14, 2025.

The same five numbers show whether an endpoint management rollout is improving IT operations: record them for a quarter before the change and compare the quarter after. Our guide to unified endpoint management covers the tooling side.

What clients want to hear

A January 2026 r/msp thread asked which KPIs clients like hearing. The top reply was blunt: clients do not care about internal numbers like ticket counts or first response time. They care whether their people can work without interruption, whether their data is secure, and whether projects land on time. Everything else is the MSP's homework.

That does not make the internal metrics useless. It means the client report translates them. First response time becomes hours of staff time spent waiting on IT this month. Patch compliance becomes "every laptop is on current patches, and the three exceptions are the CNC machine, the badge server and the CEO's old MacBook". Backup success rate becomes "restore test passed on the 14th, 22 minutes to a working file server". The vCIO reporting conversation is where those translated numbers belong.

IT department KPIs and metrics

An in-house IT department reports to the business the way an MSP reports to a client, so its KPIs should start from objectives the business would recognize rather than from the dashboard. Pick four to six objectives, attach one or two KPIs to each, and let the function metrics above feed them.

Department objectiveIT department KPIMetrics behind itMSP equivalent, per client
Keep people workingHours lost waiting on IT per monthResponse and resolution time by priority, tickets per userHours lost per client in the monthly review
Keep key services availableAvailability of the two or three services people would noticeSynthetic checks, mean time to resolve by priorityAvailability per client service against the SLA
Reduce exposurePatch compliance inside 14 days, exceptions namedPatch level per endpoint, time to patch KEV entries, MFA coverageThe same per client, each exception named
Prove recovery worksDate of the last successful restore testBackup job success rate, restore durationRestore test date and duration per client
Deliver change on timeProjects delivered on the agreed dateMilestones hit, changes rolled backProject milestones in the client review
Spend within budgetIT spend against planCost per user and per device, renewals dueMargin per client, reactive hours per endpoint

Review the department KPIs monthly with whoever owns the IT budget, and keep the function metrics for the weekly team meeting. The spend line comes straight from the IT budget planning template, which has the per-user and per-device columns.

KPI examples for IT staff

A staff KPI works when the person can move the number. A help desk technician controls their own response time and reopen rate, but not the backlog of a short-staffed team, so set individual KPIs at the level each role owns:

  • Help desk technician: first response time by priority, reopen rate within seven days, CSAT on their own closed tickets, and knowledge articles added or updated.
  • Endpoint or desktop technician: devices patched inside the window, devices out of compliance for more than 14 days, and onboarding and offboarding tickets closed by the start or leave date.
  • Systems or network administrator: availability of the services they own, mean time to resolve P1 and P2 incidents, and restore tests completed on schedule.
  • Security lead: time to patch KEV entries, MFA and agent coverage with exceptions named, and phishing report rate.
  • IT manager: hours lost waiting on IT, projects delivered on the agreed date, and IT spend against plan.

MSP technicians add reactive hours per endpoint for the clients they own. Use staff KPIs for coaching conversations rather than rankings, because a personal target with a bonus attached gets gamed the same way a team metric does, as the next section shows.

How many IT staff per employee

There is no single right ratio, because outsourcing, automation, remote sites and the complexity of the environment all move it. Pave's analysis of 1,856 companies with 100 or more employees found a median of about one IT team member per 75 employees (updated August 2026), with a wide spread between the 25th and 75th percentiles.

IT hiring across the market picked up in 2026. Avasant's IT Spending and Staffing Benchmarks 2026/2027 study (August 2026), based on a survey of more than 750 IT executives in the US and Canada, found 64% of companies increasing IT headcount and 11% decreasing it, up from 48% planning increases the year before. Avasant links much of that hiring to AI and machine learning work.

To find your own ratio, divide employees by IT staff, then check two metrics from the service desk section: tickets per user per month and reactive hours per endpoint. If both are rising while the ratio holds, the team is stretched. Work an MSP covers, such as monitoring, patching or after-hours support, comes off the internal headcount, which is how a co-managed IT arrangement changes the math.

Metrics that get gamed

Every metric with a target attached will be gamed, usually without anyone meaning to. The pattern is old enough to have a name, Goodhart's law: once a measure becomes a target, it stops being a good measure. The fix is never to drop the metric. It is to pair it with the number that exposes the shortcut.

Resolution time gets gamed by closing tickets fast. Reopen rate exposes it. SLA attainment gets gamed by parking tickets in "waiting on customer", where the clock stops. Time in pending exposes it. Backlog gets gamed by auto-closing anything without a reply in three days. Auto-close count exposes it. Utilization gets gamed by logging time generously, and a desk at 100% utilization has no hours left for documentation, which shows up six months later as a rising escalation rate.

An October 2024 r/msp thread on picking three support KPIs produced a good example of a metric that resists gaming: a "crush rate", a rolling seven-day count of open minus closed tickets. It is hard to fake, because closing tickets that come back moves it the wrong way within the same week.

Building the scorecard

Run every candidate through four gates before it earns a tile. It has an owner, one person, not a team. It has a data source you can query today, not one you plan to build. It has a target, written down, with the date it was set. And it changes a decision: if the number goes red and nobody does anything different, it is a report, not a KPI.

A starter set that passes those gates for a small internal team: first response time by priority, resolution time by priority, reopen rate, backlog trend, availability for the two services people would notice, patch compliance, restore test date, MFA coverage. Eight tiles. For an MSP, per client: the same eight plus tickets per user per month and reactive hours per endpoint. Starting thresholds are just that, starting points: a reopen rate under 5%, patch compliance above 95% inside 14 days, a restore test inside the last 30 days. Move them once you have a quarter of your own data. The patch compliance guide covers how to set that window.

Coverage numbers are the ones that get counted by hand and drift. A scheduled check of agent state, patch level and encryption status across every device, with the output collected in one place, keeps them current without a spreadsheet. In OpenFrame, the open, AI-native infrastructure for IT and security that Flamingo builds, Mingo runs those checks across an in-house fleet or every MSP client, and a technician reviews the exceptions it raises. Whatever runs the check, the rule is the same: the scorecard reads from the system, never from a person's memory of the system.

Start with three

If eight still feels like forty, start with three: first response time by priority, patch compliance with exceptions named, and the date of the last restore test. One tells you how the desk feels to users, one tells you how exposed the fleet is, and one tells you whether the backup you pay for would work. Add the rest a quarter at a time, and drop any tile that has not changed a decision in six months.

For the process that produces clean incident timestamps, read the incident management guide.

For the promise you make from these numbers, read what an SLA is.

FAQ

What is the difference between an IT metric and a KPI?

A metric is any number you can count from a system, such as tickets opened or minutes to first reply. A KPI is a metric with an owner, a target and a decision attached: when it crosses the target, someone does something different. Every KPI is a metric; only a few metrics deserve to be KPIs.

How many IT KPIs should a team track?

Five to ten per function is the working rule. Past that, the dashboard stops changing behavior. A small internal IT team can run on eight: response and resolution time by priority, reopen rate, backlog trend, availability, patch compliance, restore test date and MFA coverage.

What is a good first response time for a help desk?

It depends on priority, which is why a single average is misleading. Common starting targets are 15 minutes for a P1 outage, one hour for a P2 that blocks one person's work, and four business hours for routine requests. Measure your own numbers for a quarter, then set targets you can hit nine times out of ten.

Which IT metrics should an MSP report to clients?

Translated ones. Clients care whether their people can work, whether their data is safe and whether projects land on time, so report hours lost waiting on IT, patch compliance with the exceptions named, the date and duration of the last restore test, and project milestones. Keep first response time, utilization and ticket counts for internal review.

Conrad Lunderstedt

Conrad Lunderstedt

Solution Architect

I'm Conrad, Solution Architect at Flamingo. I've spent about 26 years in IT, roughly half of it inside MSPs and the rest in enterprise environments, so I've watched vendor decisions get made on both sides of that line. Now I spend my days talking with MSPs about the stack they already run, and helping them work through the requests and issues that come with it.

Related Content

Frequently Asked Questions

/blog/it-metrics

Still deciding?

Ask Mingo answers from our docs and customer stories.

Loading related content and questions