A completed interview can help answer several sales questions, but turning it into ten clips is not automatically useful. Begin with the question a salesperson needs to answer, then select the smallest piece of supported material that helps.
The output is an asset pack with instructions: what each item explains, where its evidence comes from, which context must remain and what use has been cleared. This is an editorial handoff after an interview, not a reason to claim that every sentence can become an advertisement.
Ask Sales for a question, not a format wish list
“We need more customer content” is hard to act on. Ask for the buyer question and the moment in the conversation when it appears. A salesperson may need to explain how implementation responsibilities changed, rather than prove that a familiar logo uses the software.
Choose one question for the first pack. Find the relevant passage and check that it contains an actual account, not merely the interviewer’s suggested answer. If the material does not answer the question, record the gap. Do not invent a linking claim to make the interview fit.
The coverage audit can help locate existing material. The evidence register supplies the source and factual boundaries once a passage is selected.
A completed three-asset handoff
Fictional exercise: a facilities coordinator has described how one location introduced a shared maintenance schedule. The agency is preparing assets for an agreed sales follow-up use. The interview, permissions and output decisions below are all invented teaching material.
The sales question is: “Who handled urgent requests while the new scheduling process was introduced?” The relevant account explains that the coordinator kept ownership of urgent requests while routine jobs moved into the shared schedule. It does not establish a financial saving or a company-wide rollout.
| Asset | Useful content | Context that stays | Release decision in this exercise |
|---|---|---|---|
| One-slide explanation | A simple before/during diagram of responsibility for routine and urgent jobs | One location; coordinator’s described process; link to the full story | Cleared for the specified sales follow-up deck, version 2 |
| FAQ answer | A short written response explaining the parallel handling of urgent requests | Descriptive example, not a guarantee that every rollout works this way | Cleared for the same follow-up email, version 1 |
| Short clip brief | A proposed extract from the coordinator’s explanation | The question and enough of the answer to retain the scope | Not yet cleared; proposed clip and caption need review |
The third item is deliberately a brief, not a finished or approved clip. A useful pack can contain two released assets and one clearly held production task.
Write the slide around a specific account
For the fictional slide, the headline is “One location kept urgent requests with the coordinator during rollout.” The diagram has two lanes: routine jobs entering the shared schedule and urgent requests still reaching the coordinator. A footer identifies it as the experience described in the customer story and links to the full account.
Avoid turning that into “Roll out without disruption.” The stronger wording would make a broader promise than the material supports. A salesperson can explain why the example is relevant to the buyer without presenting it as a universal outcome.
Include the file version and approved use in the handoff notes. Keep those operational notes separate from the visible sales slide so the buyer receives a clear explanation rather than an internal audit document.
Build an FAQ answer that can stand alone
The fictional FAQ reads:
In the location described, the coordinator continued to handle urgent requests while routine jobs moved into the shared schedule. The team introduced the new process alongside that existing responsibility. The full story explains the setting and the participant’s role; it does not establish that the same arrangement fits every organisation.
The answer preserves the actual scope without making the reader reopen an entire transcript. If the customer has not cleared this reuse, keep the text in draft. Permission for an article is not automatically permission for a deck, a paid campaign or another channel.
Edit a clip for one useful moment
Identify the source timecodes, the question being answered and the minimum context the viewer needs. Choose the runtime after reviewing the passage, rather than forcing the complete account into an arbitrary number of seconds.
For the fictional clip, the producer would first check whether the coordinator’s answer remains understandable without the interviewer. If removing the question makes the explanation ambiguous, keep it in the clip or add an accurate on-screen question. Do not stitch separate sentences into a new causal claim.
Specify caption wording, name treatment and intended placement in the production brief. Treat a new crop, translation or destination as a reviewable version. Check what the customer actually agreed to before exporting it for release.
Give the salesperson a use note and a feedback question
Hand over the buyer question, the relevant asset, the limits of the example and the link to the full story. Explain which item remains on hold. This gives Sales a way to use the material accurately without guessing at permission or inventing results.
After use, ask what question the buyer still had. Separate “the salesperson used the slide” from a customer response or a purchase. No single content handoff proves that it caused a sale. If the missing answer requires another customer conversation, coordinate that request through the reference queue rather than approaching the same participant again from another team.