Executive Guide

AIMSP

The MSP operating model for the work your reports don’t count.

A plain-English guide for MSP owners

decision digitalAn Automated Instincts framework
decision digitalAIMSP Executive Guide
The Shift

The question has changed.

The old questionHow busy are my engineers?
The AIMSP questionHow much work does my entire operation get done?

When humans did every ticket action, counting engineer hours was a fair way to measure the work. That’s no longer true.

Automation, managed partners and intelligent triage now close a big share of your tickets. Your utilization report still only counts the hours your engineers logged. So the more your operation improves, the less of it your reports can see. It’s like judging a dishwasher by how many hours you spent at the sink.

~$2.1MMeasured labor offset

That’s what Decision Digital found when we ran ARI on ourselves: 57 months of our own ConnectWise data, valued work our utilization reports had been recording as zero.

This is Decision Digital’s measured result, not a guarantee that every MSP will see the same.

AIMSP Executive Guide  ·  CATAPULT · Advisory02 / 10
decision digitalAIMSP Executive Guide
The Three Forces

Your engineers aren’t your whole operation.

Three forces get your tickets closed. Only one of them shows up on a utilization report.

People

Your engineers

Resolve what automation can’t, oversee the systems doing routine work, and build what runs next.

Systems

Your automation

Workflows, agents and intelligent triage that handle repeatable work without an engineer touching every ticket.

Partners

Your NOC, SOC and platforms

Managed services and paid platforms that absorb work that would otherwise land on your team.

What your utilization report actually sees

Engineer hours on client work
Counted
Tickets automation closed
Not counted
Tickets partners resolved
Only as a cost
Building and overseeing automation
Not counted

All of it is real work. Most of it sits below the line utilization draws. That’s the gap AIMSP closes: one view of what people, systems and partners actually got done.

AIMSP Executive Guide  ·  CATAPULT · Advisory03 / 10
decision digitalAIMSP Executive Guide
The Evolving Engineer

The engineer evolves.

AIMSP isn’t “AI replaces engineers.” The title on the org chart stays the same. What the engineer contributes grows.

Dimension 01

Resolve

The hard cases that need human judgment: security incidents, architecture decisions, escalations beyond any workflow or partner.

Dimension 02

Oversee

The judgment layer above the automation. Handling exceptions, reading edge cases, staying accountable for the systems doing routine work.

Dimension 03

Build

Designing the workflows, scripts and alert rules that run next. Every hour here pays off across thousands of future tickets.

An engineer who supervised 200 automated resolutions this week did something real. Under utilization, it’s invisible. Under AIMSP, it counts. Over time the mix shifts: less routine volume, more of the work only your best people can do.

The engineer isn’t becoming less important. The engineer is becoming more leveraged.
AIMSP Executive Guide  ·  CATAPULT · Advisory04 / 10
decision digitalAIMSP Executive Guide
Deployed Time

Keep the 75% target. Change what counts.

Every MSP knows the benchmark: 75% of available hours on billable client work. The target isn’t the problem. What gets counted is.

The workflow your engineer tuned Tuesday morning: not counted. The NOC escalation they managed that afternoon: not counted. The alert rule they rebuilt Friday that keeps 200 tickets out of next month’s queue: not counted. AIMSP replaces billable utilization with Deployed Time, the share of hours spent on work that creates value. Three things count:

1

Client resolution

Traditional billable work. Still the foundation, just not the whole story.

2

Automation oversight

Being accountable for the systems handling routine work.

3

Automation building

Capacity creation, not overhead.

And beside the 75%: leverage

What an engineer’s automation delivers while they’re doing something else is reported right next to Deployed Time, not folded into it. Their hours are their hours. The automation is the multiplier.

1.4x75% deployed, 40% more delivered
AIMSP Executive Guide  ·  CATAPULT · Advisory05 / 10
decision digitalAIMSP Executive Guide
Every Ticket Tells a Story

A closed ticket isn’t the whole story.

AIMSP looks past “closed” and asks how the work actually got done. Every ticket lands in exactly one of six buckets.

CoverageWork done without your engineers
  • 1Agentic Automation. Automation handled it start to finish.
  • 3Managed Offload. Your NOC or SOC resolved it.
  • 4Platform-Resolved. A platform you pay for fixed its own problem.
The AssistAutomation and people together
  • 2Automation-Assisted. Automation helped; your engineer finished it, faster.
