# Should our homepage testimonial and sales case study be the same video? By Wideframe Editorial Use the same source interview, but make separate cuts when the viewer's question changes. A homepage visitor may need a quick reason to care; a sales prospect may need detail about implementation, fit, or a result. Wideframe can help find the relevant source answers so the second version becomes a purposeful edit rather than a shorter copy. ## What you’ll take away - Change the audience question before changing the runtime. - Keep one source-based master and clearly named versions. - Add context to each cut so it works independently. ## Define what each viewer already knows A homepage viewer may not know the product category, the customer's problem, or why the speaker is relevant. A prospect in a sales conversation may already understand the product and want to resolve one concern. Giving both people the same introduction can waste the second viewer's time while leaving the first confused. Write one sentence for each context. For example, an illustrative homepage brief might be “Show why scattered review notes are a real problem.” A sales brief might be “Explain how this team brought reviewers into one process.” These are different questions even when they use some of the same footage. ## Choose different openings from the same interview The homepage cut can begin with a recognizable problem or concise change in the customer's work. Introduce enough identity to establish the perspective. Avoid requiring the viewer to understand a technical acronym before the story becomes meaningful. The sales cut can begin with the relevant practical answer, such as who owned implementation or how an existing tool remained part of the process. It need not repeat the broad brand introduction. A short title can state the question being answered so the salesperson can send it without a long explanation. ## Find source material for the two briefs In Wideframe, identify the interview folder and ask for separate groups of answers matching the two questions. Use the public [soundbite recipe](https://try.wideframe.com/skills/find-soundbites/) when you want to save that task. Label candidates by intended use rather than immediately committing them to a final timeline. Some excerpts will serve both versions, but their neighbors may differ. A result can be the homepage payoff while the sales cut needs the preceding explanation of how it was achieved. Keep access to the longer answer so you can restore that context. ## Make the sales cut more useful, not merely longer Additional duration should supply information the buyer needs: prerequisites, team roles, an implementation detail, or the conditions around an outcome. Do not fill the sales version with generic praise that was removed from the homepage cut. A detailed passage can work well when it answers an active question. Use supporting product footage to show the process and brief text to explain unfamiliar terms. Keep the customer's specific experience visible; a sales cut should not turn one account into a universal promise. ## Let the homepage cut stand alone The homepage version needs a clear subject and a complete thought even if it is short. Do not assume surrounding page copy will explain every pronoun or technical reference. Captions and identity text should make sense at the actual displayed size. Give the viewer a natural next step in the surrounding page or closing treatment. The customer's statement should remain their statement, not be rewritten as a sales call to action. Keep the publisher's invitation visually separate from testimony. ## Maintain two versions without losing the master Build the versions as clearly named sequences from the same source-based project. Keep the main source selections and longer answers available. Finish each version for its destination, including captions and any product visuals specific to that cut. When review notes arrive, identify which sequence they apply to. Wideframe's [review-note workflow](https://try.wideframe.com/skills/apply-review-notes/) supports explicit changes as a new version. A factual correction may affect both cuts, while a pacing request may affect only one. Do not blindly mirror every revision. ## Add future versions only when the question differs A new customer-video version is justified when it helps a distinct audience or decision. Industry-specific context, a technical buyer's concern, or a new implementation question may warrant another cut. A different filename or arbitrary runtime does not. Keep the source answers organized by question. The next campaign can draw on those selections without turning every deliverable into a completely new edit. This makes a recurring customer-story program more coherent for both the editor and the people using the videos. ## Try this request Find two sets of answers in this customer interview: one for a homepage visitor asking why the problem matters, and one for a sales prospect asking how implementation worked. Suggest separate openings and the necessary context for each, while keeping shared source references. ## Questions ### Does every customer story need two versions? No. Use a second cut when it answers a meaningfully different question or needs a different level of detail. ### Should the sales version always be longer? Not necessarily. A narrow answer to one concern can be shorter than a broad overview. Let the buyer's question determine the content. ### Can a factual correction affect both cuts? Yes. Keep shared sources and claims traceable so the editor can update every affected version. ## Sources - [Wideframe: find-soundbites](https://try.wideframe.com/skills/find-soundbites/) — consulted 2026-09-18 - [Wideframe: apply-review-notes](https://try.wideframe.com/skills/apply-review-notes/) — consulted 2026-09-18 - [Wideframe: captions](https://try.wideframe.com/skills/captions/) — consulted 2026-09-18 Published by Wideframe. Examples are not customer results or benchmarks. ## Start with your next customer story Bring one customer interview and two audience questions. Prepare distinct source selections and shape the versions in Premiere. [Start free trial](https://try.wideframe.com/onboarding?start=trial). Seven days; card required; $100/month afterward unless canceled. Apple Silicon Mac and Premiere Pro required. [Current terms](https://try.wideframe.com/pricing/).