WHY MSP AI PRACTICES FAIL AFTER THE SALE
Your AI practice doesn't fail at the sale. It fails at day 90.
Schedule a CallLast week at IT Nation Connect 2026, I led a packed session on this exact topic. Every other AI session that week taught you how to build an AI service, price it, and launch it. Mine started after the client signs.
I asked the room one question. Who knows how many of the AI seats you resell got used last week? Most hands dropped. Then everyone scored their own practice on 8 questions. Most of the room landed at 0 to 2. The second biggest group scored 3 to 5. One person scored above 6.
Here's what I showed them, and the check you can run this week. If you'd rather work through it together, Schedule a Call.
Day one gets the attention. Day two gets the bill.
Day one is building the offer, pricing it, signing the client, and turning on seats. That's what the keynote stage covers.
Day two is supporting it, proving people use it, paying the usage bills, and keeping it at renewal. That's where your margin lives.
What day two looks like on the calendar
Day 30
The first tickets arrive. They say Outlook, Teams, and SharePoint. Not AI.
Day 90
Usage drops. The people who loved the demo stopped opening it.
Renewal
The client's CFO asks what the AI line buys them. You don't have a number.
Why nobody plans day two
Your owner wants AI revenue this quarter. Your clients want the tool connected by Friday. "Can you help me connect Claude to Office 365?" is a real request, but it isn't a scope. Both sides push you to day one. Nobody plans day two.
What 58,000 tagged tickets showed
28 MSPs tagged every AI related ticket from July 1 to September 30 and searched 90 days back for AI work they'd missed. Here's what they found.
- 5% of all tickets were AI related. Run 2,000 tickets a month and that's about 100 AI tickets you aren't counting.
- 70% of the AI tickets the search found were typed as something else. Email, Teams, SharePoint, How to.
- AI tickets took 40 minutes on average. Everything else took 27.
- 35% of resold AI seats had no activity in 30 days or more.
- 1 in 4 AI tickets involved a tool the MSP didn't sell.
Most AI tickets weren't broken AI either. Access and configuration made up 32%. Training and how to made up 28%. Source data problems were 18%, incorrect output 13%, and broken automation 9%. Each one needs a different fix, which is why one AI ticket type isn't enough on its own.
The five ways AI practices fail after the sale
Every failure has a name on the fix. Hold that thought.
1. Unused seats get cut at renewal
You sold 50 Copilot seats in the spring. A dozen people use it each week, and nobody pulls the report. The fix belongs to your vCIO. Pull usage every month and look at last activity per user. Give each team two or three real uses for their actual job. Shrink idle seats before the client asks.
2. AI work hides in other tickets
"Outlook is acting weird." It's Copilot. There was no AI type to pick, so it closes as Email, and your AI line looks more profitable than it is. The fix belongs to your service manager. Create an AI ticket type, tag from day one, and search 90 days back.
3. One engineer knows the custom build
Your best engineer built a custom agent. It breaks the week they're on vacation, and tickets wait for one person. The fix belongs to your tech lead. Name an owner and a backup for every build. Then give the backup one real failure to fix using only the notes.
4. Vendors bill by usage. You bill flat.
You charge per user per month. More of your upstream costs bill per credit, message, or token every quarter. Your busiest client, the one who loves AI most, earns you the least. The fix belongs to the owner. List every AI cost that rises with usage, then read your client agreements. Can you reprice before renewal? How much notice do you owe?
5. Clients bring their own AI to your desk
Staff use personal ChatGPT. Someone expensed a Claude plan. The questions still land on your desk, and you can't bill for them. The fix belongs to your vCIO. Flag every AI ticket "not sold by us," then put in writing which of those tools you support.
It's one problem showing up five ways
I posted these five on r/msp before the session. The best reply said it plainly: "Honestly your list sounds like one problem showing up five ways. Nobody decided who owns the thing before it went live."
They're right. Most AI goes live like this: sold, configured, invoiced, done. Before go live, it needs four things. One named owner, a person and not a team. A written definition of working, in hours saved or seats used weekly. A review date. And a second person on anything custom.
None of that takes a tool. It takes a decision before the invoice goes out.
One more thing. If users can't use the AI you sold, you aren't their partner. You're a liability. Train idle teams first. Cut seats second.
Run the Day Two Check
Score one point for every yes. Doesn't apply to you? Count it as a yes. Not sure? It's a no.
- A named person pulled usage on every AI seat you resell in the last 30 days.
- Every team using AI you resell got training on two or three uses for their job.
- Your PSA has an AI ticket type, and your techs use it.
- You know last month's AI support hours for each client.
- Every custom AI build has a backup who fixed it using only the notes.
- You have a list of every AI cost you pay that rises with usage.
- Your client agreements let you reprice AI before renewal.
- Your agreements say whether you support AI tools clients bought on their own.
0 to 2 means AI costs you money now and you can't see where. Start with the AI ticket type this week. 3 to 5 means the gaps show up at renewal, so fix your lowest area first. 6 to 8 means prove it with real numbers.
Then write a person's name, not a title, next to each of the four roles above. Download the one page handout with the check and the full 30 day plan.
If the check turned up gaps beyond AI, run the MSP Owner Reality Check or the Operational Maturity Assessment next.
Want help putting names on the plan? Schedule a Call.
FAQ
Does this apply if we haven't sold AI yet?
Yes. Your clients already use AI, and those tickets already land on your desk. Questions 3, 4, and 8 apply to every MSP. Start with the AI ticket type and the "not sold by us" flag.
How do I set up an AI ticket type in my PSA?
In ConnectWise PSA, use Type, Subtype, and Item on every client service board. Type is AI, subtypes match the five categories above, and Item is the tool. Autotask uses Issue Type and Sub Issue Type. HaloPSA uses ticket types and categories.
Why not just cut unused AI seats?
An unused seat is the easiest line for a CFO to cut, and once they cut it they start asking what else on your invoice goes unused. Idle seats usually mean an untrained team. Train first. If usage doesn't move, then shrink the seats before the client asks.
WHY MSP AI PRACTICES FAIL AFTER THE SALE
Your AI practice doesn't fail at the sale. It fails at day 90.
Schedule a Call