The AIMSP Operating Model

Two MSPs closed the same 40,000 tickets. Only one knew what it was worth.

Same volume, same board, different operation — and your utilization report can't tell them apart.

~$2.1M in automated labor, measured across 57 months of our own ConnectWise data

Same tickets · different operation

Metric MSP A MSP B
Engineer utilization 74% 74%
Tickets closed 40,000 40,000
Automation coverage 0% 31%
Work not on the report 0 h 4,900 h

One number is the same. Everything that explains the difference is missing from it.

The Blind Spot

Your tickets close three ways. Your report counts one.

Engineers, automation, and your partners all close tickets now. The benchmark was built to see the first one only — so the better your other two get, the worse you look on paper.

100%
On the board

Your People

An engineer works the ticket and logs the time. The one slice your utilization number was ever built to see.

Counted
0
Logged as zero

Your Automation

A workflow closes the ticket before anyone opens it. Real work, done well, recorded as nothing.

Invisible
0
Logged as zero

Your Partners

Your NOC, SOC, or a vendor platform fixes it. The client is happy, the ticket is closed, your scoreboard shrugs.

Invisible
3Ways work gets done
1Way it's counted
2Left off the board

The better your operation runs, the worse you look on paper. You're being punished for being good at this.

The Diagnosis

Your utilization report only tells part of the story.

Utilization answers one question. Our operating model measures the entire operation, connecting people, automation, and partners to reveal what truly drives margin and move you toward becoming an Autonomously Intelligent MSP (AIMSP).

What you have

Billable utilization

  • Counts only human hours on billable work
  • Blind to everything automation handled
  • Punishes building — the highest-leverage work
  • Rewards being busy over being effective
  • Can't tell two very different MSPs apart

What AIMSP gives you

The whole operation

  • Counts coverage, oversight and building
  • Prices what your engineers never touched
  • Treats capacity creation as real work
  • Measures what the operation delivered
  • Distinguishes leveraged from drowning

How it works — three moves

1

We read your PSA

We connect to ConnectWise and pull every closed ticket. You do nothing but say go.

2

We sort every ticket

Each one gets credited to whatever actually closed it: a person, a workflow, or a partner. No work goes uncounted.

3

We put a price on it

Using your own resolution times, every ticket gets a dollar value. The hidden work finally has a number, usually a big one.

Deployed Time

Keep the 75%. Change what counts.

Utilization still matters. But when the work behind the number goes unseen, you get an incomplete picture of what your operation actually delivers.

See the difference

Visual representing traditional MSP operational reporting
Traditional measurement

What did the engineer log?

Billable time gives you a view of the work recorded by people. Automation oversight, capacity building, and work handled elsewhere can remain outside that picture.

What shows up in the report Recorded activity
✓
Client resolution Tickets and billable work recorded
Counted
◷
Automation oversight Monitoring, review, and exception handling
May be missed
✳
Automation building Work that creates future capacity
May be missed
↑
Offloaded and platform work Work delivered through other resources
May be missed

The benchmark stays. The picture gets bigger.

A 75% utilization target only means so much if the definition excludes work that keeps the operation running. AIMSP helps you look beyond recorded human hours to understand how the whole operation delivers.

The six buckets

Not all work gets done the same way.

Service delivery extends beyond technician hours. Explore the six ways work gets done to see what your current reporting may be missing.

Agentic Automation

AI-enabled workflows can interpret a situation, decide what action to take, and carry out approved steps across connected systems. Human oversight remains important when actions carry risk.

What to measure: Successful outcomes, exceptions, human intervention, time saved, and workflow reliability.
Six ways work gets done. One broader view of service delivery. Select a tab to explore each bucket.

The Math

What gets done, priced.

AIMSP doesn't start with an industry average. It starts with your own history — the figures already sitting in your PSA, turned into the value of the work you actually delivered.

What reports count

Billable time

One slice: the hours an engineer wrote down. Everything else — automation, offload, platform resolution — reads as zero.

What AIMSP prices

The whole operation

Every closed ticket, credited to whatever actually resolved it and valued at your own rates. Nothing falls between the buckets.

Your history — four inputs

