You do not need a new platform

Most L&D teams already have an LMS, and the people who run it have no appetite for another platform, another integration project or another place learners have to log in. The worry with any new vendor is that the training ends up somewhere else.

Katie does not ask you to replace your stack. The homepage says it plainly: you do not need another tool, you need more working hands. She does the instructional design and production, and the finished training goes into the LMS you already have as a SCORM package, or out as a direct link when you do not need an LMS at all. SCORM export and hosting cost no credits.

This page covers the last step of the job: how publishing works, what it looks like on a real request, and what your team approves along the way. For what happens before that step, start with PDF to course or PowerPoint to training, or with the guide to the AI instructional designer.

How publishing works

Only after approval

Nothing is exported until your team has approved the complete training. The approval points are fixed: the objectives and structure before production, the complete training before publishing, and every later change.

As a SCORM package

Katie handles the SCORM export. Your team packages the training for the LMS and uploads it the way you upload any other course. No integration project, and nothing changes for the people who administer the platform.

As a direct link

When a piece of training does not belong in the LMS, or you want it in front of people now, Katie gives you a direct link for instant sharing. The homepage's working morning ends either way: package it for the LMS or grab the link.

Localised versions

Katie works in more than 20 languages with full right-to-left support. Each adaptation is reviewed by the local team before rollout, and each one is published the same way as the original, as a package or a link.

Updates

When a rule changes, you tell Katie what changed. She updates the affected lessons, videos and practice activities, and tells you which other courses carry the old rule. Your team reviews the new version and publishes it. The packages in your LMS stay current because the update is Katie's job, not another ticket in your queue.

A worked example: from brief to a package in the LMS

This is the working morning on Katie's homepage, followed by two of the requests from her demo, so you can see the whole path to the LMS and back.

8:00: a messy request

A department head asks for new training. The L&D manager takes their brief notes and hands them straight to Katie.

8:30: the need, defined

Katie helps define the outcome, the audience and the key behaviours, then writes the strategy and the training plan. The manager approves it.

9:00: Katie builds it

She takes on the end-to-end production: the text, video, practice, simulations and assessments, delivered as a complete training program.

9:30: feedback in chat

The team and the subject-matter experts give feedback in plain English on Teams, Slack or WhatsApp. Katie makes the changes right away until it is right, and the team approves the complete training.

11:30: into the LMS

Katie handles the SCORM export. The team packages the training for the LMS, or grabs a direct link for instant sharing. By lunch the training is live where learners already go.

Later: a version in Spanish

"We need this training program in Spanish too." Katie asks "Latin America or Spain?" and adapts the language and cultural nuances accordingly. The local team reviews the adaptation and it goes into the LMS as its own package.

Later still: a rule changes

"The approval limit changed this morning. Update it in the policy training." Katie replies: "Done! The update is ready for your approval. I also found the old limit in the Manager Onboarding and Procurement courses. Should I prepare updates for those as well?" The team reviews each update and publishes the new packages, and the LMS is current again without anyone opening three courses to check.

What your team approves, and when

  • Before production: the objectives and the structure.
  • Before publishing: the complete training, reviewed against your own quality bar. This is the gate in front of every SCORM export.
  • Every later change: an update, a new language or a department version, each prepared for review and published only when your team decides.

You own your source materials and the finished programs, including the packages, and keep them if you stop working with Katie. Before rollout, Trust Katie starts a security review covering your content, learner data, the AI providers involved and your security requirements, so your IT and privacy teams can sign off before the first package is uploaded.

What the learner gets

Learners open the training in the place they already know, with the login and the records they already have. What they find is a complete program rather than a document: text, video, practice and assessment, designed on expert instructional design principles and learning science, with alt text, captions and audio description included in every training.

Katie's work does not stop at publishing. The homepage describes an AI instructor inside the training, who asks questions, role-plays scenarios and gives feedback grounded only in approved material, and describes how Katie analyses learner errors, questions and drop-offs to recommend improvements for your review. Ask on the scoping call how those work with your own LMS setup.

What it costs in workload

Publishing costs nothing extra. On the rate card, hosting, grading, SCORM export and help are included at no credit cost, every training, always. Credits pay for the work before that step: design, build, edits, video and translation. One credit is one cent, and Katie shows the exact cost before every action.

Two rate-card lines matter most on this page. A translation is 500 credits a language, so a Spanish version of an approved training is a known number before you ask for it. A learner completing a chapter, with the AI tutor included, is 25 credits a learner a chapter. The listed plan is $1,000 a month for 100,000 credits, and the pricing page shows that budget as a worked month: 20 trainings, 40 minutes of presenter video, 10 translations, 2 software simulations and 500 learners completing a two-chapter training. The same page has an estimator you can set to your own volumes.

Or bring your LMS questions to a 30-minute scoping call.