If you’re asking how long does it take to build a custom eLearning course, the honest answer is: it depends on complexity and how ready your inputs are. A single module can take anywhere from a few weeks to a few months once you include design, build, reviews, and testing. People often quote “development hours per hour of learning”, but your calendar timeline is usually driven by reviews and approvals, not just build time.
At a glance
- Fast builds happen when you have solid source content, clear sign-off, and short review windows.
- Slow builds happen when scope shifts, SMEs are hard to book, and feedback arrives late.
- If you want a reliable estimate, separate effort hours from calendar weeks.
How long does it take to build a custom eLearning course?
Most projects sit in a range because “custom” can mean anything from clean, template-based modules to scenario-heavy builds with media and multiple review rounds.
A common starting point in the industry is a development ratio of around 40 to 50 hours of effort for 1 hour of finished eLearning, but that’s only a starting point. Complexity and review cycles change it fast.
Effort hours vs calendar weeks
These are not the same thing.
- Effort hours are the hours your team spends doing the work.
- Calendar weeks include waiting time: SME scheduling, stakeholder review windows, legal or compliance sign-off, and pilot feedback.
You can have a course with “reasonable” effort hours that still takes 10 to 12 weeks because reviews move slowly. One Australian provider states a 20 to 30-minute course “usually takes about 12 weeks” from contract signing to delivery, across discovery, design, development, and delivery.
Typical effort ratios by complexity
Use ratios to estimate effort hours, then convert to calendar time based on your review process and team availability.
| Complexity level | What it looks like | Typical effort ratio (hours : 1 hour seat time) |
|---|---|---|
| Level 1 Basic | Mostly linear, light interaction, standard layouts | 20 to 40 : 1 |
| Level 2 Intermediate | More interaction, some branching, more media | 50 to 80 : 1 |
| Level 3 Advanced | Scenarios, branching, custom media, heavy testing | 100 to 160 : 1 |
Reality check: these ratios estimate build effort. Your calendar timeline still depends on review speed and content readiness.
A simple way to estimate your timeline
This section is the part most competitor posts skip. Use it to produce a rough but defensible estimate.
Step 1: Confirm your seat time
Decide the target duration for learners. Example: 30 minutes (0.5 hours).
Step 2: Pick a complexity level
Be honest. If you want scenarios and branching, it is not “basic”.
Step 3: Estimate effort hours
Multiply seat time by the ratio.
Example: 0.5 hours at Level 2 (50 to 80 : 1)
Effort estimate: 25 to 40 hours of production effort.
If you’re trying to answer how long does it take to build a custom eLearning course for your situation, this step gets you close fast.
Step 4: Add “review and approval” time
This is where timelines blow out. Articulating notes for each stakeholder review round often needs several business days, and you also need time to implement feedback between rounds.
As a default, plan for:
- 2 to 4 review rounds
- 3 to 5 business days per round for reviewers to respond
- 1 to 3 days between rounds to apply changes (more if feedback conflicts)
Step 5: Add QA and release
Include:
- functional testing
- LMS packaging and upload
- accessibility checks if required
- pilot group feedback and fixes
What usually slows projects down
These are the repeat offenders. Fix these, and your timeline improves.
Slowdown 1: Source content is messy or missing
If your content lives in old slide decks, emails, and undocumented processes, your team spends time interviewing and rewriting before building even starts. LearnExperts states that content writing effort changes a lot depending on how much source content you already have.
Fix: assign an owner to provide one source pack, then freeze it for the first build.
Slowdown 2: Too many reviewers, no decision owner
Feedback conflicts. Everyone wants changes. Nothing moves.
Fix: name one person to approve content and one person to approve design. Everyone else advises.
Slowdown 3: Reviews take weeks
This is the biggest calendar driver. It explains why the question “How long does it take to build a custom eLearning course?” varies so much across teams, even when the course is similar.
Fix: set review windows on day one. If feedback misses the window, it goes into the next release.
Slowdown 4: Custom media starts late
Voiceover, video, animation, and custom graphics add time. They also add approval steps.
Fix: lock scripts early and schedule media production before the build is “almost done”.
Slowdown 5: Accessibility is added at the end
Retrofitting takes longer than designing accessibly from the start.
Fix: set accessibility requirements during discovery and test early.
A realistic project plan you can copy
Here’s a simple plan for one 20 to 30-minute module. Adjust based on complexity and how fast your reviewers move.
Week 1
- discovery workshop
- audience, goals, success measures
- source content collected and confirmed
- roles and sign-offs agreed
Week 2
- learning design and structure
- storyboard or script drafted
- design style confirmed
Weeks 3 to 4
- built-in authoring tool
- media production (if needed)
- internal QA pass
Weeks 5 to 6
- stakeholder review rounds and fixes
- accessibility and device testing
- LMS packaging and pilot
Week 7
- final changes
- release and handover
If reviews are slow, this stretches. One Australian example describes a 12-week timeline for a 20 to 30-minute course across four phases.
Ready to Map Your Course Build?
If you want a realistic estimate, collect three inputs: target seat time, complexity level, and how fast your reviewers can respond. Then estimate effort using a ratio and convert it into calendar weeks by adding review rounds and QA. That’s the practical way to answer how long does it take to build a custom eLearning course without guessing.
Prefer to hand this off to a team that does it every day? Poncho eLearning can take your brief and create a custom eLearning course that’s built, tested, and ready to roll out.