SHRT
Standard Human Resolution Time The median time your engineers take on each ticket type.
HTE
Human Time Equivalent What a ticket that closed itself would have cost a person.
MOS
Managed Offload Savings What your partners and platforms absorbed on your behalf.
TDS
Total Deployed Savings The sum, valued at your rates — not a benchmark.
= Valued at your rate

Your Deployed Value

$ ——————

We don't publish an average, because yours isn't one. This number comes from your tickets and your rates — and it's the first time you'll see it.

The Engineer

Your engineers do three jobs.Your reports pay for one.

An engineer isn't one thing, and neither is their day. Three modes of work — and only one of them was ever designed into a utilization number.

01

Resolve

The known one

They work the ticket hands-on and log the time. This is the work your board has always seen, and the only slice billable utilization was ever built to reward.

Recognized as: billable hours

02

Oversee

The invisible one

They watch the automation, catch the exceptions, and fix what a workflow can't. Real accountability, no ticket, no time entry.

Recognized as: nothing on the board

03

Build

The punished one

They build the automation that closes the next thousand tickets. Highest-leverage work in the building — and it drags the utilization number down while they're doing it.

Recognized as: a hit to utilization

Most MSPs don't have an engineer problem — they have a recognition problem. All three modes are real work. Only one of them shows up on the report.

The ARI Report

Know where your operation stands.

The Autonomy Readiness Index report (ARI) measures how closed-ticket work moves across people, automation, and other resources using your own ConnectWise data. Your baseline. Your numbers. Your next move.

01

Connect

Establish read-only access and load the agreed ConnectWise ticket history into a dedicated data vault.

Starting point Your data, securely prepared.
02

Discover

Review boards, members, and system accounts with your team to validate what the data represents.

Outcome Validated operational data.
03

Measure

Classify closed-ticket activity across six AIMSP buckets and assess its value using agreed rates.

Deliverable ARI Report
04

Deliver

Walk through the findings and identify priorities for improving your operation.

Deliverables Executive Brief + Prioritized Roadmap

ARI establishes the baseline. Your findings inform the AIMSP Strategic Plan, with ARI Pulse available to measure progress quarterly.

Frequently Asked Questions

What is AIMSP?

Autonomously Intelligent MSP — an operating model for running and measuring an MSP by the work the whole operation gets done, not just the hours an engineer logged. People, automation, and partners all contribute. AIMSP counts all three.

How is this different from billable utilization?

Utilization counts logged human hours. That was accurate when every ticket ran through a person — it isn't now. AIMSP keeps the 75% target and changes what counts toward it, so automation and offloaded work stop reading as zero.

What is ARI?

The Autonomy Readiness Index — the score you get from the assessment. It reads your ConnectWise history and shows how much of your closed volume runs without a person, measured per bucket and valued at your own rates. It isn't a grade; it's the baseline you move from.

What do you need from us to run it?

A read-only API member in ConnectWise. That's it — no new tools, no data export, no homework. We map your boards, members, and system accounts, and you confirm each one before anything gets counted.

How long does the assessment take?

Three to six weeks, depending on size: up to three weeks for MSPs under 25 active members, four weeks up to 75, six weeks beyond that or across multiple instances.

What do we actually receive?

Three things: the ARI report for your ops leaders, an Executive Brief for ownership, and a prioritized roadmap for what to automate first. All three walked through together, not emailed over.

Is our number going to look bad?

It might look low — and that's usually the point. A low ARI means most of your volume still depends on a person, which is headroom, not failure. Most MSPs discover they're doing better than their reports showed and worse than they assumed. Either way, now you know.

What happens after the assessment?

Your findings drive the AIMSP Strategic Plan as its own engagement, and ARI Pulse re-measures quarterly against your anchored baseline — so the number stays honest over time instead of drifting back into the dark.

Does this replace our PSA or change how we work?

No. It reads what's already in ConnectWise and changes what gets counted — not how your team does the work. Nobody changes a process to make the measurement work.

How do we get started?

One short conversation about how your operation runs today. We'll confirm the right tier and scope, and give you a read-only member to set up. One point of contact is all we need from you. Book a meeting with us or send a message for more details below.

Find out what your operation actually
delivers with AIMSP.

Meet with Hubert Williams
Account & Sales Manager, Decision Digital
30 minutes · Microsoft Teams

Scheduler not loading? Open Hubert's calendar in a new tab →

This field is for validation purposes and should be left unchanged.
Name(Required)