Published on: 23 Jun , 2026
On this page
When teams search for step-by-step guide examples, they usually find polished screenshots from help centers at large enterprise companies. The examples look professional, but they do not show how those guides were created, what format decisions went into them, or whether a team without a dedicated documentation department can produce the same quality.
This article features five step-by-step guides built by real SaaS teams using Trainn. They span five industries and five different audience types, and they demonstrate that the same format (numbered steps, action-triggered screenshots, and AI-generated descriptions) produces effective customer documentation regardless of product complexity or team size.
Every guide in this article was created using Trainn. When you open any of the five examples, here is what you will see: an overview section explaining what the guide covers and when to use it, numbered steps where each step has exactly one UI screenshot captured at the moment of the action and one plain-language description, and a best practices section after the steps.
This is not a help article with screenshots scattered through paragraphs. It is not a video customers have to watch at one speed. It is a structured, step-by-step guide customers can follow one action at a time, at their own pace, on any device. The five examples below demonstrate what this format looks like across five different products, five different industries, and five different audience types.
Proves the format handles compliance-critical complexity
What it does
EDT builds case management software for government agencies, law enforcement, and courts. This guide walks a system administrator through creating a custom field in a case record: naming it, selecting the field type, setting propagation options, and adding values where needed. Custom fields let organizations capture the specific data their jurisdiction requires, making it a foundational configuration task for every new agency setting up the system.
How they built it with Trainn
EDT uses Trainn's portal to deliver a self-serve guide library that prospects and new customers can navigate without a live demo or a CSM walkthrough. An administrator recorded the workflow once, and Trainn captured a screenshot at each action and generated each step description automatically. More than 20 workflow guides are organized in the portal by area, accessible without a login, turning customer education into both a sales asset and an onboarding resource.
What this example proves
EDT's platform is used in compliance-critical environments where a misconfiguration has lasting consequences. The step-by-step format handles that complexity clearly, surfacing critical warnings at the exact decision point where they matter and including an inline reference table for field type options so administrators never have to leave the guide to find an answer. If the format works here, it works for any SaaS product.
Proves the format scales to deep enterprise-technical content
What it does
ServiceNow is the world's leading enterprise ITSM platform, used by Fortune 500 companies to manage IT workflows, incident management, change management, and HR processes. This guide is for developers working in UI Builder. It covers how to add a component, configure it, attach a client script, and wire an event handler. It is technical, developer-facing documentation for one of the most complex enterprise platforms available.
How they built it with Trainn
ServiceNow's documentation team adopted Trainn to solve a throughput problem: a platform with hundreds of configurations and modules, each needing its own guide. The guide linked here is a live example from that documentation program: enterprise-grade technical content produced at a pace that was previously out of reach.
What this example proves
ServiceNow chose Trainn to create their product videos and step-by-step guides. This proves that Trainn’s guide format is professional enough for enterprise use. ServiceNow's UI Builder documentation is about as demanding as technical content gets:multi-layered, code-adjacent steps where one missed configuration breaks the build. The step-by-step format holds up because it scopes each of those actions to its own screenshot and description, so a developer follows a complex sequence without losing the thread between UI and code. If the format can carry developer-facing enterprise documentation at this depth, simpler product workflows are well within range.
Proves the format works without a documentation team
What it does
VeeShift connects healthcare facilities with nurses and aides for flexible PRN shift coverage. This guide is for facility managers and covers the analytics reporting workflow: customizing the report timeframe, setting a date range, and exporting the data. It is a recurring operational task, the kind of workflow that gets completed every week and needs to be fast, clear, and fully self-serve.
How they built it with Trainn
VeeShift was founded in 2022 and has no dedicated documentation team. They created this guide using Trainn and deliver it through a self-serve portal their users can access independently. Screenshots in the guide show actual chart data rather than empty placeholder states, so facility managers reviewing a live report can look at the guide and immediately verify they are in the right view.
What this example proves
A startup with no documentation headcount produced professional, customer-ready documentation for a non-technical audience in a high-stakes industry. The Trainn format does the work a documentation team would otherwise do, and it does so at any company size.
Proves the format replaces answering the same question over and over
What it does
Chargebee is a subscription management and recurring billing platform used by SaaS businesses globally. This guide walks a billing team member through a specific finance workflow: identifying an excess payment in the customer record, confirming the corresponding transaction amount, and processing the refund through the Record Refund modal by selecting the correct payment method (Check, Cash, or Bank Transfer) and documenting it with a reference ID. It is the kind of high-stakes workflow where acting on the wrong record or skipping a verification step creates a reconciliation problem downstream.
How they built it with Trainn
Chargebee is also Trainn's parent company. learn.chargebee.com, their primary self-serve knowledge hub, is powered entirely by Trainn: not as a pilot or a demo, but as a fully deployed production help center serving thousands of Chargebee customers globally. A company that could build any documentation system chose to build their entire customer education experience on Trainn.
What this example proves
Processing a refund for an excess payment is exactly the kind of routine, repetitive request a billing support team fields constantly — the same workflow, explained one more time, on one more ticket. This guide turns that recurring answer into something a customer can follow on their own, step by step, without waiting on support. learn.chargebee.com runs entirely on Trainn and serves thousands of customers this way: the high-frequency "how do I do X" questions are answered once, in a guide, instead of repeatedly, in tickets. For the everyday workflows that drive most of your support volume, that is the difference between a team that scales and one that answers the same question forever.
Proves the format works for the everyday how-to guides in your help center
What it does
This guide is for Trainn users who need to add a new recorded clip to an existing training video. It covers the specific scenario where a product UI has changed and one section of a guide needs to be updated without re-recording the entire workflow from scratch. It is a practical editing task that Trainn users return to regularly as their product evolves.
How they built it with Trainn
Trainn's own help center, help.trainn.co, runs entirely on Trainn. The documentation team uses the same screen recording and guide generation workflow that every Trainn customer uses: record the workflow, let Trainn capture screenshots at each action and generate step descriptions, and publish to the knowledge hub. There is no separate internal documentation system. The product that Trainn sells to customers is the product Trainn uses to document itself.
What this example proves
When the team building the platform uses it to train its own customers, it removes any doubt about whether the format holds up in practice. Trainn’s own help center with videos, step-by-step guides, and interactive guides runs entirely on Trainn - which means every weakness in the format shows up in the docs Trainn's support team depends on daily.
Every structural decision in this guide, including the overview and "when to use" section before the steps, the inline notes for non-obvious decisions, and the best practices at the end. It reflects how Trainn's own team thinks about guiding users through a workflow. It is not a demo built to look good. It is a guide the support and documentation team depends on every day.
Across five industries, five company sizes, and five audience types, three structural decisions appear in every example above.
One action per step.
Every guide scopes each step to a single thing the user must do: one click, one selection, one input. EDT's field creation guide separates naming, type selection, propagation options, and list values into individual steps. VeeShift's reporting guide separates timeframe selection, date range, and export into their own steps. When each step covers exactly one action, users complete the guide without losing their place.
The Screenshot confirms the result
Every screenshot in these guides shows the UI state after the action: what the user should see when they have done the step correctly. It is a verification checkpoint at every step, not a general illustration of the interface. Users who see the right screen know they are on track. Users who see something different know immediately to go back.
Overview before steps, best practices after.
Every guide opens with context: what it covers and when to use it. Best practices follow the final step, where they are meaningful to someone who has just seen the workflow, not at the top where they create a wall of caveats before the customer has reached anything useful.
These are not stylistic preferences. They are what Trainn builds into every guide automatically from a screen recording. Every team in this article arrived at the same structural quality because the Trainn creation workflow makes these decisions the default.
The format every example in this article demonstrates is what Trainn produces from a single screen recording: action-triggered screenshots, AI-generated step descriptions, and the Overview–Steps–Best Practices structure, assembled automatically.
Start a free 14-day Trainn trial →
For more in this series: Step-by-step guide template, how to automatically create step-by-step guides from screen recordings
What does a step-by-step guide from a SaaS company look like?
Each guide in this article follows the same structure: an overview before the steps, numbered steps with one action-triggered screenshot and a plain-language description per step, and a best practices section after. The guide is delivered as an interactive, clickable experience, not a PDF or a help article. Open any of the five links in this article to see the format in production.
How do SaaS companies create step-by-step guides without a documentation team?
All five examples were created using Trainn, which generates guides automatically from a screen recording. The creator records the workflow once, and Trainn captures a screenshot at each action and writes a step description from screen action detection. ServiceNow produces 15–20 guides per week this way. VeeShift and EDT produce professional documentation with no dedicated technical writers.
What types of workflows can step-by-step guides cover?
The five examples in this article span system configuration (EDT), developer tooling (ServiceNow), analytics and reporting (VeeShift), billing operations (Chargebee), and platform editing (Trainn). The format works across technical and non-technical audiences, and companies ranging from a 2022 startup to a Fortune 500 enterprise.
How are step-by-step guides different from screen recordings or videos?
A screen recording requires users to watch at one speed and remember what they saw. A step-by-step guide lets users move one step at a time, with the screenshot as a persistent reference they can stay on as long as needed. Guides are searchable, updatable at the individual step level, and accessible without a fresh link being shared each time.
Trainn is an AI-powered customer education platform that helps SaaS teams create, update, and deliver step-by-step guides at scale, from a single screen recording. Learn more at trainn.co. Last reviewed: June 2026.