The real differences between ID service packages

If you've ever compared instructional design vendors, you've probably noticed that the packages on their websites all sound roughly the same. "Custom eLearning development." "End-to-end ID services." "Managed learning solutions." The labels blur together, and the pricing pages usually don't help either.

Underneath the language, there are really only four common package structures in this market, and they commit you to very different things. This guide covers what each one actually includes, what each is good for, and how to tell which one fits your project.

What "ID services" actually covers

Before getting into the packages, a quick grounding on what instructional design services include in the first place, because the scope varies.

At a minimum, instructional design covers the work of turning content (a manual, a set of SME interviews, a topic) into a structured learning experience. That means needs analysis, learning objectives, content structuring, assessment design, and a plan for how the learner will move through the material.

Some ID engagements stop there and hand off storyboards to a separate developer. Others include the full build — instructional design, development, QA, accessibility review, and SCORM packaging. When a vendor says "ID services," ask where the scope starts and stops. The answer isn't standard.

For a full picture of what a build-complete eLearning engagement includes, see How to outsource eLearning without the headaches. For a look at the cost implications of each tier, see the eLearning cost guide.

The four common package structures

Most ID service vendors sell one of these four structures. Some sell multiple.

Project-based

A one-time engagement with a defined scope and price. You sign a statement of work, the vendor builds the course, the engagement ends when the course is delivered.

The most common package structure across the industry, mostly because it's the default when neither side is sure what to commit to. Works fine for one-off projects. Less good when you need a steady stream of courses, because each project starts from zero: new kickoff, new scoping conversation, new ramp-up on your business.

Typical price range: $3,000 to $50,000+ per finished hour of seat time, depending on complexity.

Retainer

An ongoing monthly commitment for a defined amount of work. You pay a fixed monthly fee and the vendor is on the hook to deliver a set of courses, updates, or support within that fee.

Good fit when you have a predictable monthly workload. The vendor keeps context from one project to the next, so you skip the kickoff cost each time. You also get continuity — the same team knows your brand, your LMS, your review process. That continuity is worth real money if you're producing more than a course or two per quarter.

The risk is paying for capacity you don't use in slow months. Most retainers include a roll-forward clause for unused hours, but not all of them. Read that section of the contract carefully.

Productized

A productized service fixes the scope, the price, and the timeline. Every project delivers the same kind of thing. Express eLearning by Neovation is built this way: $1,999 per course, 10 business days, up to 1 hour of seat time, up to 3 modules.

Good fit when your training is bounded and standard. Onboarding, compliance refreshers, product training, policy updates, customer education — a lot of what L&D teams actually build fits this description. You trade flexibility for predictability. You can't add a fifth module to a three-module course on day nine. That's the point.

Not a fit when the scope genuinely needs to be custom — bespoke simulations, rich voiceover, branching scenarios with meaningful consequences. For those, you want a project-based engagement at the custom tier.

eLearning-as-a-service

Subscription-style access to ongoing production capacity. You pay a monthly or annual fee, and the vendor delivers a continuous pipeline of courses, updates, and support against a standing scope.

Similar to a retainer in spirit, but the commitment structure is different. Retainers are typically priced in hours or projects per month. eLearning-as-a-service is usually priced in throughput — "x courses per quarter" or "unlimited updates to the existing library." The vendor carries more of the capacity-planning risk.

Good fit when you're running a mature L&D program with a known backlog and want to treat production as operating expense rather than project-by-project capex. Less good for small programs where the subscription floor doesn't match your actual throughput.

For a deeper look at when this model makes sense, see eLearning as a service: when to switch.

Which package is right for your project?

Three questions will point you to the right package most of the time.

How much variability is there between the courses you need?

If every course you need is roughly the same — same length, same interactivity level, same LMS, same review process — productized services will usually be the cheapest and fastest option. If every course is genuinely different, productized won't fit and you're looking at project-based or custom.

Most L&D teams have more variability than they think they do at first, and less than they think they do on closer inspection. Worth running the exercise: write down the last five courses your team built. How different were they, really? If four out of five fit within "up to one hour of seat time, up to three modules, standard interactions," a productized service probably handles 80% of your workload.

How often will you need new courses?

Once or twice a year, project-based is fine — the overhead of running two separate engagements isn't worth optimizing away.

Monthly or more, retainer or eLearning-as-a-service starts paying off. Not because the hourly rate is lower (it often isn't) but because you skip the kickoff cost on every project and the team already knows your context.

Somewhere in the middle (one course per quarter, say), productized services are often the best fit. You get predictable pricing without the commitment overhead.

How bounded is the deliverable?

Tight — one hour of seat time, standard interactions, clear content — go productized.

Loose — unknown length, custom interactions, content still being written — go project-based. Productized services will feel constraining and you'll end up fighting the scope.

The pricing trap to watch for

One of the more common mistakes is buying the wrong package at a discount. A cheap retainer isn't a good deal if you only need one course a year. A cheap productized package isn't a good deal if your project genuinely needs custom work. A cheap project-based quote isn't a good deal if the vendor plans to recover margin through change orders.

The question isn't "which package is cheapest?" It's "which package is the right shape for my work, and is the price reasonable within that package?" A well-matched project-based engagement often beats a poorly-matched retainer, even when the retainer's per-hour rate is lower.

Match the package to the work first. Negotiate on price second.

If you want help figuring out which package fits your project — or whether productized is even the right tier in the first place — get in touch. We'll walk through it honestly. If Express eLearning is the right call, we'll scope it. If it isn't, we'll say so and point you toward what is.