A prospect sends over a deck and asks for a price by Friday. You count the slides, multiply by a number you once heard at a conference, and send it. Six weeks later you are on the fourth review round and working for less than you would earn stacking shelves. Sound familiar? How much should you charge for an e-learning course, and how do you build a quote that holds up?
Work out how much to charge for an e-learning course by estimating the hours it will take, using your own hours per finished minute for the interactivity level, then adding review rounds, project management, testing and a contingency, and multiplying by your rate. Do not price by slide count, because two decks with the same number of slides can take wildly different effort. Write down the assumptions behind the number, especially how many review rounds are included. The price you send is only as good as the time records behind it, so start tracking your hours on every project if you do not already.
Why Is Pricing by Slide Count a Trap?
Slide count measures the input, not the work, because a slide can be a title and three bullets, or it can be a branching decision with five feedback layers and narration. Both count as one slide, but only one of them takes a day.

Take two made-up clients who each send a 40-slide deck that will become roughly a 20-minute course. Client A wants clean text, images and a short quiz. Client B wants narration, scenarios and a drag-and-drop exercise on every topic. Using the example rates further down, Client A's course is about 60 hours of build work and Client B's is about 240. Same slide count, four times the hours.
If you had quoted both at the same per-slide price, you would have overcharged one client and gone broke on the other. Clients also learn quickly that slide count is negotiable: merge two slides and the price drops, even though the work did not.
What Does Hours per Finished Minute Mean?
Hours per finished minute is the total time it takes to produce one minute of finished learner time. If a 20-minute course took you 120 hours from kickoff to final delivery, that is 6 hours per finished minute (120 divided by 20). It is the most useful number a course builder can own, because it turns a vague creative project into something you can estimate, compare and defend.
The key word is "own," since you will see figures quoted online, but other people's numbers include their tools, their clients and their habits. Yours will differ, and the only figures worth quoting from are the ones in your own time log.
To build that log, track every project by phase: analysis, storyboard, media, build, review fixes, testing, project management. At the end, divide the total by the finished runtime. After five or six projects, you will have a range you can trust, and you will also see which phase eats your margin. For many independent builders, it turns out to be review fixes.
The scope of the work matters too. The US Bureau of Labor Statistics description of what training and development specialists do includes assessing needs, creating materials, delivering training and evaluating programs. If the client wants needs analysis or evaluation from you, those are separate line items, not something hidden inside your per-minute figure.
How Does Interactivity Change the Estimate?
Interactivity is usually the biggest driver of hours per finished minute. More interaction means more design, more build time, more states and logic to test, and more things for reviewers to comment on. A simple way to handle it is to define three levels and keep a separate rate for each.
| Level (example definitions) | What it includes | Example hours per finished minute |
|---|---|---|
| Level 1 | Text, images, simple knowledge checks | 3 |
| Level 2 | Narration, a few interactions, short scenarios | 6 |
| Level 3 | Branching, custom interactions, simulations | 12 |
Those numbers are illustrative, from a hypothetical freelancer's log. They are not industry benchmarks, so do not copy them into a quote. Replace them with your own as soon as you have data. What matters is the structure: the client picks the level, and the level sets the rate.
Many real courses mix levels. That is fine, as long as you estimate each module at its own level and add them up. A 30-minute course with 20 minutes at Level 1 and 10 at Level 3 is (20 x 3) + (10 x 12) = 180 hours, not 30 x some average you made up.
How Do Review Rounds Change the Quote?
Review rounds change the quote more than almost anything else, because every round costs you hours whether the comments are big or small. A course quote is really a guess about how many review rounds the client will want. Make that guess explicit, in writing, before the client signs anything.
Each round involves reading and consolidating feedback, clarifying conflicting comments, making the changes, testing again and republishing. On a 20-minute Level 2 course, say a round takes you about 10 hours. Quote three rounds and that is 30 hours. If the client actually takes five rounds, you have absorbed 20 unpaid hours, and on a project of about 200 hours that is a tenth of your fee gone.
Two habits help. Name each round and say what it is for: storyboard review, first build review, final check. And say what happens after the included rounds: extra rounds are billed at your hourly rate. Most clients are fine with this when they see it before they sign. They are much less fine when they learn about it mid-project.
How Much to Charge for an E-Learning Course: A Worked 20-Minute Example
Here is a complete made-up quote so you can see the math end to end. The course is 20 minutes of finished runtime at Level 2, with three review rounds included. The example rate is 80 per hour in whatever currency you bill.
| Line item (example) | Hours |
|---|---|
| Design and build: 20 minutes x 6 hours | 120 |
| Three review rounds x 10 hours | 30 |
| Project management: 10% of 150 | 15 |
| LMS testing and delivery | 6 |
| Subtotal | 171 |
| Contingency: 15% of 171, rounded | 26 |
| Total | 197 |
At 80 per hour, 197 hours is 15,760. Your effective figure is 197 divided by 20, or roughly 9.9 hours per finished minute, well above the 6 hours you started with. That gap is the point: the base rate covers the building, and everything else is the cost of building it for a particular client with particular reviewers.
Now look at what could go wrong. If you had skipped the contingency and project management lines, you would have quoted 156 hours, or 12,480. If the project then ran to the full 197 hours, you would have worked 41 hours for free. Cut a line only if you can say exactly why that cost will not happen.
Where Does the Hourly Rate Come From?
The hourly rate in that example was not pulled from the air, and yours should not be either. Work backward from what the business needs to bring in over a year, including your own pay, taxes, software, equipment, insurance and the slow months, and then divide by the hours you can realistically bill rather than the hours you are at your desk.
Try it with made-up numbers. Say the business needs 70,000 a year to cover everything. You plan to work 46 weeks, and after sales calls, admin, invoicing and learning new tools, about 25 hours a week are actually billable. That is 46 x 25 = 1,150 billable hours, and 70,000 divided by 1,150 is about 61 per hour as a floor.
Anything you charge above that floor is margin for the risk you carry on fixed-price work. That is a good reason to set your rate somewhat above the floor rather than exactly at it.
Should You Charge Hourly, Per Project or Per Minute?
Each model shifts risk between you and the client, so pick the one that matches how clear the scope is. There is no single right answer, only better and worse fits.
| Model | Good when | Watch out for |
|---|---|---|
| Hourly | Scope is fuzzy, or it is ongoing support | Clients dislike open-ended bills |
| Per project | Scope and rounds are clearly agreed | You carry the overrun risk |
| Per finished minute | Repeat clients with similar courses | Hides differences in interactivity |
My take: fixed project prices built from an hours estimate are easiest for most clients to approve, because they get one number. Keep hourly for extras and for the vague discovery phase at the start. If you charge per minute, publish separate per-minute prices for each interactivity level, or you are back to the slide-count problem in a new costume.
Reuse is where per-project pricing can work in your favor. If you already own a template, an interaction pattern or a whole course you can adapt, your hours drop while the value to the client does not. That is the business logic behind rebranding ready-made courses for clients, and it is worth thinking about how you price your reuse before a client asks for a discount because "you've done this before."
How Do You Protect the Quote From Scope Creep?
You protect the quote by writing down every assumption the price depends on and agreeing how changes will be handled before work starts. Scope creep rarely arrives as one big request. It arrives as a dozen small ones, each of which seems too minor to argue about.
Put these in your proposal:
- Runtime and interactivity level per module.
- Number of review rounds, what each is for, and how extra rounds are billed.
- Who supplies content, images and voice, and by when.
- A content freeze date after which changes become change requests.
- What the delivery includes: published package, source file, or both.
- Payment milestones, for example a deposit at kickoff and payments at key approvals.
When a change request arrives, reply with the hours and the date impact before you do the work. "Happy to add the extra scenario. That is about 8 hours and pushes delivery by two days. Shall I go ahead?" It is polite and quick, and it turns a favor into a decision the client makes with full information. For anything about contract wording, payment terms or liability, get advice from someone qualified where you work.
Pricing an E-Learning Course Is Really Pricing the Review Rounds
So, how much should you charge for an e-learning course? Enough to cover your real hours per finished minute at the right interactivity level, plus the review rounds, project management, testing and a contingency, all multiplied by a rate you can live on. Slide count tells you almost nothing. Your time log tells you almost everything.
Start tracking hours by phase on your next project, even a small one. Write your assumptions into every quote, name the review rounds, and send change requests with a number attached. You will lose a few price shoppers, but you will keep the clients who value a quote that does not move.
