If you have ever sat through a SaaS explainer video and thought, “that was nice but I still have no idea what they do”, you are not alone.
Most SaaS explainer videos look beautiful. The animation is clean. The voiceover is professional. The music swells in the right places. And the homepage that hosts the video converts at the same rate it did before the $5,000 spend.
The fix is almost never the animation. It is the script. A great script saves a mediocre animation. A weak script kills a brilliant one.
This guide is the exact 7 section framework we use at ContentBuck for every SaaS explainer script. The framework that took PeopleOS from a 1.8% homepage conversion to 2.4%, a 34 percent lift, with a 75 second explainer. The framework that has now been refined across 200+ projects. Use it as a fill-in-the-blank template if you want.
Why most SaaS explainer scripts flop
Before the framework, you need to understand why scripts go wrong in the first place. In our review of over 300 SaaS explainer scripts, the same 3 problems show up over and over.
Problem 1: The script is written for the founder, not the buyer
The founder wants to talk about the product they spent 2 years building. They list every feature. They describe the architecture. They talk about the vision. The buyer wants to know one thing. Will this fix the painful problem I have today? Most scripts answer the founder's question and ignore the buyer's.
Problem 2: The script has no structural spine
Without a framework, scripts wander. A paragraph about the problem. A paragraph about features. A vague mention of customers. A CTA tacked on at the end. The viewer never builds the mental momentum needed to take action. A structured script pulls the viewer through a story they want to finish.
Problem 3: Too many words, not enough story
A 75 second video has room for around 180 words. Most first draft scripts come in at 300 to 400 words. The voiceover artist speeds up. The animation rushes. The viewer feels overwhelmed. Cutting words is the single highest leverage edit you can make.
These three problems compound. A founder-led script with no structure and too many words is the standard $5,000 explainer that nobody can summarize after watching. The framework below fixes all three at once. For a deeper look at why videos fail, see why B2B videos fail to convert.
Want a professional script with your explainer video?
ContentBuck includes scripts with every explainer video project. We write them based on your sales call recordings, not generic templates. Most scripts are locked in 5 to 7 days and the full video ships in 14.
Book a Free 30 Min CallThe 7 section framework (with word counts)
The framework is built around a 75 second runtime, which we have found to be the sweet spot for SaaS explainers. Long enough to land the message. Short enough to keep retention above 70 percent.
| Section | Runtime | Word Count | Job |
|---|---|---|---|
| 1. Hook | 5 sec | 12-15 | Stop the scroll. State the pain. |
| 2. Problem | 10 sec | 25-30 | Make them feel the cost of not fixing it. |
| 3. Solution | 10 sec | 25-30 | One sentence on what your product does. |
| 4. How it works | 20 sec | 50-60 | 3 steps. Concrete. Show, do not tell. |
| 5. Social proof | 10 sec | 25-30 | Customer name, metric, outcome. |
| 6. Objection handling | 10 sec | 25-30 | Kill the top doubt before they think it. |
| 7. CTA | 10 sec | 20-25 | One action. Specific. With a benefit reason. |
The 75 second rule: Most SaaS founders want a 2 to 3 minute explainer because they have a lot to say. Retention curves do not lie. The drop off between 75 seconds and 90 seconds is 20 to 30 percent. The drop off between 90 seconds and 2 minutes is another 30 to 40 percent. Get to the CTA fast. See how long should a B2B explainer video be for the full data.
Now let us walk through each section in detail with examples you can copy.
Section 1: Hook (5 seconds, 12-15 words)
The hook is the most important 5 seconds of your script. If the hook fails, nothing else matters. The viewer is gone.
The job of the hook is simple. Make the viewer think, “that is exactly my problem, I need to hear what comes next”. The way you do this is by stating the painful symptom your buyer feels every Monday morning. Not your product. Not your category. The specific pain.
Hook formulas that work:
- Most [ICP] waste [X hours] every week on [painful task].
- [ICP] are losing [outcome] because [problem].
- If you are [ICP] doing [task], you are doing it wrong.
- There is a hidden cost to [common workflow]. Most [ICP] never see it.
Real example from the PeopleOS script:
“Hiring teams lose 12 hours a week chasing recruiters, candidates, and feedback. There is a better way.”
That hook drove 70 percent retention past the 15 second mark, which is the single best leading indicator of conversion. See the full PeopleOS case study for the retention curve.
Section 2: Problem (10 seconds, 25-30 words)
The problem section is where you make the viewer feel the pain. The hook stated it. This section twists the knife. Use specifics. Use numbers. Use the exact phrases your buyers say on sales calls.
Problem section rules:
- Use 2 to 3 concrete examples, not abstract concepts.
- Quote the buyer's exact internal monologue.
- Show the compound cost. Not one painful task but the weekly toll.
- Make it visual. The animator will translate your words into visuals only if your words are vivid.
PeopleOS problem section:
“You bounce between 6 tabs to schedule one interview. Candidates ghost because the back and forth takes 9 days. Your best people get hired by faster teams.”
Notice the structure. Specific tactic (6 tabs). Specific outcome (candidates ghost). Specific cost (best people hired elsewhere). Every sentence escalates the stakes.
Section 3: Solution (10 seconds, 25-30 words)
This is where most scripts go sideways. The founder takes over. They list 8 features. They name the modules. The viewer's eyes glaze over.
The job of the solution section is to deliver ONE sentence that describes what your product does in a way the buyer can repeat to their boss. That is the test. If your CEO cannot repeat the solution sentence to a board member after watching the video, the sentence failed.
Solution section formula:
[Product name] is [category descriptor] that [primary outcome] for [ICP].
PeopleOS solution section:
“PeopleOS pulls every interview, every recruiter, and every candidate signal into one inbox. So your team hires faster without the chaos.”
Note what is missing. No mention of features. No talk of integrations. No reference to AI. Just the core promise. Features come next.
Section 4: How it works (20 seconds, 50-60 words)
The how it works section is your longest. It is also where most viewers convert. They are bought in on the problem. They want to see the product.
Use a 3 step structure. Always 3 steps. Not 4. Not 5. Three. Three is the magic number for cognitive ease. Each step gets 6 to 8 seconds of runtime and 15 to 20 words.
The 3 step formula:
Step 1: Setup or input
What the user puts in. Connect calendar. Upload candidates. Paste your URL.
Step 2: The magic
What your product does behind the scenes. The unique value. The reason it is not just a workflow tool.
Step 3: The output or outcome
What the user gets. The deliverable. The save. The win.
PeopleOS how it works:
“First, connect your ATS and calendars in 90 seconds. Next, PeopleOS routes every interview request through one shared inbox and auto-fills feedback forms after each call. Then your hiring manager closes loops in minutes, not days. Time to hire drops by 40 percent.”
Every step is concrete. Every step has a verb. Every step ends with a benefit. That is the standard.
Section 6: Objection handling (10 seconds, 25-30 words)
Most B2B explainer scripts skip this section. That is a mistake. Every buyer has a top objection. It is either price, switching cost, complexity, or risk. The script that handles the objection directly converts 20 to 30 percent better.
The top 4 objections to address:
- Time to value: Sounds great, but it will take us 6 months to roll out.
- Switching cost: Sounds great, but we already use [competitor].
- Complexity: Sounds great, but my team will need months of training.
- Risk: Sounds great, but what if it does not work?
PeopleOS objection handling:
“Worried about migration? We do it in a week. Worried your team will hate it? They will not, because PeopleOS lives inside the tools they already use.”
Two objections handled in 26 words. That is the bar.
Section 7: CTA (10 seconds, 20-25 words)
The CTA is where most scripts whisper. They say “learn more” or “try it today” and pray. That is a wasted CTA.
A converting CTA has three parts. The specific action. The benefit reason. The urgency or scarcity element.
The 3 part CTA formula:
Part 1: The action
Specific verb. Book. Start. Get. Never “learn more”.
Part 2: The benefit reason
Why should they click now? What specific value will they get on the next page or call?
Part 3: The urgency element
A reason to act this week, not next month. Free trial ending, deal pricing, limited bookings.
PeopleOS CTA:
“Book a 20 minute demo this week and we will rebuild your hiring inbox live on the call.”
Notice the action (book demo). The benefit (we rebuild your inbox live). The urgency (this week). 18 words. Perfect.
Need a script that actually converts?
We write scripts based on your sales call recordings. Then we animate, voice, and deliver the full explainer in 14 days. Same framework that delivered the 34 percent conversion lift for PeopleOS.
Book a Free Strategy CallBefore and after script examples
The fastest way to internalize the framework is to compare a weak script section against a strong one. Here are 4 side by side comparisons from real client edits.
Hook
Before (flat)
Welcome to PeopleOS, the all-in-one HR platform.
After (converting)
Hiring teams lose 12 hours a week chasing recruiters, candidates, and feedback. There is a better way.
Problem
Before (flat)
HR is hard and tools are fragmented.
After (converting)
You bounce between 6 tabs to schedule one interview. Candidates ghost because the back and forth takes 9 days.
Solution
Before (flat)
PeopleOS is a unified HR platform with powerful features.
After (converting)
PeopleOS pulls every interview, every recruiter, and every candidate signal into one inbox.
CTA
Before (flat)
Visit our website to learn more.
After (converting)
Book a 20 minute demo this week and we will rebuild your hiring inbox live on the call.
For more real examples, see our breakdown of the best B2B explainer videos and what made each one work.
7 common mistakes that kill scripts
These are the patterns that show up in 80 percent of first draft scripts we review. Fix these and you will outperform 90 percent of SaaS explainer videos in market.
Leading with the product
Your buyer does not care what you built until they care about the problem you solve. Open with the pain, not the platform.
Using internal jargon
Words like orchestration, unified workspace, and operating system mean nothing to buyers. Write in the language they use in Slack.
Listing features instead of outcomes
Features are what your product does. Outcomes are what changes in the buyer's day. Always translate one to the other.
Cramming too many words in
A 90 second video has room for 220 words at most. Founders try to fit 350. The voiceover speeds up and the script loses everyone.
Weak or generic CTA
Learn more is not a CTA. Book a 20 min demo and we will rebuild your hiring inbox live is a CTA. Be specific. Give a reason.
Writing for the founder, not the buyer
The script gets approved by the founder but watched by the buyer. Always test the script against an actual ICP member before locking it.
Forgetting the loop
Tie the end of the script back to the hook. If you opened with 12 hours lost per week, close with how the product gives 12 hours back.
The single biggest unlock for most teams is mistake number 4. Cut your draft by 30 percent and you will be shocked at how much sharper the script feels. Read your draft out loud at conversational pace. If you cannot fit it in 75 seconds, cut more.
How we write scripts at ContentBuck
The framework above is what we use. Here is how we actually apply it on a client project from kickoff to locked script.
Day 1: Discovery and sales call mining
We ask for 5 to 10 of your last sales call recordings. We listen for the exact pain phrases your buyers use. Those phrases become the raw material for the hook and problem sections.
Day 2: Draft script v1
We write the first draft using the 7 section framework. Word count is locked at 180 to 200 words. Every sentence is read out loud to test pacing.
Day 3-4: Founder review and revision
We share the draft with the founder. We push back on jargon, internal language, and any feature lists. We do not move to animation until the founder can repeat the solution sentence from memory.
Day 5: ICP test
We share the script with 2 to 3 actual buyers in your ICP. If they cannot describe what your product does in one sentence after reading the script, we revise.
Day 6-7: Lock and storyboard
Script gets signed off. Storyboard begins. Voiceover artist gets booked. Animation queues up. Total time from kickoff to delivered video is usually 14 days for Core projects, 21 days for Premium.
For a full breakdown of pricing and what is included, see our SaaS explainer video pricing guide or our explainer videos for SaaS service page.
Get a script and explainer that converts
Every ContentBuck explainer comes with a professionally written script using the 7 section framework. We write based on your sales calls. We test against your ICP. We deliver in 14 days. Same framework that produced the 34 percent conversion lift for PeopleOS.
Book a Free 30 Min CallNo credit card. No commitment. Just an honest conversation about your explainer.
Frequently asked questions
How long should a SaaS explainer video script be?
A SaaS explainer script should be 150 to 220 words for a 60 to 90 second video. People speak at 150 to 160 words per minute in voiceover. A 75 second video lands at 180 to 190 words. Longer scripts force fast pacing and lose viewers before the CTA.
What is the best structure for a SaaS explainer video script?
The 7 section framework works for almost every B2B SaaS explainer. Hook (5 sec), problem (10 sec), solution (10 sec), how it works (20 sec), social proof (10 sec), objection handling (10 sec), CTA (10 sec). Total runtime 75 seconds. This structure converts because it mirrors the buyer's internal monologue.
How do you write a hook for a SaaS explainer video?
Open with the painful symptom your buyer feels every Monday morning. Not your product. The pain. PeopleOS opened with hiring teams losing 12 hours a week to manual coordination. That hook drove 70 percent retention past the 15 second mark and a 34 percent homepage conversion lift.
Should you write the script before designing the video?
Yes. Always. The script is the spine. Animation, voiceover, and music exist to serve the script. Designing first creates beautiful videos that say nothing. We have seen $10,000 explainers fail because the agency designed first and wrote second.
What makes a SaaS explainer script flop?
Three things kill scripts. Leading with the product instead of the buyer's pain. Using internal jargon your buyers do not search for. And listing features instead of describing transformations. Scripts that flop sound like they were written for the founder, not the buyer.
How much does it cost to get a SaaS explainer script written?
A standalone script from a B2B copywriter runs $400 to $1,500. A script bundled with the explainer video is usually included for free at most agencies. ContentBuck includes scripts with every explainer at $1,800 Core and $3,999 Premium.
Related reading
Keep researching
SaaS Explainer Video Pricing in 2026
Real prices for B2B explainer videos in 2026.
How Long Should a B2B Explainer Video Be?
Retention data by length. The 75 second rule explained.
Best B2B Explainer Video Examples (2026)
Real explainers broken down by what makes them work.
Product Demo vs Explainer Video
When to make which type of video for your SaaS.
Section 5: Social proof (10 seconds, 25-30 words)
Social proof in a SaaS explainer is not a logo wall. Logo walls are visual filler. They prove nothing. The script needs a named customer with a specific result.
Social proof formula:
[Customer name], a [ICP descriptor], used [product] to [specific outcome with number] in [time frame].
PeopleOS social proof:
“Series B startup Notch cut their time to hire from 32 days to 11 days in the first 90 days on PeopleOS.”
If you do not have a single named customer with a measurable outcome, this section is hard to write. The fix is to invest in one customer interview before you produce the video. Without it, you have a generic explainer.