The Hidden Compounding Problem
Every managed service provider knows the pitch: "Just $X per device per month." It sounds clean. It scales with your client base. In theory, it aligns vendor incentives with your growth.
In practice, it does something else. It turns your monitoring cost into a variable that compounds against you every time you win a new client.
The problem isn't the per-device price in isolation — it's that device counts don't grow linearly with revenue. A single mid-market client adds 80-150 endpoints at once. A healthcare client adds servers, workstations, printers, network gear, and medical devices simultaneously. Meanwhile, your per-device bill grows with every one of them, whether those devices generate a single incident or none at all.
The structural mismatch: Per-device pricing charges you based on what you monitor, not what you resolve. You pay for every dormant workstation, every printer that never alerts, every server that runs clean for 18 months. Your bill grows with enrollment, not with value.
For MSPs managing 50-100 devices across a handful of clients, this isn't a crisis. The math is tolerable. But once you cross 200 devices — and most growing MSPs do within their second year — per-device pricing starts eating into margins in ways that are hard to see until you run the numbers.
The Math at 100, 200, and 500 Devices
Let's be specific. The industry average for per-device monitoring sits between $3–$8 per endpoint per month for mid-tier RMM and monitoring tools. Premium platforms push $10–15 for full-stack coverage. We'll use a conservative $5/device for this analysis.
100 devices × $5
200 devices × $5
500 devices × $5
Those numbers look manageable until you factor in what they represent as a percentage of your service delivery cost — and how they shift with realistic device-to-revenue ratios.
| Device Count | Monthly Cost @ $5/device |
Monthly Cost @ $8/device |
Annual Spend | Trend |
|---|---|---|---|---|
| 100 devices | $500 | $800 | $6,000–$9,600 | Manageable |
| 200 devices | $1,000 | $1,600 | $12,000–$19,200 | Tight margins |
| 350 devices | $1,750 | $2,800 | $21,000–$33,600 | Margin pressure |
| 500 devices | $2,500 | $4,000 | $30,000–$48,000 | Eroding margins |
Notice what happens between 100 and 500 devices: your monitoring spend grows 5x. Your revenue from those clients likely hasn't grown 5x. The per-device model is a cost structure that fights your growth.
The Device Mix Problem
Real-world MSP environments aren't just workstations. A 150-device client might include:
- 80 user workstations (medium alert density)
- 12 servers (high monitoring value)
- 30 network devices — switches, firewalls, APs (low alert density)
- 20 printers and peripherals (very low alert density)
- 8 conference room systems (almost zero alert density)
Under per-device pricing, all 150 endpoints cost the same. You're paying the same rate to watch a printer as you are to monitor a domain controller. The vendor's revenue is identical whether those 150 devices generate 200 incidents or zero.
The utilization reality: Industry data consistently shows that 60-70% of monitored endpoints generate fewer than 2 actionable alerts per month. Under per-device pricing, you're paying full rate for devices that contribute almost nothing to your workload — and nothing to your billable time.
Real-World Scenarios: Three MSP Profiles
Profile 1: The Growing Regional MSP (180 devices)
You have 6 clients, mostly professional services firms. 180 endpoints total. At $6/device, you're paying $1,080/month for monitoring alone. Your average monthly service contract per client is $800. Monitoring alone is eating 22% of one client's contract value before you've dispatched a single tech.
You just won a new client: a 45-person law firm with 60 devices. Great news — except your monitoring bill jumps to $1,440/month before you've invoiced them once.
Profile 2: The Mid-Market MSP (300 devices)
Eight clients, mix of SMB and one enterprise account. At $7/device, $2,100/month. Your enterprise client added a branch office last quarter — 40 new devices. Your monitoring bill absorbed a quiet $280/month increase without anyone approving it. That's $3,360 per year that appeared without a purchase order.
The invisible cost creep: Per-device billing grows automatically when clients add machines. There's no renewal moment, no contract amendment, no signature. Devices appear, costs increase. Most MSP operators find these increases months later when they run a cost audit.
Profile 3: The Scaling MSP (500+ devices)
You're running a real operation. 15+ clients, dedicated NOC, maybe a junior tech handling first-line triage. At $7/device across 500 endpoints, you're paying $3,500/month — $42,000/year — just in monitoring tool costs. That's a full-time junior tech salary that's going to a vendor instead of growing your team.
At this scale, per-device pricing isn't an inconvenience. It's a structural tax on your growth that compounds every quarter.
The Flat-Rate Alternative: How the Math Changes
Flat-rate monitoring — one fixed monthly cost regardless of device count — inverts the economics entirely. Your monitoring cost becomes predictable. It doesn't compound when you win clients. It doesn't create invisible cost creep.
More importantly: flat-rate pricing aligns vendor incentives with yours. When the vendor charges per device, they benefit from you adding more endpoints. When the vendor charges a flat rate, they're incentivized to make monitoring efficient — fewer alerts, better resolution, less overhead for your team — because their revenue isn't tied to your device count.
Per-Device vs. Flat-Rate: Side-by-Side
| Per-Device Pricing | Flat-Rate Pricing | |
|---|---|---|
| Cost predictability | ✗ Varies with device count | ✓ Fixed monthly cost |
| Cost when winning new clients | ✗ Immediate cost increase | ✓ No change |
| Incentive alignment | ✗ Vendor benefits from more devices | ✓ Vendor incentivized to be efficient |
| Cost at 100 devices | $500–$800/mo | Comparable or lower |
| Cost at 300 devices | $1,500–$2,400/mo | Same fixed rate |
| Cost at 500 devices | $2,500–$4,000/mo | Same fixed rate |
| Budgeting complexity | ✗ Requires device count forecasting | ✓ One line item, no guesswork |
| Impact on margins at scale | ✗ Margins compress as you grow | ✓ Margins improve as you grow |
| Contract renewal friction | ~ Renegotiate as devices grow | ✓ Fixed rate, no renegotiation |
The crossover point — where flat-rate pricing becomes materially cheaper — typically happens around 150-200 devices. Below that, the cost difference is modest. Above that, the savings compound with every device you add.
How to Evaluate Any Monitoring Pricing Model
Before signing (or renewing) a monitoring contract, run four checks:
Project your device count 18 months out. If you're at 200 devices today and expect to reach 350 in 18 months, price the contract at 350 devices. Most MSPs underestimate device growth by 40-60% when evaluating per-device contracts. The quote you're looking at is not the bill you'll be paying in 18 months.
Calculate cost per alert generated, not cost per device. Pull 90 days of alert data. How many actionable alerts did your last 100 enrolled devices generate? Divide your monthly monitoring cost by that number. Per-device pricing often produces a cost-per-alert that's 3-5x higher than expected once you account for low-density devices.
Audit the auto-grow clauses. Per-device contracts typically auto-enroll new devices without requiring approval. Find the clause. Understand how device discovery works and whether you're billed immediately on discovery or at the next invoice cycle. Invisible cost creep is a contracts problem before it's a billing problem.
Model your monitoring cost as a percentage of revenue at 2x your current size. If you doubled your device count today, what would monitoring cost as a share of your MSP revenue? If that number is uncomfortable now, it'll be worse at actual 2x scale — because you'll be adding clients and overhead simultaneously.
The Vendor's Incentive Problem
There's a less-discussed issue with per-device pricing that has nothing to do with your cost structure: it gives monitoring vendors no incentive to reduce noise.
A vendor charging per device earns the same revenue whether your environment generates 50 alerts a month or 5,000. Alert quality doesn't affect their billing. Alert volume doesn't affect their billing. The number of false positives your team has to review doesn't affect their billing.
You're essentially paying a flat fee to enroll a device in a system that has no financial stake in whether that system helps you or overwhelms you. The vendor's growth model is enrollment growth, not outcome quality.
This is why the most aggressive alert-reduction features — automated deduplication, AI-driven threshold tuning, cross-device correlation — tend to appear in flat-rate products first. When the vendor's revenue is decoupled from device count, they're actually incentivized to make your environment quieter. Fewer false positives means lower support load for them. Better automation means your team stays on the platform longer.
Align incentives, not just costs. The best vendor relationship isn't one where both sides win at the same moment — it's one where both sides win from the same outcome. Flat-rate pricing creates that. Per-device pricing creates the opposite: the vendor profits from enrollment regardless of whether you're getting value.
What to Look for in a Flat-Rate Monitoring Model
Not all flat-rate pricing is structured the same. When evaluating options, look for:
- Tier clarity: Does the flat rate apply to all devices, or does it tier by device type (server vs. workstation vs. network)? Tiered flat rates can recreate the per-device problem for specific device categories.
- Contract flexibility: Can you scale up mid-contract without penalty? Can you scale down if a client churns? Flat-rate pricing with punitive scale-down clauses trades one kind of cost trap for another.
- Feature parity: Does the flat-rate tier include automated response, not just monitoring? Monitoring-only flat rates still require you to pay for remediation separately — often per-incident, which reintroduces variable pricing at the resolution layer.
- Transparent device limits: Is there a hard device cap, or is it truly unlimited within the tier? Some flat-rate products enforce a cap and revert to per-device above it — defeating the purpose at scale.
The Bottom Line for MSP Owners
Per-device pricing isn't inherently predatory — it's a legacy model built when MSPs were smaller and monitoring was simpler. At 50 devices, it's roughly fair. At 300 devices, you're subsidizing low-density endpoints with the same budget you spend on your most critical servers. At 500+ devices, you're paying a recurring tax that grows automatically with your success.
The MSP business model scales on margin, not revenue. Every dollar of fixed cost you eliminate at 200 devices is a dollar of margin you keep at 500. If your monitoring cost doesn't grow when your device count does, your model becomes more profitable at scale instead of less.
That's the case for flat-rate monitoring — not as a philosophical preference, but as a numbers decision.