Best for
- PMMs launching frequent feature updates
- Product-led teams that need better release communication
- B2B SaaS teams with multiple buyer personas
Translate release notes, customer pain, and sales context into persona-specific launch messaging across email, sales, website, and social.
Create a complete persona-specific launch kit for a new feature or product update.
Quick view
Check the audience, core tools, and access before you start the detailed steps.
Best for
Core tools
6 tools used across the workflow.
Access
Preview the open steps, then unlock the remaining implementation details and prompts.
Why this works
Feature launches fail when everyone receives the same announcement. Different personas care about different outcomes: admins want control, executives want business impact, users want workflow relief, and sellers need proof. This workflow turns one release into persona-specific assets without creating a custom launch from scratch each time.
Expected results
Launch assets produced
10-20 assets
A single feature can produce persona emails, sales blurbs, web copy, social posts, visuals, and enablement notes without writing each from scratch.
PMM time saved
6-10 hours per release
The structured source doc and persona map reduce repetitive asset drafting and stakeholder rework.
Message accuracy
Reviewed claims
Product review and claims-to-avoid sections reduce the risk of overselling or misrepresenting the release.
Persona relevance
Persona-specific angles
Each audience receives messaging tied to their role and outcome instead of one generic announcement.
Step-by-step workflow
The first 2 steps are open. Confirm your email to unlock all remaining steps, prompts, and implementation tips for free.
45 min
45 min
Pull release notes from Linear, product screenshots, demo notes, internal launch docs, and any customer or sales context from Gong. Work in linear, gong, and google docs and capture the concrete operating details: source material, decision criteria, working notes, owner, output link, review status, and open questions. Keep the work narrow: complete step 1, record the decision or asset created, and avoid changing unrelated parts of the workflow. Before moving on, check that the output is specific enough for the next person to use without guessing what happened; the expected handoff is A release source doc with product facts, customer context, and launch constraints.
A release source doc with product facts, customer context, and launch constraints.
Separate product facts from marketing interpretation. PMM can improve framing, but should not invent capabilities.
30-45 min
30-45 min
Use Claude to map the release to each persona. Work in claude and google docs and capture the concrete operating details: source material, decision criteria, working notes, owner, output link, review status, and open questions. When you use the prompt template attached to this step, paste the real source material, name the expected output sections, and ask the model to flag uncertainty instead of filling gaps. Before moving on, check that the output is specific enough for the next person to use without guessing what happened; the expected handoff is A persona outcome map for the feature release.
A persona outcome map for the feature release.
If a persona has no clear outcome, do not force them into the launch. Not every update deserves every audience.
Confirm your email to read the remaining 5 steps, prompts, and implementation tips. One sign-in unlocks the whole library.
By joining, you agree to the Terms and Privacy Policy.
Already have an account? Sign inMap 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.Related workflows
Continue with workflows that share a similar GTM motion, category, or tool stack.
Create a competitive displacement brief with traps, proof points, objection responses, and seller talk tracks.
Create a pricing page testing plan with message hypotheses, copy variants, and conversion measurement.
Create a multi-channel demand gen kit from one approved content offer.