A clear guide to LMS pricing models for US firms — per-active-user, per-registered-user, tiered, flat-fee, and owned — with a pros and cons table.
Got an LMS decision on your plate?
45-minute call. Plain-English audit. Fixed-price quote if there's a fit, or a "no" if there isn't. No deck. No pitch.
Every line item in an LMS budget over five years, compared across rented SaaS and a platform you own outright.
The exact math of when per-seat SaaS becomes more expensive than custom or managed Moodle — worked numbers across scale bands.
Per-seat pricing tracks your headcount; fixed-price tracks your operation. Why that difference matters for multi-site firms.
When you ask three LMS vendors for a price, you'll often get three numbers that aren't comparable — because they're using different LMS pricing models. One charges per active user, one per registered user, one a flat tier. Until you normalize them, you can't tell which is actually cheaper for your firm.
This guide lays out the five pricing models you'll meet, what each one quietly rewards or punishes, and why a multi-site US operation tends to land in a different place than a single-office company.
You pay for users who log in during a billing period. It sounds fair — you only pay for engagement — but for compliance-driven training it backfires. When everyone has to complete annual food-safety or OSHA refreshers in the same window, your "active" count spikes and so does your bill. The model penalizes exactly the all-hands training events you can't avoid.
You pay for every account that exists, active or not. Predictable, but you're billed for the warehouse worker who logged in once for orientation and the seasonal hires you onboarded for Q4 and offboarded in January. Cleanup becomes a budgeting chore, and dormant accounts are pure waste.
Pricing jumps in bands — up to 250 users, up to 500, and so on. The trap is the cliff: add one user past 250 and you pay for the whole next band. For a firm hovering near a tier boundary, or one that grows in steps as it opens locations, the jumps are jarring and hard to forecast.
One price for the platform regardless of headcount, often with usage caps in the fine print. Better for predictability, but read the caps — storage limits, admin-seat limits, and API-call ceilings are where "flat" stops being flat, and overage charges kick in.
You pay once to build and own the platform, then pay only to host and support it. No per-seat fee, no tier cliffs, no renewal uplift. Cost is decoupled from headcount entirely — covered in full in our TCO breakdown. The head-to-head between this and the subscription models is in our fixed one-time build fee versus per-seat subscription comparison.
The four SaaS models all share one property: your platform cost tracks your headcount. For a firm that's deliberately growing locations, runs seasonal labor, or has to push compliance training to everyone at once, that's a structural mismatch. You're being billed more precisely when your training program is working hardest.
An owned platform breaks that link. Add a plant, onboard 80 seasonal workers, run a company-wide refresh — the platform cost doesn't move. You're paying for the operation, not the seat count. The trade is a higher upfront build cost, which is why the crossover math matters: there's a headcount past which ownership is simply cheaper over five years.
Three steps. First, convert every quote to a five-year total, not a monthly rate — that's where renewal uplift and tier jumps show up. Second, add the lines that aren't in the headline: SSO, HRIS connectors, premium support, overage. Third, set the SaaS five-year total next to a one-time owned build plus hosting and support.
When you run that exercise, the question stops being "which model is cheapest per user" and becomes "at our size and growth, which shape of cost wins." For most multi-site mid-market firms, the answer points toward fixed-price ownership. Our pricing page shows what that looks like concretely.
Take a 250-person food producer running three plants, hiring seasonally, with annual food-safety refreshers everyone has to complete in the same window.
On per-active-user pricing, the refresh window spikes the active count and the bill with it — twice a year. On per-registered-user, the seasonal hires keep billing after they leave until someone cleans up the accounts. On tiered, opening a fourth plant could tip the firm over a band edge and into the next price band for a handful of extra users. On flat annual, the firm is predictable until it hits a storage or API cap and pays overage.
Every SaaS model has a failure mode triggered by exactly what this firm does operationally. The owned model has none of them — the build cost is fixed, hosting and support are flat, and the three plants, the seasonal cohort, and the all-hands refresh don't move the number. That's the structural reason operationally complex firms keep landing on ownership once they model it honestly.