Product launches / Prompt

Prompt: show product proof before the launch tagline

Lead with proof when the product action is understandable without a long introduction. Let the viewer inspect the useful result before asking them to accept the tagline.

By AnimroUpdated 2 min readAI-assisted · independently agent-reviewed

Who this is for: Launch teams translating a specific creative job into a motion brief.

What to prepare

  • A clear supplied starting state
  • A verified action and result
  • A proposed tagline
  • Current brand and access copy

Copyable creative brief

An authored planning example. Replace illustrative details with your approved product facts and assets.

Create a 30-second launch sequence for PRODUCT_NAME that begins with PROOF_ACTION rather than a slogan. Establish START_STATE briefly, show the supplied action and hold RESULT_STATE with its relevant labels readable. Use the same example object throughout and do not add outcome metrics or testimonials.

After the result is understandable, introduce TAGLINE. The line must describe what the demonstration actually establishes. If the tagline implies a broader guarantee, flag it and propose a narrower description of the shown action. Reveal the product name and approved logo after the evidence, keeping the result available as context.

Use a quiet visual hierarchy so the opening does not feel like unexplained clicking. Add a short task label if necessary, but avoid a category essay before the action. Close with CURRENT_STATUS and NEXT_ACTION. Preserve any prerequisite or permission condition required to interpret the demonstration honestly.

Make it your own

PROOF_ACTION
Choose a task with a readily understandable result.
TAGLINE
Keep its claim within the demonstrated evidence.
RESULT_STATE
Use the exact supplied final state and labels.
PRODUCT_NAME and START_STATE
Supply the approved identity and the initial object, role and prerequisites needed for the proof.
CURRENT_STATUS and NEXT_ACTION
Close with current access and a destination supported by the demonstrated scope.

Choose readable proof

An illustrative assignment workflow can begin with an empty owner field and end with a named owner on the same request. A suitable closing line is about a visible handoff.

The same footage would not justify “No work falls through the cracks.” That broader claim requires different evidence.

Adapt the context

If the viewer needs category knowledge, add a task sentence before the action. If the action is already familiar, keep the opening almost entirely visual.

For a short cut, reduce the identity reveal rather than removing the result hold.

Correct an unearned tagline

If the final words introduce savings, reliability or adoption absent from the proof, rewrite them. If the action is too fast to inspect, simplify transitions and extend the hold.

The final copy should feel like a precise summary of what the viewer saw, not a new unsupported pitch.

Review checklist

  • The action is understandable before the tagline.
  • The tagline adds no unsupported guarantee.
  • The same object anchors the evidence chain.
  • The result remains readable.
Explore product launches ↗