How MSPs provide their services



  • @mike-davis said in How MSPs provide their services:

    @minion-queen said in How MSPs provide their services:

    To be fair the MSP we were pitching in with might not have done a good job setting anything up so it could be because they didn't know what they were doing with it.

    Their is a fair amount of set up and tweaking to be done to make it work like you want it to. It took me a month of learning what it could do and the advantages of doing it one way or another to make all the decisions and set mine up.

    Today I finished building my first project proposal out of it. The client accepted, so now all the steps in the project turn in to tickets that I can take notes on and track time on. It's really cool.

    That's a lot of investment for a system like that. If you have hundreds of customers, it can make sense. But it takes a lot of customers to recoup the lost time into that system. It can work out well for a traditional MSP, but depends on large scale standardization to justify the investment.



  • @scottalanmiller said in How MSPs provide their services:

    That's a lot of investment for a system like that. If you have hundreds of customers, it can make sense. But it takes a lot of customers to recoup the lost time into that system. It can work out well for a traditional MSP, but depends on large scale standardization to justify the investment.

    I don't know about hundreds of customers. The number of end points might be more relevant. For me at about 10 MSP customers I can justify the investment. When you look at the time it takes to set up something like a zabbix server and maintaining a WSUS server vs not having to that helps make it worth it. Missed revenue because you didn't have a system in place to capture every minute hurts.



  • @mike-davis said in How MSPs provide their services:

    @scottalanmiller said in How MSPs provide their services:

    That's a lot of investment for a system like that. If you have hundreds of customers, it can make sense. But it takes a lot of customers to recoup the lost time into that system. It can work out well for a traditional MSP, but depends on large scale standardization to justify the investment.

    I don't know about hundreds of customers. The number of end points might be more relevant. For me at about 10 MSP customers I can justify the investment. When you look at the time it takes to set up something like a zabbix server and maintaining a WSUS server vs not having to that helps make it worth it. Missed revenue because you didn't have a system in place to capture every minute hurts.

    It would be a blend, I'm sure. A single customer with a million end points wouldn't make sense because you'd use more traditional tools in a single customer scenario. And a hundred with only one end point each wouldn't do it either. So some combination of enough end points for volume and enough customers for complexity put together.