Product Launch Email and Copy Workflow

5 steps to a reviewable draft

1. 01

   Freeze the launch boundary

   Record what launches, who can access it, when it becomes available and which claims the product owner has approved.

   Result: A launch record that prevents copy from running ahead of the product.

2. 02

   Map message to channel

   Choose the job for the landing page, email, social post and in-product message. Do not copy one long announcement everywhere.

   Result: A channel map with reader context and destination for each piece.

3. 03

   Draft the copy set

   Ask for channel copy that uses the launch record and leaves unconfirmed details visible instead of adding launch theatre.

   Result: A coordinated set of drafts that retains the same factual boundary across channels.

   Your prompt

   Copy prompt

   Create a product launch copy set from the approved launch record.
   
   Product, audience and launch scope: {{scope}}
   Approved facts and proof sources: {{facts}}
   Channel jobs and destinations: {{channels}}
   Timing, availability and approval limits: {{conditions}}
   
   Return a core message, landing-page direction, email draft, social post draft, call to action, source check and channel owner. Mark unknown details as [NEEDS LAUNCH INPUT]. Do not invent availability, pricing, customer results, integrations, release dates or future product plans.

   Example input

   Launch a reporting-template update to existing users after the product owner confirms availability and the help article goes live.

   Example output

   Email draft: explain the confirmed template change. Availability date: [NEEDS LAUNCH INPUT]. CTA: help article. Claim check: product owner.

4. 04

   Run the launch review

   Check each channel version against product, legal and delivery owners; verify links, timing, availability and support readiness.

   Result: A release-ready copy set with ownership clear.

5. 05

   Save the launch pack

   Store the final assets, source links, approval record and fallback copy for changed launch conditions.

   Result: A launch record that can be audited after the messages go out.