RMM and patching

Remote monitoring and management (RMM) software installs an agent on every managed endpoint and gives a technician one console to patch operating systems and third-party applications, run scripts, deploy software, monitor for problems, and take remote control when something needs a human. Many RMMs also offer network discovery to find unmanaged devices on a client site, basic mobile device management, and backup as an add-on module. An RMM does not replace endpoint security; patching and antivirus are different jobs, and most MSPs run a dedicated EDR product alongside the RMM agent rather than relying on whatever the RMM bundles.

RMM pricing is per managed endpoint per month in almost every case, sometimes split into separate rates for workstations and servers since servers cost more to support. A few vendors price per technician instead, which suits MSPs who want unlimited endpoints under a flat seat count. Watch for minimum endpoint commitments and whether server and workstation agents are billed at the same rate, since server pricing can be several times the workstation rate.

Patch management is the core job: check how it handles both operating system and third-party application patching, and how patch failures are reported. Scripting depth, software deployment, monitoring and alerting thresholds, and automation policies determine how much manual work is left for a technician. Network discovery matters for finding devices an MSP does not yet manage, and mobile device management matters only if you support phones and tablets under the same contract. Reporting quality varies a lot between vendors and affects how easily a technician can prove work was done.

PSA integration is the connection that matters most: an RMM alert should open a PSA ticket automatically with the device and error detail already attached, rather than a technician re-typing what the alert said. Backup integration lets a backup job's failure show up as an RMM alert too, and third-party application patching reduces how many separate patching tools you need to run. Before buying, confirm the RMM has a native, maintained connector for your existing PSA rather than a generic webhook that someone has to build and support.

Ask about the contract term, whether pricing is locked for the term or can rise at renewal, what the minimum endpoint count is, and whether there is a separate fee to add mobile device management or backup later. Also ask what happens to historical monitoring data and scripts if you leave, since some of that configuration work does not export cleanly.

A small MSP with a modest, steady endpoint count usually wants the RMM with the simplest onboarding and the fewest optional modules to configure, since a smaller team has less time to build automation policies from scratch. A larger MSP managing thousands of endpoints across many clients typically needs deeper automation, role-based access for multiple technicians, and an RMM built to run reliably at that scale, and can justify the longer setup that comes with it.