What an engagement looks like.
Every program is different, but the shape of the work is consistent. Five phases across roughly twelve to sixteen weeks, with review running alongside the build rather than after it.
We start with what your team needs to be able to do, then work backwards to what they need to know. That produces a curriculum architecture — modules, sequence, dependencies, and objectives — before any content is written.
This phase also collects the things nothing can be built without: your approved claims and reference set, brand assets, LMS and SCORM requirements, review process and turnaround, and a named subject-matter contact. Programs that stall usually stall because these arrived late.
Before the first module, we build the shared design system and the packaging shell: typography, color, layout, interaction patterns, accessibility behavior, and the SCORM wrapper. Once, properly.
It is the highest-leverage step in the project. Everything built afterwards inherits it, which is what makes the later phases fast and consistent instead of accumulating variation.
Modules are built in waves, in dependency order, with foundational material first. Each wave goes to review as it completes.
This is deliberate and it is the difference between delivering on time and not. If ten modules arrive for review simultaneously at the end, the revision volume will not fit in the remaining schedule. Reviewing in waves also means a structural problem surfaces in module two, when it is cheap, rather than in module nine, when it is not.
Medical and accuracy review runs alongside the build from week one — not as a final inspection. Claims, statistics, answer keys, and regulatory framing are checked before content is developed and again as each wave completes.
Your own review committee is the final gate, and we build toward it. The objective is that promotional review receives clean content and returns comments, rather than receiving a draft and returning a rewrite.
Final assembly into a single SCORM package, tested in your LMS environment — enrollment, launch, completion reporting, and score passback verified before handover, not after.
You receive the packaged program and the source files. There is no dependency on us to run it, and no proprietary format holding your content.
Review overlaps the build.
Sequential review is the most common cause of a missed delivery date. Ours runs in parallel by design.
Review turnaround is agreed up front.
We ask for a committed review SLA at kickoff, in writing. It is the single variable most likely to move a deadline, and it is easier to agree at the start than to negotiate at the end.