One process to teach, and no appetite for an integration project

The request is small. A new screen in the billing system, a changed step in the ticketing tool, one process that a team has to do correctly from next week. The guide exists, with screenshots, because someone wrote it for the rollout. What does not exist is a way for people to try the process before they do it for real.

The usual answers are both too big. Training software that connects to the live system turns a small need into a setup project, with IT, security and a budget line attached, and that can make it impractical when you need to teach one process quickly. A deck of screenshots teaches people what the screens look like, not how to do the task, and their first attempt happens on the real system with real customer data.

Katie takes the middle path. Give her the user guide with its screenshots and she creates an interactive walkthrough in about five minutes, with no integration with your live operational system. Employees practise the process on screenshot-based screens, and an AI guide answers their questions as they go. This page is about the job as you feel it: what Katie does step by step, a worked example, the approvals and the cost. The system training page is the product page for the walkthrough itself, and the guide to the AI instructional designer explains the role behind it.

What Katie does with the guide, step by step

You prepare the screens

Start with the instructions and screenshots you already have. Before uploading, your team removes any sensitive data you do not want in the training, by hand. That is the one step that stays with you, and it is what lets you build a practice environment without connecting it to the operational system or using real customer data.

She turns the guide into a walkthrough

The steps in the guide become guided tasks on the screenshot-based screens, in the order the process runs. The portfolio calls the format a software walkthrough: a practical introduction to a new tool, where guided tasks and realistic practice help people connect each feature to the work they need to get done. Katie creates the walkthrough in about five minutes.

She can build it into a course

When the process is part of a bigger change, the walkthrough does not have to stand alone. Katie builds complete training programs with text, video, practice, simulations and assessments, so the walkthrough can sit inside a course that also explains why the process changed and checks that people can apply it.

She stays with the learner

While employees practise, Katie is there as their AI guide. She explains and answers questions in real time, including in Hebrew, like a trainer sitting beside them, instead of leaving them stuck or waiting for help.

Your team keeps it current

Processes change. Your training team can edit and update the walkthrough as the process changes, or tell Katie what changed and review the update she prepares. Either way a focused training need stays a focused training need rather than becoming a full implementation project.

It publishes like any training

The approved walkthrough goes to your existing LMS as a SCORM package, or out as a direct link. The SCORM for your LMS page covers that step.

A worked example: a user guide into a practice walkthrough

This is the walkthrough the system training page describes, laid along the working morning Katie's homepage shows: a messy request at eight, training live by lunch.

The brief

A department head asks for training on one process in a system their team uses, and sends the user guide with its screenshots. The L&D manager hands the guide and the brief notes straight to Katie.

Preparing the screens

Before the screenshots go to Katie, someone on the team goes through them and removes the sensitive data they do not want in the training. The screens that are left show the process and nothing else.

Defining the need

Katie asks the questions a designer would ask. Who does this process, what should they be able to do afterwards, and where do people get stuck today? From the answers she defines the outcome, the audience and the key behaviours, and writes the training plan. The L&D manager approves it.

Building the walkthrough

Katie creates the interactive walkthrough in about five minutes. Learners will work through the process on the screenshot-based screens, step by step, without taking any real action in the operational system. The preview lands in the team's chat.

Feedback in chat

The person who owns the process tries the walkthrough and sends notes in plain English on Teams, Slack or WhatsApp: a step out of order, a label that changed in the last release. Katie makes the changes right away and shows the new version. The team approves the complete walkthrough.

Publishing

Katie handles the SCORM export. The team packages the walkthrough for the LMS, or grabs a direct link and shares it with the people who start next week.

The first learners

An employee works through the process on the practice screens, gets to a field they do not understand, and asks Katie. She explains it in real time, including in Hebrew, and they carry on.

Later, the process changes

A release moves a button and adds a step. The training team updates the walkthrough, or tells Katie what changed and reviews her update. Nobody books an integration project.

What your team approves, and when

  • The screens, before anything is uploaded. Your team decides what the screenshots show and removes what they should not. This step is yours, and it happens first.
  • The objectives and the structure, before production. Katie proposes them from the guide and your answers. Nothing is built until you say the plan is right.
  • The complete walkthrough, before publishing. The process owner tries it and your team approves it against your own quality bar. Every later change is prepared for review and published only when you decide.

You own the guide, the screenshots and the finished walkthrough, 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

A place to try the process before it counts. Learners work through the real steps on screens that look like the system, without taking real actions in it and without seeing real customer data. Getting it wrong costs nothing, so they can get it wrong until they get it right.

While they practise, Katie is there as their AI guide. She explains and answers questions in real time, including in Hebrew, so a learner who is stuck asks rather than waits. Alt text, captions and audio description are part of every training, and Katie works in more than 20 languages with full right-to-left support.

What it costs in workload

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

The rate card has one line for this job: a software simulation from screenshots or a recording is 500 credits a simulation. If the walkthrough sits inside a course, the build is priced as a training: one build of up to two chapters is 2,000 credits, and a typical training on the card's own arithmetic is 2,555 credits, with the design interview, edits and images included. On the learner side, a learner completing a chapter, with the AI tutor included, is 25 credits a learner a chapter. SCORM export and hosting cost no credits.

The listed plan is $1,000 a month for 100,000 credits. The pricing page shows that budget as a worked month that includes 2 software simulations alongside 20 trainings, and it has an estimator you can set to your own month. If you would rather prove it first, the pilot is eight weeks with one team, on one real training, from brief to publish.

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