Should You Outsource eLearning Development? – In-House vs Vendor

Your training requests keep growing. Your team is small. Every quarter, someone asks whether it would be cheaper to just hire a vendor, and every quarter someone else says a vendor won't understand the business. Both people have a point. The trouble is that the debate usually runs on opinions rather than numbers. Should you outsource eLearning development, or keep it in-house?

eLearning outsourcing makes sense when your volume is uneven, when you need specialized skills you don't use often, or when you need to scale quickly; keeping development in-house makes sense when volume is steady, content changes often and deep knowledge of the business matters. The deciding factor is usually utilization. An in-house developer is a fixed cost that pays off when they're busy all year. A vendor is a variable cost that pays off when the work comes in waves. Many organizations land on a hybrid: in-house design and maintenance, with outside production for peaks and special projects.

What Are the Real Pros and Cons of Each Model?

The real pros and cons come down to cost structure, speed, skills and knowledge of the business. Here's how the two models compare on the factors that matter most.

No model wins on every row. A small team that knows the business can turn around an update in an afternoon. A vendor can staff a twelve-course rollout in a month. The right answer depends on what your work actually looks like across a year.

How Do the Costs Compare?

The costs compare differently at different volumes, which is why this debate never ends. At low volume, a vendor is cheaper because you only pay for the work you need. At steady high volume, in-house is cheaper because you're paying for capacity you fully use.

The chart below is an illustrative example, not market data. It assumes one in-house developer at an example fully loaded cost of $115,000 a year (salary, benefits, tools and overhead) with about 1,200 productive development hours a year. It compares that with a vendor at an example rate of $95 per hour. Volume is measured in finished hours of moderately interactive content, using Chapman Alliance's widely cited 2010 average of 184 development hours per finished hour.

Here's the math. Two finished hours a year means about 368 development hours. At $95 an hour, the vendor costs about $35,000, while the in-house developer still costs $115,000. At six finished hours, or about 1,100 development hours, the vendor costs about $105,000, close to the in-house figure. At eight finished hours, the in-house developer is maxed out, so the overflow goes to a vendor anyway, and the two options cost about the same.

Two cautions. First, the in-house developer also does things the chart doesn't count, like quick updates, LMS support and sitting in on business meetings. Second, an underused in-house developer is the most expensive option of all. Utilization is the number to watch.

How Do You Estimate Your Own Volume?

Estimate your own volume by listing the courses you expect to build or overhaul next year, with rough length and interactivity for each. Then convert that list into development hours. The estimator below does the conversion for any single course, so you can add them up.

Once you have total hours, compare them with in-house capacity. One experienced developer typically has well under 2,000 truly productive hours a year once meetings, admin and time off are counted. If your estimate is far below one person's capacity, outsourcing probably wins. If it's well above, you either need more staff or a vendor relationship for overflow.

For the in-house side of the math, use your organization's real loaded cost if you can get it. If not, the U.S. Bureau of Labor Statistics occupational profile for training and development specialists gives pay data you can use as a starting point before adding benefits and overhead.

When Is eLearning Outsourcing the Better Choice?

eLearning outsourcing is the better choice when your work is uneven, specialized or urgent. A few situations point clearly toward a vendor:

• Big one-time initiatives, such as a system rollout or a new compliance program.
• Specialized work like 3D, simulations, video production or custom programming.
• Translation and localization into several languages.
• Seasonal peaks that would leave in-house staff idle the rest of the year.
• A need for an outside perspective on a program that hasn't been working.

Vendors also bring process. A good vendor has built hundreds of courses and has templates, checklists and testing routines that a small in-house team may never have time to develop.

When Should You Keep Development In-House?

Keep development in-house when the work is steady, when content changes frequently and when understanding the business is the hard part. Product training at a company that ships updates every month is a classic example. By the time a vendor learns the product, it has changed.

In-house teams also build institutional memory. They know which subject matter experts (SMEs) respond quickly, which stakeholders need to see drafts early and which past courses can be reused. That knowledge doesn't show up on a budget line, but it saves real time on every project.

Is a Hybrid Model Worth Considering?

A hybrid model is worth considering for most mid-sized and large organizations. It combines a small in-house team with one or two trusted vendors, so you get business knowledge and flexibility at the same time.

A common split looks like this. The in-house team handles needs analysis, design, stakeholder management and ongoing maintenance. Vendors handle production peaks, specialized media and large rollouts. The in-house team becomes the quality gate, reviewing vendor work against standards it owns.

This works best with a written style guide, shared templates and clear file standards, so vendor work drops neatly into your library. Some vendors also partner with agencies to add capacity behind the scenes, a model known as white-label eLearning development, which can be useful if you're an agency yourself.

Which Hidden Costs Belong in the Comparison?

Hidden costs exist on both sides, and a fair comparison counts them. Leaving them out is how a "cheaper" option turns expensive halfway through the year.

On the in-house side, count recruiting time, training for new tools, authoring software licenses, computers, audio gear and the manager's time spent supervising. Count the risk of turnover, too. When a solo developer leaves, projects stall for months while you hire again.

On the vendor side, count your own project management time, the hours your SMEs spend bringing a new vendor up to speed, the cost of extra review rounds and any change orders. Count the learning curve on the first project, which is almost always slower than the second.

Put both lists into the same spreadsheet as the core costs. The answer may not change, but your confidence in it will.

How Do You Manage a Vendor Well?

You manage a vendor well by treating them like an extension of your team, with clear standards and a single point of contact. Most vendor problems are really communication problems.

• Give them a kickoff packet: audience profile, brand guide, templates, LMS details and examples of courses you like.
• Name one person on your side who approves work and resolves conflicting feedback.
• Agree on review rounds and turnaround times in writing.
• Hold a short weekly check-in during active projects.
• Run a quick retrospective after each project and share what you'd change.

Vendors who work with you repeatedly get faster and cheaper over time, because they've learned your business. That's a good reason to build a long relationship with one or two vendors instead of shopping every project.

What Mistakes Do Teams Make When Outsourcing?

The most common mistakes are handing off the thinking along with the building, skipping the onboarding and losing the source files.

1. Outsourcing analysis entirely. A vendor can run analysis well, but someone inside must own the performance goal.
2. Skipping vendor onboarding. An hour spent explaining your audience, brand and LMS saves many hours of rework.
3. Not asking for source files. Without them, every future update becomes a new project.
4. Comparing a vendor's hourly rate with an employee's salary. Compare loaded cost against loaded cost.

Outsource the Peaks, Own the Core

Should you outsource eLearning development? If your volume is low or uneven, or the work needs specialized skills, eLearning outsourcing usually wins on cost and speed. If your volume is steady and the content changes often, in-house usually wins on cost and responsiveness.

For many teams, the best answer is both: keep design, maintenance and business knowledge in-house, and send peaks and specialty work to a trusted vendor. Run your own numbers with real loaded costs and a realistic utilization rate, and the right mix will usually be obvious.

← All articles