Product launches / Prompt

Prompt: tease an upcoming product without implying access

Use a waitlist teaser to explain a product direction without implying immediate access. Keep concept labels and release status inside the main visual story.

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

  • Approved problem statement
  • Clearly identified concept or verified product assets
  • Current availability wording
  • Waitlist destination

Copyable creative brief

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

Create a 15-second teaser for PRODUCT_NAME around PROBLEM_LINE. The public state is WAITLIST_STATUS. Use CONCEPT_ASSET only with a readable concept label; do not make it resemble an already available product demonstration. Do not invent integrations, release dates, usage counters or customer endorsements.

Open with the recognizable problem in one short sentence. Introduce the intended job through a small visual arrangement or approved concept screen. Keep PLANNED_BEHAVIOR explicitly framed as planned. Use restrained motion to connect the problem and direction rather than implying a completed interactive workflow.

End with the product name, the accurate availability statement and “Join the waitlist” when that is the supported action. Keep the closing text large enough to read. If the supplied asset shows actual verified behavior, identify that narrower evidence without claiming public access. Flag any conflict between the concept, copy and destination before final production.

Make it your own

PROBLEM_LINE
Describe a task the intended viewer recognizes.
CONCEPT_ASSET
State whether the material is a concept, prototype or verified screen.
PLANNED_BEHAVIOR
Use future-oriented wording without a guarantee or invented date.
PRODUCT_NAME and WAITLIST_STATUS
Use approved identity and the current waitlist wording that matches the real destination.

Build an honest preview

An illustrative task-planning concept could show cards arranged into a proposed week with “Concept preview” visible. It should not show a fake live account or a success notification suggesting public functionality.

The teaser's useful promise is an explanation of what is being built, not proof that every planned capability already works.

Adapt the level of detail

For a 30-second version, add one concrete problem example and a fuller explanation of the intended job. Do not fill the extra time with additional speculative features.

If only abstract brand assets are ready, pair them with a specific task statement. A logo animation alone may leave the product direction unclear.

Correct premature access copy

Replace “Start now” with the action the destination supports. Remove dates that are not approved. Keep a concept label present while the asset is on screen, not only in the ending.

If the product enters beta, revise the status throughout the film rather than treating the old waitlist teaser as a current beta demonstration.

Review checklist

  • Concept material is clearly labeled.
  • Planned behavior is not presented as released.
  • No invented launch date or adoption signal appears.
  • The final action leads to the current waitlist.
Explore product launches ↗

Use case / Product launches

Waitlist teaser videos

Explain an upcoming product with a useful waitlist teaser brief that labels concept assets, separates plans from facts and uses an accurate next action.

Read resource