# 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 SPAN or TAP 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.

FAQ: [MSPs and MSSPs](https://netsenx.com/en/faq/msp) · https://netsenx.com/en/faq/per-device-or-per-site-pricing-for-an-msp

## Read next

- https://netsenx.com/en/problems-we-solve
- https://netsenx.com/en/partners

## Related questions

- [How can an MSP monitor very small clients profitably?](https://netsenx.com/en/faq/how-can-an-msp-monitor-very-small-clients-profitably)
- [Can MSP clients start on the Free plan and upgrade later?](https://netsenx.com/en/faq/can-msp-clients-start-on-the-free-plan-and-upgrade-later)
- [Which security stack suits an MSP with many small clients?](https://netsenx.com/en/faq/which-security-stack-suits-an-msp-with-many-small-clients)
- [How can an MSP turn security monitoring into a recurring service?](https://netsenx.com/en/faq/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?](https://netsenx.com/en/faq/how-can-an-msp-discover-all-devices-on-a-new-clients-network)
