Three gates, in this order 1. The brief Audience, LMS, standard, seat time, languages, review capacity 2. The design A storyboard for a job like yours, plus a written change request policy 3. The LMS test A real package, launched in your LMS, tracking and resuming correctly Outside the gates: the showreel, the client logo wall, the award badge None of these predict whether the course will track in your LMS High on Tales, September 2026

How to Choose an eLearning Development Company: A Procurement Guide

Choose an eLearning development company on three tests: whether they can turn your raw material into a defensible learning design, whether their output actually behaves inside your LMS, and whether their price is built from a rate card you can audit line by line. Everything else in a pitch, the showreel included, is decoration. In our experience vendors rarely fail on visual quality. They fail on tracking, on review cycles and on change requests, and all three are visible before you sign if you ask for the right artefacts.

On this page

Write the brief before you write the shortlist

Most procurement processes start at the wrong end. Someone collects five vendor names, sends them a paragraph describing "an interactive online course on workplace safety", and then tries to compare five wildly different quotes. The quotes are not comparable because the brief was not specific enough to constrain them. That is not the vendors being slippery. It is the brief doing no work.

Before you contact anyone, write down eight things. Who the learners are and what they will be doing differently afterwards. Which LMS you use, and which version. Which standard it must be delivered in. Target seat time. Number of languages, and whether the voiceover is human or synthetic. Accessibility requirement, if there is one. How many people have to approve the content, and how quickly they can turn a review around. And the deadline that actually matters, as distinct from the one written on the plan.

That last pair carries more risk than anything else on the list. Training magazine's 2025 Industry Report found that 41 percent of L and D respondents named lack of resources and personnel as their biggest training challenge, and that while 68 percent of respondents recommend a purchase, only 21 percent hold the final decision. Read those two findings together and the picture is clear. The person writing the brief is usually short of time and does not sign the contract. So the brief has to survive being read by people who were never in the room.

Here is the thing though. A brief that specifies the review chain is worth more to a vendor than a brief that specifies the animation style. Style is negotiable in week two. A subject matter expert who takes three weeks to return comments will move your delivery date no matter who you hire. We have run projects where review time exceeded build time, and none of them were rescued by a better designer.

The market context is worth knowing while you set your budget. US training expenditure rose 4.9 percent to 102.8 billion dollars in 2025, and spending on outside products and services rose 29 percent to 16 billion dollars, while the average spend per organisation on outsourcing actually slipped to 217,178 dollars from 241,311 dollars the year before. More organisations are buying from outside, and each of them is buying more carefully. Our eLearning development cost page breaks down what those numbers look like at a per-course level.

Five questions that separate vendors

Any agency can answer "do you do custom eLearning". These five are harder to bluff.

1. Who writes the storyboard, and can I see one from a project like mine? Not the finished course. The storyboard. A redacted screen-by-screen document tells you whether there is an instructional designer in the building or whether a developer is dropping your PowerPoint into a template. Look for stated learning objectives, an assessment mapped to those objectives, and on-screen text that is different from the narration rather than identical to it.

2. What happens when the SME rejects the script at screen 40? This will happen. The answer you want describes a process: a checkpoint before build starts, a defined number of review rounds, a named person who consolidates conflicting comments. The answer you do not want is "we are flexible". Flexible is what people say before they invoice you for it.

3. Show me your change request policy in writing. Two revision rounds after storyboard sign-off is normal. Unlimited revisions is either priced into the quote or it is a fiction. Ask what counts as a revision and what counts as new scope, and ask for an example of each from a past project.

4. Which LMS platforms have you delivered into, and what broke? Moodle, TalentLMS, SAP SuccessFactors and iGOT Karmayogi all behave differently with the same package. A vendor with real delivery history will have a war story about completion statuses not posting or a course that ran fine in preview and stalled on the production server. A vendor without one has either been lucky or has not shipped much.

5. Who owns the source files? Get this in writing before the kickoff call, not after the final invoice. The Storyline .story file, the Rise course export, the After Effects project, the voiceover stems, the editable graphics. If you cannot make a small legal update in year two without going back to the same vendor, you have not bought a course. You have rented one.

The technical checks most buyers skip

Procurement teams evaluate design and price. They almost never evaluate the package. That is backwards, because a beautiful course that reports nothing to your LMS is worth less than a plain one that reports correctly.

Start with the standard. SCORM is not going anywhere: Rustici Software, who run SCORM Cloud, reported that 92 percent of course launches in 2025 were SCORM packages across SCORM 1.2 and SCORM 2004 combined. So the practical question is not SCORM versus xAPI in the abstract. It is which version your LMS supports well, and which one your course design needs.

Course launches in SCORM Cloud, 2025, by standard SCORM 1.2 and SCORM 2004 combined 92% Everything else: xAPI, cmi5, AICC, LTI 8% Ask a vendor which standard they will ship in, and why. If the answer is a shrug, they are guessing about the one thing your LMS actually cares about. Source: Rustici Software, SCORM Cloud data, February 2026

That choice has consequences you can measure. SCORM 1.2 caps suspend data at 4,096 characters, while SCORM 2004 allows 64,000. Bookmarking, branching state and interaction data all compete for that same allowance. Publish a long branching course to SCORM 1.2 and learners will silently lose their resume position partway through, which then arrives on your desk as a complaint about the course being broken. It is not broken. It ran out of room.

Why a long course forgets where the learner stopped SCORM 1.2 suspend data limit 4,096 chars SCORM 2004 suspend data limit 64,000 chars Bookmarking, branching state and interaction data all compete for the same bucket. Source: SCORM.com support documentation, verified 7 September 2026

