If you've shopped MSP platforms recently, you've noticed a divide. Most charge per technician (or per endpoint, which usually amounts to the same thing): $50, $80, $120 per month per seat. A few charge a flat rate: one fee for the whole organization regardless of how many techs use it.
The conventional wisdom is that flat-rate is “better.” That's only sometimes true. The pricing model matters more than the per-seat number, but which model wins depends entirely on where you are now and where you're going.
This post does the math.
The two models, side by side
To make the math concrete, let's pick two representative offerings:
- Per-seat platform: $80/tech/month. (That is roughly the middle of the market. ConnectWise PSA, Atera Pro, Syncro and NinjaOne PSA all land in the $50-150 range.)
- Flat-rate platform: $4,500 setup + $350/month flat at launch pricing (regular price $6,000 setup and $500/month after December 31, 2026), plus $1,500 per additional integration beyond the 3 included at launch pricing ($2,000 regularly). (That is Morton Command Center’s published pricing, and it carries no per-user tier. The comparison below is drawn at small-shop headcounts because that is where the per-seat model is easiest to picture, not because the rate stops applying above them.) See current pricing on the homepage →
The break-even comparison depends on tech count over time. Let's walk through it. The flat-rate figures below are launch pricing, locked in for anyone who signs up on or before December 31, 2026.
Year 1 totals
| Tech count | Per-seat (yr 1) | Flat-rate (yr 1) | Difference |
|---|---|---|---|
| 3 techs | $2,880 | $8,700 | Per-seat saves $5,820 |
| 5 techs | $4,800 | $8,700 | Per-seat saves $3,900 |
| 8 techs | $7,680 | $8,700 | Per-seat saves $1,020 |
| 10 techs | $9,600 | $8,700 | Flat-rate saves $900 |
Inside the published tier, year one favors per-seat up to roughly nine technicians, and flat-rate above that. That is the honest read, and the year-one gap is largely an artifact of what is being compared: a one-time build set against a recurring subscription, so year one carries a cost that never comes back. Year two is where the shape of each model shows.
Year 2 onward, once the build is paid off
Without setup cost in subsequent years:
| Tech count | Per-seat (yr 2) | Flat-rate (yr 2) | Difference |
|---|---|---|---|
| 5 techs | $4,800 | $4,200 | Flat-rate saves $600 |
| 10 techs | $9,600 | $4,200 | Flat-rate saves $5,400 |
Once the build year is behind you, five techs is roughly break-even and every tech above it is money you keep.
The comparison most posts get wrong, including this one until recently
Everything above treats the two as substitutes. They are not, and pretending otherwise flatters neither side.
A per-seat PSA is a system of record. You migrate into it, your tickets and contracts live in its database, and it bills by the person. Morton Command Center is a layer over the tools you already run. Your PSA stays your PSA, your RMM stays your RMM, and nothing moves. Plenty of our customers keep paying for the PSA they already had.
So the useful question is not "which of these two do I buy." It is: what is the whole stack costing you per head? A five-person MSP does not pay for five seats. Counted across the PSA, the RMM, time tracking, reporting, quoting and the BI layer, it is closer to twenty-three billable units. About a third of that is the viewing layer, the tools whose fifth login is worth no more than the first. We put real numbers on that here. That is the spend a flat rate actually displaces, and it is why the model can pay off well inside ten techs even though the head-to-head table above says otherwise.
The non-financial argument: incentive alignment
Money isn't the only thing pricing model affects. Per-seat creates perverse incentives:
- Adding a junior tech becomes a per-month decision. The senior tech's time is freed up to do higher-value work, but only after the spreadsheet shows the platform fee is justified. This delays hiring decisions that should happen organically.
- Read-only access becomes contentious. A bookkeeper, a sales person, or an intern would benefit from limited access to the platform. Per-seat pricing makes you charge yourself for every login. Most MSPs end up sharing logins instead, which is a security problem.
- Customer-portal users are awkward. Some platforms charge per “portal user” too. If your client wants 8 different employees to log in, that's 8 more seats. Either you eat the cost or you ration your client's access.
Flat-rate eliminates all of these. Add as many users as you want; the cost stays the same. Hiring decisions, access decisions, portal decisions all happen on their merits, not against a per-seat tally.
The argument for per-seat
To be fair, per-seat has real strengths:
- It's predictable. Flat-rate platforms are often flat-rate only up to a tier (under 10 users, under 25, etc.). Above the tier, the price jumps. Per-seat scales smoothly.
- It's familiar. Per-seat is the SaaS norm; finance teams understand how to model it.
- It aligns vendor incentive with growth. If you grow, the vendor makes more money. They're motivated to make features that benefit larger teams.
- It lets you start small. Any flat-rate platform has a floor you pay whether you are two people or ten. At two people, that floor is the whole argument against it.
If a PSA is genuinely all you need, with one tool, no sprawl and no growth plans, then per-seat is the right answer, and we will say so on the call. The flat-rate case depends on there being a stack to unify.
The hidden cost most pricing comparisons miss
Per-seat platforms typically charge for additional seats with friction: a sales call, a contract revision, an onboarding fee. Adding a flat-rate seat is free; adding a per-seat seat takes 30 minutes of admin time to provision.
It's a small cost individually, but at scale it shapes behavior. MSPs on per-seat platforms often delay onboarding new techs to the platform until they're sure the hire will stick. That's lost productivity for the new hire's first 1-3 months. Multiply by the number of new hires per year and it's a real number.
The honest decision matrix
Framed as "which model," not "which vendor":
- One tool does everything you need. Per-seat. If a PSA covers your whole operation you are not paying a sprawl tax, and there is nothing for a unifying layer to earn back.
- Two or three tools, and they mostly behave. Roughly even. Decide on fit, not on price.
- Six or more tools, and half the day goes on moving between them. Flat-rate. Here the seat tax across the whole stack, not any single subscription, is the number that matters.
- Growing, or hiring juniors and part-timers. Flat-rate. Provisioning friction quietly shapes who you give access to, which is a bad way to make hiring decisions.
- You want a customer portal clients actually use. Flat-rate. Per-seat portal pricing makes you ration your own clients' access.
Note what is missing from that list: headcount as the deciding factor. It is the wrong axis. A four-person MSP running eight tools has a worse seat-tax problem than an eight-person shop running three, and the four-person shop is the one a flat rate helps.
What the flat rate actually includes
Worth saying plainly, because a flat rate invites the assumption that it buys a stripped tier. It does not. Ticketing, client billing and invoicing, a dashboard each person builds themselves, a white-label customer portal, native timecards, a security operations queue, backup monitoring, revenue analytics, procurement and quoting and a sales pipeline are native modules, included in the build. The per-user math above covers every one of them, and there is no per-portal-user charge on top.
What is priced separately is the integration layer: the connections we build to your specific PSA, RMM, accounting system, phone system and security tools. That is the part that has to match your stack rather than a vendor's supported list, and it is why a quote depends on how many tools you run rather than how many people you employ.
What moves a quote is the shape of the work rather than the size of the team: the number of systems to integrate and the size of the fleet under management. Same model, a number scoped to you.
Run it on your own numbers
The pricing model matters more than the per-seat figure, but don't take the model on faith either. The exercise that settles it takes about twenty minutes: list every tool your team logs into, write down what each charges per person or per endpoint, and total the ones whose job is mostly looking at things. That total is what a flat rate is really competing against, and it is usually a good deal larger than the PSA line everyone benchmarks against.
If it comes out small, stay where you are. If it comes out uncomfortable, our current pricing is on the homepage, and the live demo is open without a sales call.