Turn a feature release into a persona-specific launch kit

Pull release notes from Linear, product screenshots, demo notes, internal launch docs, and any customer or sales context from Gong. Capture what changed, why it matters, who benefits, limitations, setup requirements, and proof. Put everything into a short launch source doc.

Use Claude to map the release to each persona. For each persona, identify the pain relieved, outcome promised, objection likely to appear, proof needed, and CTA. Keep the release grounded in different value drivers instead of one generic message.

Map this feature release to persona-specific outcomes.

Release source material:
{{release_source_material}}

Target personas:
{{target_personas}}

For each persona, output:
1. What they care about
2. Pain relieved
3. Business or workflow outcome
4. Likely objection
5. Proof needed
6. Best CTA
7. Message angle
8. Whether they should be included in launch

Do not exaggerate the feature impact.

Turn the persona map into a message house. Include master positioning, persona-specific headlines, supporting proof, claims to avoid, competitor or alternative framing, and internal talking points. This becomes the source of truth for every launch asset.

Use Claude to create emails, sales blurbs, website copy blocks, social posts, in-app notification copy, and internal enablement notes for each approved persona. The assets should share a product truth but change the angle by persona.

Create persona-specific launch assets from this message house.

Message house:
{{message_house}}

Personas:
{{approved_personas}}

Brand voice:
{{brand_voice}}

For each persona, create:
1. Email subject lines
2. Launch email
3. Sales blurb
4. Website copy block
5. LinkedIn post
6. In-app notification copy
7. CTA
8. Proof note

Rules:
- Keep claims within the release facts
- Change the angle by persona
- Do not use generic launch hype

Use Canva to create launch visuals, simple diagrams, screenshot callouts, and optional one-pagers for sales. Keep visuals tied to the feature outcome rather than generic product imagery. Use screenshot annotations when possible because they make the release more tangible.

Route the launch kit to product, legal or compliance if needed, and sales leadership. Ask reviewers to check accuracy, claims, persona fit, and objection handling. Track changes in the source doc and mark every asset as approved, revised, or rejected.

Send approved emails in HubSpot, publish website blocks, equip sales, and share the launch internally. Track email engagement, sales usage, demo mentions, feature adoption, support questions, and qualitative feedback. Feed common confusion back into the release messaging.