A deck is a talk, not a course

The deck was built for a room. Someone stood next to it and said the important parts out loud. The speaker notes are thin or missing, slide fourteen has the rule and slide fifteen the exception, and nothing on any slide says what a learner should do differently on Monday.

Putting the deck into the LMS with a quiz at the end gets you a completion record, not a change in behaviour. Turning it into a module means deciding which slides matter, finding out what the presenter said that never made it onto them, building practice for the decisions people will face, and writing an assessment that checks the behaviour. On an authoring tool, that is your team's hours in the tool, slide by slide.

And the request usually comes with a date. On Katie's homepage it reads: "New hires start next week and we need training on the new pricing rules. Here's the deck." Katie takes on that job. You brief her in plain conversation, she does the design and the production, and your team approves at each step. The guide to the AI instructional designer explains the role in full.

What Katie does with the deck

She reads the deck and asks what is missing

A deck tells Katie the content and the order someone chose to present it. It does not tell her the outcome, the audience or the mistakes people make. She helps define those, then writes the strategy and a training plan for your approval. Where the slides leave gaps, your subject-matter experts provide the knowledge, answer her questions and review the drafts. Katie runs that data gathering herself.

She drafts the outline and the practice first

Before anything is built, Katie proposes the objectives and the structure. In the homepage demo her first reply to the new-hire request is: "I drafted the training outline and two practice scenarios. Take a look, and once approved, I'll start building." You review the outline, not a finished course you would have to unpick.

She builds the module

From the approved outline she produces the complete training: text, video, practice, simulations and assessments. For a deck that means the content becomes lessons rather than slides, the talk-track becomes presenter video or a short animated explainer, and the decisions become scenarios. Alt text, captions and audio description are part of every training.

She revises in chat

Your team and your experts give feedback in plain English on Teams, Slack or WhatsApp, and Katie makes the changes right away until it is right.

She publishes to your LMS

The approved module goes out as a SCORM package to the LMS you already have, or as a direct link. The SCORM for your LMS page covers the details.

A worked example: the pricing deck for new hires

This is the new-hire request from Katie's demo on the homepage, laid along the working morning the homepage shows. Nobody on the team opens an authoring tool.

The brief

The L&D manager forwards the request as it arrived: "New hires start next week and we need training on the new pricing rules. Here's the deck." The deck goes to Katie with the message.

Defining the need

Katie asks who the new hires are, which pricing decisions they will face in their first weeks, and where the rules are most often misapplied. From the answers she defines the outcome, the audience and the key behaviours. She replies with the training outline and two practice scenarios, and the preview card in the team's chat reads "Pricing rules, new hire training, training outline, review outline." The manager reviews the outline, asks the pricing lead to check the two scenarios, and approves.

Building it

Katie takes on the production end to end. The module takes the shape the portfolio calls an onboarding journey: clear priorities, relevant practice and a path that helps new starters find their feet. The two practice scenarios become branching scenarios, where learners weigh the options, see the consequences and try again with feedback. The parts the presenter used to say out loud become a short presenter-led video with one clear learning goal.

Feedback in chat

The pricing lead reads the draft and sends notes in the chat. Katie makes the changes right away and shows the new version. The team reviews the complete module and approves it for publishing.

Publishing before the start date

Katie handles the SCORM export. The team packages the module for the LMS, or shares a direct link, and the new hires start the following week with the module live.

The same module in another language

In the homepage's global rollout demo the next request is "We need this training program in Spanish too." Katie answers "¡Perfecto! Latin America or Spain? I'll adapt the language and cultural nuances accordingly." The local team reviews the adaptation before rollout.

What your team approves, and when

  • The outline and the practice scenarios, before production. This is the step the demo shows. Nothing is built until the structure is right.
  • The complete module, before publishing. Your team reviews it against your own quality bar. Katie learns your terminology, business context and standards from each approval.
  • Every later change. A new language, a version for one department or a rule change is prepared for review and published when you decide.

The deck stays yours, and so does the module, including 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.

What the learner gets

Not the slides in a player. New starters get a guided path with clear priorities, practice built around the decisions they will meet, and an assessment that checks they can apply the rules rather than recite them.

Inside the training, learners can talk to Katie. She asks questions, role-plays realistic scenarios and gives feedback grounded only in the material your team approved. After launch she analyses learner errors, questions and drop-offs and recommends fixes for you to review and publish.

Katie works in more than 20 languages with full right-to-left support, so the same module can go to every team with a local reviewer in the loop.

What it costs in workload

Katie is priced on workload, never per creator or learner seat. One credit is one cent, and she shows the exact cost before every action.

On the rate card, a typical training is 2,555 credits: a 14-message design interview at 30 credits a message, one build of up to two chapters at 2,000 credits, five AI edits at 15 credits each and three images at 20 credits each. Turning the talk-track into video is priced by the minute: AI presenter video is 400 credits a minute, and an animated explainer with no presenter is 150 credits a video. Another language is 500 credits a translation. SCORM export and hosting cost no credits.

The listed plan is $1,000 a month for 100,000 credits. The pricing page has the full rate card and an estimator you can set to your own month. The pilot is eight weeks with one team, on one real training, from brief to publish.

Or bring the deck to a 30-minute scoping call.