If you run a 5-tech MSP, you don't pay for 5 seats. You pay for ~20.
That sounds wrong until you sit down and add it up. The PSA charges per agent. The RMM charges per endpoint. The marketing tool charges per contact. Time tracking charges per user. Every "per-seat" platform you add is sized to your headcount, not your revenue, not your client count, not the work you actually do — your headcount. And almost every platform an MSP touches uses some version of that model.
Here's a real-world breakdown for a 5-tech MSP managing 40 client orgs. Numbers are conservative; your mileage may vary depending on which tools you've picked.
The actual annual cost stack
| Tool | Pricing model | Annual cost |
|---|---|---|
| PSA (ConnectWise Manage) | 5 agents × ~$70/mo | $4,200 |
| RMM (NinjaOne) | ~700 endpoints × ~$2/mo | $16,800 |
| Time tracking (Harvest, Clockify Pro, etc.) | 5 users × ~$10/mo | $600 |
| Email marketing / client comms (HubSpot Starter) | 3,000 contacts | $2,160 |
| Reporting / dashboards (BrightGauge or similar) | 5 seats × ~$30/mo | $1,800 |
| Quote management (QuoteWerks, Quoter, etc.) | 3 sales seats × ~$50/mo | $1,800 |
| Custom dashboards (Power BI per-user) | 5 users × $10/mo | $600 |
| Total platform spend | $27,960/yr |
That's ~$5,600 per technician, per year in platform fees alone — and that's before any "growth tier" upgrades that get triggered when you cross arbitrary thresholds (101 users on HubSpot, 1,000 endpoints on RMM, etc.).
The kicker: every one of those tools is sized against your headcount or contact count, so each new hire (or each new client whose contacts you sync) directly increases your fixed cost — even if that tech or those contacts don't actually use every platform.
Why per-seat made sense for the vendors and not for you
Per-seat pricing was invented by SaaS companies in the 2010s as a clean way to bill SMB customers — a 50-person company pays 50 seats, a 100-person company pays 100. Two assumptions baked in:
- Each seat actually uses the tool roughly equally.
- The tool's value scales linearly with the user count.
Both assumptions break for MSPs.
Your "users" are technicians, but most platforms are used non-uniformly: only billing touches QuickBooks, only sales touches the quoting tool, only ops touches BrightGauge. Yet every per-seat tool charges as if every seat lives in it daily. That's why MSPs end up provisioning fewer seats than headcount, then trading one login between two techs — paying full fare for half the value.
The other assumption — "value scales with users" — is even more broken. Your fifth tech doesn't get more value from BrightGauge than your first; the dashboards are the same. But the price doubled.
The tools that don't follow per-seat pricing (and why)
The exceptions are interesting because they signal a different posture toward MSP customers. NinjaOne charges per endpoint, which is closer to "per managed asset" — it actually scales with the work the platform is doing, not the number of seats logging in to look at it. Pax8 and other distributors don't charge for the platform at all; they make their margin on the products you resell. Huntress charges per agent (endpoint) and per identity, not per MSP user.
You'll notice these are all platforms whose business model lines up with MSP economics: they make money when you grow, but in a way that's tied to the assets you're managing or the licenses you're reselling — not arbitrary "seats" that may or may not log in this month.
What the alternative looks like
The alternative isn't "throw away your per-seat tools." Most of them are genuinely good products and the lock-in to switch is high. The alternative is to consolidate the dashboard layer — the part where you're paying per-seat for a viewing experience — into something that doesn't have a per-seat model.
Take whatever your stack actually is — your RMM (NinjaOne, Datto, or whatever you run), your PSA (ConnectWise, HaloPSA, Freshdesk, or anything else), your accounting system (QuickBooks, Xero, Sage, or anything with an API), and your security/EDR (Huntress or otherwise). Those data sources are doing the actual work. The dashboards on top of them — the BrightGauges, Power BIs, custom Excel sheets, and "view-only" PSA seats — are all charging you per-seat for something that just renders the data your existing tools already store. A consolidation layer doesn't care which vendor you picked: if your tool exposes an API, we can connect it during your build.
That's the part you can flatten. A unified dashboard that reads from your existing tools (without adding a per-seat layer of its own) collapses 3-5 of the line items in the table above into one flat-fee subscription. For a 5-tech MSP that's typically $8,000-15,000/year recovered. For a 10-tech MSP it's closer to $20,000.
How we ended up at flat pricing
When we started building Morton Command Center, the very first decision was the pricing model. The MSP we run it for (IT Pro Source) had been bitten enough times by per-seat surprise increases — every November, "just a small adjustment for inflation," 12% annual compounding — that flat-fee was non-negotiable.
So Command Center is a flat monthly fee — no per-seat, per-client, or per-invoice charges. Hire ten more techs tomorrow, your bill doesn't change. Add 200 more managed endpoints, your bill doesn't change. Scale up your client base 3×, your bill doesn't change. The only thing that changes the bill is if we build new integrations for you. See current pricing on the homepage → The Founding Five program is active — the first customers lock in their rate for the lifetime of their account.
And because the platform is API-driven, it reads from whatever you already run. We build every integration custom to your stack as part of your engagement. Any accounting system, RMM, PSA, phone system, or EDR that exposes an API connects the same way. If your tool has an API, we build the adapter for it — fit to your exact workflows, not forced onto someone else's pre-wired list.
This works for us because the platform's cost is dominated by ongoing development and infrastructure (both flat costs), not by the marginal seat. It works for you because your platform spend stops scaling with your growth.
What to do this week
If you've never sat down and tallied your per-seat spend, do it. Use the table above as a template. Add a column for "could this be flattened or consolidated?" Be honest about which tools you actually need a per-seat license for (the ones whose work product is genuinely user-specific) versus the ones where you're paying for a viewing seat on data that lives in another tool.
If the consolidatable column adds up to more than ~$10,000/year, you have a real business case to either renegotiate with your vendors (most will give a discount when you ask the right way) or look at flat-fee alternatives that read from your existing tools.
Per-seat pricing isn't going away — too many vendors are addicted to it. But you don't have to keep paying it on every layer of your stack.