← All posts

Customer education: the guide for SaaS teams

Customer education for a SaaS team with no education hire: what it includes, who owns it, how to start with your next release and how to tell it works.

Ryan StevensRyan Stevens November 17, 2026 · 11 min readTutorials
Customer education: the guide for SaaS teams

On this page

If your SaaS team has no education hire, tie customer education to the release. For each release that changes what customers do, make a tutorial for each new task and the matching help docs. Add a short launch video when the release is big enough to announce. Give the work one named owner and publish it on launch day.

For a SaaS team, customer education is the work of teaching customers how to use your product, so they can get the result they bought it for without having to ask you.

Before writing this, we read four of the guides that ranked on Google for "customer education" on 14 November 2026, from Trupeer, Smith.ai, CloudShare and FreshLearn. Three of them mention product updates or new features, and Trupeer's comes closest to what we cover here: it says to review your education content whenever you ship. None of the four plans the work around a release, and none says who should own it at a company where it's nobody's job. At 20 to 200 people, shipping every week or two, you need both settled before anything gets made.

What is customer education?

For a SaaS team, customer education is the planned work of teaching customers how to use the product. It's the videos, tutorials, help articles and courses you make so customers can do things themselves. It covers new customers learning the basics and existing customers learning what changed. Some companies define it more broadly and include training programs, certifications and communities. People also call it customer training.

Support, onboarding and release notes sit close to it, and each has a different job.

WorkIts jobWhen it happens
Customer educationTeaches customers how to use the product, before they get stuckAll the time, and again at every release
Customer supportAnswers one customer's question after they get stuckWhen a ticket or a chat comes in
Customer onboardingGets a new customer set up and to a first resultThe first days and weeks of an account
Release notesTell customers what changedEvery release

What is product education?

Product education is our name for this work at SWFTMENT. We use it to mean the same thing as customer education: teaching the people who use your product how to use it.

What does customer education include?

For a SaaS product, customer education comes down to four pieces: a launch video, tutorials, help docs and, when partners or new customers need a full path, an academy level.

PieceIts jobWho it's forHow we size it at SWFTMENT
Launch videoSays what's new in the release and why it mattersExisting customers, on launch day60 to 90 seconds
TutorialsShow one task each, step by stepA customer who wants to do the task now3 minutes or less each
Help docsGive the same steps in writingPeople who'd rather read, and anyone searching your help centerMatched to the tutorials, so the video and the page say the same thing
Academy levelTakes a learner through a set of lessons in order, from first login to a first real resultNew partners and new customers5 to 6 videos of 5 minutes or less, each with a matching article

The first three belong to a release. The academy level doesn't. It's for people who have to learn the whole product from the start, such as partners who have to learn it and start selling it.

In-product education is the same teaching placed inside the product: a tooltip on a new button, a checklist in a new account, a link from a feature to its tutorial. It needs a tutorial or an article behind it to point to, so make those first.

If nobody owns customer education yet, start with the first three in the table. Webinars, eBooks and certifications can come later.

Why tie customer education to the release?

Tie customer education to the release because a release is when customers have something new to learn. It's also when some of what you taught them before stops being right. If the education isn't part of the release, a feature can ship as one line in the release notes while its tutorial waits for someone to have time.

A release is also the right size of job for a small team, for three reasons:

  • The scope is already written down. The release notes list what changed, so they're also the list of what to teach.
  • The date is already set. Nobody has to invent a deadline for the education work.
  • The job is small. The example release in step 2 needs two tutorials, two help articles, one update and one launch video.

Working by release also helps with content going out of date, because the old pieces get checked every time you ship.

You don't need goals, personas or a learning platform in place before you start.

Who should own customer education?

One named person should own customer education, even when two teams share the work. At a company of 20 to 200 people with no education hire, that person already has another role, so pick whoever is closest to the release: the head of marketing, the founder, the support lead or the product manager. If you're the head of marketing or the founder, ask first whether it should be you.

Possible ownerWhat they already haveWhat they'll need
Head of marketingThe launch plan, the customer email list and the company's voiceTest access, and someone who knows the product to check the steps
FounderThe reason the feature exists, and the authority to put education on the release checklistTime. This works for a few releases, then needs handing on
Support leadThe questions customers really ask, and the help centerA say in the launch plan, and help with video
Product managerThe release notes, the screens and the dateHelp with scripting and recording

Owning it doesn't mean making all of it. The owner runs the six steps for each release, or briefs whoever does.

You can also hand the making to an outside partner. That's the work we do at SWFTMENT: for each release, we make a launch video, step-by-step tutorials and the matching help docs, and we keep them current as the product changes. You still approve the script and everything we send.

How do you get started with customer education?

Get started with customer education at your next release, and make only what that release needs. There are six steps.

  1. Name one owner.
  2. List what the release asks customers to learn.
  3. Choose the smallest set of pieces.
  4. Make each piece inside the real product.
  5. Check every step, then publish on launch day.
  6. Log what you made and check it at the next release.

Step 1: Name one owner

Pick one person and tell the team. Put their name on the release checklist next to the release notes. If you can't name anyone, fix that before any video gets made.

Step 2: List what the release asks customers to learn

Read the draft release notes and sort each change by what it asks of a customer: a new task, a changed screen, news big enough to email everyone about or nothing they'll see.

