Sales enablement
Turn a recorded product demo into a one-feature sales follow-up
Turn an existing product demonstration into a focused answer for a buyer. Keep prerequisites, actions, visible results and limitations in the cut.
After a sales conversation, the buyer may need an answer to one practical question. Sending the full product demo makes them find it again. Sending a polished feature montage may remove the steps that would have answered it.
A useful follow-up cut shows one feature doing one relevant job. It preserves enough setup for the buyer to understand what they are seeing, shows the action and its result, and explains any condition that affects whether the same workflow would work for them.
For an in-house product marketing team, this is a way to reuse a recording the business has already invested in. The starting point is the buyer's question, not the most impressive screen in the footage. Wistia's sales-video examples include a focused demo made to answer a prospect's earlier question.
01
Define the question before choosing the feature
Write down what the buyer needs to decide. “Interested in reporting” is too broad. “Can we automatically send each regional team its weekly report?” gives the edit a clear purpose.
Then locate a passage that actually demonstrates the answer. A presenter mentioning the capability is weaker evidence than showing the configuration and the resulting view. Sometimes the recording contains the explanation but not the proof. In that case, use it as an explanation, ask for a focused new recording, or arrange a live demonstration. Do not present missing evidence as though it appears on screen.
Confirm that the recorded product version and the demonstrated configuration remain relevant before starting the cut. An accurate recording can become an inaccurate follow-up when a setting, interface or availability condition changes.
02
Build the six-part proof chain
Use this sequence to decide what the edit needs:
Buyer question. Establish the task or concern in terms the buyer recognises. This can be supported by the accompanying message if the recording does not contain a suitable introduction.
Prerequisite. Preserve the required starting state: an existing connection, a saved filter, prepared data or a particular account capability. A feature that works after setup should not appear to work without it.
Action. Show the meaningful interaction. Retain enough of the interface for the viewer to understand which control was used and what changed.
Result. Show the resulting screen, output or confirmation. Let the viewer inspect it rather than cutting away as soon as it appears.
Qualification. Keep conditions that affect the answer, such as configuration requirements, scope limits or a manual step elsewhere in the workflow.
Next step. Choose one action that follows naturally: confirm a requirement, review a sample output or arrange a demonstration using the buyer's own scenario.
This is an editorial structure, not a promise that every recording contains all six parts. Missing prerequisites and qualifications may need a product owner's confirmation before the asset is sent.
03
A hypothetical selection decision
Imagine a recorded demo of a reporting product. The presenter shows how an administrator selects a region and exports a report. Later, they explain that the example uses a preconfigured data connection and saved filters.
For a buyer asking about recurring reports, the preconfiguration matters. The clip needs to explain the prepared connection and filters. It also needs to distinguish producing a report manually from scheduling its delivery. Showing a successful export does not demonstrate that the product can send that report automatically every week.
This scenario is invented to illustrate the editing decision. It is not a customer story, an Anjin Media demonstration or a claim about a real reporting product.
If the footage never demonstrates the scheduling behaviour the buyer asked about, choose a narrower promise for the clip: it shows how to prepare and export the regional report, while automated delivery needs a separate answer. A precise partial answer is more useful than a confident but unsupported one.
04
Choose the footage that proves the narrower answer
For the hypothetical reporting demo, the useful edit would retain the prepared connection, the regional filter selection and the resulting export. Those three moments explain the starting state, action and visible result.
The scheduling claim would stay out. A spoken mention of recurring reports, without the relevant setup or delivery being shown, does not turn the export into a demonstration of automation. The accompanying message can identify scheduled delivery as the remaining question to verify.
Use these decisions when selecting a real passage:
- Keep the prerequisite if removing it would make a prepared workflow look ready from a blank account.
- Keep the action and output together so the buyer can see what changed and why.
- Leave time to read the result if its labels or values are the proof of the answer.
- Narrow the promise if the recording explains a capability but does not demonstrate it.
A colleague who has not watched the full demo should be able to explain what the user supplied, what the product did and what remains to be done. If they cannot, restore the missing step or make a smaller claim.
05
Protect the screen evidence
Choose the output shape around the interface. A wide application screen may be clearer in landscape than in a vertical crop. Before cutting, identify the labels, controls and output values the viewer must read.
Watch the export at its likely viewing size. Check that captions do not cover the button being used or the result being discussed. Listen for references such as “over here” that become unclear when the frame changes.
Do not remove a processing wait in a way that creates an unsupported speed claim. You can shorten irrelevant waiting, but keep the sequence understandable and make any consequential time compression clear. Similarly, do not join an input from one example to an output from another as though they belong to the same run.
A cleaner recording may be necessary when the original screen is too small. Enlarging an unreadable source cannot reliably recover information that was never captured clearly.
06
Review the answer, not just the finish
Ask the product owner or appropriate reviewer to check the exact export against four questions:
- Does the video answer the buyer's actual question?
- Are the required setup and availability conditions clear?
- Does the shown result follow from the shown action?
- Does the title or accompanying message promise more than the evidence supports?
Record the product version or review date with the asset so the team knows what to recheck before reusing it. Store the buyer-facing description separately from any internal notes about missing proof.
Keep the next step specific. If the remaining uncertainty is configuration, invite a configuration check rather than attaching a generic request to book another meeting.
07
Where Anjin Media fits
Anjin Media takes a written brief and selected footage to produce a source-grounded edit. Use the six-part structure to explain what the cut must show and what it must not imply. Anjin Media overview
Its plan records source passages, and render results identify the plan version used. Those references help a reviewer compare the proposed sequence with the demonstration. Composition results
For screen-heavy footage, the documented bars crop mode preserves the full frame; it does not guarantee readable interface text. Composition settings
The practical test is whether the buyer can understand the starting state, follow the action and judge the result. Once that is true, the recording has become a useful follow-up rather than another tour of the product.
For the wider process of choosing useful edits from existing recordings, see the B2B video content repurposing system.
For another screen-heavy source, see the slide-heavy webinar guide and its phone-readability checks.
08
Common questions
What if the interface has changed since the recording?
Check whether the underlying workflow and availability conditions still hold. Small visual differences may need a clear note; changed steps or behaviour may require new footage. Do not send an old screen sequence as current merely because the feature name is unchanged.
Can I use test data in the follow-up?
Yes, if the demonstration is appropriate to share and clearly identified as using test or sample data. Avoid presenting a prepared example as a buyer result, a live customer outcome or evidence of typical performance.
What if the buyer forwards the clip without my message?
Make the video title and opening context specific enough to stand alone. Any condition essential to interpreting the demonstration should travel with the asset, not exist only in an email that the next viewer may never receive.
About this field note
Written by Anjin Media's editorial team from hands-on work with long-form video, cut plans and searchable archives. Product details are checked against the documented platform behaviour before publication.
