For companies · L&D, training providers, agencies
The material has been written. The course has not.
This page is for internal learning and development teams, and for training providers and agencies producing courses on behalf of clients. Both know the same picture: the handbooks, work instructions and training material exist — and still no course comes out of them, because every attempt starts from scratch.
What eCourse takes on: the stretch from the document you already have to a finished course package — in six fixed stages, with you at exactly the points where something is decided.
What teams use it for
Three jobs that come back every year
What separates these from a one-off course project is not the subject matter but the repetition: the same structure, new source material every time.
Onboarding
What a new colleague needs in the first weeks is usually already written down somewhere — in onboarding handbooks, process descriptions, safety briefings. eCourse reads those files and turns them into modules, lessons and learning objectives you can still change before anything is produced.
Mandatory and refresher training
This kind of content does not go stale at random — it goes stale when the source document changes. That is exactly where eCourse starts: you upload the new revision and have the course generated from it again, instead of chasing the changes through it by hand.
Client projects
Training providers and agencies work for several clients at once. Teams, projects and courses model that separation: one project per client, holding that client's courses — and consumption is measured per team.
The way in
Your material is the starting point
There is no empty prompt box at the start — there is what your organisation has already written. Files go straight into storage, are activated once they have arrived durably, and are converted into readable text one by one.
- Every file gets its own conversion job and its own status
- Knowledge is extracted per file first, then aggregated into one course-scoped knowledge base
- The course design comes out of that knowledge base — not out of a model's general knowledge
Repeatability
The same structure, course after course
When twenty courses a year go out, the hard part is not any single course — it is the spread between them. eCourse holds the structure steady and leaves the editorial judgement with you.
Guidance
You record the brief, the context and the target audiences as free text. Guidance is versioned and only ever appended to, never overwritten — the history stays fully readable.
Course design
Modules, lessons and learning objectives can be edited by hand. Every edit is stored as a new version and overwrites nothing.
Production
Each lesson runs as its own job, and each lesson can be regenerated on its own. Video runs in two phases: the transcript comes first, you approve or rewrite it, and only then is it rendered.
Organisation
Separation, roles and consumption
A team holds projects, a project holds courses. Those three levels are the dividing line — between departments as much as between clients.
Roles, not conventions
Members join by invitation and carry a role: Owner, Co-Owner, Admin or Member. Every action goes through the same authorization check — there is no way around it.
Consumption per team
Metering runs across eight dimensions: AI calls, storage, projects, courses per project, pages per file, job runs, video minutes and OCR pages.
Budgets that only tighten
A team or a project can be held tighter than the plan allows — never wider. More headroom comes from purchasing an addon, not from a setting.
Bring your own key
Model spend stays on your account
Organisations that already hold contracts with AI providers do not want to sign them a second time. In the team settings you register your own credentials: a default provider for text and one for video, with a per-stage override underneath.
- Credentials are validated against the provider when you register them, and can be rotated.
- A provider catalogue decides which provider, with which model, may serve which stage at all.
- Where your plan requires your own key, we stop metering that dimension altogether.
This is why the price ladder runs backwards. The smallest plan costs more because the AI is bought for you inside it. From the Team plan on you bring your own keys and pay for the software only.
See pricing
The result
A package for your LMS — and that is where eCourse stops
The last stage renders, assembles and uploads. Out comes an LMS-ready ZIP package with one folder per module; each lesson is an HTML file — for text, quiz or transcript — or an MP4 file for video. The download link is deliberately short-lived.
What eCourse does
Authors courses: turns your documents into modules, lessons, learning objectives, texts, videos and quiz questions — through to a distributable package.
What your LMS does
Delivers courses: assignment to staff, learner progress, records of completion. eCourse does none of that, and does not pretend to.
The handoff sits exactly on that edge: the package is imported into your learning platform — for example into ELP, the learning platform from the same house. eCourse is part of TyskTech's ELP ecosystem, built in Hamburg.
What happens in the Publishing stage ›Common questions
What procurement and the business ask first
- How do we keep departments or clients apart?
- Through the three levels team, project and course. In practice each client or department gets a project of its own, holding its courses. Who may see and do what follows from the role in the team — checked at the same seam as every other action.
- A work instruction changed — do we have to rebuild the course?
- You upload the new revision as a source file and have the course generated from it. Afterwards you can pull the course design back by hand wherever something should stay; every edit is stored as a new version. Individual lessons can be regenerated without repeating the whole course.
- Can consumption be capped per department?
- Downwards, yes. A team or a project can be held tighter than your plan allows — never wider. If you want more headroom than the plan provides, that comes from purchasing an addon, not from a setting inside the product.
- Do the model calls run through our own provider accounts?
- From the Team plan on, yes. You register your credentials in the team settings and bind them to individual pipeline stages; that stage's calls then go through your own account with the provider. Credentials are validated against the provider when registered and can be rotated at any time.
- Does eCourse assign courses to staff and record completion?
- No. eCourse authors courses and hands over a package; assignment, learner progress and records of completion belong in your learning platform. If you do not have one yet, ELP from the same house is the obvious next step.
Not quite the right page? For Education · For Creators
Start with your own material.
Create an account, pick a plan, upload your first source documents — the LMS-ready ZIP package comes out of exactly the pipeline you have just read about.