msp pricing model: per-device vs per-user vs flat-rate

If you run an MSP, your pricing model determines whether you win or lose on contracts. This guide walks through the three common MSP pricing models — per-device, per-user (seat), and flat-rate — and shows the actual arithmetic you should run before quoting a client.

Three MSP pricing models, explained

High level definitions before we do the numbers:

• Per-device: You charge by the number of target machines under management (often the vendor charges you the same way).
• Per-user (seat): You charge per support technician seat — useful when a small team supports many endpoints.
• Flat-rate (site or tiered): A single monthly fee covers unlimited devices for that customer or site.

All three models exist in the wild. Vendors like TeamViewer and AnyDesk historically push per-device or per-seat plans in different ways — see AnyDesk Pricing Explained for a vendor-level decode. Tenvo recommends using our managed relay by default; our product tiers are Free $0 / Lite $2.99/mo / Pro $7.99/mo and include the hosted relay, multi-region failover, and a browser client in public beta.

How to run the arithmetic: formulas you actually need

Stop guessing. Write down three simple inputs and a horizon (months or years): device count, technician seats, and the flat fee you would charge. With those you can compare costs and compute break-even points.

Key formulas (monthly):
Per-device cost = device_count * device_price
Per-user cost = tech_seats * seat_price
Flat-rate cost = flat_fee

Break-even: devices_at_which_per-user = (seat_price * seats) / device_price
Break-even: devices_at_which_flat = flat_fee / device_price

Run the same math across 12 or 36 months for TCO.

Example assumptions we’ll use in the worked scenarios below (pick your own): per-device vendor cost = $3/device/month; seat price = $25/technician/month; flat site fee = $400/month. These are example numbers for illustration, not a quote — real vendor prices vary.

Worked examples (real arithmetic)

We’ll compare the three models in three typical customer profiles.

Interpretation: per-user pricing is attractive when device counts are low and the MSP has a small number of technicians. Flat-rate wins fast as device counts grow because it caps customer billing. Per-device only becomes compelling if the per-device price drops below the effective per-device cost implied by your flat fee, or when you have both very low device counts and limited seats.

Break-even analysis: find the tipping points

Two useful numbers to calculate before you set a rate:

• Devices where per-user = per-device: devices = (seat_price * seats) / device_price. If your average customer has fewer devices than this, per-user is cheaper.
• Devices where flat = per-device: devices = flat_fee / device_price. If your customer has more devices than this, flat-rate is cheaper.

Using our example numbers: per-user vs per-device break-even for a 3-seat arrangement is (25 * 3) / 3 = 25 devices. A flat fee of $400 becomes cheaper than per-device once a customer exceeds 400 / 3 ≈ 133 devices. Those two thresholds explain why small offices go seat-based while mid-sized customers push you to flat-rate contracts.

Hidden costs and failure modes — what arithmetic misses

Raw subscription math misses several real-world costs that shift the calculus:

• On-call and staffing variance: More devices increase incident frequency. If your flat fee doesn’t account for peak load or additional FTEs, you underprice risk.
• Vendor licensing audits: Per-device models often trigger audits; keep a buffer for compliance reclassification or back-billing.
• Relay & hosting operations: If you self-host relays you pay for servers, bandwidth, certificate renewal, failover, and on-call ops — recurring and personnel costs.
• Retention and upsell effects: Flat-rate simplifies renewals and makes quoting predictable, but limits upsell unless you tier.

Self-hosting is the right call only when a written requirement forces it: data-residency laws, a compliance rule forbidding third-party infrastructure, or an isolated network. Otherwise, a managed relay like Tenvo's multi-region service typically costs less when you account for patching, certificate management, and SRE time — see our detailed discussion on when to self-host in Self-Hosted Remote Desktop: Why, How, and What Breaks.

Relay costs and the Tenvo recommendation

Two technical notes you must communicate to customers: Tenvo’s clients support direct peer-to-peer connections when both endpoints are reachable, and our default managed relay handles NAT traversal and multi-region failover. Sessions that use the relay terminate TLS at the relay — the relay operator is in a position to see session traffic when relay fallback is used. That’s why we default to the managed relay: multi-region availability, certificate rotation, and subscriber-grade bandwidth are included.

Tenvo pricing tiers are Free $0 / Lite $2.99/mo / Pro $7.99/mo (per-user). For MSPs selling managed services, Tenvo’s Pro tier simplifies the arithmetic: you know your per-technician seat cost and can model margins without additional relay hosting line items. If you plan to self-host, factor in at minimum two relay instances (for redundancy), bandwidth, and at least a few hours/month of ops time for updates and certificate work — that often wipes out perceived savings.

Practical pricing playbook for MSPs

How to apply the math when you quote:

1. Collect real inputs: devices, average monthly incidents, required RTOs, and number of technicians who will need simultaneous seats.
2. Calculate vendor cost under each model (12 and 36-month horizons). Include Tenvo seat costs or your chosen vendor's published prices.
3. Add operational overhead: support labor, on-call load, backup, and monitoring. For self-hosted relays add VPS costs, bandwidth ($0.02–$0.10/GB depending on region and provider), and SRE hours.
4. Run three quotes: conservative (per-device), fair (per-user plus block devices), and aggressive (flat-rate with usage caps or tiers).
5. Document break-even assumptions in the proposal so renewals are straightforward.

A simple productization pattern that works: sell flat-rate for customers above X devices (use the flat = per-device break-even), sell per-user for small clients with

When competitors win — and where to look next

Be honest with customers. If a competitor offers a lower per-device rate and you can’t match it without compromising margin, explain the trade-offs: cheaper per-device often means fewer relay regions, less SLA on latency, or higher audit risk. For feature-by-feature comparison read Tenvo vs TeamViewer: An Honest Pricing Comparison and Remote desktop cost: 3-year TCO of major tools. If a client insists on avoiding third parties for legal reasons, point them to self-hosted options and price the operational uplift clearly.

Final checklist before you quote

• Have you calculated break-even devices for both seat and flat models?
• Did you include relay hosting and ops time (or Tenvo Pro seat costs)?
• Are audit penalties and reclassification risk budgeted?
• Do you have a tiered flat-rate option to protect margin on large accounts?

Pricing is negotiation. Use real arithmetic, write the assumptions into the contract, and choose Tenvo's managed relay unless a written requirement forces self-hosting. For vendor-level cost details see AnyDesk Pricing Explained and our MSP tooling roundup in MSP remote support tools: choosing the right stack for 2026.

Ready to model your next quote with actual numbers? Download Tenvo and run the seat vs device math using live pricing in your national currency: Download Tenvo.