What an LMS really costs a US firm over five years — license, setup, integrations, hosting, admin, and exit — SaaS vs owned, line by line.
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.
The five ways LMS vendors charge you, what each one rewards, and which one fits a multi-site operation.
The line items that turn a clean per-seat quote into a bill 40 to 60 percent higher than the headline.
The payback math behind custom LMS ROI — break-even points and illustrative USD models across different headcounts.
Most L&D leaders size an LMS by the number on the sales quote: "around $9 per user per month." That number is the down payment, not the price. The LMS total cost of ownership is the full five-year sum of every dollar the platform pulls out of your budget — license, setup, integrations, hosting, the admin time it eats, the content you build, and the bill you pay to leave.
For a mid-market US firm running 200 to 300 people across plants, distribution centers, or retail locations, those hidden lines routinely add up to more than the license itself. This breakdown walks every category, shows the difference in shape between a rented SaaS subscription and a platform you own outright, and gives you illustrative five-year math you can adapt to your own headcount.
TCO is the sum of every cost a system creates across its useful life — typically modeled over five years for an LMS, because that's a realistic span before a major platform decision comes up again. It breaks into eight categories. Most quotes show you one.
The two that surprise people are integrations and exit. We'll get to both.
The headline line. For SaaS it's per-user-per-month, billed annually, and it almost never holds flat — renewal uplifts of 5 to 12 percent a year are common, and they compound.
Run the illustrative math. Say a 250-person firm pays $9 per user per month. That's $27,000 in year one. Add a conservative 7 percent renewal increase each year and you're paying about $35,400 in year five — roughly $156,000 over the five years, before a single add-on.
An owned platform inverts this. There is no per-seat fee. You pay to build it once, then you pay to host and support it — the fixed one-time build fee versus per-seat subscription is the choice underneath this whole line. Whether you add 50 seasonal workers for a Q4 retail push or onboard a newly acquired plant, your platform cost does not move. That decoupling of cost from headcount is the core financial argument for ownership, and it's covered in depth in our pricing models explainer.
What it costs to get live: discovery, configuration, branded theme, content migration, integrations, user acceptance testing, and admin training.
SaaS vendors quote implementation between $5,000 at the low end and $60,000-plus for enterprise suites. Owned and managed-Moodle builds typically run $30,000 to $150,000 depending on scope — but it's a one-time cost, not an annual one, and it buys configuration that fits how your sites actually run instead of forcing your process into someone else's template. We break this down to the line item in our implementation cost guide.
The detail that matters for multi-site firms: configuration that handles separate locations, role-based reporting per plant, and shift-based enrollment is where generic SaaS setups get expensive fast, because every deviation from the standard template is billed as customization.
This is the line that quietly doubles SaaS budgets. Connecting your LMS to your HRIS (Workday, UKG, Bamboo HR), your SSO provider, and any compliance or ERP systems is rarely included in the base tier.
Many SaaS platforms gate SSO behind an enterprise tier — an "SSO tax" that can add thousands a year — and charge per-connector fees for HRIS sync. For a firm that needs automatic provisioning when a new hire is added at a plant, that's not optional; it's the whole point of the integration.
On an owned platform, HRIS integration and SSO/SAML are scoped into the build and then belong to you. There's no recurring connector fee and no tier you have to climb to unlock single sign-on. If you also run ERP-driven training requirements, ERP integration follows the same model.
For SaaS, hosting is invisible — it's inside the subscription, though it's worth knowing where your data physically sits.
For an owned platform, hosting is a real but modest line you control. At 2,000 users on US cloud infrastructure, expect roughly $400 to $1,200 a month including backups, monitoring, and a CDN, depending on traffic patterns and redundancy. Because it's your cloud account, you can right-size it, and you keep data residency and security decisions in-house — which matters for SOC 2 posture and audit readiness.
The cost nobody puts in a spreadsheet: the hours your team spends running the thing. Enrolling learners, building reports, chasing completions, managing renewals.
This is roughly the same whether you rent or own, with one caveat — platforms configured to fit your structure (automated enrollment by location, scheduled compliance reports) cut admin time, while generic platforms that force manual workarounds increase it. A half-FTE of admin time is real money; at a loaded cost of, say, $35,000 a year for a half-time coordinator, that's $175,000 over five years that rarely appears in any LMS comparison. We put a number on the hidden cost of LMS admin time and how to size it for your own team.
SaaS support is tiered. Basic support is included; fast response times, a named contact, or guaranteed SLAs usually require a premium support plan billed on top.
Owned platforms carry a maintenance and support agreement too — you need security patching, version upgrades, and someone to call. The difference is that it's a fixed, negotiated line rather than an upsell ladder, and it's covered under post-launch support rather than rationed by tier. We dig into the SaaS version of this in the fees nobody quotes.
Course content — building it, buying it, maintaining it — is a cost in either model and often the largest single ongoing expense after license. It's platform-neutral, so it usually washes out of a SaaS-vs-owned comparison. Include it in your total budget, but don't let it tilt the build-vs-buy decision; that decision turns on the platform lines, not the content.
The line that's worth the most and gets measured the least.
When you outgrow or want to leave a SaaS platform, you pay to get out: extracting your data in a usable format, rebuilding completion histories, re-implementing on a new system, and the staff time to manage a migration while keeping training running. Vendor lock-in is precisely the leverage that makes renewal uplifts stick — leaving is expensive, so you renew. Knowing this shapes how you negotiate the contract or renewal, because your exit cost is the vendor's strongest card.
With an owned platform, exit cost is low because there's nothing to exit. You hold the data, the configuration, and the code. If you change hosting or support partners, the platform comes with you. That's the practical meaning of "own it, don't rent it," and it's the foundation of the build-vs-buy decision.
Here's a simplified model for a 250-person multi-site firm. Treat these as illustrative figures to adapt, not quotes.
The shape is the point. SaaS starts cheap and climbs every year as headcount and renewals grow. Owned front-loads the build, then flattens — and the gap widens further the longer you keep the platform and the more sites you add. For most multi-site US firms past roughly 200 users, the curves cross inside the five-year window.
Run your own numbers before you trust ours — the TCO calculator takes your headcount, growth, and renewal assumptions and does the math live. When you're ready to scope a real build, our pricing lays out the fixed-price options.
Build your model in three passes. First, list every category above — including admin, content, and exit — not just license. Second, project SaaS lines forward with realistic renewal uplift, because flat-rate assumptions understate the five-year total badly. Third, compare against an owned build where cost is decoupled from headcount.
If you're a manufacturer onboarding seasonal labor, a food producer with FSMA training that has to survive an audit, or a multi-location retailer scaling stores, the per-seat model penalizes exactly the growth and seasonality you're planning for. An owned platform prices the operation, not the headcount.
The first is treating the per-seat quote as the budget. It's the floor, not the ceiling — integrations, SSO, premium support, and renewal uplift sit on top, and they're the lines that move the five-year total most. We catalog them in the fees nobody quotes.
The second is assuming flat pricing. SaaS contracts almost always carry contractual annual increases, and a model that holds the rate flat across five years can understate the total by a third or more. Always project the uplift forward.
The third is ignoring exit cost entirely. Most spreadsheets stop at the cost of running the platform and never price the cost of leaving it — the data extraction, the re-implementation, the staff time. That's precisely the cost vendor lock-in is built to make painful, and it's why a platform you own carries a structurally lower risk profile over a five-year horizon. For the full decision logic, read the build-vs-buy guide alongside this breakdown.
Get those three right and your model will hold up under finance scrutiny — which is the whole point of building it. Once the TCO is solid, the next step is to turn it into an ROI a CFO will sign off on.