What the release doesWhat to make
Adds a task customers will want to doA tutorial and a help article for each new task
Changes a screen that's in a tutorial or an articleAn update to those pieces
Is big enough that you'd email every customer about itA launch video as well
Fixes bugs, or changes nothing a customer seesNothing new

Take an invented release that adds scheduled reports.

Change in the example releaseWhat a customer has to learnWhat to make
New: send a report by email on a scheduleHow to set a scheduleA tutorial and a help article, "Schedule a report"
New: pick who receives itHow to add and remove recipientsA tutorial and a help article, "Choose who gets a report"
Changed: Export moved into the Share menuWhere Export wentAn update to the existing "Export a report" tutorial and article
The release as a whole, which you'd announce to every customerWhat's new and why it mattersOne launch video

Step 3: Choose the smallest set of pieces

Make only what the release calls for, and keep the launch video for a release you'd email every customer about. If you ship every week, you shouldn't be making one every week.

If that's still more than you can finish before launch, cut the number of tutorials and keep the checking. Make the tutorial for the task a customer has to do first, and add the others in the days after launch.

Step 4: Make each piece inside the real product

Get test access to the release and write every tutorial script while you click through it. Don't write from the spec. You can start recording as soon as you have access, but don't finish a piece until the screens have stopped changing.

That takes dates. At SWFTMENT, every release runs on the same clock. We agree the video script 14 days before launch. Test access and release notes arrive 10 days before, and we start recording the screens. Six days before, the screens stop changing and we finish.

Write each tutorial script first, then the help article from the same script, so both use the same names for the same buttons. The article also needs what the video can skip: who can do the task, what has to be set up first and what to do when a step fails.

If you want a link to the tutorial inside the product, ask for it now. Someone has to build it before the screens stop changing.

Step 5: Check every step, then publish on launch day

Before anything goes out, someone follows every step in the real product, clicking what the video and the article say to click. If a step doesn't match, fix the piece. At SWFTMENT, an editor does this before anything goes live.

Then publish everything together, on the day the release ships, where customers will look:

  • in the release notes, with a link to the launch video
  • in the help center
  • next to the feature inside the product
  • in the email that announces the release

Step 6: Log what you made and check it at the next release

Keep one list with a row for each piece: the screens it shows, where it's published and the release it was last checked against. A spreadsheet is enough.

At the next release, read the release notes against that list before you plan anything new. Whatever the release touches goes on the update list, so the older pieces get checked too.

What about the features you've already shipped?

Working by release only teaches what's new. Everything you shipped before today still has no tutorial, and a new customer has to learn all of it.

Don't stop to build the whole library. At each release, add one piece for the product you already have: the task that comes up most in your "how do I" tickets, or in help center searches that found nothing. If new customers get stuck at the start, begin with the tasks a new account has to do first.

Once that set is big enough to need an order, you have the start of an academy level.

How do you tell if customer education is working?

You can tell whether customer education is working without a data team. Count four things in tools you already have: help center searches with no result, support tickets that begin "how do I", use of the new feature and tutorial views. None of them proves the education caused a change, because you can't cleanly separate what a tutorial did from what the feature did by itself.

What to countWhere to find itWhat to look for
Help center searches with no resultThe search report in your help center toolWords from the release that found nothing
Tickets that begin "how do I"Your support inbox, searched or tagged by featureHow many arrive in the two weeks after launch, and which question repeats. More tickets can also mean more people are trying the feature
Use of the new featureYour product's own analyticsHow many accounts used the feature in its first 30 days, next to the same number for the last feature you launched
Tutorial viewsYour video hostViews set against the number of accounts that have the feature, and where viewers stop

Some tools report the first and the last of these for you (all pages read on 14 November 2026):

Many searches with no result are tasks with no article yet. Some aren't: Help Scout's page says some are misspellings or other words for an article you already have, and Intercom's says search terms can contain typos. Check before you write a new article.

Write the four numbers down for every release, in the same sheet as the list from step 6. One release tells you little. After several, you can see whether "how do I" tickets for new features are going up or down, and which tutorials nobody opens.

Questions people ask about customer education

Do you need to hire someone for customer education?

You don't need to hire anyone to get started. Someone who already works on your releases can own customer education next to their main job, and an outside partner can do the making. A dedicated hire makes sense once the work is more than that person can fit around a release.

Can an AI video tool do customer education for you?

A tool can make the video. Whichever tool you use, someone still has to decide what the release needs, follow each step in the real product before it's published and update the video when a screen changes.

What are some customer education examples for a SaaS product?

Customer education examples for a SaaS product include a launch video for a new integration, a tutorial on inviting a teammate, a help article on changing a billing plan and a tooltip that links a new button to its tutorial. For partners, an example is an academy lesson on running a first client demo.

Do you need a learning platform to start customer education?

No. A help center and a video host are enough for the launch video, the tutorials and the help docs. A learning platform becomes useful when you build an academy, where lessons run in a set order and you want to see who has finished them.

Ryan Stevens
Ryan Stevens Founder of SWFTMENT. We make the launch video, tutorials and help docs for each release, and keep them current.
About SWFTMENT →

Rather have it done for you?

Book a free 20-minute release review. We look at your next release and what your customers need to learn it. No pitch.

Book a release review