AI Studio
Let's Talk
Stacks AI Studio / IT Services Companies and MSPs
AI for IT Services Companies and MSPs
"I feel behind on AI, and there is no chance I can catch up." If that is the sentence in your head, you are exactly who I work with. I am not selling software or theory-based advice. I run my own ten person managed services business on Claude, I know the value it adds every week, and now I help owners do the same inside IT services companies and MSPs like yours: your team trained, jobs automated, hours saved. Saying yes to starting puts you ahead of many of your competitors.
Experience, Not Theory
That is our first four automations at Stacks, across a ten person team. We took on more clients, and gross margin went from 26% to 56% in twelve months. AI was not the only driver. It was the biggest one. It also set a new standard for what my team sends out: the same bar for research, formatting, and finish on everything that leaves the building, no shortcuts.
Casey Templeton, Founder of Stacks. Nashville.
"In one week I went from a two-hour session with Casey to a brand new marketing site and firing the marketing firm I'd used for two years. If Casey wants to work with you, don't be a dummy. Just do it."
The Week
Your Week. I Know It.
Five jobs that never make the board. This is the work an automation goes after first.
Ticket notes get written in five words. The next tech works the same problem from scratch.
The QBR deck gets built the night before. A year of ticket history turns into three slides.
Client documentation drifts the week after onboarding. Nobody finds out until a tech is on site at midnight.
A new client signs on Friday. The onboarding runbook gets rebuilt from the last one by hand.
The owner rebuilds the same monthly numbers. MRR, project revenue, and hours get retyped from three exports.
The desk keeps running while a seat sits open, and the queue does not wait for a new tech.
Source: U.S. Bureau of Labor Statistics, August 2025.
The First Step
Two Sessions. Two Hours Each.
For most IT services companies and MSPs, this is the first step. Homework first, then two sessions, two hours each. In person if you are near Nashville, or over Zoom. $1,950.
For the math: one person at $25 an hour who gets two hours a week back is worth about $2,600 a year. If the first automation does that for one employee, it pays for itself with room to spare. And if after our first session you do not see a job worth automating, you pay nothing.
An automation is a repeated piece of work you teach Claude once. Your team runs it every day, you own it and tune it, and it carries the work to 80 percent so your people finish the 20 that needs their judgment.
"Casey taught me how to actually put AI to work. I generate quotes faster, my workflow is smoother, and I'm making more money because of it. One of the best investments I've made in my business."
01
Homework
Before we ever meet, you pull real examples of the work that eats your week: actual documents, actual messages, nothing cleaned up for me.
02
Session One
Two hours. We map how your company actually runs, get Claude set up for your team, and train you on how to operate it.
03
Session Two
Two hours. We start building your first automations and put together the training your team needs to run Claude every day.
04
What You Leave With
Claude running for your team, your people trained on it, and one job automated and in use.
Five Automations We Could Build In Your Company.
One page, no obligation. Proof of what we could build together, before we ever talk.
One email with the PDF. No newsletter, no drip campaign.
2024 median annual pay for computer support specialists.
Source: U.S. Bureau of Labor Statistics, August 2025.
Where a client carries HIPAA or CMMC obligations, the data path is written down and you approve it before any automation runs.
The Stack
Claude Sits In The Middle.
It works with the tools you already run. It reads from your PSA, your monitoring, and your documentation, and writes back where it can.
Start with one connection, not all of them. The first automation usually needs one export from your PSA, and that is the whole first step. Once it earns its keep, the next system comes in, then the one after that. Every automation gets sharper as it goes, because Claude can finally see across the whole client base instead of one console at a time.
The Numbers
The Numbers MSP Owners Are Seeing.
That feeling of being behind is not in your head. Your clients got there before the policy did, and most of the questions your MSP fields are not technical.
US small businesses using generative AI
Source: U.S. Chamber of Commerce, August 2025.
Surveyed SMBs with documented AI policies
Source: Pax8, reported by Channel Dive, July 2026.
Questions
Questions, Answered.
I feel like I am already behind on AI. Is it too late?
No, and you are not as far behind as you think. The owners who feel furthest behind often move fastest once they start, because they have not spent a year on tools that did not stick. You do not need a strategy, a budget cycle, or a technical person on staff. You need four hours and one job that is costing you time every week. That is the whole first step.
Will this replace my staff?
No, and that is the whole design. An automation carries a job to 80 percent quickly and your engineer takes the final 20 percent over the finish line. Efficiency goes up for everyone, the company grows without the headcount it used to need, margins grow with it, and your people spend their time on client work instead of writing.
Will it work with the software we already run?
Usually, whether that is ConnectWise, Autotask, HaloPSA, Syncro, or IT Glue. Some systems give me an API, some give me a scheduled export, and a few give me nothing but a screen to copy from. I tell you which one you have before I scope anything.
Does any of this touch production or alerts?
No. Everything I build is admin. No automation logs into a client environment, runs a script, or acts on an alert. Remediation stays with your engineers and your change process. I work on the writing, the reporting, and the documentation around the work.
What happens to our clients' data?
You approve the data path before any automation runs. Many of these jobs run on ticket text and your own documentation, and where a client name is not needed I leave it out. Where it is needed, the data path gets written down and you approve it first. You answer that question for your own clients, and it gets answered here the same way.
We sell IT. Why would we bring in an outside firm?
Because the hard part is documentation, not code. Your team can wire up an API faster than I can. What stalls is writing down how your own company runs, which is the one thing nobody bills for. I do that with your people in the room, then hand it over.
How long before we see something working?
The first automation runs in weeks, not quarters. The two sessions scope it, I build it against your real ticket history, and your team uses it while I refine it. One automation in production beats five in a plan.
Who owns what you build?
You own the automations and the documentation. They live in your account, written in plain language, so your team can read them and change them. If you stop working with me, nothing walks out the door.
What if we get to the end and nothing is worth automating?
Then you pay nothing. If after our first session you do not see a job worth automating, the engagement ends there and there is no charge. The first session either surfaces a job worth the money or it does not, and that risk is mine, not yours.
Why $1,950?
Because the format is small on purpose. Homework, two working sessions of two hours each, and the setup work around them. For the math: one person at $25 an hour who gets two hours a week back is worth about $2,600 a year. If the first automation does that for one employee, it has paid for itself with room to spare. Every number in that sentence is yours to check.
Who You Will Be Working With
Casey Templeton.
Founder of Stacks, a ten person business in Nashville that runs on Claude. Both sessions are with him directly, and every message from this page lands in his inbox, not a queue.
Start Here
Start With A Conversation Between Two Small Business Owners.
Tell me about your MSP. I take on two or three of these engagements a month. Every message comes to me and I answer it myself. The first conversation costs nothing.
Book A 15 Minute Call"A fear of not understanding AI had kept me from diving in. Casey's coaching changed that. It opened my eyes to a sea of possibilities and left me more confident to explore. Come open-minded, and see where your imagination takes you."
I reply to every message. No newsletter, no drip campaign.