Product launches / Prompt

Prompt: explain a newly announced plan structure

Treat a plan announcement as a factual communication task. Use approved plan details and give conditions enough space to remain understandable.

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

Who this is for: Product teams preparing focused launch motion briefs.

What to prepare

  • Current approved plan names and terms
  • Exact prices and billing context if shown
  • Eligibility and transition conditions
  • The official plan-information destination

Copyable creative brief

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

Plan a 30-second announcement for PRODUCT_NAME using APPROVED_PLAN_FACTS. Reproduce supplied names, amounts, currency, billing period and conditions accurately. Do not invent a free tier, discount, tax treatment, savings percentage or price comparison.

Begin with WHAT_CHANGED in one clear sentence. Introduce the relevant plan information in a readable hierarchy: name, included scope and the conditions needed to interpret the amount or access. Use one active card at a time. Keep existing-customer and new-customer conditions distinct if the supplied facts differ.

Show a concise summary of the choice the viewer needs to make. Do not simulate a purchase or imply that a payment completed. End with the verified destination for full current terms and NEXT_ACTION. If important information is missing or contradictory, mark it for the responsible owner rather than substituting a plausible price or condition.

Make it your own

APPROVED_PLAN_FACTS
Use current owner-approved facts, with date and source recorded in the production packet.
WHAT_CHANGED
Describe the specific change without promotional exaggeration.
NEXT_ACTION
Match the actual information or account flow.
PRODUCT_NAME
Use the approved product identity and ensure the supplied plan facts belong to that exact offering.

Prepare a factual packet

For an illustrative announcement, the creative structure could introduce a new plan name, its supplied scope and who can select it. Do not create example monetary amounts merely to make the card look finished.

A blank price field should remain a production dependency, not become a publishable guess.

Adapt for existing customers

If existing customers need different instructions, use a separate labeled scene or asset. Avoid mixing new signup copy with migration conditions in a tiny footnote.

If the explanation cannot remain readable in 30 seconds, narrow the announcement and direct viewers to the official detail page.

Correct misleading hierarchy

If an amount dominates while its billing condition is unreadable, rebalance the layout. If a comparison lacks approved evidence, remove it.

Recheck the facts and destination before publication. This prompt supplies a communication structure, not pricing advice or a claim about Animro's plans.

Review checklist

  • Plan facts match the approved current source.
  • Amounts retain required currency and billing context.
  • No discount or comparison is invented.
  • Different eligibility groups remain distinguishable.
Explore product launches ↗