<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Ali | Explainalab on Medium]]></title>
        <description><![CDATA[Stories by Ali | Explainalab on Medium]]></description>
        <link>https://medium.com/@aliislive42?source=rss-8abc38f4d326------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*mK1iQQ2BEkPgSFqr</url>
            <title>Stories by Ali | Explainalab on Medium</title>
            <link>https://medium.com/@aliislive42?source=rss-8abc38f4d326------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 12:33:00 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@aliislive42/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Onboarding Videos That Reduce Support Tickets]]></title>
            <link>https://medium.com/@aliislive42/onboarding-videos-that-reduce-support-tickets-61e15b73097a?source=rss-8abc38f4d326------2</link>
            <guid isPermaLink="false">https://medium.com/p/61e15b73097a</guid>
            <category><![CDATA[customer-onboarding]]></category>
            <category><![CDATA[explainer-videos]]></category>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[saas]]></category>
            <category><![CDATA[video-marketing]]></category>
            <dc:creator><![CDATA[Ali | Explainalab]]></dc:creator>
            <pubDate>Mon, 16 Nov 2026 14:04:03 GMT</pubDate>
            <atom:updated>2026-11-16T14:04:03.548Z</atom:updated>
            <content:encoded><![CDATA[<p><em>Why the most useful video you make might be the one new users watch after they sign up</em></p><p>Most SaaS teams put all their video energy into the homepage. That makes sense. It’s the first impression, and it’s where a good explainer earns its keep.</p><p>But a lot of the confusion that costs you customers doesn’t happen on the homepage. It happens in the first session after sign-up, when someone is staring at an empty dashboard trying to work out what to click first. If they can’t figure it out, one of two things happens: they open a support ticket, or they quietly leave and never come back.</p><p>I’m Ali. I make SaaS explainer videos at Explainalab, mostly hand-animated in After Effects. Some of the most practical work I do isn’t the big homepage piece. It’s short, focused walkthroughs that help new users get to their first win without needing to ask anyone. Here’s how I think about them.</p><h3>Your support inbox is a script library</h3><p>Before anyone writes a word of script, I ask clients one question: what do new users ask your support team in their first week?</p><p>Almost every SaaS company has the same handful of questions on repeat. How do I connect my account? Where do I invite my team? Why is this report empty? How do I change this setting? Each of those questions is a person who got stuck at a specific step and couldn’t find the answer themselves.</p><p>That list is the most valuable brief you’ll ever get, because it isn’t a guess. It’s your users telling you exactly where your product stops being self-explanatory. Sort the questions by how often they come up, and the top three or four are usually your first onboarding videos.</p><h3>One video, one task</h3><p>The most common mistake I see is the “complete product tour” onboarding video. Eight minutes, every feature, every menu, narrated like a training course. It feels thorough. In practice, almost nobody watches it to the end, and the people who do can’t remember which part covered the thing they needed.</p><p>Onboarding videos work best when each one does exactly one job:</p><ul><li><strong>Connect your first integration.</strong></li><li><strong>Create your first project.</strong></li><li><strong>Invite a teammate.</strong></li><li><strong>Read your first report.</strong></li></ul><p>Each one should be short enough that someone will watch it while they’re actually doing the task, often well under a minute. If a single task takes longer than that to explain, that’s useful information too. It might mean the flow itself needs simplifying, not a longer video.</p><p>This is a different job from your homepage explainer. The explainer convinces a stranger the product is worth trying. The onboarding video helps someone who already decided to try it actually succeed. I wrote more about matching the format to the stage in <a href="https://explainalab.com/which-video-type-fits-each-stage-of-your-funnel-a-practical-guide/">which video type fits each stage of your funnel</a>, and onboarding sits at the very end of that list, after the purchase. It’s also not quite the same as a sales demo, which I compared in <a href="https://explainalab.com/product-demo-vs-explainer-video/">product demo vs. explainer video</a>.</p><h3>Show the real interface, and point at things</h3><p>For onboarding, illustrated metaphors mostly get in the way. The user is looking at your actual screen and needs to match what they see in the video to what’s in front of them. So I build these from real UI captures, then animate on top of them:</p><ul><li><strong>Zoom in on the part that matters.</strong> A full-screen recording of a dashboard at normal size is hard to follow, especially on a laptop or inside a small help-center player. Push in on the button, the field, the menu.</li><li><strong>Highlight before you click.</strong> A brief glow or outline on the target, then the click. That half-second pause lets the viewer find the same spot on their own screen.</li><li><strong>Cut the waiting.</strong> Nobody needs to watch a loading spinner. Trim every pause that isn’t teaching something.</li><li><strong>Keep the cursor calm.</strong> Raw screen recordings are full of nervous mouse movements. In an animated walkthrough, the cursor moves with purpose from one target to the next.</li></ul><p>That’s the main difference between an onboarding video and a quick screen recording someone on your team made between meetings. Both show the same steps. One is easy to follow and one isn’t.</p><h3>Write the script for someone mid-task</h3><p>Onboarding scripts follow different rules from marketing scripts. The viewer isn’t deciding whether to care. They already care. They’re just stuck.</p><p>So I skip the hook and the pitch. The first line says what we’re about to do: “Here’s how to connect your Google account.” Then each step gets one short sentence, timed to land exactly as it happens on screen. Use the exact labels from your interface. If the button says “Add source,” the voiceover says “Add source,” not “click the plus to bring in your data.”</p><p>End with what success looks like: “You’ll see your data appear in the dashboard within a few minutes.” That last line matters more than people think. A lot of tickets come from users who actually did everything right but didn’t know what to expect next.</p><h3>Put them where the confusion happens</h3><p>A great onboarding video buried in a help center nobody visits won’t change much. Place each video at the moment someone needs it:</p><ul><li>On the empty state of the screen it explains.</li><li>In the welcome email or onboarding checklist, next to the step it covers.</li><li>Linked from the matching help article, at the top, not the bottom.</li><li>As a canned reply your support team can send when that question comes in anyway.</li></ul><p>That last one is easy to overlook. Even if a video doesn’t prevent every ticket, it can make answering those tickets much faster.</p><h3>Plan for your UI changing</h3><p>The honest downside of real-UI videos is that your product will change. A button moves, a menu gets renamed, and suddenly your video shows something that doesn’t exist anymore.</p><p>You can’t avoid that, but you can make it cheaper:</p><ul><li><strong>Keep videos short and single-task</strong>, so a UI change means updating one small video, not re-editing a long tour.</li><li><strong>Avoid showing things that change constantly</strong>, like dates, version numbers, or sample data that looks dated.</li><li><strong>Keep the project files.</strong> When I deliver, the After Effects project and source captures mean an update is a matter of swapping a screen, not starting again.</li><li><strong>Use a voiceover you can regenerate.</strong> I often use ElevenLabs for voiceover, which makes a one-line script change cheap months later.</li></ul><h3>How to know if it’s working</h3><p>I won’t promise you a specific drop in tickets, because I don’t know your product or your users. But you don’t need a guess. You can check it yourself:</p><ol><li>Note how many tickets you get for a given question over a few weeks before the video goes live.</li><li>Place the video where that confusion happens.</li><li>Compare the same period after.</li></ol><p>If the number for that question drops, make the next video. If it doesn’t, look at where you placed it, or whether the video answers the question people actually ask. Usually one of those is the problem.</p><h3>Start with three</h3><p>You don’t need a full video library on day one. Pull your most common first-week support questions, pick the top three, and make one short video for each. That’s a small project, it’s easy to measure, and it tells you quickly whether more are worth making.</p><p>If you want to see how I handle real product UI in animation, there are examples in the <a href="https://explainalab.com/#work">Explainalab work section</a>.</p><p><strong>Got a support inbox full of the same three questions?</strong> Send me your product link and those questions through <a href="https://explainalab.com/#contact">the contact form</a>, and I’ll tell you honestly which ones a short video would actually fix.</p><p><em>Ali makes SaaS explainer videos at </em><a href="https://explainalab.com/"><em>Explainalab</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=61e15b73097a" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[AI Video Tools Won’t Make Your Explainer (But They Help)]]></title>
            <link>https://medium.com/@aliislive42/ai-video-tools-wont-make-your-explainer-but-they-help-fccd99252589?source=rss-8abc38f4d326------2</link>
            <guid isPermaLink="false">https://medium.com/p/fccd99252589</guid>
            <category><![CDATA[explainer-videos]]></category>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[ai]]></category>
            <category><![CDATA[saas]]></category>
            <category><![CDATA[video-marketing]]></category>
            <dc:creator><![CDATA[Ali | Explainalab]]></dc:creator>
            <pubDate>Fri, 13 Nov 2026 14:11:50 GMT</pubDate>
            <atom:updated>2026-11-13T14:11:50.832Z</atom:updated>
            <content:encoded><![CDATA[<p><em>Where Runway, Kling and Sora actually earn a place in a SaaS explainer, and where hand animation still wins</em></p><p>Every few weeks a founder asks me some version of the same question: “Can’t AI just make this now?”</p><p>It’s a fair question. The demos look incredible. You type a sentence, and a few minutes later you have a moody, cinematic clip of a city at dawn or a robot pouring coffee. If a tool can do that, surely it can make a 60-second video about your scheduling app.</p><p>I’m Ali. I run Explainalab, where I turn dense SaaS products into short explainer videos, mostly hand-animated in After Effects. I use AI tools in my work, and I’ll tell you exactly where. But I also turn down the idea that they can make your explainer for you, because I’ve tried, and I know where it breaks.</p><h3>What an explainer actually has to do</h3><p>Before talking about tools, it helps to be clear about the job. A SaaS explainer isn’t a mood piece. It has to:</p><ol><li>Name a problem your buyer recognizes, fast.</li><li>Show your actual product solving it, clearly enough that a stranger follows.</li><li>Keep every shot in service of one argument, from the first second to the call to action.</li><li>Look like <em>your</em> brand, not like everyone else’s feed.</li></ol><p>Generative video is impressive at producing footage. It’s weak at almost everything on that list. That’s the core of it.</p><h3>Where AI tools fall short</h3><p><strong>They can’t show your real interface.</strong> This is the big one. The proof section of a SaaS explainer is your product: the dashboard, the button, the report that builds itself. AI video models don’t know what your UI looks like, and when you feed them a screenshot, they tend to warp text, invent buttons, and melt layouts mid-motion. A viewer who signs up after seeing a “dashboard” that doesn’t exist is going to feel misled. For this part, I capture the real screens and rebuild the moments that matter in After Effects, frame by frame.</p><p><strong>They don’t follow a script precisely.</strong> An explainer is built around timing. The voiceover says “and it flags the error before it ships,” and at that exact moment the warning appears on screen. Generative clips give you roughly what you asked for, at roughly the length you wanted. Roughly is fine for a background. It isn’t fine for a line of narration that has to land on a specific beat.</p><p><strong>Consistency is hard.</strong> If your video has a character, a color palette, or a set of icons, they need to look the same in shot two as in shot nine. AI tools are getting better here, but in my experience you still spend a lot of time re-rolling clips to match, and the result often looks close but not quite the same. Viewers notice that, even when they can’t say why.</p><p><strong>Revisions are unpredictable.</strong> When a client says “can that chart come in half a second earlier and be blue instead of green,” in After Effects that’s a few minutes of work. With a generated clip, it often means generating again and hoping the new version keeps everything else you liked. Explainers go through review rounds, and a process that can’t take precise notes is a problem.</p><p><strong>It tends to look generic.</strong> A lot of AI footage shares the same glossy look. That’s not a disaster, but it works against the one thing an explainer should do for your brand: look like nobody else in your category.</p><h3>Where AI tools actually help</h3><p>None of that means the tools are useless. I use them, just not as the main engine. Here’s where they earn their place in my process:</p><ul><li><strong>Filling gaps.</strong> A short establishing shot, an abstract background texture, a transitional clip between two scenes. These are moments where “roughly right” really is good enough, and generating one is faster than building it from scratch.</li><li><strong>Early exploration.</strong> When a client can’t picture a visual direction, a few quick generated frames can help us agree on a mood before I start the real storyboard. They’re a sketch, not a deliverable.</li><li><strong>Voiceover.</strong> I use ElevenLabs for voiceover on many projects. It gives clients a clean, consistent read and makes script changes cheap late in the process. It’s one of the places where AI has genuinely changed how I work.</li><li><strong>Grunt work.</strong> Cleaning up audio, removing a background, upscaling an old asset a client sends over. These save time without touching the creative decisions.</li></ul><p>Notice the pattern: AI handles the parts where precision doesn’t matter much, and hand animation handles the parts where it does.</p><h3>How it fits into a real project</h3><p>My process doesn’t change much because of AI. It goes roughly like this: brief and script, a shot-by-shot storyboard the client approves, animation in After Effects, voiceover, then the final cut delivered in whatever specs you need. I walk through each of those stages in more detail in my post on the <a href="https://explainalab.com/saas-explainer-video-production-process/">SaaS explainer video production process</a>.</p><p>AI shows up inside a few of those steps, not as a replacement for any of them. In the storyboard, each row says what’s on screen and where it comes from. Most rows say “real UI, animated” or “illustrated.” Occasionally one says “generated background” or “AI-assisted transition.” If a storyboard ends up with lots of generated rows in the proof section, that’s a warning sign. It usually means we’re avoiding showing the product.</p><h3>“But AI agents can demo my product now”</h3><p>Some founders bring this up next: with AI agents that can click through software, do you still need an explainer at all? Agents and interactive demos are interesting, and for some buyers further down the funnel they’ll be useful. But someone landing on your homepage for the first time hasn’t decided to spend ten minutes poking around yet. They need to understand what you do and why it matters in the first few seconds. I wrote more about that in <a href="https://explainalab.com/agentic-ai-is-changing-how-saas-products-get-demoed-your-explainer-video-still-wins-the-first-30-seconds/">why your explainer video still wins the first 30 seconds</a>, even as AI changes how products get demoed.</p><h3>A simple way to decide, shot by shot</h3><p>If you’re planning a video and wondering whether a given shot can be generated, ask:</p><ul><li><strong>Does this shot prove something about my product?</strong> If yes, it needs your real interface, animated by hand. Don’t generate it.</li><li><strong>Does it need to hit a specific word in the voiceover?</strong> If yes, you want precise control over timing. Generated clips will fight you.</li><li><strong>Does it have to match other shots exactly?</strong> Characters, icons, brand colors. If consistency matters, build it.</li><li><strong>Is it atmosphere?</strong> A background, a mood, a brief transition. This is where generation can save real time.</li></ul><p>Most explainers end up with very few shots in that last category, and that’s fine.</p><h3>The honest version</h3><p>AI tools have made parts of my work faster, and I’d be lying if I said otherwise. But the hard part of an explainer was never generating footage. It was figuring out what your product actually does for someone, cutting everything else, and showing the real thing clearly enough that a stranger gets it in a minute. That part is still judgment and craft, and it’s still where the time goes.</p><p>If you want to see what that looks like in finished videos, some recent projects are in the <a href="https://explainalab.com/#work">Explainalab work section</a>.</p><p><strong>Wondering which parts of your video could be AI-assisted and which can’t?</strong> Send me your product link through <a href="https://explainalab.com/#contact">the contact form</a>, and I’ll give you a straight answer, including when you don’t need me at all.</p><p><em>Ali makes SaaS explainer videos at </em><a href="https://explainalab.com/"><em>Explainalab</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=fccd99252589" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Real UI vs. Illustrated Metaphors]]></title>
            <link>https://medium.com/@aliislive42/real-ui-vs-illustrated-metaphors-369c2ab33ade?source=rss-8abc38f4d326------2</link>
            <guid isPermaLink="false">https://medium.com/p/369c2ab33ade</guid>
            <category><![CDATA[saas]]></category>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[video-marketing]]></category>
            <category><![CDATA[explainer-videos]]></category>
            <category><![CDATA[ui-design]]></category>
            <dc:creator><![CDATA[Ali | Explainalab]]></dc:creator>
            <pubDate>Wed, 11 Nov 2026 14:09:28 GMT</pubDate>
            <atom:updated>2026-11-11T14:10:11.752Z</atom:updated>
            <content:encoded><![CDATA[<p><em>When to animate your actual interface in a SaaS explainer, and when a simple visual metaphor does the job better</em></p><p>Every SaaS explainer I make hits the same fork early on. Do we show the real product, the actual dashboard and buttons and tables, or do we show a picture of the idea: a tangle of wires straightening out, a stack of paper turning into one clean card, a little rocket taking off?</p><p>Founders usually arrive with a strong opinion either way. Some want “the real thing, nothing fake.” Others say their UI is ugly or about to change, so “just make it look nice.” Both instincts have a point. Both can sink a video if you follow them all the way.</p><p>I’m Ali. I run Explainalab, where I turn dense SaaS products into short explainer videos, hand-animated in After Effects. Here’s how I actually make this call, shot by shot, and why the answer is almost never “all one or all the other.”</p><h3>What each option is good at</h3><p><strong>Real UI</strong> is proof. When a viewer sees the actual screen, they’re not taking your word for it. They see the button they’ll click and the result they’ll get. That’s what moves someone from “sounds interesting” to “I could use this.”</p><p><strong>Illustrated metaphors</strong> are clarity. They’re good at showing things your interface can’t: the problem before your product exists, an abstract benefit like “less context switching,” or a process that happens behind the scenes, like data syncing between three tools.</p><p>The mistake is using one to do the other’s job. A metaphor can’t prove your product works. A raw screen recording can’t explain why anyone should care.</p><p>I go through the broader menu of styles (whiteboard, character animation, UI-led, kinetic type and so on) in my <a href="https://explainalab.com/explainer-video-styles-for-saas-founders-a-practical-cheat-sheet/">cheat sheet on explainer video styles for SaaS founders</a>. This piece zooms in on the one decision that comes up in almost every project.</p><h3>When to show the real interface</h3><p>I lean on real UI when:</p><ol><li><strong>The interface is part of the pitch.</strong> If your argument is “look how simple this is,” you have to show it. Telling people it’s simple over a cartoon is the weakest version of that claim.</li><li><strong>Your buyer has seen ten competitors.</strong> In crowded categories, viewers are comparing. They want to see the actual workflow, not another generic illustration that could belong to any tool.</li><li><strong>The viewer is close to buying or already signed up.</strong> Demo pages, onboarding, feature announcements. These people need the real screens because they’re about to use them.</li><li><strong>One specific moment is your “aha.”</strong> A report that builds itself, a booking that confirms instantly, an error that gets flagged before it ships. That moment deserves real pixels.</li></ol><p>“Real UI” doesn’t mean a raw screen recording, though. Raw recordings are usually the worst way to show a product. The cursor wanders, the screen is full of sidebars and menus that have nothing to do with the point, the text is too small to read on a phone, and everything moves at the speed of someone who already knows the app.</p><p>What I do instead is capture the real screens, then rebuild the relevant parts in After Effects. I isolate the one panel that matters, hide the clutter, enlarge what needs to be read, and animate the clicks and transitions at a pace a stranger can follow. The viewer still sees your actual product. They just see the clean version of the moment, not the whole messy desktop.</p><h3>When a metaphor works better</h3><p>I reach for a metaphor when:</p><ol><li><strong>You’re showing the problem.</strong> Before your product enters the story, there’s nothing to screen-capture. Scattered spreadsheets, a flood of notifications, a team waiting on one person: these read faster as simple visuals than as screenshots of other tools.</li><li><strong>The benefit is abstract.</strong> “Fewer handoffs.” “One source of truth.” “Less time in meetings.” You can’t screenshot a feeling. A quick visual can land it in two seconds.</li><li><strong>The work happens out of sight.</strong> Integrations, background syncing, security, AI processing. Showing a loading spinner isn’t explanation. A simple diagram of data moving between things usually is.</li><li><strong>The UI genuinely isn’t ready.</strong> If the interface is being redesigned next month, building half the video on screens that won’t exist is a waste. In that case, I’ll often keep UI shots short and simplified, so they can be updated later without rebuilding everything.</li></ol><p>The risk with metaphors is that they drift into decoration. A gear turning, a lightbulb popping on, a rocket taking off. These don’t explain anything. They fill time. If I can’t say in one sentence what a metaphor shot teaches the viewer, it gets cut.</p><h3>The mix I use most often</h3><p>Most of the SaaS explainers I make follow a rough pattern:</p><ul><li><strong>Open with a metaphor for the problem.</strong> It’s quick, relatable, and doesn’t require the viewer to understand your product yet.</li><li><strong>Transition into real UI for the solution.</strong> The messy metaphor collapses or resolves into your actual interface. That handoff is one of the most satisfying moments in an explainer when it’s done right.</li><li><strong>Spend the middle on real UI proof.</strong> Two or three key product moments, isolated and readable.</li><li><strong>Use a light metaphor or a clean outcome shot to close.</strong> What life looks like now, then the call to action.</li></ul><p>So the metaphor sets up the problem and the real interface proves the solution. When I plan this out in a shot-by-shot table, every row gets marked as “real UI” or “metaphor” so the client can see the balance before any animation starts. If the proof section is mostly metaphors, that’s a red flag. It usually means we’re avoiding the product instead of showing it.</p><h3>A quick test for every shot</h3><p>When I’m unsure which way to go on a particular shot, I ask three questions:</p><ul><li><strong>What does the viewer need to believe after this shot?</strong> If it’s “this product can actually do X,” show real UI. If it’s “this problem is real and annoying,” a metaphor is usually faster.</li><li><strong>Would a screenshot here need explaining?</strong> If the screen only makes sense with a paragraph of context, it’s the wrong moment for it. Simplify the UI or use a visual that carries the idea on its own.</li><li><strong>Will this still be true in six months?</strong> Interfaces change. Metaphors age more slowly. That doesn’t mean avoid UI, but it does mean being deliberate about which screens become the backbone of the video.</li></ul><p>These overlap with a few points on my <a href="https://explainalab.com/what-makes-an-explainer-video-actually-work-an-editors-checklist/">editor’s checklist for what makes an explainer video work</a>, especially around clarity and whether each shot earns its place.</p><h3>What about AI-generated visuals?</h3><p>Since someone always asks: yes, AI image and video tools can generate metaphor shots quickly. I use them now and then to fill a gap, like a background texture or a short transitional clip. But they’re bad at the part that matters most here. They can’t show your real interface accurately, and they tend to produce generic visuals that look like every other AI clip in someone’s feed. For the proof section of a SaaS explainer, there’s no shortcut around capturing and animating the actual product.</p><h3>Common mistakes I see</h3><ul><li><strong>All metaphor, no product.</strong> The video is charming, and at the end the viewer still has no idea what the software looks like. Nice for brand awareness, weak for sign-ups.</li><li><strong>All UI, no story.</strong> A two-minute tour of every feature, with no problem set up and no reason to care. People leave long before the good part.</li><li><strong>Fake UI that doesn’t match the product.</strong> An illustrated “dashboard” that looks nothing like the real one sets up a letdown the moment someone signs up. If you simplify the UI, keep it recognizable.</li><li><strong>Tiny, unreadable screens.</strong> If the viewer has to squint to see what changed, the shot didn’t do its job. Zoom in, crop, isolate.</li></ul><h3>The short version</h3><p>Use metaphors to make people care. Use real UI to make them believe. Plan which is which before anyone opens After Effects, and cut any shot that’s only there to look busy.</p><p>If you want to see how this plays out in finished work, a few recent projects are on the <a href="https://explainalab.com/#work">Explainalab work section</a>.</p><p><strong>Not sure how much of your product to show in your explainer?</strong> Send me your product link and your current landing page through <a href="https://explainalab.com/#contact">the contact form</a>, and I’ll tell you which moments I’d show as real UI and where a simple visual would do more.</p><p><em>Ali makes SaaS explainer videos at </em><a href="https://explainalab.com/"><em>Explainalab</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=369c2ab33ade" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Storyboard Before You Animate]]></title>
            <link>https://medium.com/@aliislive42/storyboard-before-you-animate-b308ace5fe23?source=rss-8abc38f4d326------2</link>
            <guid isPermaLink="false">https://medium.com/p/b308ace5fe23</guid>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[explainer-videos]]></category>
            <category><![CDATA[video-marketing]]></category>
            <category><![CDATA[storyboard]]></category>
            <category><![CDATA[saas]]></category>
            <dc:creator><![CDATA[Ali | Explainalab]]></dc:creator>
            <pubDate>Mon, 09 Nov 2026 14:11:35 GMT</pubDate>
            <atom:updated>2026-11-09T14:11:35.059Z</atom:updated>
            <content:encoded><![CDATA[<p><em>Why a shot-by-shot table saves revisions on SaaS explainer videos, and what that table should actually look like</em></p><p>Here’s a pattern I’ve seen more times than I’d like. A SaaS team signs off on a script. Animation starts in After Effects. Two weeks later, someone watches the first cut and says, “Actually, can we open on a different feature?” Or: “The middle section feels wrong. Let’s show the dashboard instead of the onboarding flow.”</p><p>Both requests sound reasonable. Both are expensive.</p><p>Once a shot is animated, changing what it shows usually means rebuilding it: new UI captures, new timing, new transitions, sometimes a new voiceover line. One late change can cost more than a whole round of planning. That is the problem a storyboard exists to prevent.</p><p>I’m Ali. I run Explainalab, where I edit dense SaaS products into short explainer videos, hand-animated in After Effects. The step that saves the most money and the most arguments is a plain shot-by-shot table that everyone approves before a single keyframe is set.</p><h3>What “storyboard” means here (and what it doesn’t)</h3><p>When people hear “storyboard,” they often picture illustrated frames: little drawings of every scene, like a comic strip for a film. That can be useful for character-driven explainers. For most SaaS product videos, it’s the wrong mental model.</p><p>What I need is not pretty frames. I need a plan that answers, for every second: what is on screen, what the voice says, what moves, and roughly how long it lasts. A spreadsheet or a simple markdown table does that better than a stack of sketches.</p><p>Call it a storyboard, a shot list, or a shot-by-shot table. The name doesn’t matter. The approval does.</p><h3>The columns people can copy</h3><p>Here is the table I use on nearly every project. Five columns. Nothing fancy.</p><ul><li><strong>Shot 1 (0–4s).</strong> On-screen: phone notifications stacking over a calendar. VO: “Your class schedule lives in five group chats.” Notes: phone mock; keep UI readable.</li><li><strong>Shot 2 (4–8s).</strong> On-screen: crowded studio door, quick push-in. VO: “And someone always shows up to a full room.” Notes: still or short stock; no product yet.</li><li><strong>Shot 3 (8–15s).</strong> On-screen: mess collapses into a clean booking calendar. VO: “This tool puts bookings in one place.” Notes: real product calendar UI.</li><li><strong>Shot 4 (15–24s).</strong> On-screen: cursor books a class; confirmation appears. VO: “Students pick a slot. You get a confirmation.” Notes: isolate booking panel; hide sidebar.</li></ul><p>What each column is for:</p><ul><li><strong>Shot #.</strong> Makes feedback specific (“change shot 4”) instead of “somewhere in the middle.”</li><li><strong>On-screen action.</strong> What the viewer sees, in one short sentence. Not “animate something cool here.”</li><li><strong>VO line.</strong> The exact voiceover for that shot, from the locked script. If it doesn’t fit the duration, fix it now.</li><li><strong>UI / notes.</strong> Which screen, which panel to isolate, what to hide, whether this is real UI or a metaphor shot.</li><li><strong>Duration.</strong> Rough start and end times. They flex a little in the edit, but the table should add up to your target length.</li></ul><p>You can fold motion notes (zoom, cursor click, panel slide) into On-screen action to keep the table readable.</p><h3>Why you approve it before After Effects</h3><p>Animation is the expensive, irreversible part of an explainer. Script changes are cheap. Storyboard changes are still cheap. Changing a finished animated sequence is not.</p><p>When a client approves the shot-by-shot table, they are approving:</p><ol><li><strong>The order of ideas.</strong> Problem → product → proof → outcome → CTA.</li><li><strong>Which product moments get screen time.</strong> Feature A is in; feature B is out.</li><li><strong>How much time each beat gets.</strong> Half the video for proof is normal. If proof is squeezed into eight seconds, we fix that in the table, not after I’ve animated eighteen layers.</li><li><strong>What “done” looks like.</strong> Nobody is surprised by a first cut that shows a different workflow than they imagined.</li></ol><p>This is also where disagreements inside the company surface early. If marketing wants the homepage claim and product wants a deep feature tour, the table makes that conflict visible before anyone has spent a week in After Effects. Better a hard conversation on Tuesday than a rebuild on Friday.</p><p>I walk through this table with clients as part of the same process that covers brief, script, and UI capture. You can see how that fits together <a href="https://explainalab.com/#about">on the about section of Explainalab</a>.</p><h3>How a locked table cuts revision cost</h3><p>Revisions are not all equal. Think of three buckets:</p><ol><li><strong>Script revisions.</strong> Swap a sentence, cut a claim. Minutes of work.</li><li><strong>Storyboard revisions.</strong> Move shots, replace a metaphor with a UI screen, shorten the open. Still mostly thinking and typing.</li><li><strong>Animation revisions.</strong> Rebuild a sequence because the message changed. Hours or days.</li></ol><p>The storyboard’s job is to force decisions into buckets one and two. When the table is locked, animation feedback should sound like “the click lands a beat late,” not “can we show a different product area?”</p><p>A late message change often invalidates work that looked finished. A locked storyboard is how you keep “revision” meaning polish, not restart.</p><h3>Common mistakes that waste the storyboard</h3><p><strong>Skipping it because “we already have a script.”</strong> A script is the words. A storyboard is the picture plan. Animators cannot build from voiceover alone without guessing. Guessing is how you get a first cut that feels “off” until you draw the shots out.</p><p><strong>Treating the storyboard as pretty frames only.</strong> Illustrated boards can look finished and still be vague about which UI panel appears, how long each beat runs, or what the cursor does. For SaaS, the table’s precision matters more than the drawings. Drawings are optional; the columns are not.</p><p><strong>Changing the message after animation starts.</strong> New positioning, a different hero feature, a stakeholder who joins late and rewrites the claim. If the claim changes, go back to the script and the table. Do not ask the animator to “just tweak” a section built for a different story. That tweak is usually a rebuild wearing a soft name.</p><p><strong>Leaving durations blank.</strong> If the table doesn’t add up to 60 or 90 seconds, the edit will stretch or crush shots later. Rough timings catch that early.</p><p><strong>Approving without reading VO against the picture.</strong> Read each line while imagining the shot. If a line describes something the picture already shows, cut the line. If a shot has no clear visual job, cut the shot.</p><h3>What this looks like with real product UI</h3><p>Most of the explainers I make lean on the actual interface, cleaned up and timed so a stranger can follow it. The storyboard is where those UI decisions get written down: which screen, which panel to isolate, what clutter to hide, which single click to show.</p><p>That planning is what makes UI motion feel intentional instead of like a sped-up screen recording. If you want a sense of the end result, the <a href="https://explainalab.com/#work">selected work on Explainalab</a> includes UI-driven explainers across healthcare, fitness booking, AI tooling, and more. Each started as a table like the one above.</p><h3>A short checklist before you greenlight animation</h3><ul><li>Does every shot have a number, a visual, a VO line (or a clear silent beat), notes, and a duration?</li><li>Do the durations add up to your target length?</li><li>Can you state the one claim the video proves, and does every shot serve it?</li><li>Has everyone who can block the project looked at the table?</li><li>Are message changes closed, or still open?</li></ul><p>If the last answer is “still open,” you are not ready to animate. Lock the plan first.</p><h3>Storyboard first, animate second</h3><p>Animation is where an explainer becomes real, and where changes get expensive. A shot-by-shot table moves the hard decisions earlier, while they still cost almost nothing.</p><p>Approve that table. Then open After Effects. That order is the difference between a project that finishes clean and one that revises itself into overtime.</p><p><strong>Planning an explainer and want the storyboard done before anyone animates?</strong> I’m Ali at Explainalab. I handle brief, script, shot-by-shot table, After Effects animation, voiceover, and final delivery in one pass. <a href="https://explainalab.com/#contact">Tell me about your product</a>, and I’ll tell you what the first draft of that table should look like.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b308ace5fe23" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[What a SaaS Explainer Video Actually Costs (and What Drives It)]]></title>
            <link>https://medium.com/@aliislive42/what-a-saas-explainer-video-actually-costs-and-what-drives-it-568f239bd499?source=rss-8abc38f4d326------2</link>
            <guid isPermaLink="false">https://medium.com/p/568f239bd499</guid>
            <dc:creator><![CDATA[Ali | Explainalab]]></dc:creator>
            <pubDate>Wed, 04 Nov 2026 14:09:55 GMT</pubDate>
            <atom:updated>2026-11-04T14:10:49.390Z</atom:updated>
            <content:encoded><![CDATA[<p>No made-up price tables. Just the honest list of things that move the number up or down, so you can scope before you ask for quotes.</p><p>“How much does an explainer video cost?” is the first question I get on almost every call. It’s a fair question. It’s also one I can’t answer in a sentence, and anyone who can, without knowing anything about your product, is guessing or selling you a template.</p><p>I’m not going to give you a price table here. Prices on the internet are all over the place, and a number pulled out of context does more harm than good. What I can give you is the list of things that actually drive the cost of a SaaS explainer, based on how I scope projects at Explainalab. If you understand these, you’ll get better quotes, compare them more fairly, and spend your budget where it matters.</p><h3>1. Length is a factor, but not the one you think</h3><p>People assume cost scales neatly with seconds. It doesn’t, quite.</p><p>A 90-second video costs more than a 30-second one, sure. More animation, more voiceover, more review. But the expensive part of a good explainer is often the thinking at the start: figuring out what the video needs to prove, writing a script tight enough to fit, and planning every shot. That work exists whether the final cut is 30 seconds or 90.</p><p>So a very short video isn’t automatically cheap. Sometimes it’s harder, because there’s no room to waste. If you’re comparing quotes, ask how much of the price is planning versus production. It tells you a lot about how the studio works.</p><h3>2. How much of the work is already done</h3><p>This is the biggest swing factor and it gets ignored the most.</p><p>Some clients arrive with a finished script, a clear message, brand guidelines, and clean access to their product. Others arrive with “we need a video for the launch” and a link to the homepage. Both are completely normal. They’re just different amounts of work.</p><p>Things that reduce scope on my end:</p><ul><li><strong>A clear, agreed message.</strong> If your founders and your marketing lead disagree about what the product is for, the video will surface that fight. Better to settle it before production.</li><li><strong>A script, or at least a solid draft.</strong> Even a rough one saves a round.</li><li><strong>Brand assets in usable form.</strong> Logo files, fonts, colors, any existing illustrations.</li><li><strong>Access to the real product.</strong> A staging account or recorded screen flows, so I can capture actual UI instead of rebuilding it from screenshots.</li></ul><p>None of this is required. Writing the script and building the storyboard is part of what I do. But be honest about where you’re starting, because that’s what you’re paying for.</p><h3>3. Real UI animation versus illustrated metaphors</h3><p>SaaS explainers usually lean one of two ways. Either they show your actual interface, animated and simplified so the viewer can follow it, or they explain the idea with illustrated characters and metaphors.</p><p>Both have a place. They cost differently for different reasons.</p><p>Animating real UI means capturing screens, cleaning them up, rebuilding parts in After Effects so they can move smoothly, and choreographing clicks and transitions so they read clearly. It’s precise work, and dense products with lots of screens take longer.</p><p>Illustrated explainers need custom artwork: characters, scenes, props. If none of that exists yet, someone has to design it before anything moves.</p><p>Most of the work I do leans toward real UI, because for software, showing the actual product tends to build more trust than a cartoon of it. You can see examples on <a href="https://explainalab.com/#work">my work page</a>.</p><h3>4. Animation complexity</h3><p>Within either style, there’s a wide range.</p><p>Simple motion, like screens sliding in, text appearing, and a cursor clicking through a flow, is quicker to produce. Complex motion, like camera moves through a 3D-ish space, morphing shapes, detailed character animation, or lots of layered elements per shot, takes much longer per second of finished video.</p><p>You don’t always need the complex version. A clean, well-timed walkthrough often explains a product better than something flashy. When you get a quote, ask what level of motion it assumes, and ask to see a past example at that level.</p><h3>5. Voiceover, music, and languages</h3><p>Voiceover can be a professional human voice actor, a high-quality synthetic voice, or the founder’s own voice. Each has different costs and different trade-offs. I use ElevenLabs for many projects because it’s fast to revise and sounds natural when it’s directed well, but some brands want a specific human voice, and that’s a valid choice.</p><p>Music is usually licensed stock. Custom music is possible but rarely necessary for a product explainer.</p><p>Languages add real work. A bilingual version isn’t just a second voiceover track. On-screen text, UI captures, and sometimes timing all have to change. I do Spanish and English versions regularly, and the second language is meaningfully less work than the first, but it isn’t free.</p><h3>6. Revisions and approval process</h3><p>Revisions are where budgets quietly leak.</p><p>The cheapest change is the one made at the script stage. Moving a sentence costs nothing. The most expensive change is one made after animation is done, like “actually, can we show a different feature here?” That can mean redoing a whole section.</p><p>This is why I build a shot-by-shot storyboard table and get it approved before animating anything. It’s not bureaucracy. It’s how changes stay cheap. When you compare quotes, ask:</p><ul><li>How many revision rounds are included?</li><li>At what stages?</li><li>What counts as a revision versus a new request?</li></ul><p>A studio that’s vague about this will usually cost more by the end, even if the first number was lower.</p><h3>7. Who’s actually doing the work</h3><p>Some studios have a salesperson, a scriptwriter, an illustrator, an animator, and a project manager. That can work well for big projects, but every handoff adds coordination cost and a chance for the message to drift.</p><p>I run Explainalab solo. I handle the conversation, the script, the storyboard, the animation, the voiceover, and the final cut. That’s a deliberate choice: fewer handoffs, and the person you talk to on day one is the person editing your video. You can read more <a href="https://explainalab.com/#about">about how I work</a>.</p><p>Neither model is right for everyone. Just know what you’re paying for.</p><h3>8. Deliverables and formats</h3><p>One 16:9 video for your homepage is one deliverable. The same video cut into a 9:16 version for social, a 1:1 version for ads, a 15-second teaser, and a silent looping version for the hero section is several.</p><p>Cutdowns are much cheaper than the main video because the assets already exist. But they’re not zero work, especially for vertical formats, where the layout often needs rethinking rather than just cropping. Plan your formats up front. Adding them later usually costs more than including them in the original scope.</p><h3>What about AI tools? Don’t they make this cheap now?</h3><p>Partly, and in specific places.</p><p>I use tools like Runway, Kling, and Sora to fill gaps: a background shot, a texture, a quick concept. They can save time there. What they can’t do yet is reliably animate your actual product interface with the precision a SaaS explainer needs, or decide what your video should say. The parts that cost the most, planning, scripting, and clear UI motion, are still human work.</p><p>If someone quotes you a suspiciously low price for a fully custom product explainer, it’s worth asking how much of it is generated and whether it will actually show your software.</p><h3>How to get a useful quote</h3><p>Before you contact anyone, write down:</p><ol><li>The one thing the video needs to prove to a viewer.</li><li>Where it will live (homepage, onboarding, ads, sales calls).</li><li>Rough length you have in mind.</li><li>Whether you have a script, brand assets, and product access.</li><li>The formats and languages you need.</li><li>Your deadline.</li></ol><p>With that, any decent studio can give you a real quote instead of a range wide enough to drive a truck through. And you can compare quotes on the same basis.</p><h3>If you want a real number</h3><p>If you’re planning an explainer for your SaaS and want a quote based on your actual product, <a href="https://explainalab.com/#contact">send me the details here</a>. Tell me what you’re working with from the list above, and I’ll tell you honestly what it would take, including whether you need a full explainer at all.</p><p><em>Ali, Explainalab</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=568f239bd499" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How to Script a 60-Second SaaS Explainer]]></title>
            <link>https://medium.com/@aliislive42/how-to-script-a-60-second-saas-explainer-ef49b0c83211?source=rss-8abc38f4d326------2</link>
            <guid isPermaLink="false">https://medium.com/p/ef49b0c83211</guid>
            <category><![CDATA[video-marketing]]></category>
            <category><![CDATA[saas]]></category>
            <category><![CDATA[copywriting]]></category>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[explainer-videos]]></category>
            <dc:creator><![CDATA[Ali | Explainalab]]></dc:creator>
            <pubDate>Mon, 02 Nov 2026 14:19:57 GMT</pubDate>
            <atom:updated>2026-11-02T14:19:57.229Z</atom:updated>
            <content:encoded><![CDATA[<p>A practical, step-by-step way to go from a messy brief to a script and shot list that actually fit in a minute</p><p>Most SaaS explainer scripts I get sent are too long. Not a little too long. Usually two or three times too long.</p><p>That’s not because founders are bad writers. It’s because a script feels like the place to finally say everything about the product. Every feature you shipped this year, every integration, every type of customer. On paper it reads fine. Read out loud against a timer, it runs past two minutes, and the animation that’s supposed to make it clear gets squeezed into a blur.</p><p>Sixty seconds is a good target for a homepage or launch explainer. It’s long enough to show a real workflow and short enough that people finish it. But a minute is far less room than most people think, so the script has to be built on purpose.</p><p>Here’s the process I use, start to finish.</p><h3>Step 1: Do the math before you write a word</h3><p>Spoken voiceover usually lands somewhere around 130 to 160 words per minute at a comfortable, clear pace. Explainers should sit at the slower end, because the viewer is also reading the screen and following motion.</p><p>So a 60-second explainer gets roughly <strong>130 to 150 words of voiceover</strong>, total. Take off a few seconds for an opening beat and a closing logo or call to action, and you’re realistically writing about 120 words.</p><p>That number changes how you think. 120 words is a short email. It’s this section of this article, more or less. You can’t fit a feature list into that. You can fit one clear idea and a little proof.</p><p>Write that number at the top of your document. Every draft gets checked against it.</p><h3>Step 2: Write the brief as five short answers</h3><p>Before the script, I ask for a brief. Not a long one. Five answers, a sentence or two each:</p><ol><li><strong>Who is watching?</strong> Be specific. “Operations managers at mid-size clinics” beats “healthcare.”</li><li><strong>What are they doing right now instead?</strong> Spreadsheets, a competitor, email threads, nothing at all.</li><li><strong>What’s the one thing they must believe by the end?</strong> One sentence. This is the spine of the video.</li><li><strong>What proves it?</strong> Two or three moments in the product that show the claim is true.</li><li><strong>What should they do next?</strong> Book a demo, start a trial, join a waitlist. Pick one.</li></ol><p>If you can’t answer number three in a single sentence, don’t start the script yet. Every script problem I’ve had to untangle later traces back to a fuzzy answer there.</p><h3>Step 3: Split the minute into five beats</h3><p>Once the brief is clear, I split the 60 seconds into rough beats. The timing flexes, but this shape works for most SaaS products:</p><ul><li><strong>0–8 seconds: The problem.</strong> Say it in the viewer’s words. Open on the pain or the payoff, never on your logo.</li><li><strong>8–15 seconds: The shift.</strong> Your product enters. One line on what it is.</li><li><strong>15–45 seconds: The proof.</strong> Two or three product moments, each one showing a step of the workflow doing its job.</li><li><strong>45–55 seconds: The outcome.</strong> What’s different afterwards. Time saved, fewer mistakes, less back-and-forth.</li><li><strong>55–60 seconds: The next step.</strong> One call to action.</li></ul><p>Notice where the time goes. Half the video is proof. That’s on purpose. The problem and the outcome are claims; the middle section is where you earn the right to make them.</p><h3>Step 4: Write the first draft long, out loud</h3><p>Now write. I’d rather have a draft that’s too long than a draft that’s stiff, so the first pass is loose. Write it the way you’d explain the product to a friend across a table.</p><p>Then read it out loud with a timer running. Not in your head. Out loud, at a pace you’d want to listen to. Silent reading lies about length every time.</p><p>If it’s over, and it will be, move on to cutting.</p><h3>Step 5: Cut anything the picture will already show</h3><p>This is the step that makes or breaks an explainer script.</p><p>Voiceover and visuals are partners. When the screen shows a cursor dragging a file into a folder, the voiceover doesn’t need to say “drag your file into the folder.” It can say why that matters instead: “and it’s filed for the whole team.”</p><p>Go line by line and ask: <strong>will the viewer already see this?</strong> If yes, cut it or replace it with the reason it matters.</p><p>A few other cuts that almost always help:</p><ul><li><strong>Adjectives about your own product.</strong> “Powerful,” “intuitive,” “seamless.” Show it, don’t call it.</li><li><strong>Lists of three features.</strong> Usually one is the hero and two are filler.</li><li><strong>Stakeholder roll calls.</strong> “Whether you’re a manager, a team lead, or an individual contributor…” Pick the viewer you named in the brief.</li><li><strong>Setup sentences.</strong> “Let’s take a look at how it works.” Just show how it works.</li></ul><p>After this pass, most scripts drop by a third or more. That’s normal and good.</p><h3>Step 6: Turn the script into a shot list</h3><p>A script on its own isn’t something an animator can build from. The next step is a simple shot-by-shot table with four columns: time, voiceover, what’s on screen, and what moves. A few rows might look like this:</p><p><strong>Shot 1 (0–4s).</strong> Voiceover: “Your class schedule lives in five group chats.” On screen: a phone buzzing with overlapping messages. Motion: notifications stack up fast.</p><p><strong>Shot 2 (4–8s).</strong> Voiceover: “And someone always shows up to a full room.” On screen: a crowded studio door. Motion: a quick push-in.</p><p><strong>Shot 3 (8–15s).</strong> Voiceover: “This booking tool puts it all in one place.” On screen: a clean calendar UI. Motion: the messages collapse into the calendar.</p><p><em>(This example is a made-up product, just to show the format.)</em></p><p>Writing the table does two useful things. It exposes lines that have no visual, which usually means they’re vague. And it gives you and your team something concrete to approve before anyone spends hours animating. Changing a row in a table takes a minute. Changing a finished animated scene takes much longer.</p><p>At Explainalab, this table is the thing clients sign off on before animation starts. You can see how that process fits into the full workflow on the <a href="https://explainalab.com/#about">About section of the site</a>.</p><h3>Step 7: Plan for real UI, not just illustrations</h3><p>For most SaaS products, the proof section should show your actual interface. Viewers trust what they can recognize when they log in later.</p><p>That doesn’t mean pasting a raw screen recording under the voiceover. Raw recordings are cluttered and slow. When you write the shot list, note for each UI shot:</p><ul><li><strong>Which panel or element matters</strong>, so it can be isolated or zoomed.</li><li><strong>What can be hidden</strong>, like sidebars, test data, and extra menus.</li><li><strong>The single interaction to show</strong>: one click, one result.</li></ul><p>This keeps the script honest, too. If a step in your workflow takes nine clicks, you’ll notice it in the table and either simplify the story or choose a different moment to show.</p><p>If you want to see what UI-driven explainers look like when the script and the motion are planned together, the <a href="https://explainalab.com/#work">selected work on Explainalab</a> has examples across healthcare, fitness booking, AI tools, and more.</p><h3>Step 8: Do a final read with the voice in mind</h3><p>Before locking the script, read it one last time as if you were the voiceover artist:</p><ul><li><strong>Can every sentence be said in one breath?</strong> If not, split it.</li><li><strong>Are there words that trip the tongue?</strong> Product names, acronyms, and number strings often do. Decide how each one is pronounced now.</li><li><strong>Is there room to breathe?</strong> A half-second pause before the outcome line often lands harder than another sentence.</li></ul><p>Whether you use a human voice or a synthetic one, this pass saves a round of re-recording.</p><h3>A note on AI script generators</h3><p>You can ask an AI tool to write an explainer script, and it’ll give you something in seconds. It can be a decent way to get unstuck on a first draft.</p><p>But it doesn’t know your viewer, your one claim, or which three product moments actually prove it. Those come from the brief, and from someone who understands the product. Use AI for a rough draft if it helps, then apply every step above. The cutting, the shot list, and the timing are still human work.</p><h3>A quick checklist</h3><p>Before you hand your script off for animation:</p><ul><li>Is the voiceover around 120 to 150 words?</li><li>Can you state the one claim in a single sentence?</li><li>Does at least half the runtime go to product proof?</li><li>Has every line that just describes the visuals been cut?</li><li>Is there a shot list with a visual for every line?</li><li>Have you read it out loud, with a timer, at least twice?</li></ul><p>If yes to all six, you have a script that fits in a minute and still says what matters.</p><p><strong>Want a second pair of eyes on your explainer script, or someone to take it from brief to finished video?</strong> I’m Ali at Explainalab, and I script, storyboard, and hand-animate SaaS explainers in After Effects. <a href="https://explainalab.com/#contact">Send me your product and your one-sentence claim</a>, and I’ll tell you what the first 60 seconds should look like.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ef49b0c83211" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Your SaaS Is Clear to You. That’s the Problem.]]></title>
            <link>https://medium.com/@aliislive42/your-saas-is-clear-to-you-thats-the-problem-0f7e1ea64e3a?source=rss-8abc38f4d326------2</link>
            <guid isPermaLink="false">https://medium.com/p/0f7e1ea64e3a</guid>
            <category><![CDATA[saas]]></category>
            <category><![CDATA[explainer-videos]]></category>
            <category><![CDATA[marketing]]></category>
            <category><![CDATA[video-marketing]]></category>
            <category><![CDATA[startup]]></category>
            <dc:creator><![CDATA[Ali | Explainalab]]></dc:creator>
            <pubDate>Fri, 30 Oct 2026 15:26:07 GMT</pubDate>
            <atom:updated>2026-10-30T15:26:07.568Z</atom:updated>
            <content:encoded><![CDATA[<p>Why explainer videos fix the “curse of knowledge” on SaaS landing pages, and how to make one people actually finish</p><p>You’ve lived inside your product for months, maybe years. You know every feature, every edge case, every reason it beats the spreadsheet your customers are using today. So when you write your homepage, it feels obvious.</p><p>To a first-time visitor, it isn’t.</p><p>That gap has a name: the curse of knowledge. Once you know something deeply, it’s very hard to remember what not knowing it felt like. And SaaS products, being abstract, layered, and often invisible until you log in, suffer from it more than most.</p><p>This article is about one of the most practical fixes for that gap: a short, well-built explainer video. Not a sizzle reel. Not a 4-minute feature tour. A focused piece of motion that makes your product click quickly.</p><h3>Why SaaS is uniquely hard to explain</h3><p>A physical product can be photographed. A restaurant can show its food. SaaS, though, is usually a workflow: data goes in, something happens, a better outcome comes out. The value lives in the <em>change</em>, and a static screenshot can’t show change.</p><p>That’s why so many SaaS homepages slide into vague language: “streamline,” “empower,” “all-in-one platform.” The founder knows what those words mean in context. The visitor doesn’t, so they bounce.</p><p>Motion solves this because it can show before-and-after in seconds. A cursor clicks, a messy table becomes a clean dashboard, a notification fires. The viewer doesn’t have to imagine the workflow. They watch it.</p><h3>Start with the one thing the video has to prove</h3><p>The biggest mistake I see in SaaS explainers is trying to say everything. Every feature gets a scene, every stakeholder gets a mention, and the video ends up as long and confusing as the page it was meant to fix.</p><p>Before any script, answer this: <strong>what is the one thing a viewer must believe by the end?</strong></p><p>Some examples of a strong “one thing”:</p><ul><li>“This booking tool removes the back-and-forth of scheduling classes.”</li><li>“This platform cuts patient wait times.”</li><li>“This AI tool turns your notes into a finished book.”</li></ul><p>Everything in the video should serve that single claim. Features show up only as evidence for it. If a scene doesn’t support the claim, it goes, however proud you are of that feature.</p><h3>Show your real product, not just metaphors</h3><p>Abstract illustrations (floating clouds, gears, rockets) have their place, but they can make a product feel generic. For many SaaS companies, the most convincing visual is the interface itself, animated with intent.</p><p>That doesn’t mean a raw screen recording. Raw recordings are slow, cluttered, and full of distractions. The craft is in turning real UI into motion: isolating the panel that matters, zooming at the right moment, simplifying the screen, and timing each interaction to the voiceover.</p><p>If you want to see what that looks like in practice, the <a href="https://explainalab.com/#work">selected work on Explainalab</a> includes UI-driven explainers across healthcare, fitness booking, AI tooling, and EdTech, each built around the product’s actual interface.</p><h3>Script short, then cut shorter</h3><p>A good SaaS explainer script usually follows a simple arc:</p><ol><li><strong>The problem</strong>, in the viewer’s words, not yours.</li><li><strong>The shift</strong>: your product enters.</li><li><strong>The proof</strong>: two or three moments of the product doing its job.</li><li><strong>The outcome</strong>: what life looks like afterwards.</li><li><strong>The next step</strong>: one clear call to action.</li></ol><p>Write it out loud. Read it at a natural pace. Then cut every sentence that explains something the visuals will already show. Voiceover and picture should work as partners, not say the same thing twice.</p><p>The first few seconds matter most. Many viewers decide almost instantly whether to keep watching, so open on the problem or the payoff. Don’t open on your logo.</p><h3>Storyboard before you animate</h3><p>Animation is the expensive, time-consuming part of any explainer. Changing your mind halfway through it is the fastest way to blow up a timeline.</p><p>That’s why a storyboard, or even a simple shot-by-shot table, is worth its weight. For each shot, write down:</p><ul><li>What the viewer sees</li><li>What the voiceover says</li><li>What moves, and why</li><li>Roughly how long it lasts</li></ul><p>When you approve that table, you’re approving the plan, not getting a surprise at the end. It also forces the hard decisions (what to cut, what to emphasize) to happen while they’re still cheap.</p><h3>Where AI tools fit, and where they don’t</h3><p>There’s a lot of noise right now about generating whole videos from a prompt. AI video tools are genuinely useful: they can fill a gap with a background shot, an atmospheric transition, or a quick visual idea that would otherwise take hours.</p><p>But a SaaS explainer lives or dies on precision. Your UI has to look exactly like your UI. Timing has to land on the right word. Transitions have to carry meaning, not just look cool. Today that still calls for deliberate, hand-built motion, with AI as a helper, not the method.</p><p>A sensible rule: use AI where it saves time without costing accuracy, and keep your product’s actual interface and story under careful human control.</p><h3>Keep the process in one set of hands where you can</h3><p>Explainer projects often go wrong in the handoffs. A scriptwriter writes something the animator can’t stage. The voice artist’s pacing doesn’t match the edit. Feedback gets lost between three freelancers and a project manager.</p><p>Whoever you work with, look for continuity: the person who understands your brief should be close to the person making the edit. Explainalab, for example, runs the whole thing end to end, from brief and script through storyboard, After Effects animation, voiceover, and final delivery. The <a href="https://explainalab.com/#about">process and background are laid out here</a>.</p><h3>Deliver for where it will live</h3><p>The same video often needs to work in several places: a homepage hero, a product launch post, a paid ad, a sales email. Each has its own constraints, like aspect ratio, length, sound-off viewing, and file size.</p><p>Plan for that from the start:</p><ul><li><strong>Homepage:</strong> a clear explainer, plus perhaps a silent looping cut that plays behind the fold.</li><li><strong>Social and ads:</strong> shorter, captioned, vertical or square versions.</li><li><strong>Sales and onboarding:</strong> feature-specific cuts that answer the questions prospects actually ask.</li></ul><p>A little planning here turns one project into a set of assets your whole team can use.</p><h3>A quick checklist before you commission an explainer</h3><ul><li>Can you state the one thing the video must prove, in one sentence?</li><li>Do you know who the viewer is and what problem they’d describe?</li><li>Will the video show your real product, or a convincing simplified version of it?</li><li>Is there a storyboard step before animation begins?</li><li>Do you know where the video will live, and in which formats?</li></ul><p>If you can answer all five, you’re ready, and your video will likely be shorter, clearer, and more effective than most.</p><p><strong>Want help turning your product into a video people finish?</strong> I’m Ali at Explainalab, and I build SaaS explainers hand-animated in After Effects. <a href="https://explainalab.com/#contact">Tell me about your product</a> and I’ll tell you what the video needs to do.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=0f7e1ea64e3a" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Crypto Craze: The 07 Hottest AI Coins to Watch Out for in 2023]]></title>
            <link>https://medium.com/@aliislive42/crypto-craze-the-07-hottest-ai-coins-to-watch-out-for-in-2023-b039b283315?source=rss-8abc38f4d326------2</link>
            <guid isPermaLink="false">https://medium.com/p/b039b283315</guid>
            <dc:creator><![CDATA[Ali | Explainalab]]></dc:creator>
            <pubDate>Thu, 09 Feb 2023 22:33:55 GMT</pubDate>
            <atom:updated>2023-02-09T22:33:55.505Z</atom:updated>
            <content:encoded><![CDATA[<p>Hey there, fellow crypto enthusiasts! Are you tired of constantly hearing about the same old Bitcoin and Ethereum? Don’t get us wrong, they’re heavy hitters in the game, but have you ever considered branching out and exploring the world of AI-powered alt coins?</p><p>That’s right, the future of finance is becoming more and more intertwined with artificial intelligence, and we’ve got the inside scoop on the top 7 trending AI coins to invest in this year.</p><p>Neo (NEO) — This Chinese-based platform is often referred to as the “Ethereum of China.” It offers smart contract capabilities, but with a focus on digital identity and asset management.</p><p>VeChain (VET) — This blockchain platform is all about supply chain management. It’s already being used by big names in industries like luxury goods and agriculture.</p><p>IOTA (MIOTA) — This German-based platform is focused on the Internet of Things (IoT) and aims to provide a secure and scalable platform for machine-to-machine transactions.</p><p>NEM (XEM) — This Japan-based platform offers multisignature capabilities, encrypted messaging, and an overall focus on security.</p><p>Cardano (ADA) — This platform, created by the co-founder of Ethereum, is focused on sustainability and scalability. It’s also the first blockchain platform to be built on the principles of peer-reviewed research.</p><p>EOS (EOS) — This platform offers decentralized applications and smart contracts, with a focus on scalability and user experience.</p><p>Solana (SOL) — This platform boasts incredibly fast transaction speeds, making it a top choice for decentralized finance (DeFi) applications.</p><p>These are just a few examples of the exciting AI-powered alt coins out there. So why not take the leap and diversify your crypto portfolio with some of these hot picks for 2023?</p><p>Ready to start investing in AI coins but don’t know where to begin? Look no further! As a creative writer and editor, I offer services to help guide you through the world of cryptocurrency and make informed investment decisions. Let’s make some crypto magic happen!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b039b283315" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How to land job with killer resume in 2023?]]></title>
            <link>https://medium.com/@aliislive42/how-to-land-job-with-killer-resume-in-2023-e2ea72dd5694?source=rss-8abc38f4d326------2</link>
            <guid isPermaLink="false">https://medium.com/p/e2ea72dd5694</guid>
            <dc:creator><![CDATA[Ali | Explainalab]]></dc:creator>
            <pubDate>Wed, 18 Jan 2023 14:05:00 GMT</pubDate>
            <atom:updated>2023-01-18T14:05:00.370Z</atom:updated>
            <content:encoded><![CDATA[<p>“In today’s job market, it’s not enough to simply have a resume. It’s not enough to list your qualifications and hope for the best. It’s time to level up and make your resume a work of art — one that will make you stand out from the crowd, and land you that dream job in 2023.</p><p>Let’s start with the basics. Make sure your resume is up-to-date, with your most recent experience and qualifications at the top. Use a modern, professional design that reflects your personal brand. And don’t be afraid to get creative with the format — use a mix of text, bullet points, and even infographics to make your resume visually appealing.</p><p>But the real key to creating a killer resume is showcasing your unique talents and skills. Forget the generic phrases and buzzwords — use specific examples and metrics to demonstrate your achievements. Highlight your accomplishments, and show how they have made a real impact on your previous employers.</p><p>And remember, a resume is not just about what you’ve done, but also about who you are. Let your personality shine through, and don’t be afraid to let your voice come through in your writing. Use active verbs, and avoid passive language. Make sure your resume reflects your own personal brand, and showcases what makes you truly unique.</p><p>But don’t stop there. Be proactive. Go beyond the traditional resume and create an online presence for yourself. Develop a professional website or blog, create a portfolio of your work, and use social media to showcase your skills. Network with people in your field, attend conferences, and join online communities.</p><p>Finally, take the time to tailor your resume to the job you’re applying for. Research the company, and make sure your skills and experience align with what they are looking for. Customize your cover letter, and use the job description as a guide to highlight relevant qualifications.</p><p>Remember, landing your dream job is not about luck, it’s about putting in the work. So invest in yourself, and make sure your resume is a true reflection of who you are and what you can do. Stand out from the crowd, and make 2023 the year you land that killer job.”</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e2ea72dd5694" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>