Budget for the whole system, not just the production fee
Most content budgets underestimate the cost because they count only the external production fee. The work also consumes internal subject matter expert time, internal design and review capacity, a learning management system and authoring tool subscription, translation and localisation, media stock and music licensing, accessibility remediation after launch, and ongoing updates as policies change.
Itemise these as separate lines, because they behave differently and are controlled by different people. The external fee is the part you can negotiate; internal time is the part you can plan; licensing and tool costs are largely fixed. Presenting them separately prevents the negotiation from being about the wrong number.
Internal effort is usually the largest hidden cost and the most under-counted, because subject matter expert time is rarely tracked. Estimate it in person-days per module, using the review rounds you have agreed, and be honest that the first review of a poorly prepared script takes longer than the fifth.
Model cost drivers rather than a per-unit rate
A flat per-module rate hides the fact that cost varies widely by module. A short factual video and an interactive scenario with branching paths and synthetic avatars are not the same unit of work, and a budget built on a single blended rate will drift in whichever direction your actual mix differs from the assumption.
Build the budget from the drivers: number of courses and modules, minutes of finished video and the production method, number and type of interactions, number of personas and scenarios, number of review rounds, number of languages and the level of adaptation, technology integrations, and post-launch update obligations. Apply your supplier's rates to a specific, itemised volume, and check the total against your independent estimate.
Our guide on what affects the cost of custom eLearning development covers each driver in detail, and the drivers are also the basis for a rate card that makes future buying predictable. A rate card with fixed definitions for module types is one of the most effective budget controls available, because it turns each new request into a line item rather than a negotiation.
Phase the spend against a real release plan
Annual budgets for content are often a single line divided by twelve, which is not a plan. Phase the spend against what will actually be live, and be explicit about what happens if a phase slips. A budget that assumes full production starting in month one is the most common reason content programmes quietly lose their funding when the first phase slips.
Include the cost of a pilot and a standards phase at the front, and treat that as an investment rather than overhead. The pilot usually pays for itself by preventing a full programme from being built on an untested approach.
Be honest about the profile of work, because a mixed portfolio is cheaper than a uniform one. A small number of flagship courses plus a larger set of lighter modules, built on a shared template, will usually deliver more learning per budget than many mid-weight courses built individually. If your budget only allows the second, that is a legitimate choice, but it should be made deliberately.
Reserve for the things that always happen
Build in a contingency that reflects the uncertainty in your plan, and label it as such rather than spreading it invisibly. A figure around a tenth of the production value is a common starting point, but the right level depends on how well-defined your scope is and how stable your subject matter experts are. A first project in a new area should carry more than a repeat of a well-understood pattern.
Reserve separately for a small set of predictable events: additional review rounds beyond the agreed cap, accessibility remediation found after launch, translation layout rework, and updates triggered by policy change. Naming these lines in advance makes them a planning conversation rather than a dispute later.
Also budget for what happens when a key person leaves your organisation. Documented, modular content and reusable templates reduce the cost of recovery, and specifying them in the contract with a supplier is cheaper than paying a supplier to rebuild your catalogue later. For the mechanics of comparing what suppliers propose against your budget, see our guide on comparing enterprise content production proposals.
Budget the years after the build
Most content budgets describe a year of production and ignore everything afterwards. Set a multi-year view that includes the subscription and licensing of authoring tools, the cost of post-launch updates, the periodic re-audit of the catalogue, and the ongoing cost of keeping content in multiple languages current.
Make the ownership explicit, including who inside the organisation will manage the supplier after launch, who will approve updates, and what an update costs. Where the supplier holds the tooling, establish what the exit cost would be and whether a one-time buyout is possible, so the organisation is not locked in without knowing the price of freedom.
Finally, connect the budget to a stated outcome. A budget that funds production volume rather than a defined capability improvement will always be under pressure, because production volume is easy to measure and the improvement is not. If a business case is required, our guide on how to plan a content modernization project shows how to tie spend to a defined capability and measure whether it was delivered.
Commonly overlooked pitfalls
- Budgeting only the external production fee and omitting internal expert time, tooling, and post-launch costs.
- Applying a single blended per-module rate to a mix of module types with very different effort profiles.
- Assuming a flat annual run rate rather than phasing spend against a real release plan.
- Leaving review overruns, accessibility remediation, and translation rework as unfunded surprises.
- Ignoring the multi-year cost of updates, licences, and language currency once the build is finished.
Next steps
- Build a cost model with separate lines for external fees, internal effort, tooling, localisation, and post-launch updates.
- Itemise volume by module type and apply rates to that specific mix, then sanity check against an independent estimate.
- Agree a rate card with fixed module definitions so future requests are quoted consistently.
- Add named contingency lines for review overruns, accessibility remediation, and translation rework.
- Produce a multi-year view covering licences, updates, and re-audits, and assign internal ownership explicitly.
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.