Key takeaways
- eLearning as a service (eLaaS) is a subscription arrangement where a vendor provides ongoing course-development capacity for a recurring fee. It's a different commitment model from project work, not a better one by default.
- eLaaS makes financial sense when you have predictable monthly workload (roughly 6–12+ courses a year), a mature L&D backlog, and clear value in working with one continuous team.
- Watch for the subscription floor. Most eLaaS contracts have a monthly or annual minimum that can cost more than project-based work if you don't use the capacity.
- Productized services match a lot of what L&D teams want from eLaaS (fixed price, fixed timeline, team-based delivery), without the monthly commitment.
- Evaluate eLaaS vendors on throughput guarantees, scope definition, and exit terms before you negotiate the monthly rate.
L&D backlogs are what drive the eLearning as a service conversation more often than any other factor. When training requests outpace what your team can deliver month after month, the project-by-project vendor model starts to feel exhausting. Each course is scoped from scratch, kicked off with a fresh team, and delivered with the assumption that your need will end when the project does. Most L&D teams know better.
eLearning as a service (sometimes shortened to eLaaS) is the model vendors offer in response. Instead of quoting each course separately, you pay a subscription and the vendor delivers ongoing capacity against a standing scope. That can be a genuinely better arrangement for some L&D programs. It can also be a worse deal than project-based work or productized services if your program isn't structured to take advantage of it.
This guide covers what eLaaS actually means, how it compares to retainers and productized services, when the math works, and what to ask before signing a subscription contract.
What is eLearning as a service?
eLearning as a service is a subscription arrangement where a vendor provides ongoing eLearning development capacity in exchange for a recurring fee. You pay monthly or annually, and the vendor delivers against a standing scope (typically expressed as throughput, like "x courses per quarter") rather than quoting each course separately.
There's no industry-standard definition of eLaaS. Different vendors use the term differently, and the differences matter when you're negotiating contracts. Most eLaaS arrangements share a few features:
- Subscription pricing. A fixed monthly or annual fee instead of per-project quotes.
- Standing scope. A pre-defined set of what the vendor will deliver, often expressed as throughput rather than hours.
- Ongoing relationship. The vendor keeps context from one project to the next and treats your L&D function as a continuous client.
- Bundled services. Development, updates, light advisory, and sometimes LMS support all included within the subscription.
The practical effect is that eLaaS looks more like a service contract than a project engagement. For buyers, that means less per-project negotiation and more focus on the overall relationship. That trade-off is valuable for some programs and irrelevant for others.
How eLaaS compares to retainers and productized services
eLearning as a service is one approach within the broader category of eLearning outsourcing. The three most common outsourced models (eLaaS, retainers, and productized services) solve similar problems with different commitment structures.
| Project-based | Retainer | eLaaS | Productized | |
|---|---|---|---|---|
| Pricing | Per-project quote | Hours or projects per month | Subscription against throughput | Flat fee per course |
| Commitment | None beyond the project | Monthly minimum | 6–12 month minimum typical | None beyond the order |
| Capacity model | Negotiated per project | Reserved hours | Standing throughput | Standing per course |
| Continuity | Low | High | High | Low |
| Switching cost | Low | Medium | High | Low |
| Best fit | Bursty, infrequent needs | Predictable monthly hours | 12+ courses a year | 1–10 courses a year |
| Watch out for | Per-project kickoff cost | Reserved hours you don't use | Subscription floor; vague scope | Less context between projects |
The differences that matter most are commitment length, switching cost, and the assumption built into the pricing about how predictable your workload is. Retainers and eLaaS both bet on continuity. Project-based and productized services don't. Which side of that bet makes sense for your program comes down to how steady the next twelve months of L&D production actually looks.
The line between retainer and eLaaS is fuzzy and vendor-specific. Read the contract, not the label. The terms that matter are the throughput guarantee, what counts as in-scope, how overages are priced, and how you get out of the arrangement.
When does eLaaS make financial sense?
eLaaS makes financial sense when you have predictable monthly workload, a mature L&D backlog, and clear value in working with one continuous team. The math doesn't work without all three. Programs that have one or two of those conditions usually save money with project-based or productized work.
Predictable monthly workload
The basic math: the vendor is pricing for steady throughput. You pay a flat rate assuming you'll use a consistent amount of capacity each month. If your actual usage matches, the vendor's margin is reasonable and your cost per course drops compared to ad-hoc project work. If your usage is lumpy (three courses in March, nothing until September), you're paying for capacity you don't use in the slow months.
Most L&D programs aren't as steady as they think they are. Before signing an eLaaS contract, pull the last twelve months of completed courses and map them by month. If you see steady production of two or three courses a month, the math will probably pencil out. If you see six in Q1, one in Q2, nothing in Q3, and four in Q4, that's a bursty program. Project-based or productized work usually serves a bursty program better.
Check your real production pattern before signing. Pull the last twelve months of completed courses and map them by month. A steady cadence means the eLaaS math is worth running. A pattern that spikes and crashes means a subscription will charge you for flat capacity in months where your actual workload is light, so you pay the most exactly when you need it least.
A known backlog
eLaaS works when you know roughly what the next four quarters look like. A refresh of the onboarding library. Quarterly compliance updates. New product training timed to three product launches. The vendor can plan capacity, and you get the courses you need when you need them.
Programs that don't know what they'll need six months out usually struggle with eLaaS. You end up either paying for unused capacity or fighting scope disputes when the vendor thinks a request falls outside the standing scope. If your backlog is more "we'll know it when we see it" than "here's the list," project-based work keeps your options open.
Continuity with one team
One of the real benefits of eLaaS is that the same team keeps working on your courses. They learn your brand, your LMS, your review process, your subject-matter experts. That continuity is worth real money. It's essentially the same kickoff cost, amortized across many projects.
For a team producing two or three courses a year, the kickoff savings are small and probably don't justify a subscription floor. For a team producing roughly a course a month, the continuity is significant, and eLaaS often wins on both cost and speed.
When is eLaaS the wrong fit?
A few patterns tend to produce buyer's remorse:
- Small program, low throughput. You produce two or three courses a year. An eLaaS floor will cost more than two or three project-based quotes, and you won't use enough capacity to benefit from the continuity.
- Highly variable projects. Every course you need is genuinely different in format, complexity, and technical requirements. Standing scopes don't fit variable work well, and you'll spend more time negotiating what's in scope than you save on subscription pricing.
- Unclear budget ownership. If eLaaS is a line item in someone else's budget and you can't guarantee renewal, short-term project-based work is usually safer than a 12-month subscription commitment.
- You want optionality. eLaaS subscriptions create switching costs. If you expect to evaluate multiple vendors or change providers based on performance, project work keeps your options open.
If you're in any of the situations above, the better question is often how to source the production capacity itself rather than what subscription model to choose. Our guide to how to hire eLearning designers walks through the trade-offs between freelancers, in-house staff, and done-for-you vendors.
How to evaluate an eLaaS vendor
The questions that matter aren't about the headline monthly rate. They're about the terms underneath it.
Throughput guarantees
What exactly is the vendor committing to deliver? "Unlimited updates" is not a commitment; it's marketing. "Up to three new courses per quarter plus ten hours of update work per month" is a commitment. Ask for the throughput in writing and check that it's realistic given your actual workload.
Scope definition
The projects that go sideways in eLaaS engagements are almost always the ones where scope was left vague. Get it in writing before you sign: what counts as in-scope, what counts as a change, and what happens if you ask for something the vendor considers out of scope.
Exit terms
What's the notice period? Is there a minimum commitment? Do you keep the source files for courses the vendor produced during the engagement? (You should. Always negotiate this up front if it isn't clearly stated.) What happens to work-in-progress if you end the subscription mid-quarter?
Team continuity
One of eLaaS's main benefits is working with the same team over time. Ask who will actually be on your account, how often the team changes, and what happens if a key person leaves the vendor. A subscription where the team rotates every quarter is worse than a project-based relationship where you pick the team each time.
Be cautious of "unlimited." Unlimited updates in eLaaS marketing almost always have hidden limits in the contract. The pattern is unlimited within a defined scope, throttled through a defined queue, and billed as overage once you cross an undefined threshold. If the word "unlimited" appears in a pitch, ask the vendor to define the specific monthly and annual caps in writing before you sign.
Is there an alternative to eLaaS?
For programs that want most of what eLaaS offers without the monthly commitment, productized services are the alternative. They share the predictable pricing, fixed timelines, and team-based delivery of eLaaS, but they're priced per course rather than per month.
Express eLearning by Neovation is a productized eLearning development service that delivers a professional, SCORM-compliant course in approximately 10 business days for $1,999. Each project includes instructional design, development, QA, WCAG 2.1 AA accessibility review, SCORM 1.2 or 2004 packaging, and clean HTML5/JS source files you own. There's no subscription minimum and no monthly throughput requirement.
That structure tends to work better for programs producing roughly one to ten courses a year. You aren't paying for unused capacity in slow months. You can compare per-course pricing directly across vendors. There's no exit friction. The trade-off is less continuity between projects, which matters more the more courses you produce. For programs near the high end of that range, the choice between productized and eLaaS comes down to whether the savings from one continuous team outweigh the risk of a subscription floor.
If you're evaluating productized services alongside other delivery models, our breakdown of eLearning service packages walks through how productized work fits next to consultancy, agency, and turnkey offerings.
A working comparison at six courses a year. An eLaaS subscription at $4,000 per month is $48,000 a year. Six Express eLearning courses at $1,999 each is $11,994. The eLaaS number only makes sense if you're using the full throughput a subscription includes, typically 12–20 courses plus updates and advisory. At six courses a year, per-course pricing wins by a factor of four. Your specific break-even depends on the eLaaS contract you're comparing against, but running the math is almost always worth doing before you sign.
Working out what fits your program
The first move is honest math, not vendor evaluation. Pull last year's course production by month. Estimate next year's. Compare what each model would have cost against your actual workload. The right model is the one with the lowest true cost for your real production pattern, which is often a smaller number than the headline subscription rate suggests.
For a fuller view of the trade-offs before running that math, our broader guide to outsourcing eLearning development covers how productized work, eLaaS, and project-based outsourcing fit alongside each other.
When you're ready to compare a productized option against your eLaaS quotes, send us your project details and we'll walk you through how Express eLearning would handle the same scope.
Frequently Asked Questions
eLearning as a service (eLaaS) is a subscription arrangement where a vendor provides ongoing eLearning production capacity for a monthly or annual fee, rather than quoting each course as a separate project. The vendor delivers against a standing scope (typically expressed as throughput, like "three courses per quarter") and keeps context across projects as an ongoing client relationship.
Retainers usually price in hours or projects per month. eLaaS usually prices in throughput ('x courses per quarter' or 'unlimited updates within the standing scope'). The vendor carries more of the capacity-planning risk with eLaaS than with a traditional retainer. The two models overlap a lot in practice, and different vendors use the terms differently, so the contract terms matter more than the label.
It depends on your production pattern. eLaaS is worth it when you have a predictable monthly workload (roughly 6–12 courses or more a year), a mature L&D backlog you can plan against, and value in working with one continuous team. Below that volume, project-based or productized services are usually cheaper because you aren't paying a subscription floor for capacity you don't use.
Most eLaaS subscriptions have a floor that only pencils out if you're producing roughly 6–12+ courses a year, depending on the vendor. Below that volume, the per-course cost works out higher than project-based or productized alternatives. Run the math against your actual production volume both ways before committing to a subscription.
Often yes. A productized service like Express eLearning by Neovation gives you predictable per-course pricing ($1,999), a fixed timeline (approximately 10 business days), and team-based delivery without a monthly commitment. You get most of the operational predictability of eLaaS, priced per course rather than per month, with no exit friction if your needs change.
Related resources
Done-for-you eLearning: the model, explained
What done-for-you eLearning includes, how it compares to other models, and when it fits.
Instructional design services: a buyer's guide
Stop overpaying or under-scoping training by learning what instructional design actually buys you.
How to outsource eLearning without the headaches
Outsource eLearning without scope creep, surprise invoices, or a third-month rebuild.
