Our conclusion
Outsourcing production while retaining internal learning design and governance is the position most organisations reach, and it is usually the right one. Full outsourcing of strategy to a supplier is fragile, and full in-house production is expensive for organisations whose primary business is not content production. The decisive variable is not cost, it is whether you have the people who can direct a supplier effectively.
Comparison table
| Dimension | Option A | Option B |
|---|---|---|
| Cost shape | Variable and project-driven, with a design phase that front-loads spend. Cheap to start, expensive to change scope mid-build. | Fixed and predictable, dominated by salaries, tooling and management overhead, which continues whether or not you ship. |
| Time to capability | Immediate for a single programme, but you learn very little about the craft. | Slow. Capability takes a year or more to build and must be maintained through changing tools. |
| Quality control | External reviewers with fresh eyes and specialist standards. You get what you pay for and must still review. | Consistent, but constrained by internal capability, tooling and team familiarity. Same problem, every time. |
| IP and source files | Must be contractually specified. Several vendors in this directory publish explicit IP positions, which is a good negotiating benchmark. | Full control by default, which is the main practical argument for in-house. |
| Scaling | Flexible. Volume is a procurement decision. | Hiring is slow and the fixed cost rises with headcount whether or not output rises. |
| Strategic knowledge | Transferable if you design and review it. Weak if you outsource design and only accept delivery. | Deep and permanent, and it is the part that makes the investment worthwhile. |
| Ongoing maintenance | Often a separate and easily forgotten line item. Confirm what annual maintenance and updates cost and how they are triggered. | Naturally absorbed, though competing for the same scarce time as new development. |
Column headings reflect the two options as named in this comparison. Read the dimensions row by row rather than treating the table as a ranking.
Who should choose which
Organisations with variable or lumpy content demand, specialised needs, hard deadlines, or a mandate to avoid building a content function. Also organisations in markets where the required specialisms, such as instructional design at scale or a particular language pair, are hard to hire for.
Organisations with sustained, high-volume content demand, content as a genuine differentiator, a need to iterate in-house at speed, and a strong reason to control IP and source files directly.
When both are the right answer
A workable middle pattern retains an internal learning design and governance function of two to four people, outsources production, and keeps a standing internal owner of standards, terminology and quality. The failure mode to avoid is outsourcing everything and then finding you can no longer evaluate what you receive, which is a strategic risk that a supplier dependency quietly creates.
Limitations of this comparison
No cost figures are offered here. Cost depends on the interaction between scope, media method, review rounds, language count and maintenance commitment, and any figure presented as an industry average would be misleading.
Turn this into a decision
The comparison worksheet lets you weight your own criteria and score the responses you actually receive, rather than relying on a general comparison.