eLearning as a service: when to switch

"eLearning as a service" (sometimes eLaaS) has become one of those terms vendors use to signal something modern and flexible without always explaining what it means. Underneath the language, eLaaS is a specific commercial model: you pay a recurring subscription fee, and a vendor provides ongoing production capacity against a standing scope.

That can be a great arrangement for the right L&D program. It can also be a worse deal than project-based work or productized services if your program isn't a fit for the model. This guide covers what eLaaS actually means, when the math works, and how to decide whether switching is worth it.

What "eLearning as a service" actually means

There's no industry-standard definition of eLaaS. Different vendors use the term differently, and the differences matter when you're negotiating contracts. That said, most eLaaS arrangements share a few features:

• Subscription pricing. A fixed monthly or annual fee rather than per-project quotes.
• Standing scope. A pre-defined set of what the vendor will deliver — typically expressed as throughput ("x courses per quarter") 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 rather than a series of one-off engagements.
• Bundled services. Development, updates, light advisory, and sometimes LMS support all included within the subscription.

The practical effect is that eLaaS tends to look more like a service contract and less like a project engagement. For buyers, that means less per-project negotiation and more focus on the overall relationship — a trade-off that's valuable for some programs and irrelevant for others.

How eLaaS differs from a retainer

Retainers are the older model. Most retainers are priced in hours per month ("40 hours of ID work per month") or projects per month ("up to 2 courses per quarter"). The vendor is on the hook for availability; you're on the hook for having work ready.

eLaaS subscriptions usually flip some of that risk. Pricing is often tied to throughput rather than hours, and the vendor carries more of the capacity-planning responsibility. If one month is light, the vendor absorbs it. If one month is heavy, the vendor's supposed to flex without a change order.

In practice, the distinction 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 the math actually works

Three conditions make eLaaS a better deal than project-based or productized alternatives.

Predictable monthly workload

The basic math of eLaaS: 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 comes down versus 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 deal, look at the last 12 months of course production. Was it genuinely monthly, or was it a few bursts with long gaps? Bursty programs usually do better with project-based or productized services.

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 when each of three product launches ship. The vendor can plan capacity; 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, because you end up either paying for unused capacity or running into scope disputes when the vendor thinks a request is out of the standing scope.

Value in continuity

One of the real benefits of eLaaS (versus project-based work) is that the same team keeps working on your courses. They learn your brand, your LMS, your review process, your SMEs. 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 cost savings are small and probably don't justify a subscription floor. For a team producing a course a month, the continuity is significant and eLaaS often wins on both cost and speed.

When eLaaS is the wrong fit

A few patterns that 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 — different formats, different complexity levels, different technical requirements. Standing scopes don't fit variable work well; 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 a bake-off. eLaaS subscriptions create switching costs. If you expect to evaluate multiple vendors or switch providers based on performance, project-based keeps your optionality.

How to evaluate eLaaS vendors

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 3 new courses per quarter plus 10 hours of update work per month" is a commitment. Ask for the throughput in writing and make sure it's realistic given your actual workload.

Scope definition

What counts as in-scope? What counts as a change? What happens if you ask for something the vendor considers out of scope? The projects that go sideways in eLaaS engagements are almost always the ones where this was left vague.

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's not 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 they change, and what happens if a key person leaves the vendor. A great eLaaS deal where the team rotates every quarter is worse than a project-based relationship where you pick the team each time.

The productized alternative

A lot of what L&D teams want from eLaaS — predictable pricing, fixed timelines, team-based delivery, less per-project negotiation — is also available from productized services, without the subscription commitment.

Express eLearning by Neovation is built this way. Each course is $1,999, delivered in 10 business days, with a fixed scope: up to 1 hour of seat time, up to 3 modules, SCORM-packaged, WCAG 2.1 AA compliant. You get the operational predictability of eLaaS — you know what each course will cost and when it will land — priced per course rather than per month.

For programs that produce a course every month or two, this often works better than eLaaS. You're not paying for unused capacity in slow months, you can easily compare costs across vendors, and there's no exit friction. The trade-off is less continuity — you're starting fresh on each course, rather than amortizing kickoff across a relationship — but for most bounded training that difference is small.

If you're weighing eLaaS against project-based or productized options, run the math honestly. How many courses did you actually produce last year? What would each model have cost? The model with the best number wins. The rest is marketing. If you'd like help thinking through the math for your program, get in touch.