OpportunityWhere to automate next
  • 5Human Dismissal. Closed by a person with zero time logged. Your biggest automation opportunity.
BaselineThe comparison set
  • 6Fully Human. An engineer worked it start to finish.
Two MSPs can close the same number of tickets while running completely different operations underneath.
AIMSP Executive Guide  ·  CATAPULT · Advisory06 / 10
decision digitalAIMSP Executive Guide
From Tickets to Dollars

Make invisible work visible.

AIMSP doesn’t start with an industry average. It starts with your own ConnectWise history.

For every type of ticket, we find how long it typically takes your engineers to resolve. We use the median, so a handful of marathon tickets can’t skew it. That’s your baseline, called SHRT (Standard Human Resolution Time). Think of it as your internal price list for engineer time. Then three questions put a dollar value on everything else:

HTE

Human Time Equivalent

If automation handled this ticket, how much engineer time did that save?

MOS

Managed Offload Savings

If a partner or platform handled it, what would it have cost our own engineers?

TDS

Triage Dispatch Savings

If triage routed it automatically, how much dispatcher time did we avoid?

A quick example

Say a password reset takes your engineers 20 minutes. Automation closed 3,000 of them last year. That’s 1,000 engineer hours that never hit your payroll.

3,000 tickets×20 min=1,000 hours
½an engineer you didn’t have to hire

No formulas required. Different kinds of work, translated into one common language: human labor.

AIMSP Executive Guide  ·  CATAPULT · Advisory07 / 10
decision digitalAIMSP Executive Guide
The Diagnostic · ARI

Now you can see the operation.

ARI, the Autonomy Readiness Index, brings it all together. Think of it like a home inspection report: built entirely from what’s actually there.

Where are we?

How work is really being handled across people, systems and partners.

What is it worth?

The labor value being created, avoided or absorbed, in dollars.

Where are the gaps?

Where automation, routing, process or data opportunities sit.

What comes next?

Which areas deserve attention first, and in what order.

ARI isn’t a magic score. It’s a diagnostic report grounded in what your operation has already done. Every figure traces back to your own PSA data, so there are no industry averages or assumptions to argue with.

Inside the report

Operations leadership gets the full report. A separate Executive Brief covers the same findings for ownership.

AIMSP Executive Guide  ·  CATAPULT · Advisory08 / 10
decision digitalAIMSP Executive Guide
Clearing the Air

What AIMSP isn’t.

×

Replacing your engineers with AI

It expands the engineer’s role. It doesn’t eliminate it.

×

Automating everything

Some work will always need human judgment.

×

Another utilization dashboard

It changes the measurement model, not just the report.

×

A software platform

AIMSP is an operating model, not a product.

×

A certification

It’s a framework for running and measuring an MSP.

×

A one-time report

It’s a loop: measure, improve, measure again.

The owner’s view

The old viewThe AIMSP view
Are my engineers productive?Is my entire operation productive?
Engineer hours are the evidence of work.Engineer hours are one part of the evidence.
Automation reduces utilization.Automation creates capacity.
Partner work is an expense.Partner work is labor you didn’t have to spend.
A closed ticket is the end of the story.A closed ticket tells you to ask how it got done.

You don’t abandon utilization. You stop treating it as the whole picture.

AIMSP Executive Guide  ·  CATAPULT · Advisory09 / 10
decision digitalCATAPULT · Advisory
The Next Step
Built on AIMSP. Measured by ARI.

The Automation Intelligence Assessment

What is your MSP actually getting done that your reports don’t count? A fixed-scope engagement that runs ARI against your own ConnectWise data and answers exactly that, in three to six weeks.

1

Connect

A read-only connection loads your ConnectWise history into SMARTvault. Included, and yours to keep.

2

Discover

We map your boards, people and system accounts. You confirm each one before anything is counted.

3

Measure

Every ticket sorted into the six buckets, your SHRT baseline built, and the dollar values calculated.

4

Deliver

Your ARI report, the Executive Brief and a prioritized roadmap, walked through together.

EssentialBalance Builder · up to 25 active ConnectWise members
StandardValue Builder · 26 to 75 active members
EnterpriseEmpire Builder · 76+ members or multiple instances
info@decisiondigital.com  ·  (404) 303-0330  ·  decisiondigital.com/consulting
ARI and the AIMSP framework are products of Automated Instincts, LLC, delivered under license by Decision Digital, Inc.
AIMSP Executive Guide  ·  CATAPULT · Advisory10 / 10