How to Price Corporate Training and eLearning Projects

Pricing is where most independent training consultants lose money — not by charging too little per hour, but by structuring the engagement so that every unforeseen thing comes out of their margin.

The three common models

Day rate

Simple, transparent, and caps your income at hours available. Works well for facilitation and consulting days where the deliverable is your time. Works badly for course development, because you're penalised for being efficient — the faster you build, the less you earn.

Per-course or fixed project fee

The client buys a deliverable, not your hours. This is where efficiency pays, and it's how most experienced eLearning developers price. It requires you to scope tightly, because you now own the risk of the project running long.

Value-based

Priced against the outcome — reduced incidents, faster onboarding, avoided penalties. Difficult to sell, occasionally spectacular, and dependent on the client agreeing to a measurable outcome up front. Rare in practice outside large engagements.

What actually drives cost in course development

Quoting well means knowing what varies. In order of impact:

• Source material quality — content that exists and is current versus content you must extract from six people's heads. This is the single largest variable and the one clients underestimate.
• Number of review cycles — two rounds is normal; unlimited rounds is where projects die.
• Media production — video and custom graphics dwarf the cost of the course itself.
• Interactivity depth — a branching simulation is an order of magnitude beyond a linear module with a quiz.
• Number of stakeholders — cost scales with the number of people who can request changes, not with course length.

The clauses that protect your margin

More important than the number:

1. Define review rounds explicitly. 'Two rounds of consolidated feedback' — consolidated being the operative word, so you get one document, not six conflicting emails.
2. Define what a round is. Additional rounds billed at day rate.
3. Name the source material assumption. 'Quote assumes content is provided in final, approved form.' If you're also writing the content, that's a separate line.
4. Set a decision-maker. One named person whose sign-off is final.
5. Put a scope boundary on the deliverable. Number of modules, approximate duration, one language, one LMS.

Rough market bands

Treat these as orientation, not a rate card — they vary enormously by region, sector and seniority:

• Simple linear course (existing content, light interactivity, ~30 min): typically a few days' work.
• Standard interactive course (content development, quizzes, some media): a couple of weeks.
• Complex build (branching, custom media, multiple audiences): a month or more.
• Facilitation: day rate, plus preparation time that is genuinely billable and often forgotten.

Convert those to money at your own rate. The useful discipline is estimating effort honestly before pricing, rather than pricing to what you think the client will accept and discovering the effort afterwards.

The reusable-assets question

If your process produces artifacts you can reuse — templates, question banks, a document toolkit — your effective rate rises over time without raising your price. That's the quiet economics of doing this professionally: the second compliance course costs you far less than the first, and the client is buying the outcome, not your effort.

On discounting

Discount scope, not price. Cutting your rate teaches the client your rate was inflated. Removing a module, a language, or a review round keeps the rate intact and makes the trade explicit.