So put three technical requirements into the RFP itself. First, the vendor delivers a test package before contract award, and you launch it in your own LMS, not in their demo environment. Second, they state the standard and version and justify it. Third, they confirm behaviour on the devices your learners actually use, which for most government and PSU deployments means mid-range Android phones on unreliable connections rather than a desk monitor. Our SCORM and xAPI development page covers what each standard can and cannot report.

Our opinionated take: the portfolio is the least useful thing in the pitch. Every showreel is a vendor's best two percent, produced with their most cooperative client and their longest timeline. It tells you what the studio can do at its ceiling, not what it will do on your project. Ask instead for a project that went wrong, and what changed afterwards. A vendor who cannot name one is either very new or is managing you. We would rather lose a pitch than pretend our timelines have never slipped, because the studios that pretend are the ones who go quiet in month three.

How to read a price

Quotes arrive in three incompatible units: per finished minute of media, per screen or slide, and per hour of learner seat time. Convert everything to one unit before you compare, and ask every vendor to split the total across instructional design, media production, development, voiceover, quality assurance and project management. A vendor who will not break out those six lines is either hiding a subcontractor margin or does not track their own costs.

Then look for what is missing. In our experience the gap between a cheap quote and a realistic one is almost never the build. It is the things listed below the line: voiceover re-records after a script change, retesting the package in the LMS once per language, accessibility remediation, and the second and third rounds of review that the plan assumed would not be needed.

Take a concrete case. A 45 minute Storyline course in three languages, quoted at a flat per-minute rate, looks cheap until you notice the quote covers one LMS test cycle rather than three, and treats each localised voiceover as a straight swap rather than a re-sync. Those two omissions can move a project by weeks. Ask the question directly: what is not included in this number. A good vendor will have a ready answer, because they have been asked before.

One structural point on rates. Studios that run animation and eLearning production under one roof can quote a course with 2D animation, motion graphics or whiteboard sequences without adding a second supplier's margin on top. There are not many firms doing both, and at Indian rates the difference on a multi-module programme is not marginal. Our outsourcing page sets out how that model works in practice.

Score it, pilot it, then contract it

Build a weighted scorecard before the proposals arrive, not after. Weighting them afterwards is how a nice deck wins. A workable split for a mid-sized custom course programme: instructional design quality 30 percent, technical and LMS competence 20 percent, relevant domain experience 20 percent, price 20 percent, and delivery capacity, meaning team size and current load, 10 percent.

Then pilot. Commission one module of roughly ten minutes as a paid piece of work from your top two vendors, delivered as a finished package into your LMS. Yes, it costs money and adds two or three weeks. It is still the cheapest insurance available on a programme worth many times that, and it surfaces the things a pitch cannot: how they handle your SME, how they take feedback, whether the second draft is better than the first.

Finally, put four clauses in the contract. Source files transfer on final payment. Revision rounds are defined and priced. The vendor retests the package in your LMS after any content change. And acceptance, along with the final payment milestone, is tied to the course running correctly in your production LMS, not to files landing in a shared folder. That last clause changes vendor behaviour more than any other sentence in the agreement. If you want to see how that plays out across a full build, our custom eLearning development page walks through the stages.

If you are partway through a shortlist and want a second opinion on a proposal, send it over. We are happy to tell you what we would ask next, including when the honest answer is that another studio is the better fit for that particular job.

Frequently asked questions

How long does it take to choose an eLearning development company?

Allow four to eight weeks from brief to contract for a mid-sized programme. That covers roughly a week to write the brief, two to three weeks for vendors to respond properly, a week of clarification calls and technical checks, and two to three weeks if you run a paid pilot module. Compressing this below three weeks usually means skipping the LMS test, which is the check that catches the most expensive problems.

What should an eLearning RFP include that most of them miss?

Three things. The LMS name and version plus the required standard, so quotes are technically comparable. The review chain, meaning how many approvers there are and how fast they can respond, because that drives the timeline more than build effort does. And a requirement that the vendor deliver a test package into your LMS before contract award.

Should I choose SCORM or xAPI for a new course?

Choose the standard your LMS supports well. Rustici Software reported that 92 percent of course launches in SCORM Cloud in 2025 were SCORM packages, so SCORM remains the safe default for LMS-hosted compliance and completion tracking. Choose xAPI or cmi5 when you need to track activity outside the LMS or capture richer interaction data, and confirm your LMS or LRS can actually receive it before committing.

Is a cheaper offshore eLearning vendor a false economy?

Not inherently. The failure mode is not location, it is scope definition. A well-specified project with defined revision rounds, named reviewers and a contractual LMS acceptance test delivers reliably at Indian rates. A vague brief overruns everywhere, at any price point. Compare quotes only after converting them to the same unit and confirming what each one excludes.

Who should own the course source files?

You should, and it should be written into the contract before kickoff. That means the Storyline project file or Rise export, editable graphics, After Effects project files and voiceover stems. Without them, a small regulatory update in year two forces you back to the original vendor at whatever rate they quote.

Do I really need a paid pilot module?

For anything beyond a single short course, yes. A pilot reveals how a vendor handles your subject matter expert, whether their second draft improves on the first, and whether the package tracks correctly in your production LMS. Those three answers are not available from a pitch deck, and each one is a common reason programmes stall after signature.

Sources

High on Tales logo

High on Tales builds custom eLearning, SCORM and xAPI courses, and 2D, 3D, whiteboard and motion graphics video for government, PSU and corporate clients from India. We are one of the few studios that runs animation and eLearning production under one roof, at Indian rates. Read more from the blog.

how to choose an elearning development company elearning vendor selection elearning rfp checklist scorm course development custom elearning development elearning company in india