An academy that keeps pace with your release notes
Every course you build starts decaying the day it publishes. The UI moves, the flow changes, and re-recording forty lessons is a quarter of work nobody has. So the academy quietly becomes wrong, and customers stop trusting it.
How to create a shipment
Updated today · 11 steps · 2 min read
Open the Shipments workspace
From the left navigation, select Shipments.
Start a new shipment
Click New shipment in the top-right corner.
Choose origin and destination
Search by port code or city name.
The part nobody puts in the job description
Content decay outpaces production
You can record six lessons a month. The product changes twelve things a month. The gap only ever widens.
Video and docs drift apart
The video shows the old flow, the article shows the new one, and the customer trusts neither after they contradict each other once.
Localization never happens
Forty lessons in eight languages is three hundred and twenty assets. It is not that the team said no — it is that nobody could ever say yes.
How teams like yours actually use it
Video and article from one take
Every lesson produces both, generated together, so they can never contradict each other. Learners who prefer to read get the same content as learners who prefer to watch.
How to create a shipment
Updated today · 11 steps · 2 min read
Open the Shipments workspace
From the left navigation, select Shipments.
Start a new shipment
Click New shipment in the top-right corner.
Choose origin and destination
Search by port code or city name.
Fix a step, not a lesson
When a screen changes, re-record that one step. The video, the article, the GIFs and every language rebuild around it. A UI refresh becomes an afternoon, not a quarter.
The whole curriculum, localized
Course, lesson, article and captions in thirty-four languages, with staleness tracked per language so you know what needs re-approval after a change.
Create a shipment · 1:48
6 selectedSee where learners actually get stuck
Per-second retention across a course shows you the lesson everyone abandons and the exact step where they do it. That is a product insight as much as a content one.
Views
8,412
Avg. watched
71%
CTA clicks
1,033
Conversion
12.3%
Viewers drop when pricing config starts. Suggested: move the outcome ahead of the setup.
What a week looks like
- 01
Record the curriculum
One session per lesson, narrated naturally by whoever knows the feature.
- 02
Generate both formats
Video lesson and written article produced together from the same source.
- 03
Publish everywhere
Hosted academy, your LMS, the help center, and in-product at the moment of need.
- 04
Keep it honest
Staleness flags on every asset the product change touched, with one-click rebuild.
What changes, measured
- −51%
- Onboarding support tickets
- 6 langs
- Published per lesson, by default
- 4×
- Lessons published per quarter
- +29%
- Course completion rate
The written guides are the sleeper feature. Every video we publish also becomes a help article, in six languages, with screenshots that are always current. Support ticket volume on onboarding fell by half.
Common objections
Yes — SCORM and xAPI packages export from any course, and videos can be served by direct link or embed. Teams using Docebo, Skilljar, Thought Industries and WorkRamp typically publish straight from DemoRiff into the LMS via the API.
Yes. Everything is transcribed and semantically indexed, so a search for “change a shipment after it has departed” finds the lesson and jumps to the timestamp where it is explained — not just the lesson title.