Per-device or per-site pricing: which works better for an MSP with small clients?
For small clients, a model where one sensor covers a whole site usually works better, because per-endpoint pricing grows with every PC and phone and can exceed what the client pays you. Look at your client book: count the devices per client and the number of sites, and price both models for your five most typical clients before you choose a vendor. With NetSenX the unit is the device, but a device is a host running the agent, and one agent on a SPANSPAN: switch port analyser. A switch setting that sends a copy of network traffic to one port, where a sensor can watch it. or TAPTAP: test access point. A small device that copies the traffic on a network cable for a sensor to watch. port counts as one device for the whole segment it watches. A typical small office is therefore one or a few devices, which may fit the Free plan's 3 devices or the Starter plan at €49 per month.
Read next
Related questions
- How can an MSP monitor very small clients profitably?
- Can MSP clients start on the Free plan and upgrade later?
- Which security stack suits an MSP with many small clients?
- How can an MSP turn security monitoring into a recurring service?
- How can an MSP discover all devices on a new client's network, and how quickly?
Terms used here
- SPAN (switch port analyser)
- A switch setting that sends a copy of network traffic to one port, where a sensor can watch it.
- TAP (test access point)
- A small device that copies the traffic on a network cable for a sensor to watch.