How to cut MSP software costs without weakening the stack

Why the software bill outgrows revenue

Vendor pricing is built on units: per endpoint, per technician seat, per mailbox, per user, per tenant. Each looks reasonable on its own. The trouble is that the units do not move with your revenue.

• Per-endpoint pricing grows with the client’s device count, while many MSP agreements are priced per user or as a flat fee.
• Per-technician seats are bought for everyone who might need access, then never removed when people leave or change roles.
• Per-mailbox pricing punishes shared mailboxes, service accounts and clients that keep departed staff mailboxes for records.
• Minimum commitments and annual true-ups mean you pay for the peak, and keep paying for it after a client leaves.
• Overlap accumulates: a second backup product for one client’s special case, two remote tools after a technician preference, an RMM’s bundled feature duplicating a standalone one.

Run a stack audit

This takes an afternoon with the accounts payable export and the admin consoles. Do it before any vendor conversation.

1. List every recurring software charge for the last twelve months, from the card statements and invoices, not from memory. Include the small ones.
2. Record the pricing unit and quantity for each. Per what, and how many are you paying for today.
3. Record actual use. Seats with a login in the last 30 days; agents that have checked in this week; mailboxes that received mail.
4. Compute cost per managed endpoint and per client. This is the number to compare with what each client pays you.
5. Mark overlap. Any two products that do the same job for any client.
6. Add the renewal date and the notice period. Many contracts auto-renew and require 30 to 90 days’ notice.
7. Rank by annual cost multiplied by how easily it could change. Unused seats are first; core platforms are last.

Match the pricing unit to how you grow

Once the waste is out, the next lever is the pricing unit itself. The right unit is the one that tracks what you are paid for. A worked example, with the assumptions stated so you can substitute your own numbers:

Email security: per mailbox or per domain

Suppose a per-mailbox product costs p per mailbox per month, and a per-domain product costs d per protected domain per month. For a given domain, per-domain pricing is the cheaper of the two once the domain has more than d ÷ p mailboxes.

The per-mailbox prices are illustrative assumptions, not any vendor’s list price. The $39 figure is the published entry rate for MailThreatZero (up to 250 receiving addresses per protected domain), checked on 2026-10-10. MailThreatZero is operated by mspreboot.com.

The reverse is true too: a client with many small domains and few mailboxes is cheaper per-mailbox. Run your own client list through both, rather than picking a model on principle.

Documentation: per technician seat or self-hosted

Per-seat documentation pricing creates a quiet incentive not to give junior technicians a login, which is how documentation stops being written. Compare seats × seat price against hosting plus the admin time described in the self-hosting cost checklist.ClientSt0r, an MIT-licensed documentation platform by the developer behind this site, is one self-hosted option with no seat count. The answer differs by team size and by whether anyone on the team wants to run a server.

Vulnerability and exposure tools: per asset, per finding, or per environment

Tools priced per scanned asset can make you hesitate to scan everything, which defeats the purpose. Ask how the price changes when discovery finds more than you expected. Exploit Hound, built by the same developer as this site, publishes per-environment plans for that reason; see its pricing page for current figures.

Where the alternatives are

Once you know what you are paying for and how it is priced, alternatives fall into three groups:

• Same category, different pricing unit. Usually the least disruptive change; the workflow stays the same.
• Open-source or self-hosted. Documentation, remote support, backup management, firewall management and PSA all have credible options now. The open-source MSP software guide covers which, and how to count the operational cost.
• Consolidation. Using a feature you already pay for in another product. Check that it is genuinely equivalent, not a checkbox.

What not to cut

• Backups you have not test-restored recently. If the replacement is cheaper but nobody has restored from it, it is not yet a replacement.
• Security tooling without a like-for-like replacement running first. A gap of a month is a real exposure.
• The hours of whoever knows the stack. A migration that saves licence fees but consumes your best technician for a quarter may not save anything.
• Anything a client contract names explicitly. Check the agreements before you change a tool the client was promised.

Use the renewal before you migrate

The audit data is negotiating leverage on its own. A vendor shown actual usage, a cleaned-up seat count, and a credible alternative with a date attached will often move on price or terms. Ask about co-terming renewals, removing minimums, and dropping seats at the next renewal rather than at term end. Migrate where the numbers still do not work after that conversation.