Most MSP owners we talk to already run a PSA, an RMM, a documentation platform and a quoting tool. The problem is rarely missing software. It is that dispatch still reads every ticket by hand, QBR decks take a service manager a full day each, and agreement renewals surface when the client calls to complain. Your techs automate client environments all day, yet your own back office runs on spreadsheets and memory.
InTheory acts as your fractional AI and technology lead for the business side of the MSP. We would pick one expensive recurring workflow, such as ticket triage in ConnectWise PSA or HaloPSA, or proposal assembly in Quoter, measure how it runs today, and lead a scoped 90-day improvement. People still approve pricing, client communication and anything that touches a client's security posture.
Alerts from the RMM, password resets, printer issues and real outages all land in the same service board. A dispatcher or senior tech reads each one, sets priority and type, and assigns it. When that person is out, response times slip, SLAs breach and engineers get pulled off project work to clear the queue.
Per-user and per-device agreements were priced years ago. Seat counts drift, clients add locations, and some accounts quietly consume twice the support hours of others. Without a clean view of effective hourly rate by agreement, the owner cannot tell which clients to reprice, which to keep and which are losing money.
A useful quarterly business review pulls ticket trends from the PSA, patch and backup status from the RMM, license counts from Microsoft 365 and a roadmap from the vCIO. Assembling that by hand for thirty clients means QBRs get skipped, and skipped QBRs are where renewals and project revenue are lost.
IT Glue or Hudu holds passwords and configurations, but the reasoning behind each client's setup sits with the tech who built it. New hires take months to become useful, and the same questions bounce around Teams every week. Documentation drifts out of date because nobody owns keeping it current.
We fix one at a time, starting with the one that costs you most. Each page shows the steps, the tools, what stays human and what we would measure.
Classify incoming tickets by type, priority and client, suggest the right board and resource, and draft a first response, with a dispatcher confirming before anything reaches the client.
See the workflow →Turn a discovery call and site survey into a draft proposal with hardware, licensing and labor lines, so a vCIO or account manager reviews pricing instead of building the quote from scratch.
See the workflow →Pull ticket, patch, backup and license data into a consistent QBR pack per client, ready for the account manager to add commentary and recommendations before the meeting.
See the workflow →Track agreement end dates, Microsoft 365 commitments, warranty expirations and satisfaction signals so account managers see at-risk clients and renewal conversations months ahead, not days.
See the workflow →Let techs ask plain questions of your own runbooks, client documentation and past ticket resolutions, with answers that cite the source and respect who is allowed to see what.
See the workflow →Review the PSA, RMM, security, backup and documentation tools you run internally and resell, find overlap and unused licenses, and decide what to consolidate before the next renewal.
See the workflow →Make sure every open project quote and hardware quote gets a timely, specific follow-up, and that stale quotes are closed out or requoted when distributor pricing changes.
See the workflow →Give owners and service managers one view of MRR, effective hourly rate, SLA attainment, utilization and agreement profitability without exporting PSA reports into spreadsheets every week.
See the workflow →How we deliver this: AI automation for small business or fractional CTO leadership, scoped in writing and run over 90 days. See pricing or the sample scope.
Need someone to own systems, vendors and data policy too? See fractional CIO.
We start with what you already pay for. New tools have to earn their place.
MSPs hold privileged access to many client environments at once, so any AI or automation touching tickets, documentation or RMM data needs strict scoping. We would keep credentials and secrets out of AI prompts entirely, use tenant-level permissions, and log what automations can read and change. Clients in healthcare, finance or defense may bring HIPAA business associate terms, the FTC Safeguards Rule or CMMC expectations into your contracts. Cyber insurance questionnaires increasingly ask about these controls too. We flag those obligations; your counsel interprets them.
General information, not legal advice.
Defaults are illustrative for IT managed service providers (new managed clients per month). Change them to your numbers.
a month in staff time, before any lost sales
Illustration only, not a forecast or guarantee. Recovered staff time becomes a cash saving only if spending actually declines or the time goes into paid work. Tool costs are an assumption; we replace every number here with yours before recommending a scope.
RMM scripting automates client endpoints. The workflows that hurt margin are usually internal: dispatch, quoting, QBR assembly, renewals and agreement review. Those cross the PSA, quoting tool, accounting and email, and they need someone accountable for choosing the change, building it and getting service managers to adopt it. That is the gap a fractional lead fills while your senior techs stay on billable work.
That is not the goal we would set. A typical first step is to have the system suggest ticket type, priority and assignment while the dispatcher confirms. Over time the dispatcher spends less time reading noise and more time on escalations, scheduling and client communication. We would measure misroutes and time to first response so you can judge whether the suggestions are good enough to trust.
We would work with whatever you run, most commonly ConnectWise PSA, Autotask or HaloPSA, plus the quoting, documentation and RMM tools around them. Each has an API and its own workflow rules. Sometimes the best fix is a board or workflow rule change inside the PSA itself, which costs nothing extra and is easier to maintain than a new integration.
Credentials stay in your documentation platform and never go into AI prompts or third-party automation tools. We would scope each automation to the minimum data it needs, prefer tools with clear data processing terms, and keep an access log. For clients under HIPAA or CMMC we would review contract obligations with you before any data leaves your PSA.
Lead plus delivery is $5,000 per month over an initial 90 days, with a written scope before kickoff. Tool subscriptions and any major custom build are budgeted separately. For an MSP, one retained managed client or one repriced unprofitable agreement can cover a meaningful part of that, but we would build the business case from your own numbers before you commit.
In 30 minutes we look at one recurring workflow, what it costs you today and whether there is a credible case to improve it. If there is not, we will say so.
30 minutes with Phil or Martin. No technical brief, no pitch deck. Phil or Martin replies personally, usually within one business day.