FAQ
Answers before you ask.
Common questions
01How long does a project take?
It depends on the length and complexity of your course, and how much existing material you have. As a guide, a short, focused module typically takes [1–3 weeks], a mid-sized course [3–6 weeks], and a larger, fully bespoke course [6–12 weeks]. We'll agree a realistic timeline on our first call and confirm it in the Learning Specification before work begins.
02What do you deliver — is it LMS-ready?
Yes. We deliver published packages ready for your LMS, plus the editable source files. Standard outputs include SCORM 1.2, SCORM 2004 and xAPI — we agree the right option for your platform before build.
03Which authoring tools and LMS do you support?
We build primarily in Articulate Storyline 360 and Rise 360, with PowerPoint and print for blended materials. We publish to standard LMSs including [Moodle, Totara, SuccessFactors, Cornerstone and others] — if yours isn’t listed, just ask.
04Will you sign an NDA?
Yes, happily. We work with confidential source material regularly and can sign your NDA, or share our own mutual NDA, before any detail is exchanged.
05What’s the smallest project you’ll take?
We don’t have a hard minimum, but single-module work typically starts at around [£X / Robin level]. For anything smaller, we’ll be honest if a template or off-the-shelf option serves you better.
06What do you need from us to start?
As little as a rough goal and any existing source material. For scoping it helps to know: who the learners are, what should change, what content already exists, and any constraints (deadline, budget, platform, accessibility requirements).
07How do revisions and sign-off work?
Every project has defined revision rounds, agreed up front in the Learning Specification. You sign off the blueprint (objectives, structure, assessment) before production begins, so scope and feedback stay predictable — no scope-creep surprises.
08Can you work with existing content or half-built courses?
Yes. We regularly take existing decks, documents, or part-built Storyline files and rebuild or finish them — including improving structure, accessibility and interactivity.
09Who owns the source files?
You do. Both the finished package and the editable source files are handed over and are yours to keep, edit and reuse — no lock-in.
010What does accessibility look like in practice?
Accessibility is built in from the start, not bolted on: captions and transcripts, keyboard navigation, screen-reader support, colour contrast and readable structure. We work to [WCAG 2.1 AA] and confirm any specific standard you need during scoping.
Still wondering something? We’ll answer honestly — even if the answer is “we’re probably not the right fit.”
Ask us anythingReady to get started?
Book a short call. No obligation. We'll talk through what you need.
