What to Show Between Screen Recordings in a SaaS Explainer

Your SaaS explainer opens on the dashboard, follows the cursor into a menu, and stays inside the product for the next minute. Every feature is visible. The reason anyone needs those features is harder to see.

Adding office footage at random will not solve that problem. Use screen recordings to demonstrate the product, and use the space between demonstrations to explain the work happening around it. A supporting shot should establish a situation, connect two tasks, or give a finished result room to register.

The useful question is not “How often should we cut away?” It is “What does the viewer need to understand before the next interaction?” That answer tells you whether to use stock footage, a simple graphic, or another moment in the actual interface.

Mark the Product Proof Before Choosing B-Roll

Read the script and underline any sentence that promises a specific behavior: “Assign an owner,” “See the request history,” or “Change the due date.” Those lines need footage of the actual product doing the described thing, using a prepared demonstration account.

A person checking a laptop can establish the work setting. It cannot show that an assignment succeeded. A graphic can summarize the flow from request to completion, but it cannot demonstrate how the interface behaves. Protect those proof moments before filling the surrounding gaps.

Then circle sentences about the user's situation: requests arriving during a meeting, a colleague needing a decision, or preparation for a weekly review. These are possible cutaways. Use one only when it adds information the interface cannot easily show.

A Hypothetical SaaS Explainer: From Request to Owner

Imagine a fictional request-management app used by an operations team. Its explainer follows one request to replace a broken office chair. This is a planning example, not a customer story or a description of ScenePull features.

“A request arrives while you are preparing the weekly office review. Bring it into one queue. Open the request to see the details, then assign an owner and a due date. When the team meets, filter the queue to see what still needs attention.”

Before recording, confirm that your own product supports each action. Replace anything it cannot do. Create one fictional request, choose a consistent assignee, and use the same request title throughout. The viewer should recognize the item as the story moves between screens.

The following cut plan uses stock for the surrounding workplace and real product captures for the promised actions. The stock descriptions are desired candidates, not verified search results. Timing comes later, after the narration is recorded.

Notice the uninterrupted stretch through beats two, three, and four. The viewer is learning a connected operation. You do not need B-roll between every screen recording. The meeting cutaway belongs after the assignment is complete because the story has moved to a new occasion.

Choose a Cutaway That Sets Up the Return

A good transition makes the next screen understandable. In this example, a group taking seats introduces the weekly review. Returning to the filtered queue now answers a question: what will they discuss?

A clip of people celebrating would suggest a result the script has not established. A close-up of a complicated spreadsheet might imply a competing workflow you never explain. Both add interpretation that the next screen would have to correct.

Keep the workplace plausible for the audience. A small operations team does not need an executive boardroom to convey a meeting. Avoid assembling unrelated stock actors into what appears to be a continuous account of one customer's experience. You can use an empty meeting space or hands arranging papers when individual identity adds nothing.

If the transition is conceptual rather than physical, use a graphic you create in your editor. A short “Weekly review” card may introduce the next stage more clearly than another office clip. Our guide to matching B-roll to narration explains how to judge the action a supporting shot communicates.

Keep a Handoff Note for Each Screen Sequence

Copy this note into your production document before recording. It keeps the cutaway connected to what the editor needs to preserve:

• Viewer question: What should this sequence answer?
• Proof capture: Which actual screen action answers it?
• Required ending: What completed state must remain readable?
• Bridge: What changes before the next demonstration?
• Return cue: Which item, heading, or label helps the viewer reorient?

For the assignment sequence, the note might read: “Show who owns the chair request. End with the saved assignee and date visible. Bridge to the weekly meeting. Return on the queue heading and the same request title.” The editor now knows which frames carry meaning and which pauses can be trimmed.

Source Context, Then Test the Sequence

ScenePull analyzes your script, detects scenes, and finds matching existing stock videos and images. Review the candidates manually against the cut plan. A result for a product sentence does not mean that sentence should use stock.

Preview the useful action and check the intended crop. A meeting shot might work horizontally but lose everyone except a shoulder in a vertical version. Record the selected filename and source alongside its scene. ScenePull offers stock assets organized by scene in a downloadable ZIP, with access and limits depending on your plan. You import the files into your editor and assemble the video yourself.

With the recorded narration in place, watch each product action through to its result. If the explanation finishes before the interface becomes readable, extend the shot or shorten the narration. Do not cover an unclear demonstration with attractive footage.

Finally, watch the two transitions without sound. Can you recognize the move from individual request handling to a team review? Then restore the audio and check whether the returning screen answers the sentence being spoken. For more on choosing original captures, see our product-explainer footage guide.

A useful SaaS explainer gives the viewer a reason to care about the screen, then lets them see the product deliver the specific behavior described. Your cutaways earn their place by making that connection clear.