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. 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.

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.

Turn the persona map into a message house. 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. If an AI assistant is involved, give it the source inputs and the exact structure you want back instead of asking for a broad summary. 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 launch message house with master and persona-specific messaging.

Use Claude to create emails, sales blurbs, website copy blocks, social posts, in-app notification copy, and internal enablement notes for each approved persona. Work in claude, hubspot, 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 prompt includes the actual inputs, the requested output format, and clear rules against invented facts; the expected handoff is Persona-specific launch copy for email, sales, web, social, and internal enablement.

Use Canva to create launch visuals, simple diagrams, screenshot callouts, and optional one-pagers for sales. Work in canva and capture the concrete operating details: source links, buyer context, audience, claims, proof points, owner, review status, and the final deliverable link. Keep the work narrow: complete step 5, 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 Launch graphics, screenshot callouts, and optional one-pager assets.

Route the launch kit to product, legal or compliance if needed, and sales leadership. Work in google docs and linear and capture the concrete operating details: account name, contact role, source signal, CRM status, fit reason, next action, owner, and confidence level. Keep the work narrow: complete step 6, record the decision or asset created, and avoid changing unrelated parts of the workflow. Before moving on, check that the handoff is tied to the right account or record and the owner knows the next action; the expected handoff is An approved launch kit with product and go-to-market review completed.

Send approved emails in HubSpot, publish website blocks, equip sales, and share the launch internally. Work in hubspot, gong, and linear and capture the concrete operating details: campaign name, audience, channel, offer, message angle, asset URL, performance baseline, owner, and approval status. Keep the work narrow: complete step 7, 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 launched feature campaign with adoption and feedback signals tracked.