e-Learning

Three things. The content — slides, manuals, SME notes, recordings, whatever exists. Your brand assets — logo, colours, fonts, any style guide. And your LMS details — which system, which SCORM or xAPI version it expects. With those we can scope the work and quote. Rough content is fine; we can structure it with your subject expert.

Before any build, we write a storyboard: every screen laid out with on-screen text, narration script, visual notes and interactions. You review it, mark changes, and sign it off. Only then do we build. This matters because text changes in a storyboard take minutes; the same changes after animation and voice-over are expensive. Sign-off is the main checkpoint in the project.

Whichever your LMS supports best. SCORM 1.2 is old but runs almost everywhere — the safe default. SCORM 2004 adds better sequencing and more detailed scoring. xAPI tracks learning outside the LMS too — mobile, simulations, offline — but needs an LRS. If you are unsure, tell us your LMS and we will recommend. We publish to all three.

Any standards-compliant one. We test regularly on Moodle, and our packages run on common commercial systems like Cornerstone, SAP SuccessFactors, Docebo and TalentLMS because we publish standard SCORM and xAPI rather than anything proprietary. Before final delivery we test the package on your actual LMS, or on a sandbox login you give us.

Yes. If you have the source files (.fla, Captivate, Storyline), we rebuild from those — fastest and cheapest. If only the published SWF survives, we recreate the course from screen recordings and extracted assets, which costs more. Either way you get an HTML5 course that runs on current browsers and tablets, repackaged for your LMS. Send one course for a free assessment.

Professional human narrators or synthetic voices. Human voice-over sounds better and is worth it for flagship courses; synthetic voice costs much less and makes script updates cheap, which suits compliance content that changes yearly. We record in English and most of the 70+ languages we translate, using native speakers. You approve voice samples before we record anything.

2D — characters, motion graphics, whiteboard style — covers most training and costs far less. 3D earns its price when learners need to see inside something: machinery teardowns, medical anatomy, plant walkthroughs. Plenty of good courses use no animation at all, just clean graphics and interactions. We will tell you honestly if 3D adds nothing but cost to your topic.

Yes. Software simulations — guided show-me, try-me and test-me modes of your application — and scenario simulations, where learners make decisions and see consequences, useful for sales, safety and customer-handling training. Software sims need access to the application or detailed screenshots. Scenario sims need an SME to define the branches. Both are quoted per simulation, not per minute.

Mainly the level of interactivity, then the media. A page-turner with narration is the cheapest. Add custom graphics, interactions and quizzes and the price roughly doubles. Heavy animation, simulations or video put it higher again. Seat time matters less than people expect — a complex 10-minute module can cost more than a simple 60-minute one. We quote per module after seeing the content.

Two formal rounds at each stage — storyboard and built course — are included; that covers most projects comfortably. We collect comments in one consolidated list per round, which keeps things moving and avoids contradictory feedback from different reviewers. Extra rounds are billable, mostly to discourage open-ended churn. Changes to already-approved storyboard content after the build starts are treated as new work.

Yes. We build to WCAG: keyboard navigation, screen-reader compatible text and labels, captions on video, transcripts for audio, sufficient colour contrast. Tell us the requirement up front — accessibility built in from the storyboard is straightforward, while retrofitting a finished course costs more. Some interaction types do not adapt well, so we design alternatives where needed.

Yes — that is where our translation and e-learning teams overlap. We translate the storyboard and on-screen text, re-record or re-synthesize narration with native speakers, adjust layouts for text expansion and RTL languages like Arabic, and republish per language. It is much cheaper with source files; without them, costs rise. We cover 70+ languages.

Standard. Multiple choice, multi-select, drag-and-drop, hotspots, scenario questions, with question pools and randomization if you want them. Scores, pass marks and completion report to your LMS through SCORM or xAPI. You supply the questions or our instructional designer drafts them from the content for your SME to approve. Pass criteria are set however your compliance rules require.

Send us the changes and we update the course — text and image swaps are quick and cheap, re-recorded narration costs more, which is one reason synthetic voice suits frequently changing content. Since you hold the source files, you can also update in-house. There is no compulsory maintenance contract; you pay per update, or we can agree a retainer if updates are regular.

Yes. On final payment you receive the published LMS package and the source — Storyline or Captivate files, graphics, audio, scripts. That means you are not tied to us for future edits. Plenty of vendors keep source files to lock clients in; we think the work should stand on its own.

A typical 30-minute interactive module runs four to six weeks: a week or two for storyboarding and your sign-off, two to three for build and voice-over, then reviews and LMS testing. Simple page-turners are faster; simulations and heavy animation take longer. The single biggest schedule risk is slow review turnaround on your side, so plan reviewer time early.

Send a sample of your content and tell us the audience and LMS. We will propose an approach, a per-module price and a timeline. On most projects we build one short sample module free or at nominal cost, so you judge the actual output rather than a portfolio. We sign an NDA before you share anything, if you ask.