Full-length AI training videos for employees

Start from what you already have

The operating procedure, the equipment protocol, the induction pack, the safety policy, the vendor contract, the board deck - whatever your staff are meant to know, that is the material. Then answer two questions: how much the audience already knows, and how long they have.

The "Your content" track teaches the document back in plain words: it maps the source, states the key definitions, works through the passages that matter, and ends on consolidation. A typical request: a flying instructor hands over ground-school notes and asks for a preparatory course in that order, in those words.

The "Your content" track asks for the document by name, and the name is what travels into the brief: that picker reads nothing and sends no bytes. If the text of the document itself has to reach the build, attach the document at the Files step.

What the Files step takes, and what it does with it

A request can carry reference files, and the Files step is where they go. It is optional - the default answer is no and it costs one tap. The picker offers PNG, JPEG, WebP and GIF images, PDF, plain text and Markdown, and nothing else: there is no DOCX, PPTX or EPUB path, and a file dragged past the picker is refused with the same sentence.

You can attach up to 5 files, each with your own one-line note. An image is resized in your browser and uploaded to storage only our build worker can read. A PDF or a text file is never uploaded - its text is read in your browser, and only that text travels with your request, where the model that plans your course reads it.

Each file has to be under 10 MB, at most 20000 characters are read out of a PDF or a text file, and what you attach is material to work from rather than an instruction that must be obeyed: the pipeline decides whether each one fits the video it is building.

One document, pitched per team

The level is set per build, so the same manual becomes a beginner course for new starters and an advanced one for the people who already know the vocabulary. Beginner assumes nothing. Intermediate assumes the vocabulary and skips the basics. Advanced goes straight at the hard parts. Expert assumes the literature - no recap and no analogies.

Runtime follows the material, not a template: a new scanner protocol before Monday might be 20 minutes, and a full induction might be 10 hours. A long course gets more modules, not longer ones, and there is no limit on how many training videos you build.

What each employee gets

Every module has one job and says what it is before it starts. The whole course is built to the same structure, whatever the runtime.

• Modules in order, each with its own narration and worked examples drawn from your material.
• A level fixed before anything is built, so nothing the audience already knows is explained again.
• A close on consolidation - recall, and the judgement calls that only make sense once the mechanics are known.
• One video bundle per course, designed to be downloadable and yours to keep.
• A watch page per build, private until you open it.

Who can watch it

Every finished build gets a watch page of its own. It is private to begin with - you, and the team on your account - and you can open it to people you name by email address, or make it public, in which case anyone holding the link can watch it and only then can it be embedded on another site or posted to a social network.

Where the module list comes from

No step asks you to approve a module list before you commit. The runtime you pick is the lever that decides the shape: no module may run longer than 30 minutes, so a longer runtime is split into more modules rather than longer ones, and the deterministic plan for a 30-hour course is 225 modules of 8 minutes.

The chapter titles themselves are decided when the build starts, by a model that reads the whole brief - your own words, every answer you tapped, the track, the level, the runtime, and each file you attached with the line you wrote on it. If that model cannot be reached or answers unusably, the deterministic plan is used instead. Either way the plan lands on the build card in your library, and the event log on that build names which of the two decided it. If particular chapters matter to you, say so in the notes box in your own words.

Changing it when the procedure changes

A change to a finished video is a NEW BUILD, not an edit inside the file you already have. You type the change in plain words, a confirm strip names the cost before anything is spent - the full runtime of that video in minutes, so a 30-hour course is 1800 minutes again - and the new build appears in your library beside the first one.

Nothing in the product edits inside an existing file, so there is no way to ask for one stretch of a video to change and leave the rest alone. The build you have is kept exactly as it is, with its own event log, and the new one is a build of its own.

Early build: an update request spends real minutes and hands back another sample file, not your rendered course. The video you have now is kept exactly as it is, and we will tell you the day real rendering begins.

Pricing is on minutes only, and the level never changes the price. There is no per-plan limit on how many training videos or modules you build.

What this early build does today

ZUQ is an early build, and the part of it that is live is the part that costs money. A request is saved, minutes really are debited, the build runs and its chapter list is decided - and then it hands back a sample file rather than your rendered video. We will say so on this page the day real rendering begins.