Who this is for: Sales, solutions and product teams preparing focused evaluation follow-ups.
What to prepare
- Approved conversation summary
- Known requirements and open questions
- Verified task evidence
- Fictional or permitted sample material
Copyable creative brief
An authored planning example. Replace illustrative details with your approved product facts and assets.
Illustrative brief: a fictional operations lead asks how a reviewer finds requests awaiting their decision. Create a 30-second video in a configured sample workspace. Show the actual reviewer and status filters, inspect matching request R-052 and hold its assigned reviewer and Awaiting review status together. Close by stating that delegation during absence is a separate question to confirm. Use fictional identities and supplied product evidence. Do not invent a customer quote, business result or promise that the example meets all evaluation requirements.
Choose a specific open question
Suitable questions concern observable behavior: where a reviewer finds work, how a record is handed off or which role can change a field. A video can demonstrate that narrow path under stated conditions.
A vague request to prove total business value, satisfy an unspecified policy or guarantee an outcome needs clarification and evidence beyond a short demonstration. Do not replace missing requirements with an attractive but unrelated workflow.
Turn conversation notes into an evidence brief
Separate what the prospect actually stated from your interpretation. Record the required role, object and completion criterion. In the illustrative example, finding the reviewer’s pending queue is known; absence delegation is not yet defined.
Collect matching screens for the conditions and result. If the product cannot show the requested behavior, say what the available example does demonstrate. A follow-up that accurately exposes a gap is more useful than a polished scene implying unsupported capability.
Personalize through the task
Use terminology from the approved conversation when it improves understanding, while retaining accurate product labels. Decorative logo changes do not make a generic tour answer a specific concern. Keep confidential material out of a public or reusable version.
Build the scene order as question, conditions, action, result and boundary. The closing action should resolve the next uncertainty: confirm the needed delegation rule, inspect a sample output or discuss an exception. It need not assume the evaluator is ready to buy.
Review against the actual requirement
Have the product owner check the demonstrated behavior and the conversation owner check the question. Ask whether the final state proves the promised answer and whether the limitation is understandable. Do not treat enthusiastic visual approval as requirements verification.
For a shorter cut, narrow the question further instead of hiding setup. For a longer cut, add one relevant exception with evidence. Keep a source register so the follow-up can be updated when the workflow changes. The sample brief here describes no real customer conversation or completed render.
Review checklist
- Known requirements are distinct from assumptions.
- Every scene helps answer the open question.
- The result is bounded to the demonstrated conditions.
- The closing action addresses the remaining uncertainty.