Scope drives everything else
The largest single driver of custom eLearning cost is how much content you are commissioning and how much of it is genuinely new. A course built from scratch, with original scripting, original media, and new interactivity, sits at one end of the range. A course that reuses existing modules with a new introduction, a restyled visual template, and a refreshed assessment sits at the other, and the gap between the two is large.
The useful discipline is to itemise your project into units before any quote arrives. How many courses, roughly how many minutes of finished video, how many branching or scenario-based interactions, how many knowledge checks, how many distinct personas used in examples. A supplier working from your own itemised list will produce a far more useful estimate than one working from a paragraph.
A useful rule of thumb for buyers is that the specification of the deliverable explains more of the final number than the choice of supplier. But supplier expertise still matters, because an experienced producer can often achieve the same outcome with a leaner asset set, and can tell you which parts of your wish list are not worth the money.
Media volume and production method
Video is usually the largest controllable media cost, and it varies enormously by method. Studio-recorded presenter footage with a professional crew, remote capture with good audio, in-house studio builds using a fixed set, and animation or screen-capture production are different cost structures with different trade-offs in realism, pace, and maintenance burden.
Decision points that move cost: the number of distinct presenters, the number of recording days, the number of locations, whether a physical set is built, how many takes are needed for quality, whether scripts are written by the supplier or by your subject matter experts, and how much scripting is required for compliance accuracy.
Synthetic captioning and machine-assisted transcription reduce turnaround and cost for a first pass, but a human-reviewed pass is generally still needed for accuracy, timing, speaker labelling, and terminology. The distinction between machine-generated and human-verified captions is worth pricing explicitly, because the two are not equivalent deliverables.
The number and depth of review cycles
Reviews are where schedules, and therefore costs, quietly expand. Each substantive revision round on a script, a storyboard, a build, and a video multiplies the effort of specialists, and every additional stakeholder who must sign off adds coordination overhead even if no changes are required.
Agreeing in advance on who reviews what, at which stage, and how many rounds are included is one of the highest-leverage cost controls available to a buyer. Naming one consolidated approver per stage prevents a review process where five people comment on the same asset in parallel.
A supplier who quotes a firm number of rounds and then treats additional rounds as a change request is protecting both programmes. Buyers sometimes read that as rigidity, but it is the mechanism by which a project stays on budget. Our guide on how to assess content quality before full production describes how to front-load the review effort so fewer rounds are needed later.
Languages, markets, and localisation overhead
Translation is rarely a single line item. The real cost sits in the workflow: maintaining a glossary, matching layouts across text expansion, adapting locally inappropriate examples and imagery, and re-testing functionality in each language, not only re-exporting the same package.
Certain markets push costs further, particularly where legal or regulatory review is required per language, or where cultural adaptation of scenarios is expected rather than a literal translation. Ask whether the quote includes a per-language review cycle and functional testing, and whether a shared terminology base already exists.
There is a strategic decision here too. A language set that is stable for several years justifies heavier localisation investment; a set that changes every quarter may be better served by a more modular authoring approach that lets non-specialists update translated content safely.
Technology, integrations, and maintenance
Technical scope has a cost that is easy to under-estimate. Each learning management system integration, single sign-on requirement, reporting specification, or data sync adds engineering time that rarely appears in a visual storyboard but very much appears in the schedule.
Standardised authoring tools such as those in the Articulate family, and hand-built SCORM or xAPI packages, sit at different points on the cost and maintenance spectrum. Off-the-shelf authoring tools reduce initial build cost and speed publishing, while hand-built packages can offer precise control but demand more engineering and more care at every update. See our guide on how to evaluate AI-assisted content production for how this calculus is shifting.
Budget for the life of the content, not only the build. Some suppliers price a low initial fee and charge for subsequent changes, updates, and re-publishing. A higher initial investment in templates and modular architecture often reduces the total cost of ownership over several years, particularly for organisations with more than a handful of assets in active use.
Commonly overlooked pitfalls
- Treating a low headline quote as a low total cost, without checking what excluded items and future change requests will cost.
- Under-specifying media requirements, so a single revised video session changes the whole production method and the estimate.
- Not capping review rounds, which is the most common source of unplanned cost growth in custom projects.
- Quoting translation as a flat per-language fee when the real drivers are layout, testing, and local review cycles.
- Ignoring the cost of maintaining and updating content after launch, which compounds across a large catalogue.
Next steps
- Itemise your requirement into courses, video minutes, interactions, personas, and languages before requesting quotes.
- Ask each supplier to price the same itemised scope, and to flag which line items they would reduce first if the budget moved.
- Decide the video production method deliberately, and specify captioning and accessibility levels within the requirement.
- Cap review rounds per stage in writing and name one consolidated approver for each.
- Model the maintenance path, including who can update content and at what hourly or per-item cost, over a multi-year horizon.
Related guides
Put this into practice
The vendor evaluation checklist and the RFP template turn a guide into a process you can run this week.