In January of this year, NinjaOne sent a survey to all MSP customers worldwide asking them to quantify the amount of time they were saving using NinjaRMM versus their prior RMM solution. Normally we reserve our blogs for educational topics, but the results of the survey were so compelling, we had to share.
We sent 11 questions ranging from how long it takes our MSP customers to implement NinjaRMM, to whether their mean time to resolution (MTTR) had been reduced. We got over 250 responses from 6 different countries and were frankly surprised (but delighted) by the results. The complete report is available here, but we wanted to share a few key findings and a sample of verbatim comments to give you the highlights.
NinjaRMM Deployment. The first question we asked was how long it took our MSP customers to be operational with NinjaRMM.
- 58% were up and running in under one week
- 92% were operational in under one month
That’s the kind of time to value our customers deserve!
Technician Onboarding. We also asked how long it took to fully train a new technician on NinjaRMM.
- 89% of respondents said it took them under 6 hours to onboard new techs
- 66% had new techs full trained on NinjaRMM in under 3 hours
That’s right, under 3 hours. As one MSPs said, “The quickness and intuitiveness of Ninja is very nice. Easy to train new techs, easy to handle quick service calls even without having to login to the machine. Easy to pull a lot of different kinds of reporting.”
Tech to Endpoint Ratios. And speaking of servicing more customers, we were astounded by this finding.
- 62% of respondents say their techs are each now able to manage more than 100 additional endpoints, as compared to their previous RMM
Extending existing staff to easily handle more clients and endpoints is a key to MSP growth. Almost a third of the respondents named easy automation as at least one of their favorite efficiency-boosting NinjaOne capabilities enabling this kind of technician-to-endpoint ratio growth.
Patching. Patching vulnerabilities can be a huge time sink, but with automation through policies and automation scripts, our MSPs were able to shave off many hours, which is probably why it was named by a good percentage of our respondents as their favorite feature.
- 62% of respondents said they now spend up to 10 fewer hours per week on patching
- 32% said they’re saving over 10 hours per week
Want to learn more? Download our full survey report here!