Social teaser production

The working approach

Open with a recognisable problem.
Show two or three distinct proof moments.
Use a destination-specific closing action.

Earn the next view with proof

The opening should let the right person recognise their situation. A specific work problem is often more useful than a vague claim about transformation. Follow it quickly with a real product moment. The teaser does not need to explain every prerequisite, but its cuts should preserve a believable connection between the problem, the action and the result.

Prepare a separate closing action for the placement. A social post can lead to a full walkthrough, a feature page or a trial entry. Match the invitation to the amount of understanding the teaser has earned. Someone who has only seen a brief result may need a longer explanation before signing up. Keep different hooks tied to the same verified evidence when you want to learn which message resonates, rather than changing the entire creative at once.

A concrete example

For a content tool, show review, saved ideas and the calendar, then invite the viewer to explore the full demo.

Before recording this scenario, write down what the starting screen contains and what should be different at the end. This gives the reviewer an observable result to check, rather than asking them to approve a general impression.

The mistake to avoid

A mystery hook can attract attention from people the product cannot help.

If the source cannot support the intended message, narrow the claim or capture the missing evidence. A transition, caption or voiceover can explain a real change; it should not manufacture one.

Put it into a production brief

Replace the bracketed fields before using this brief. The scenario is illustrative; keep only the actions your product actually supports.

EDITABLE PRODUCTION BRIEF

Purpose: Social teaser production.
Audience: [specify the viewer and their familiarity with the product].
Decision: [what should the viewer understand or do next?].
Approach: A teaser offers enough evidence to earn a second look. It does not need to teach the complete workflow.

Required evidence:
1. Open with a recognisable problem. Show the relevant entry state, action and completed result.
2. Show two or three distinct proof moments. Show the relevant entry state, action and completed result.
3. Use a destination-specific closing action. Show the relevant entry state, action and completed result.

Reference scenario: For a content tool, show review, saved ideas and the calendar, then invite the viewer to explore the full demo.
Avoid: A mystery hook can attract attention from people the product cannot help.

Deliverable: [duration], [format], [placement].
Use only recorded product behaviour. Preserve the full original.
Acceptance: check each claim against its visible scene, review at actual viewing size, and test the final file.

Review before delivery

Evidence: can a new viewer identify the result described in the example without being told where to look?
Reading distance: are the relevant controls and labels understandable at the intended placement size?
Continuity: does each cut preserve the relationship between the action and its result?
Accuracy: does the final caption describe the visible product state, including any limits?

Using this with Demovela

The automatic URL workflow currently supports Postraid and Adfolio. Other product scenarios on this page are production-planning examples, not compatibility claims. Adapt the brief to your own recorder or editor. Demovela preserves originals and creates separate outputs; review the resulting file before publishing.

Check the current preview scope →

Keep the workflow moving

Choose the next resource based on the decision you still need to make.

Browse the complete resource library →