11-minute read · Customer selection, evidence, interviewing, narrative, and approval
The praise-without-proof problem
Many customer videos contain warm statements—great partner, easy to use, transformed our process—but give a skeptical buyer nothing to evaluate. The customer sounds sincere; the story remains generic.
SaaS operators often note that a specific customer statement about time saved can carry more weight than extensive product footage. The power comes from specificity and relevance, not from placing a percentage on screen. A defensible observation about one workflow is better than a dramatic metric no one can explain.
Choose the customer by buyer relevance
Select a story that helps a current prospect resolve an objection or imagine a path. The biggest logo is not always the best subject. Look for a recognizable starting problem, an identifiable decision owner, a meaningful implementation moment, observable use, and an outcome the customer can discuss.
Confirm participation, internal communications approval, recording access, data permissions, trademark use, review process, distribution, and expiration before the interview. A customer willing to speak but unable to approve the final story can stall the production indefinitely.
Build an evidence ladder
| Evidence | Example | Control |
|---|---|---|
| Specific observation | “Weekly reporting no longer starts with exporting three files.” | Show or explain the former and current workflow |
| Operational change | One owner now reviews exceptions instead of compiling every record | Confirm scope and who experienced the change |
| Measured result | Preparation time changed from one approved baseline to another | Document period, method, denominator, and attribution limits |
| Strategic consequence | The team can review results before the weekly meeting | Present as customer experience, not a universal guarantee |
Interview for scenes, not slogans
Ask the customer to reconstruct events: What did the old process look like on a difficult day? Who felt the problem first? What alternatives were considered? What happened during implementation? When did they trust the new workflow? What still requires human judgment?
Follow abstract answers with “Can you give me a specific example?” and “What would I have seen?” Record the questioner’s silence so the customer finishes the thought naturally. Do not feed the desired phrase back to them and call the result authentic.
Use a change narrative
- Former reality: a specific operational situation.
- Cost of staying: the consequence for people, speed, risk, or decision quality.
- Decision: why the team changed and what made them cautious.
- Implementation: how the product entered real work, including friction worth understanding.
- Mechanism: the part of the workflow that caused the change.
- Evidence: approved observation or measurement.
- Perspective: who should consider a similar approach and under what conditions.
Make product footage serve the testimony
Show the workflow the customer describes, using approved data or a representative environment. Do not cover a specific operational claim with a generic dashboard animation. Use role, location, process artifacts, and customer environment to establish that the story belongs to a real organization.
Give the customer an accuracy review, not an open invitation to reinvent the edit. Separate factual, legal, and brand corrections from stylistic preference, and identify one final approver on each side.
What SaaS teams report
The article is informed by SaaS discussions emphasizing that specific customer evidence can outweigh generic product polish, that video assets should serve different stages of a complex buyer journey, and that marketing should draw from real product insight instead of production for its own sake. Those discussions reinforce the value of a narrow, defensible customer story over a polished collection of generic praise.