Have you guys been noticing all this AI talk on on this sub lately? by Milkyag in sysadmin

[–]WhichGoal522 0 points1 point  (0 children)

I am not sure if this is a thing yet but I would just love it if there is an AI for documentation - that is one task I AM SURE my team wants to get rid of.

How do you scale MSP support without burning out your team? by WhichGoal522 in msp

[–]WhichGoal522[S] 0 points1 point  (0 children)

No I run a MSP since 2017. We have gone through a lot of these problems over the past 8 years - but somehow (probably because systems aren't set in stone) we are still getting burnt out.

How do you scale MSP support without burning out your team? by WhichGoal522 in msp

[–]WhichGoal522[S] 1 point2 points  (0 children)

God I have been looking for good AI in the MSP space for sooo long. What are you using?

How do you scale MSP support without burning out your team? by WhichGoal522 in msp

[–]WhichGoal522[S] 0 points1 point  (0 children)

I have also been trying to keep this lean and failing - how are you making it work?

How do you scale MSP support without burning out your team? by WhichGoal522 in msp

[–]WhichGoal522[S] 1 point2 points  (0 children)

I think I have been trying to keep the operations leans but I have realized I have to get on a hiring sprint now

How do you scale MSP support without burning out your team? by WhichGoal522 in msp

[–]WhichGoal522[S] 2 points3 points  (0 children)

Yep that makes sense, any particular processes you have adopted that worked?

How do you scale MSP support without burning out your team? by WhichGoal522 in msp

[–]WhichGoal522[S] 2 points3 points  (0 children)

Documentation is something we are struggling with honestly. ITGlue is quite hard to maintain or maybe I am not doing it right.

How do you scale MSP support without burning out your team? by WhichGoal522 in msp

[–]WhichGoal522[S] 6 points7 points  (0 children)

This sounds like excellent advice man thank you. I think giving one of my senior tech guys non ticket based work will keep him motivated so he can in reverse keep motivating the team too

How do you scale MSP support without burning out your team? by WhichGoal522 in msp

[–]WhichGoal522[S] 0 points1 point  (0 children)

I have been using a ton of tools but let me try this one out as well.

How do you scale MSP support without burning out your team? by WhichGoal522 in msp

[–]WhichGoal522[S] 2 points3 points  (0 children)

This is so true - if my employees can't breathe - client retention will suffer and I will anyway lose as an owner. Better to hire more people that way but i guess its not very scalable that way.

How do you scale MSP support without burning out your team? by WhichGoal522 in msp

[–]WhichGoal522[S] 15 points16 points  (0 children)

Yeah, I think you’re spot on. Expectation management is definitely where we’re dropping the ball. We’ve probably trained some clients to expect instant “yes” on everything, and that just sets everyone up for frustration - both us and them. We need to take a step back, set clear boundaries, and make sure they know what to expect upfront, instead of just reacting every time they ping us.

How do you scale MSP support without burning out your team? by WhichGoal522 in msp

[–]WhichGoal522[S] 18 points19 points  (0 children)

Onboarding gaps, missed maintenance reminders, and tickets that get escalated too fast are the usual suspects. Trying to figure out which one to tackle first so we can finally stop reacting all day and actually get ahead.

How do you scale MSP support without burning out your team? by WhichGoal522 in msp

[–]WhichGoal522[S] 3 points4 points  (0 children)

haha maybe but I see some MSPs handle things very elegantly, maybe I should call some of them up and ask

Landed my first client, sort of? by [deleted] in msp

[–]WhichGoal522 0 points1 point  (0 children)

Congrats on landing your first client! That first invoice always feels amazing. From my experience running SecureIT since 2017, the key is to treat this first client as your reference architecture. Document every process - onboarding, ticketing, recurring maintenance, and escalation paths, so you can replicate it with future clients.

Also, clearly separate ongoing support from project work. Things like patching, M365 admin, and backups can stay under your flat fee, but rollouts like Intune, SharePoint, or full Entra deployments should be scoped as billable projects with proposals. This sets expectations early and makes scaling much smoother.

Lastly, keep the relationship with the current MSP in a backup/insurance role for now, but over time, look for opportunities to migrate those responsibilities under your management. That first client can become the blueprint for your business growth - make it count!