--- title: "SaaS onboarding video template — Editable Source | Murmur" description: "Guide a new team through workspace creation, CSV import, owner assignment and its first completed task." canonical: "https://www.murmurtts.com/templates/video/saas-onboarding" --- [Murmur](https://www.murmurtts.com/)/[Video templates](https://www.murmurtts.com/templates/video)/SaaS onboarding video template EDITABLE VIDEO PROJECT / SaaS onboarding # SaaS onboarding video template Guide a new team through workspace creation, CSV import, owner assignment and its first completed task. Download the editable local project and replace its story, scene visuals and voiceover with your own. [Download editable source](https://www.murmurtts.com/downloads/video-templates/saas-onboarding.zip)Read the scene transcript ZIP download · source, narration and captions · MIT template source *28.60 seconds · 1280 × 720 · 24 fpsRelay is a fictional example. These are original motion layouts, not real app screenshots.* OPEN IT. CHANGE IT. RENDER IT. ## Inside the download - project.json, script.txt and storyboard.md for the editable story - render.py, revise.py, requirements.txt and a step-by-step README - One supplied WAV per stable scene ID in audio/ - Finished MP4 preview, poster and WebVTT captions - LICENSE, NOTICE.md and checksum manifests [Download captions separately](https://www.murmurtts.com/video-templates/saas-onboarding/captions.vtt) · [Download the preview MP4](https://www.murmurtts.com/video-templates/saas-onboarding/preview.mp4) ## How this preview was made **Narration** Kokoro · Eric (am_eric) **Generation build** Murmur 1.0.18 / build 19 development app helper **Renderer** Python/Pillow + FFmpeg **Dependencies** python 3.9.6, Pillow 11.3.0, FFmpeg 9.0.2, ffprobe 9.0.2 Rendered assets and one-line revision checks are recorded. Human listening and visual approval are not recorded. This preview used a development generation helper; regeneration with the released Murmur CLI has not been verified. THE STORY, SCENE BY SCENE ## Preview transcript & storyboard Stable scene IDs for revisions 1. 0:00–0:07`onboard-workspace` ### 01 / Create a workspace **On screen:** A workspace field types in the team name and confirms creation. > Welcome to Relay. Create a workspace and give your team one shared place to begin. 2. 0:07–0:14`onboard-import` ### 02 / Bring the work in **On screen:** CSV rows travel into the project table; a completed import counter appears. > Import your project list. Review the rows, then bring the work into your new workspace. 3. 0:14–0:21`onboard-assign` ### 03 / Give every task an owner **On screen:** Owner avatars attach to tasks, followed by a team invitation-ready label. > Assign an owner to each task and invite your teammates. Everyone can see what comes next. 4. 0:21–0:28`onboard-first-win` ### 04 / Finish the first task **On screen:** The first task moves to done and a project completion bar updates. > Complete your first task together. Your workspace is ready for the rest of the week. MAKE THIS PROJECT YOURS ## Customize the saas onboarding 1. 01 ### Define the first successful action Choose the one outcome a new team should reach. The Relay example creates a workspace, imports a project list, assigns task owners and completes the first task; replace it with a real activation journey in your own product. 2. 02 ### Keep the steps in the user’s order Edit project.json and render.py for the workspace, CSV import, owner assignment and first-task scenes so each action begins where the previous action ended. Match the displayed labels to your current interface and use a safe sample CSV. 3. 03 ### Replace each instruction as a separate take Preserve the stable scene IDs. Generate WAV files for the revised scene lines in Murmur and replace the corresponding audio/[scene-ID].wav files. Re-render to measure the new durations and update captions. 4. 04 ### Test with a fresh workspace Walk through the sequence using a new test workspace. Confirm CSV formatting, import results, task-owner permissions and the first completion action. The fictional preview demonstrates a structure, not your product’s actual onboarding. ### Render the downloaded project From the extracted folder, the first command renders the supplied narration. Python 3.9+, Pillow and FFmpeg/ffprobe are required; dependencies are not bundled. Use a new output directory for each render. The revision commands require an available Murmur generation helper and the Kokoro/Eric preset. They were checked with a development helper; read the included README to discover your installed helper and review compatibility first. The helper creates a sibling project and preserves the other scenes’ audio. Edit project.json for app name, palette, scene titles and matching script. Interface labels/drawing logic live in render.py. Text edits need matching replacement audio. Keep stable scene IDs. ``` python3 render.py --output-dir ../render-01 python3 revise.py --scene onboard-import --text "Your new narration sentence." --output-dir ../revision-01 python3 ../revision-01/render.py --output-dir ../revision-render-01 ``` Run from the extracted project directory. Source and output directories must be distinct. Rendering supplied audio needs no Murmur installation; generating replacement narration requires a working Murmur CLI/model. Final archive was extracted and rendered in a fresh folder. Keep the stable scene ID when replacing a line. Regenerate its WAV, then render again so durations and captions follow the new audio. Listen and inspect the resulting preview before sharing it. ## Before you publish - The example interface and product are fictional. Replace names, claims and visuals with your own approved material. - The supplied project is a local source download, not a hosted video editor. Python, Pillow and FFmpeg are separate renderer requirements. - Caption timing follows scene audio. Review readable line lengths and sync after changing narration; automatic timing is not human caption approval. - The preview uses a development narration helper. Released Murmur CLI regeneration and human listening have not been verified for this package. - The template includes one landscape layout. Check a new composition and text size if you adapt it for a vertical or square export. Source license: MIT. Original template source and fictional visual layouts; see LICENSE and NOTICE.md in the archive. The source archive includes usage terms; your replacement assets and selected speech model may have separate terms. Download checksums **preview · SHA-256** `d7caa43c20ba933da74cd9b9a546f404948b560f4ad4624a802c5abb076b7ab8` **poster · SHA-256** `0dba7b6fd25b39ed5bb431f68be2da1de31a8e86cf40241026dde0dc25a6cbd8` **captions · SHA-256** `07afdadc9777b948dd844e6acc0ca0a31223145dfd033b3cf1f1650d42047ebc` **download · SHA-256** `e6d1491048ca7d4799de4897afd0caa7737591ec43167e71ad9af8ccd07a8c5d` REPLACE THE VOICEOVER LOCALLY ## Your script. Your next take. Use Murmur to generate replacement scene narration on Apple Silicon with macOS 15 or later. Export WAV, place it in the project’s scene-audio folder, and use the renderer to rebuild the video. A purchased Murmur license is required; model capabilities and hardware requirements vary. Speech generation is local after setup. The video renderer and any assistant you choose have their own requirements. [Explore Murmur](https://www.murmurtts.com/#product)[CLI & MCP setup](https://www.murmurtts.com/docs/automation) [Connect Murmur to an assistant](https://www.murmurtts.com/blog/resources/connect-murmur-mcp-local-voiceover)[Build a local video workflow](https://www.murmurtts.com/blog/resources/remotion-local-voiceover-mac)[Browse all video templates](https://www.murmurtts.com/templates/video)